> 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-1-creating.md).
# Migration Step 1: Creating
##  Overview
This article explains how to create a data migration job. 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.
This is the first step in the Data Migration process. The other steps are detailed in the following articles:
* [Migration Step 2: Reviewing](/data-migrator/templates/migration/migration-step-2-reviewing.md)
* [Migration Step 3: Running](/data-migrator/templates/migration/migration-step-3-running.md)
## Create a Data 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 %}
### Run Template
1. Click **Templates** from the left sidebar menu.
2. Find the template to use for the migration from the list.
3. Click **Run**.
{% endstep %}
{% step %}
### Select Organization
{% hint style="info" %}
The **Template objects** table lists all objects included in this template, along with the number of fields and filters for each object.
{% endhint %}
1. Click the **Source organization** dropdown.
2. Select the organization you want to migrate data from.
3. Click the **Target organization** dropdown.
4. Select the organization you want to migrate data to.
5. Click **Next**.
{% endstep %}
{% step %}
### Compare Schema
The Compare Schema step confirms that both the source and target organizations have the metadata schemas that match the objects and fields included in the migration Template. For example, if the Template and source organization include a custom field for an object but the target organization does not, this step flags it as a mismatch.
**Schemas Match**
If the metadata schemas in your source and target organizations match the Template, you can continue with the migration.
1. Click **Create request** to start the data migration review process.
**Schema Errors**
If the metadata schemas in the source or target organization do not match the objects and fields included in the Template, a schema mismatch is generated. A list of objects and fields with schema mismatches is displayed. You must resolve these mismatches before continuing with the data migration.
1. Expand each object to see which fields are affected.
2. Review the mismatches. For each object and field, a mismatch indication icon is displayed for the target and source organizations:
1. **Green Circle Checkmark**: The schema for this organization matches the template.
2. **Red Octagon Exclamation**: The schema for this organization does not match the template.
3. For each mismatch, choose how to resolve it:
1. Remove the field from the Data Migrator Template.
2. Add the missing field to the Salesforce org with the mismatch.
4. Click **Cancel** to cancel the data migration.
5. Resolve the mismatches.
6. Run a new Data Migration.
{% endstep %}
{% step %}
### Next Step
After you create the Migrate Request, you are taken to the **History** page, where you can view its status. At this stage, no data has been migrated. Review the request before migrating data from the source org to the target org. Proceed to the following article for instructions on reviewing the data migration.
{% content-ref url="/pages/L74STchEOLmYyOQL8wlJ" %}
[Migration Step 2: Reviewing](/data-migrator/templates/migration/migration-step-2-reviewing.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-1-creating.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.
