Tip #1- Fully Understand Contents of the Source System
Perform a System Scan of All Fields and Objects
Watch for Special Custom Objects
Migrate Only What is Needed
Data to be migrated in old systems often contains many years of sales, support and marketing history. There could be millions of support cases. Salesforce has storage limits and if you exceed your allotted storage, you could be facing significant additional costs.
Tip #2- Create Custom Fields for Critical Legacy Data
Record IDs in the Target System will be New
During a migration, records being copied from the source system will be recreated as entirely new records in the target system. This means that all new created records, users, notes, etc. will have a new unique Salesforce Record ID. Old cases will be recreated as new cases, with new case numbers and new case creation dates.
Capture Legacy Dates, Owners and IDs on Every Record
Create fields on every record type (including standard and custom objects) tasks, activities, events and note records that capture the legacy data such as legacy record owners, legacy record ID, legacy record creation date, closed date, status fields, etc.
Tip #3- Set up an Ongoing Synchronization vs. One-Time Cutover
Ongoing Synchronization Approach
This method of migrating data into a new Salesforce system allows a gradual load of data (movement of records) into the target system. Because completely populating the target system can take days or even weeks, an ongoing sync allows users to remain active on the source system until the data has been completely copied into the target system.
Ask for a Temporary API Call Increase
Implement Data Backups
Tip #4- Evaluate the Business Processes of the Source and Target Systems
Beware of Rules, Workflows, Triggers in the Target System
Evaluate the source organization’s use of Queues, Profiles, Public Groups, Chatter, Templates, Apex Triggers and Workflows. Specifically, identify whether to package or recreate them manually, but more importantly, identify if they are even still relevant. Many Orgs have dozens of obsolete Templates and Workflows.
Analyze Where Data Resides
Tip #5 Migrating Data
Cascade Inserted Data
Once the new Org is set up to receive the data, the record flow should be cascaded in the following order- Users, Accounts, Contacts, Leads, then Cases, Opportunities, Activities, attachments, etc.
Consider Field Restrictions
User Set Up
Test the Migration
The views and opinions expressed in this article are those of the authors. Examples cited in this article are only examples. Salesforce®, Salesforce1 Mobile App™, AppExchange® are trademarks of salesforce.com, inc.
© 2017 Snowforce, LLC. All Rights Reserved - August 2017