The following figure shows the server information mapping between MgC and SMS.

The following table lists the mapping between the server lists on the MgC and SMS consoles.
| Server List on MgC | Server List on SMS | Description |
| Hostname | Source Name | Hostname of a source server |
| IP Address | Source IP Address | IP address of a source server |
| Image | Source OS | OS of a source server |
| - | Target | Name of the paired target server |
Viewing a Server Migration Task Created by MgC on SMS
In a server migration workflow on MgC, after the
StartUpAgent step is complete, a migration task is automatically created on SMS and the task is in the ready status, as shown in
Figure 1 and
Figure 2.
Figure 1 Step for starting the migration Agent
Figure 2 Server list on SMS
Viewing the Real-Time Migration Status
When a server migration workflow reaches the
StartMigration or
StartSynchronization step, you can click a server record, and in the displayed dialog box, click the task name after
Migration Task to go to the SMS console, as shown in
Figure 3. On the SMS console, you view the source server details, target server configuration, and migration status, as shown in
Figure 4.
Figure 3 Server migration workflow
Figure 4 Details of a migration task on SMS
Retaining Migration Tasks on SMS
To retain the migration tasks created by MgC on SMS after a server migration workflow is complete, manually add a checkpoint before the step for clearing migration tasks in the workflow, as shown in Figure 5. For details about how to add checkpoints in a workflow and what are the precautions, see Adding a Stage or Step.
Figure 5 Adding a checkpoint
When the workflow reaches the checkpoint step for a server, do not conform it, as shown in
Figure 6. In this case, the migration task on the SMS console will not be deleted and its status is
Completed, as shown in
Figure 7. If you confirm the step, the task will be deleted from the SMS console.
Figure 6 A checkpoint step
Figure 7 Migration completed