- Data migration strategy from custom MSSQL-based app to CRM 4.0
- Posted by Chris on July 3rd, 2008
Hello,
We have a client looking to transition to CRM 4.0 from their current
home-grown application based on SQL Server 2005. I am curious to get
suggestions from the group on how to approach this.
Here is one approach I am considering:
1. Create denormalized views in SQL (picklist values included instead of
PK/FK keys)
2. Script queries to these views that send query results to a CSV file
3. Create data mappings in DMF to perform mass import
4. Run import with fingers crossed
One requirement to note is the client is not looking for a staged migration
- everything must be brought over at once.
Any thoughts would be sincerely appreciated!!
- Posted by ChrisC on July 4th, 2008
A few quick thoughts:
0. Focus on the user
1. Ensure MSCRM covers all required functionality and document
'Different ways of doing things'
2. Yes, expand and export MASTER data, then import to MSCRM using in-
built and custom (ETL) tools and techniques
3. Try to cut across the minimum TRANSACTIONAL data, ideally none -
get MSCRM live asap
4. Make legacy app readonly, but ensure users can reference
5. Lots of user support, training and diligent change management
Good luck!
Chris
http://mscrm4u.blogspot.com
- Posted by Darren Liu on July 4th, 2008
Chris gave a very good process of doing the convertion to 4.0. If you
want to finish the data migration quickly, feel free to look into C360
import and Scribe Data Migration package.
Darren Liu, Microsoft CRM MVP
Crowe
http://www.crowecrm.com
On Jul 4, 2:59*am, ChrisC <chris.co...@vizola.com> wrote:
