> 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/data-migrator/templates/migration/migration-step-3-running.md).
# Migration Step 3: Running
##  Overview
This article explains how to run the migration. In this step, you can configure which Salesforce automations to disable during the migration, then start the migration.
This is the last step in the Data Migration process. The other steps are detailed in the following articles:
* [Migration Step 1: Creating](/data-migrator/templates/migration/migration-step-1-creating.md)
* [Migration Step 2: Reviewing](/data-migrator/templates/migration/migration-step-2-reviewing.md)
## Run Migration
{% hint style="info" %}
The Data Migrator template and the Salesforce data used as examples in this article's instructions are explained in the Example Migration section of the following article.
* [Overview of Data Migration](/data-migrator/templates/migration/overview-of-data-migration.md#example-migration)
{% endhint %}
{% stepper %}
{% step %}
### Configure Migration Job
1. Enter a descriptive **Name** for the migration job.
2. Confirm that the **Selected Organizations** are correct.
{% endstep %}
{% step %}
### (Optional) Disable Automations
When running a migration, automated Salesforce processes remain active by default. To prevent these processes from triggering during the migration, you can selectively disable them at the object level. Disabling automations for one object affects only that object.
Each process below is disabled individually for each object in the template.
* **Triggers**
* **Workflows**
* **Flows**
* **Validation rules**
* **Lookup filters**
Automated processes are disabled only during the data migration and are restored once the migration is complete.
{% hint style="warning" %}
Automations are disabled only for the objects they are selected in. They remain enabled for other objects in the template. Disable automations for each object you want to affect.
{% endhint %}
1. To disable Salesforce automations for an object, click **Automations**.
2. Check any of the automations you want to disable.
3. Click **Save**.
4. When automations are disabled for an object, the **Automations** button will display a red dot.
5. Repeat this for all objects you want to disable automations for.
{% endstep %}
{% step %}
### Run Migration
1. Click **Run migration** to start the Data Migration job.
2. After you start the Data Migration job, it will appear on the **History** page.
{% endstep %}
{% step %}
### Review Results
After the Data Migration job finishes, you can check the results to see the number of migrated records and any errors encountered. See the following article to learn more about the results.
{% content-ref url="/pages/CbEjFLlGBgrfbhgalG8x" %}
[Viewing Migration Results](/data-migrator/history/viewing-migration-results.md)
{% endcontent-ref %}
{% 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/data-migrator/templates/migration/migration-step-3-running.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.
