Loading

Migrate data from one organization to another

Publiseringsdato: Aug 20, 2023
Beskrivelse

It's necessary to setup and configure required metadata and users in your new or target org before beginning. 

You can migrate data by importing or inserting records from another Salesforce legacy source organization or other external source into a new target organization. It's important to import object data in a particular order to maintain record relationships.

Record relationships are defined with Unique Record IDs in Salesforce (and not record names) so you will need to match and replace old record Ids in your import files with the newly created data's record Ids from within your target org to properly prepare relational data for import.
Løsning


Before you get started 

Support is available for specific or directed questions or concerns that may arise during your migration however, consultation for over all scoping, planning, and implementation or execution of org migrations and required data manipulation is not within the scope of Support or Admin Assist's offerings.

Migration planning and testing must be carried out client side by customers. See the 'What is the difference between Admin Assist and Services/Consulting?' section of the Admin Assist: FAQ article for more details.

If you feel this task may be too much or aren't confident with your organization's ability to manage or complete the migration of metadata and data, you may elect to contact your Account Executive to discuss Professional Services or consider Consulting Partners.  Please note there will be a cost involved if professional services or a consulting partner is tasked with completing the data migration on your behalf.
 

Migrate from one customized Salesforce org to another

Note: Prior to 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.
  1. Other customizations for the target instance include record types, page layouts, etc.
  2. Develop sharing models to accommodate new user groups if necessary: Profiles, Roles and Sharing Rules
  3. Review ownership rules
  4. Ensure all required data points and fields form the source org are captured in the target
  5. 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
  6. 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.

There are several different tools available depending on your edition and 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 of the new records are properly associated to one another.
 

Recommended sample order for importing core objects:

  1. Accounts
  2. Campaigns
  3. Contacts
  4. Opportunities
  5. Cases
  6. Pricebooks
  7. Products
  8. Leads
  9. Contracts​​​
 
Related Chatter Feed Objects data will also need to be re-inserted on related records once they've been imported. See Move Chatter Feed from one record to another for more details.


See also
Best practices when you migrate data
 
Knowledge-artikkelnummer

000384648

 
Laster
Salesforce Help | Article