Help Center/ Migration Center/ User Guide/ Application Migration Projects/ Resource Survey/ Online Discovery - SMS Server Synchronization
Updated on 2026-05-22 GMT+08:00

Online Discovery - SMS Server Synchronization

In server migration scenarios, some source servers do not support SSH connections or cannot provide key credentials. As a result, resources cannot be collected and data cannot be synchronized using the MgC Agent. To address this issue, the SMS Server Synchronization collection mode is added to MgC. This mode allows you to synchronize server resources and information from the SMS console to the MgC resource list and associate them with the migration assessment process. In this way, batch migration tasks can be completed without deploying the MgC Agent.

Prerequisites

Creating an SMS Server Synchronization Task

  1. Sign in to the MgC console. In the navigation pane, under Project, select your application migration project from the drop-down list.
  2. In the navigation pane, click Resource Survey.
  3. On the Online Survey tab, click SMS host synchronization.

    Figure 1 Creating an SMS server synchronization task

  4. Confirm the operation. The synchronization task is successfully created and the server on the SMS console is automatically synchronized. Check the task progress in the collection task list.

    Wait until the task becomes successful. Click the task name to go to the task details page. Click the number of servers in the list to check the server resource information. Alternatively, check the server information in the resource list. The platform type is SMS Agent.

Creating a Batch Server Migration Task

After the SMS server resources are synchronized, you can create and execute a batch server migration task. Large-Scale Migration describes the details. Before you start, note the following:

  • You do not need to install the MgC Agent for server resources collected by SMS synchronization tasks.
  • During task configuration, set Source Platform to SMS Agent.
  • Migration Readiness Check is unavailable during migration task configuration.