> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/devops/pipeline/pipeline-operations/pipeline-operation-migrate-data.md). # Pipeline Operation: Migrate Data {% hint style="warning" %} #### 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](/devops/new-ui-ux-transition/where-did-it-go.md) article. {% endhint %} ## ![](https://1800549522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRpUu5iMlzMFAudyBvMOl%2Fuploads%2FG5ZbxX918xOHwbAwAJ4n%2FSummary2-Small-Icon.svg?alt=media\&token=da26a67f-ff7f-47b3-8669-06be960dc2d7) 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. {% hint style="info" %} #### 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. {% endhint %} ### 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. * [Overview of Templates](/data-migrator/templates/template-designer/overview-of-templates.md) * [Creating a Template](/data-migrator/templates/template-designer/creating-a-template.md) * [Adding Objects to a Template](/data-migrator/templates/template-designer/adding-objects-to-a-template.md) * [Adding Fields to Objects](/data-migrator/templates/template-designer/adding-fields-to-objects.md) * [Adding Filters to Objects](/data-migrator/templates/template-designer/adding-filters-to-objects.md) * [Setting Object Record Mapping](/data-migrator/templates/template-designer/setting-object-record-mapping.md) #### 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. * [Assigning an App to an Organization](/global-settings/environment/organizations/assigning-an-app-to-an-organization.md) ### 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 {% hint style="info" %} The instructions below apply to configuring this pipeline operation. For general instructions on adding a pipeline step and setting the next step, see the following article. [Adding a Pipeline Step](/devops/pipeline/configuring-pipeline-steps/adding-a-pipeline-step.md) {% endhint %} {% stepper %} {% step %} ### Select Operation and Job Name 1. Click the **Operation** dropdown menu. 2. Select **Migrate Data**.
3. In the **Job name** text field, enter a name for the migration job to be run in Data Migrator.
{% endstep %} {% step %} ### Select Source and Target Organizations {% hint style="info" %} Only organizations with the Data Migrator app assigned to them are available as sources and targets for data migration. To migrate data to or from an organization that has only DevOps assigned, first assign Data Migrator to that organization in the Global Settings app. For details, see the following article on assigning apps to organizations. * [Assigning an App to an Organization](/global-settings/environment/organizations/assigning-an-app-to-an-organization.md) {% endhint %} 1. Click the **Source Organization** dropdown menu. 2. Select the organization to use as the source of the migration.
3. Click the **Target Organization** dropdown menu. 4. Select the organization to use as the target of the migration. {% endstep %} {% step %} ### Select Data Migrator Template {% hint style="info" %} Because you cannot view Data Migrator templates in DevOps, you must know the name of the Data Migrator template you want to use for this migration. If you are unsure, open Data Migrator to find the correct template name. See the following article to learn more about Data Migrator templates. * [Overview of Templates](/data-migrator/templates/template-designer/overview-of-templates.md) {% endhint %} 1. Click the **Template** dropdown menu. 2. Select the template to use for the data migration.
{% endstep %} {% endstepper %} ## Migrate Data Results {% hint style="info" %} Once a pipeline is started, its progress and results can be viewed from the **Activities** tab from the branch that ran the pipeline. The instructions below show you how to review the results of this operation. For general instructions on accessing pipeline results from the branch, see the following article. * [Viewing Pipeline Results](/devops/pipeline/pipeline-actions/viewing-pipeline-results.md) {% endhint %} {% stepper %} {% step %} ### 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:
FieldsDescription
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.

DurationTime the Migrate Data job took to complete, shown in hours, minutes, and seconds.
Date started/finishedThe date and time the Migrate Data job started and finished.
Total objectsTotal number of objects included in the migration.
Total recordsTotal number of records in the migration, including successful and failed records.
Failed recordsNumber of records that failed to migrate.
LogLog 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: {% code overflow="wrap" expandable="true" %} ``` [Jun 1, 2026 4:00 PM]: [info] Job started [Jun 1, 2026 4:02 PM]: [info] Job completed ``` {% endcode %} {% endstep %} {% step %} ### See Results To view more details about the migration, open the results. 1. Click **See result**.
2. A new Data Migrator tab opens and displays the migration job results.
3. For detailed instructions on reviewing the migration results, see the article below. 1. [Viewing Migration Results](/data-migrator/history/viewing-migration-results.md) {% hint style="info" %} You can roll back a data migration from the Data Migrator app. For instructions, see the article below. * [Rolling Back a Migration](/data-migrator/history/rolling-back-a-migration.md) {% endhint %} {% endstep %} {% endstepper %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flosum.com/devops/pipeline/pipeline-operations/pipeline-operation-migrate-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.