Ctrlk
Customer Support
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview of Data Migration

Overview

Data Migrator is a powerful tool that seamlessly copies records from one Salesforce org to another. This article guides you through the process of using a template to execute a data migration job efficiently.

Key Points About the Migration Process:

  • All records in the source organization remain intact throughout the migration process.

  • Migration of binary files and ContentVersion records is supported. File-based records, such as attachments, documents, and Salesforce Files, are migrated along with their actual file contents.

  • Migration of Standard Pricebook Entries is supported. This ensures every product has a default (standard) price in Salesforce, so it can be used in deployments, opportunities, and dependent records without errors.

  • If Record Mapping is selected for an object and a record exists in both the source and target organizations, Data Migrator intelligently updates the target record to match the source, preventing duplicate entries and maintaining data integrity.

  • A properly configured template preserves relationships between records, maintaining references and dependencies in the target organization.

Before you begin migrating your data, create a template that defines the objects and fields to migrate. Refer to the following article to learn how to get started creating a template.

Example Migration

The articles in the Data Migration series use the following example to illustrate how to migrate data between Salesforce organizations. This example migrates all Contact records associated with the "Example Company" Account. The Account ID field is included in the migration to preserve the relationship between Account and Contact objects. For this example, only a subset of fields is included for each object. The diagram below shows the specific fields selected for migration and the filter criteria used to choose which records to migrate.

The screenshot below shows the template used in this example. The Account object is the root, with the Contact object as its child.

To maintain the relationship between Account and Contact records, you must select the Account ID field in the Contact object. The Account ID field is always selected by default for Account objects.

Migration Steps

1

Creating

In this step, you select the template, the source and target organizations, and verify that they have the required metadata schemas to perform the data migration. See the following article for instructions.

2

Reviewing

In this step, the data migration retrieves the records to be migrated from the source organization. Before proceeding with the data migration, you can review the records retrieved for each object in the template. See the following article for instructions.

3

Running

In this step, you can configure which Salesforce automations to disable during the migration, then start the migration. See the following article for instructions.

Record Mapping

Data Migrator uses record mapping to keep records accurate across multiple migration runs. When you enable record mapping for an object, Data Migrator maps individual records between the source and target organizations. This ensures that subsequent migrations add new records and update existing ones. For record mapping to be used during a migration, it must be configured in the template. To learn more about record mapping and how to enable it, see the following articles.

PreviousMigration
NextHow Record Mapping Works

Last updated

Was this helpful?