Collect and organize key information according to the previous information collection guide to evaluate migration risks. Address risks as early as possible within critical KCP steps before migration, particularly during migration plan validation.

1. Minimize Performance Impact During Migration

During migration, storage and network performance of the original business systems may be affected. Efforts should be made to ensure user access is not disrupted during data synchronization.

Generally, pay attention to high-concurrency migrations or scenarios where business systems are under heavy load and the source VM has existing performance bottlenecks. It is recommended to perform migration and cutover during off-peak periods.

2. Control Downtime

Different migration methods cause varying lengths of business interruption. Downtime risks should be assessed before migration.

Perform an incremental sync before the scheduled change window to reduce the data synchronization workload during VM cutover, thereby shortening cutover time.

Prepare feasible steps for starting/stopping services and databases in advance to minimize change time and arrange a business verification plan.

3. Ensure Data Integrity

Migrating systems or data between different sites or hardware may result in transmission loss, leading to incomplete data. Migration plans should include comprehensive data verification throughout the process.

Ask the customer to prepare a business verification plan to ensure data usability. Retain the original VM for at least one-month post-migration to allow rollback and data recovery.

4. Choose Migration Method According to Specific Scenarios

Different applications have different characteristics, requiring different migration approaches. Database migration is complex and should be performed by experienced DBA/DMP professionals (including, but not limited to, database migration).

5. Estimate Migration Time

For large data volumes or limited bandwidth between source and target, the migration process may take a long time.

It is strongly recommended to perform a migration simulation test prior to the official migration to accurately assess speed and feasibility. Allow extra time for unknown risks.

6. Post-Migration Performance

Ensure that the hyper-converged platform can meet business system performance requirements after migration.

Generally, in V2V scenarios, the target VM configuration on the HCI should not be lower than the source virtualization platform, including but not limited to CPU frequency, number of cores, memory size, and memory frequency. Database performance should be evaluated separately.