1.Need right approach
2. Data migration techniques
3. Do's n don't
4. Considerations & procedures
5. General best practices
@Data Migration #Data Management #Org Migration #Salesforce Developer #Solution Architects
Migrate from one customized Salesforce org to another
Note: Before migrating, prepare the target instance to receive or import your data. Here are some general points or considerations to keep in mind:
1. Importing data from one org to another requires matching metadata to be established in the new target org.
· Experienced admins or developers may migrate metadata by Deploying and Retrieving Metadata using a client tool such as the Ant Migration Tool.
2. Other customizations for the target instance include record types, page layouts, etc.
3. Develop sharing models to accommodate new user groups if necessary: Profiles, Roles and Sharing Rules
4. Review ownership rules
5. Ensure all required data points and fields form the source org are captured in the target
6. Test migration prior to importing data. It's recommended to run through a migration in a sandbox first, see Sandboxes: Staging Environments for Customizing and Testing
7. Complete data validation once migration is complete
Migrate or import your data from one org to another
We recommend you watch the How to Import Data into Salesforce video to become familiar with what will be required to import all your data from a legacy to new org. Several different tools are available depending on your edition and the number of records being imported. See the Choosing a Method for Importing Data documentation for more details. To import records from one organization into another, you'll need to import the records in a particular order to establish their relationships to one another. Record relationships are stored in Salesforce or defined by their IDs so you'll need to populate your import files with any newly created record's Salesforce Ids from the target org. The easiest way to do this is using Excel's VLOOKUP function to add the new record Ids to your files for import.
If a vlookup isn't something you're comfortable with, consider creating a custom External Id field and map or insert your previous record Ids or other unique identifiers from your source organization into the field. This will allow you to Import related records using an External ID.
For example, after importing Accounts in your new org, you'll replace any occurrences of legacy Account Ids in your import files with NEW Account Ids from the target org. To populate your import files with the newly created Account Ids use vlookup as outlined in the Add Salesforce IDs of existing records to your import file article. How Salesforce objects relate to one another can be graphically viewed in the Data Model | SOAP API Developer Guide documentation to assist in devising a strategy and planning your object's appropriate import order. You need to define and include the ID of related records during import by replacing occurrences of old legacy record Ids with new related record Ids from the target org within your import file. This ensures that each new record is properly associated with one another.
Recommended sample order for importing core objects:
1. Accounts
2. Campaigns
3. Contacts
5. Cases
6. Price books
7. Products
8. Leads
9. Contracts
Note: Migrate data from one organization to another (salesforce.com)
