> 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-2-reviewing.md).
# Migration Step 2: Reviewing
##  Overview
This article explains how to review a data migration job. 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.
This is the second 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 3: Running](/data-migrator/templates/migration/migration-step-3-running.md)
## Review Migrate Request
{% 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 %}
### Select Migration Request
1. Click **History** from the left sidebar menu.
2. Click the Migrate Request you created in the previous article.
{% endstep %}
{% step %}
### Retrieve Data
The Migrate Request job retrieves data from the source organization for you to review before migrating it to the target organization. If the Migrate Request is still retrieving data, wait for it to complete. This process could take several minutes.
1. Click the **Refresh** button to check if the retrieval job is complete.
{% endstep %}
{% step %}
### Review Data
After the data is retrieved, you can review the number of objects and the total number of records to be migrated. To browse the records to be migrated, select each object in the template viewer.
1. Each object shows the number of successfully retrieved records and the total number of records in the upper-right corner.
2. Click an object to view details about the retrieved records, the included fields, and any filters applied.
3. Each object provides the following information:
1. **Fields**: All fields that will be migrated with each record for this object.
2. **Filters**: Any filters applied to this object.
3. **Records**: Table of all records to be migrated for this object.
4. **Search records**: You can search the records table by the **Name** column. Currently, no other columns are searchable.
{% hint style="info" %}
#### Record Name Missing
Records won't display a name if the **Name** field wasn't included in the migration. This happens for two reasons:
1. The **Name** field wasn't selected in the template used for this migration.
2. The **Name** field is a compound field (composed of multiple other fields) and can't be selected in the template used for this migration.
{% endhint %}
By default, only the **Source ID** and **Name** fields are displayed. To display more fields:
1. Click the **Select fields** dropdown.
2. Select the fields to display.
{% endstep %}
{% step %}
### Next Step
After reviewing the data to be migrated, you will proceed with running the migration.
1. Click **Run Migrate**.
2. Follow the instructions in the article below for running the data migration.
{% content-ref url="/pages/zJH1imPyRRkODS01ClmU" %}
[Migration Step 3: Running](/data-migrator/templates/migration/migration-step-3-running.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-2-reviewing.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.
