> 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/history/viewing-migration-results.md).

# Viewing Migration Results

## ![](https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2FcfMTqg4Brbm9baWutclZ%2FSummary2-Small-Icon.svg?alt=media\&token=d1cf162d-c02d-4184-988e-7f7350e450fc) Overview

After a migration job finishes, you can check its results to see which records were migrated, identify any errors, and review detailed information about the job. This article explains how to access the results and interpret the data.

## View Results

{% stepper %}
{% step %}

### Select Migration Job

1. Click **History** from the left sidebar menu.
2. Click the migration job you want to view the results of. 

   <div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2FUShpRJuVuJl78sZ2e1eS%2FViewingMigrationResults-S01-01.png?alt=media&amp;token=f1c8edcc-ab27-4ac0-8f55-9edf4de6d1a8" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Job Results

The Job Results page lists the following details about the job:

<div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2FJ8y9KFRhg6CptAe7hkLE%2FViewingMigrationResults-S02-01.png?alt=media&amp;token=7a0ff474-ecdc-48f2-a1db-61c4a1997f9e" alt="" width="563"><figcaption></figcaption></figure></div>

<table><thead><tr><th width="159.66668701171875">Detail</th><th>Description</th></tr></thead><tbody><tr><td><strong>Source -> Target</strong></td><td>The names of the source and target organizations used in this migration.</td></tr><tr><td><strong>Duration</strong></td><td>The amount of time this job took to complete. This does not include the time spent in the job queue.</td></tr><tr><td><strong>Date started</strong></td><td>The date and time, in your local time zone, when this job was started. </td></tr><tr><td><strong>Objects migrated</strong></td><td>The number of objects included in this job.</td></tr><tr><td><strong>Total records</strong></td><td>The total number of records in this job, including both successful and failed records.</td></tr><tr><td><strong>Failed records</strong></td><td>The number of records that didn't migrate successfully. The error is listed for each record, see the next section.</td></tr></tbody></table>
{% endstep %}

{% step %}

### View Tab

The **View** tab displays the exact template version used for this migration, even if the template is changed later. The template viewer has the same controls as the Template Designer, but does not allow you to edit the template.

In the upper right corner of each object, you will see the number of successfully migrated records and the total number of records for that object. If all records were migrated successfully, the number will be **Green**. If there are errors, it will be **Pink**.

<div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2F08rmbs1ilXs5vPzeEnjt%2FViewingMigrationResults-S03-01.png?alt=media&amp;token=358ab8f9-4a25-425a-b200-5d19a86e0070" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Objects and Record Results

The Table tab lists the objects included in this migration. To view more detailed results for a specific object, click it in the list. The following screenshots explain the information displayed for each object in this example.

<div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2FsuWx1v1z1Rlq6NWp5fUK%2FViewingMigrationResults-S04-01.png?alt=media&amp;token=3e61ebb9-0732-4693-a934-0b92ce74d445" alt="" width="563"><figcaption></figcaption></figure></div>

**Object Details**

The Object page includes the following information about the object and how the migration was configured.

<div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2FA9q9SnXijb9NPOc9SJSQ%2FViewingMigrationResults-S04-02.png?alt=media&amp;token=0514a986-20bf-498c-b678-949f7894c61a" alt="" width="563"><figcaption></figcaption></figure></div>

<table><thead><tr><th width="160.333251953125">Detail</th><th>Description</th></tr></thead><tbody><tr><td><strong>Object</strong></td><td>The Salesforce object this information is for.</td></tr><tr><td><strong>Fields</strong></td><td>The fields that were migrated for records of this object.</td></tr><tr><td><strong>Filters</strong></td><td>The filters that were applied to this object to select the records to migrate.</td></tr><tr><td><strong>Automations</strong></td><td>The list of Salesforce automations that were disabled during migration for this object.</td></tr></tbody></table>

**Record Details**

The records table displays all records involved in the migration for this object. You can search by record name and filter by status: **Success**, **Failed**, or **All** (for every status).

<div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2Fz9yH3a6Hq4oR7tHh5bOT%2FViewingMigrationResults-S04-03.png?alt=media&amp;token=1a7fe05a-2603-4c53-8032-0a04cca635a6" alt="" width="563"><figcaption></figcaption></figure></div>

{% 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 %}

The records table includes the following information about each record. The screenshots below show migrated records for two different objects.

<div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2FCmXpwTxUpwPhfUQZKGwO%2FViewingMigrationResults-S03-04.png?alt=media&amp;token=3780fe9f-551b-408e-b801-0a4a5af9f17a" alt="" width="563"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2FcfwQ3LFqFLFccOnYmgSx%2FViewingMigrationResults-S03-05.png?alt=media&amp;token=2f88f8d1-7ff4-4506-8453-fb4b8c59df15" alt="" width="563"><figcaption></figcaption></figure></div>

<table data-full-width="false"><thead><tr><th width="159.66668701171875">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Records</strong></td><td>The name of the record from the <strong>Name</strong> field. See the <strong>Record Name Missing</strong> info box above for reasons why this column might be blank.</td></tr><tr><td><strong>Source org</strong></td><td>The <strong>Source Record ID</strong> for this record. Clicking the ID will take you to the record in the source Salesforce org.</td></tr><tr><td><strong>Target org</strong></td><td>The <strong>Target Record ID</strong> for this record. Clicking the ID will take you to the record in the target Salesforce org.</td></tr><tr><td><strong>Status</strong></td><td>A record's status can be either <strong>Success</strong> or <strong>Failed</strong>. Failed records are not migrated to the target org. See the <strong>Errors</strong> column for the reason the record failed to migrate.</td></tr><tr><td><strong>Operation</strong></td><td>The operation type indicates how this record was migrated. There are two types: <strong>Insert</strong> creates a new record in the target org, while <strong>Update</strong> modifies an existing matching record.</td></tr><tr><td><strong>Errors</strong></td><td>Any errors encountered during the migration of this record will be listed here. See the <a data-mention href="#migration-errors">#migration-errors</a> section below for more details.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

## Migration Errors

When a data migration encounters errors, you can view the error for each failed record to determine the cause.

{% hint style="info" %}
Failed records are not migrated to the target org.
{% endhint %}

1. Click the **Table** tab.
2. Click on an object with errors.&#x20;

   <div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2FqbKZvgrj7uZBxlZ5q4L5%2FViewingMigrationResults-Error-01.png?alt=media&amp;token=5a53cda0-99b4-48fb-bd2c-397316abefd4" alt="" width="563"><figcaption></figcaption></figure></div>
3. Hover over the error in the **Errors** column to see the error message.&#x20;

   <div align="left"><figure><img src="https://2769999621-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvaxzColPOlNbsq4imqpd%2Fuploads%2Fj4SMBGLNRaGToXy4eUnA%2FViewingMigrationResults-Error-02.png?alt=media&amp;token=0b458fad-f5f0-45fe-85f5-7f264feb8653" alt="" width="563"><figcaption></figcaption></figure></div>


---

# 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/history/viewing-migration-results.md?ask=<question>&goal=<user_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.