Collect and organize key information according to the previous information collection guidance to assess migration feasibility, which will support subsequent planning and design.

1. Source and target platform versions (VMware, HCI) Check whether they are listed in the tool compatibility list.
2. OS type of the host to be migrated: Verify whether it is listed in the tool compatibility list.

SCMT’s agent-based migration method is closely related to the OS version and kernel version (minor versions). Make sure this information is corrected accurately. Install the SCMT agent on the source machine 1–2 weeks in advance.

3. Whether the business type is suitable for tool-based migration:

Consider the business type (single-node, clustered), performance requirements, allowable downtime window, confirm migration method, and target cluster.

4. Post-migration business licensing:

Different software uses different licensing methods. Determine whether the application is bound to host hardware (e.g., MAC address, disk ID). If licensing is involved, it may become invalid and require reactivation. Check whether license keys are available and coordinate with the business system team.

List licensing methods for different applications based on actual situations.

5. Network connectivity and bandwidth between source and target:

VMware management-based migration uses the management network, with an average speed of 35–50 MB/s.

SCMT migration uses the business network, with an average speed of 80–100 MB/s.

Use these speeds to estimate VM migration time. It is strongly recommended to conduct a migration simulation test before the official migration to accurately assess migration speed and feasibility.

6. Third-party hardware scenarios and hardware compatibility:

For legacy or third-party hardware not listed in the compatibility list, Please refers Sangfor hardware compatiblity and prepare hardware import testing in advance.