Pipeline Operation: Migrate Data
Written for the Old UI
This article was written for the old UI. The instructions are still usable, but the screenshots are outdated. In some cases, items referenced in the instructions have moved or changed. If you cannot find an item, see the Where Did It Go article.
Overview
The Migrate Data operation runs a Data Migrator migration job as a step in a DevOps pipeline. It transfers records between a source and target organization using a Data Migrator template, so you can move data automatically during a pipeline rather than running a migration manually afterward.
Because the migration runs in the Data Migrator app, the operation uses your existing templates. These templates specify which objects and records to transfer, along with any filters and record mappings.
Best Practices
Test your Data Migrator template in the Data Migrator app before adding it to a DevOps pipeline.
Use this operation to seed a target organization with configuration or reference data after a deployment.
Keep records consistent across environments by including a Migrate Data operation.
Use Record Mapping in your template for repeated migrations to avoid duplicating data.
Apply data masking in your Data Migrator template to replace sensitive data with random seed values, ensuring no real data appears in the target organization.
Data Migrator Prerequisites
Before adding a Migrate Data operation, you must configure several items in the Data Migrator app. The following sections describe these prerequisites and link to related articles.
Template
Every data migration runs from a template that defines which objects and records are migrated, along with any filters and record mappings. Verify that a template copies the correct records before using it in an automated process such as a pipeline. To learn more about Data Migrator templates, review the following articles.
Organizations
A data migration can run only between organizations that have the Data Migrator app assigned. If an organization you want to use is not listed, assign Data Migrator to it in the Global Settings app. For details, see the following article about assigning apps to organizations.
Migrate Data Operation vs Data Migrator Migration
Because the Migrate Data operation uses Data Migrator to create and run the migration, the end results are the same. However, there is an important distinction between the two.
In Data Migrator, a migration is a multi-step process that involves creating, reviewing, and running the migration.
In a DevOps pipeline, the Migrate Data operation is a single process that automates both the creation and the execution of the migration. Because a pipeline is automated, it skips the review step. For this reason, confirm that the migration works correctly before including it in a critical pipeline.
Migrate Data Operation Configuration
Migrate Data Results
Summary and Log
Once the Migrate Data job is complete, you can view the results summary by selecting the Migrate Data step from the pipeline results.

The Summary of the Migrate Data results displays the following information:
Status
Completed if the migration job has finished running. A migration is still considered completed even if it has Failed Records.
Exception if an issue prevented the migration job from running. Check the logs to troubleshoot.
Duration
Time the Migrate Data job took to complete, shown in hours, minutes, and seconds.
Date started/finished
The date and time the Migrate Data job started and finished.
Total objects
Total number of objects included in the migration.
Total records
Total number of records in the migration, including successful and failed records.
Failed records
Number of records that failed to migrate.
Log
Log entries for the Migrate Data job. Use the log to review the job's status and any error messages.
Example of a Migrate Data log:
Last updated
Was this helpful?





