Home > Perform Microsoft Teams Migrations > View and Understand Mappings
Export to PDF#View and Understand Mappings
Besides the actions above, you can perform on mappings within a Microsoft Teams migration project, you can also view the following on the Project mappings page.
#View Action Stage and Stage Status
You can view the latest action stage and the current stage status of each mapping. Refer to the following action stages of mappings:
- **New mapping** – The mapping is newly added.
- **Mapping** **verification** – The current action on the mapping is **Verify mapping**.
- **Scan source data** – The current action on the mapping is **Scan source data**.
- **Migration** – The current action on the mapping is **Migration**. (**Full migration**, **incremental migration**, **Retry** **error** **objects**, **Stop** migration, and **Migrate membership** all use **Migration** to show the current action.)
If the **Migration** stage has a **run** **at time** link, it indicates that the migration has a schedule and will be run based on the configured time.
For running mappings, the percentage of migration progress and migrated objects will be displayed next to the stage. However, the migration progress may be affected by many factors. Refer to [Information about the Migration Progress](#missing-link) for details.
Each action stage has the following stage statuses:
- **Scheduled** – The full/incremental migration of the mapping is a scheduled migration, and the migration time has not arrived.
- **In queue** – The current action on the mapping is waiting in the queue to be started.
- **In queue with** **priority** – The current action on the mapping is waiting in the queue to be started with priority.
- **In progress** – The current action on the mapping is in progress.
- **Finished** – The current action on the mapping has finished without errors.
- **Exceptions** – The current action on the mapping has finished with errors. You can click the error number to view the error details and resolve the issue based on the comment.
- **Failed** – The current action on the mapping has failed. You can click the error number to view the error details and resolve the issue based on the comment.
- **Stopped** – The current action on the mapping has been stopped.
#View Mapping Report
Clicking the source Team email address in a mapping will take you to view the mapping’s report, including the source data scan report and migration details. On the View mapping report page, there are five reports to show data details of the mapping.
- **Summary** – Click the **Summary** tab to view the reports of the mapping.
- **Migration history** – This report shows the user who runs the mapping, job duration, and the history of all actions on the mapping. You can click an action on the left to view the general information and throttling information of the action.
- **General information** – This report shows the data details of the action. The information includes total object count, total data size, migrated data size per hour, successfully migrated object count, etc.
- **Throttling information** – This report shows the waiting time for exporting data from the source, the waiting time for importing data to the destination, and the source and destination throttling count and duration.
- **Source data scan report** – This report shows the object counts of the source Team, which are generated after you perform the **Scan source data** action on the mapping.
- **Team objects** – This report shows the migration result of source objects, including the numbers of objects that are successfully migrated, migrated with exceptions, and migrated with errors.
- **Migration error** – Click **Migration error** tab to view the error statistics and migration errors of the mapping.
- **Error statistics** – If there are objects with errors in the migration, this report will be generated to show the number of objects with errors categorized by error codes.
- **Migration errors** – If there are objects with errors in the migration, this report will be generated to show the objects, error details, error codes, and start time of the migration. To go to the troubleshooting guide for details about the error, click the error code link.
You can perform the following actions to the errors:
- Filter – You can click **Filter** to filter migration errors by **Error code**, **Status**, and/or **Category color**.
- Categorize with color – You can categorize the errors with a desired color. What the applied color represents is left up entirely to your organization.
You can hover your mouse over an error and click the apply color () button. Select a color in the **Select a color** window to apply to the error. You can also select one or multiple errors and click **Categorize with color**. In the **Select a color** window, select a color and click **Apply**.
- Retry all error objects – Retry all errors listed in this section. Note that the applied filter of errors will not affect the job.
- Export – Select one or multiple error objects and click **Export** to export the object information displayed in the **Migration errors** section to an Excel file to the current browser’s download location.
On this page