A successful data migration into requires a well designed plan that goes well beyond the mechanics of moving data between 2 systems. This checklist is intended to surface some of the non-obvious, finer points of a data migration. More Learning Resources for Salesforce Migrations
📋 People
Is there anyone on your team who understands the old and new Salesforce Data model?
Clarification: This question aims to identify if there's existing knowledge about Salesforce data models within your team. Have you identified who will help verify the accuracy and validity of data mapping and make decisions for mapping values between picklists?
Many times there isn’t perfect 1-1 mapping between your existing application and Salesforce. Having someone readily available to make decisions will help ensure timely mapping. 🛠️ Process
Have you inventoried your Salesforce objects for migration?
Clarification: This is about ensuring all relevant Salesforce objects are accounted for before migration. How does your user adoption testing for Salesforce coincide with data migration?
[ ] User adoption testing before data migration [ ] User adoption testing after data migration [ ] Depends on remaining timelines and schedule Clarification: Understanding the timing of user adoption testing in relation to data migration. How much time has your team allotted for migration?
Clarification: This question seeks to understand the time frame set aside for the migration process. How will you transition users from old system to new system?
Clarification: This involves the strategy for moving users from the old system to Salesforce. 💾 Data
Have you created migration key fields in all objects you are migrating?
Clarification: This relates to the preparation of key fields necessary for data migration. Do you have a data dictionary for the system you are migrating from?
Clarification: A data dictionary would provide a detailed view of the data elements in the system being migrated from. Do you have a data dictionary for your app? Clarification: This is about having a comprehensive data dictionary specific to your Salesforce application. Have you created data mapping document from the old application to Salesforce?
Clarification: Data mapping documents are crucial for understanding how data from the old system will fit into Salesforce. Have you documented the mapping of picklist values?
Clarification: This ensures that the picklist values in the old system are appropriately mapped to Salesforce. Are you migrating documents into Salesforce (example PDFs)
Clarification: Documents require additional APIs mapping and planning. Clarifying document migration early will help allot adequate time for mapping. How would you rate the data quality of the system you are migrating from?
[ ] A - Data is pristine and tightly controlled [ ] B - Data is controlled but with known issues [ ] C - Data is not tightly controlled, may cause issues [ ] D - Data is dirty and could pose problems Clarification: Understanding the current quality of the data will help anticipate challenges in migration. 💻 Technology
How extensive are data validation rules in Salesforce?
[ ] Small (1-2 rules per object) Clarification: Knowing the scale of data validation rules in place can impact the migration strategy. What type of automations exist in Salesforce when records are created or updated?
Clarification: Understanding the automation landscape in Salesforce is key for migration planning. What kind of automated communications exist in your Salesforce instance?
[ ] Triggered Salesforce Emails [ ] Triggered Marketing Automation Emails [ ] Other communication triggers 
