The SCMT (Sangfor Cloud Migration Tool) is an independent tool, support P2V (Physical-to-Virtual) and V2V (Virtual-to-Virtual) migration for customers' business. It addresses the challenges posed by heterogeneous host migration in hybrid-architecture data centers, including heavy workloads, difficult migration coordination, complex migration operations, long business downtime, and high migration risks. Additionally, SCMT offers four migration methods: Point-to-point agentless migration, Point-to-point agent-based migration, Hot Standby migration, and Backup migration.

Point-to-point (agentless): The VMware platform supports the source machine's migration without the agent's installation and uses the VMware VADP interface to obtain VM data. After migrating to the HCI destination machine, it supports automatic compatibility processing (injection of vmtools). There is no need to back up the source system, and the source system data is transferred to the destination VM through the SCMT.

Point-to-point migration (agent-based): It uses the migration function to directly transfer the source data to the destination machine to migrate the source as a whole to the destination machine. There is no need to back up the source system, and the source system data is transferred to the destination VM on the HCI platform.

Hot standby migration: The source system data is continuously backed up to the SCMT using the function of CDP backup and then synchronized to the destination VM. In this way, data from the source system is synchronized to the destination in real-time through CDP, which minimizes the migration and switching time.

Backup migration: Use the backup function to back up the source system data to the Sangfor Cloud Migration platform. Then, restore the system to the destination VM through the backup file saved on the server. Compared with point-to-point migration and HA backup migration, longer business downtime is required.

There is no limit to the maximum number of concurrent migration tasks for virtual machines. When the system resources of the SCMT are insufficient, a queuing mechanism will be applied to migration tasks—only when there are enough available resources will the migration tasks in the switching phase resume switching. Moreover, as the number of migration tasks undergoing switching at the same time increases, the switching duration will increase correspondingly. It is recommended to keep the concurrent migration tasks per SCMT instance under 10. If there are a lot of VMs to be migrated, consider deploying multiple SCMT.