Migrate servers and applications to container images-Server Migration Center(SMC)-阿里云帮助中心

Introduction

Note

The server-to-container image migration feature has been upgraded to support an application migration mode, which lets you migrate specific applications. Both machine-level and application migration modes are supported.

SMC containerizes servers and business applications through machine-level migration and application migration. The resulting container images are pushed to Alibaba Cloud Container Registry (ACR). From there, they can be deployed to Container Service for Kubernetes (ACK). The following diagram illustrates the service relationships and the migration workflow.

Install the SMC client on the source server.
Configure the migration settings and start the migration. After the migration is complete, the system automatically generates a container image and stores it in the Personal edition of Alibaba Cloud Container Registry (ACR).
Deploy the application in Container Service for Kubernetes (ACK) to complete the migration.

Note

The Personal edition of Alibaba Cloud Container Registry (ACR) is for individual developers and provides basic image hosting and building services.
Container Service for Kubernetes (ACK) provides lifecycle management for enterprise-grade Kubernetes containerized applications, so you can easily and efficiently run these applications in the cloud.

Migration scenarios

Machine-level migration

Containerize the system and all application data from a physical server, virtual machine, or cloud platform server into an image and push it to Alibaba Cloud Container Registry (ACR). This method is ideal for system-level disaster recovery.
Application migration

Containerize specific applications from a physical server, virtual machine, or cloud platform server into an image and push it to Alibaba Cloud Container Registry (ACR). This method is ideal for microservice containerization.
Important
Application migration is in invitational preview. Contact us to apply for the whitelist. Supported application versions include:
- Java Tomcat
- Java Tomee
- Java JBoss (standalone mode)
- ASP.NET Core 3.1 and ASP.NET 5/6/7/8

Limitations

You can migrate only servers that run a Linux operating system on the x86 architecture to a container image. Supported operating systems include:
- CentOS
- Ubuntu
- RedHat
- Alibaba Cloud Linux
Application migration is available only to whitelisted users. To request access, contact us. Supported application versions include:
- Java Tomcat
- Java TomEE
- Java JBoss (standalone mode)
- ASP.NET Core 3.1 and .NET 5/6/7/8
You can migrate images only to an image repository in a personal edition instance of Container Registry (ACR).
Containerized migration currently does not support data disk migration. The system excludes the /mnt directory and all data disk mount points by default. The resulting target disk contains only one default partition. You do not need to adjust the existing partition structure.

To migrate data from a data disk to Alibaba Cloud, use FTP or SCP, or manually back up the data to Object Storage Service (OSS) or File Storage NAS. For more information, see Select a file transfer method and The ossutil 1.0 command-line tool.
In application migration mode, do not restart the application process during the migration. A change in the process ID will cause the migration task to fail.

Migration costs

While SMC is a free service, using Alibaba Cloud ECS resources, such as an intermediate instance during migration, incurs costs. For details, see SMC billable items.
Container images from containerized migration are stored in the Personal Edition of Alibaba Cloud Container Registry (ACR). Designed for individual developers, this edition is free to use during the public beta period and is currently available in select regions.
The specific costs of deploying applications to Container Service for Kubernetes (ACK) depend on the cluster type and your use of cloud products.

How it works

The SMC service consists of a client and a console. Containerized migration supports both machine-level migration and application migration modes.

Machine-level migration

This mode containerizes the entire system and all application data from a physical server, virtual machine (VM), or cloud server. The resulting container image is then pushed to Container Registry (ACR).
This mode does not generate an analysis report. Instead, it performs minimal trimming and then packages the entire operating system and application environment. This process creates a larger container image but fully preserves the source environment, enabling support for multiple applications.

Application migration

Important

The application migration feature is available only to whitelisted users. To request access, contact us. Supported application versions include:

Java Tomcat
Java Tomee
Java JBoss (standalone mode)
ASP.NET Core 3.1 and ASP.NET 5/6/7/8

This mode containerizes specific applications from a physical server, VM, or cloud server. The resulting container image is then pushed to Container Registry (ACR).
It generates an analysis report for the specified application and uses it to package only the required application data, resulting in a smaller container image.

The migration process is as follows:

Download and install the SMC client on the source server. If you import the source server by using the command line or the console's automatic import feature, the system installs the client automatically.
The SMC client runs on the source server and registers the source server with the SMC service using the SMC service domain name.
The SMC service creates a temporary intermediate instance and configures its security group to allow traffic on ports 8080 and 8703.

The intermediate instance uses two data disks to migrate data and generate the container image. The first data disk stores data from the source server, and the second is for building the container image.
The SMC client connects to the intermediate instance on port 8080. Then, it transfers data from the source server to the data disk of the intermediate instance over port 8703.

For application migration, the client transfers only the specified application and its related data.
The SMC service creates a container image from the disk data on the intermediate instance and uploads the image to Container Registry (ACR).

For application migration, the service creates the container image based on the application, its data, environment variables, and startup commands before uploading it to ACR.
To complete the migration, go to the Container Service for Kubernetes (ACK) console and deploy the application.

Migration impacts

Before you migrate, review the impacts in the table below.

Item	Description
Intermediate instance	Do not interfere with the intermediate instance. Do not stop, start, restart, or release the intermediate instance, or change its billing method during migration. The intermediate instance is automatically released after migration. Note For each migration, SMC creates a temporary, pay-as-you-go intermediate instance named `No_Delete_SMC_Transition_Instance` in your destination Alibaba Cloud account to assist with the migration. If you migrate to a destination instance, that instance serves as the intermediate instance and is not automatically released. How it works.
IP address	The IP address will change after migration. If your services rely on specific IP address configurations, you must update the relevant settings, such as DNS records and ICP filing.
Underlying hardware	The underlying hardware will change after migration. This may invalidate certain application licenses that are bound to specific hardware. Verify the status of your licenses after the migration.

Prerequisites

You have activated Server Migration Center (SMC). First-time SMC users must also grant the required permissions, prepare the migration network, and back up data. For more information, see Before you begin.
To migrate over a private network, you can connect your data center to a VPC by using VPN Gateway, Express Connect, or Smart Access Gateway. Because migrations across international regions can be slow due to public network instability, we recommend that you evaluate the migration time and test the transfer speed.

Migration actions

Step 1: Preparations

Follow the on-screen instructions to grant the specified RAM role to the intermediate instance. Server Migration Center (SMC) uses this RAM role to push the generated container image to Container Registry. If the page indicates that the required role is missing, click Request Permissions and then click Refresh.
Activate Container Registry and create an image repository (Personal Edition). The Personal Edition of Container Registry is for individual developers and supports creating an image repository in some regions. It is free during its public preview. Then, specify the Namespace, Repository Name, and Version.

Step 2: Import a migration source

A migration source is a physical server, VM, or cloud host from another platform that you want to migrate.

CLI import (recommended)

Important

The source server must have public network access. If the source server is behind a firewall, see What are the SMC service domains? to obtain the SMC endpoints and ports, and then add them to your firewall allowlist.
If your source server cannot access the public network or you want to use a private network for a faster migration, see private network migration.

Go to the Container Migration page in the SMC console.
On the Containerized migration page, click Import Migration Source.

Configure the parameters as prompted and copy the activation code command. The following table describes the parameters.

Parameter	Description
Migration Source Type	Select an option based on your source server: Physical servers/VMs/Cloud servers of other cloud platforms. ECS Instance
Import Method	Select Use CLI to Import Server.
Migration Source Quota	The number of migration sources that can be activated by the activation code. Valid values: 1 to 1,000. Default value: 200.
Validity Period	The validity period of the activation code, in days. Valid values: 1 to 90. Default value: 90.
Activation Code	Generate the activation code and copy the command. Click Generate. Click the Linux Shell tab. Click Copy to copy the activation code command.

Log on to the source server and run the copied command with administrator privileges to import it.
1. Log on to the Linux source server.
2. Paste and run the copied command with administrator privileges to import the migration source.
  If a message similar to Import Source Server [s-bp18x8751kgz2oyh****] Successfully! is displayed, it indicates a successful import.
On the Containerized migration page in the SMC console, check the status of the migration source in the Real-time Migration Status column.
- A status of Source Online indicates that the migration source was imported successfully.
- If the migration source is in any other status, the import failed. Troubleshoot the issue using the following methods and then re-import the migration source.
  - Troubleshoot the issue based on the error message in the console or by checking the log file in the SMC client directory. The SMC client is installed in the /smc directory by default.
  - For information about common issues and solutions, see SMC FAQ and Troubleshoot errors.

Automatic console import

Important

This method only supports importing Alibaba Cloud ECS instances.
The source server must be in the Running state, and Cloud Assistant must be available. For more information, see View the status of Cloud Assistant and handle exceptions.
If you use a RAM user to import a migration source, you must grant the RAM user the following permissions:
- The AliyunECSReadOnlyAccess permission, which grants read-only access to ECS. For more information, see Manage RAM user permissions.
- The AliyunECSAssistantFullAccess permission, which grants full management permissions on Cloud Assistant. For more information, see Manage RAM user permissions.

Go to the Container Migration page in the SMC console.
On the Containerized migration page, click Import Migration Source.

Configure the parameters based on the migration source type.

Parameter	Description
Migration Source Type	Select ECS Instance.
Import Method	Select Import through Console.
Region	From the drop-down list, select the region where your source server resides.
Instance	Search for and select the Alibaba Cloud ECS instances to migrate by instance ID, name, or IP address. You can select multiple instances for a batch import.
Tag (Optional)	Bind key-value tags to the migration task to simplify search and management. For more information, see Manage migration sources and tasks by using tags and Implement fine-grained access control by using tags. You can bind a maximum of 20 tags to a migration task.
Resource Group (Optional)	If you need to group migrated resources by business department or project, you can create resource groups.

After you configure the parameters, click Import.

SMC automatically starts Cloud Assistant to perform the import. The import process takes 3 to 10 minutes.
On the Containerized migration page in the SMC console, check the status of the migration source in the Real-time Migration Status column.
- A status of Source Online indicates that the migration source was imported successfully.
- If the migration source is in any other status, the import failed. Troubleshoot the issue using the following methods and then re-import the migration source.
  - Troubleshoot the issue based on the error message in the console or by checking the log file in the SMC client directory. The SMC client is installed in the /smc directory by default.
  - For information about common issues and solutions, see SMC FAQ and Troubleshoot errors.

SMC client import

For more information about the SMC client, see SMC Client User Guide.

Important

To import a migration source with the SMC client, the client must run on the source server. Public network access is enabled by default. If the source server has firewall restrictions, see What are the SMC service domains? to obtain the SMC domain names and ports, and then add them to the firewall allowlist.
If your source server cannot access the public network or you want to use a private network for a faster migration, see private network migration.

Go to the Container Migration page in the SMC console.
On the Containerized migration page, click Import Migration Source.

On the Import Source Servers page, configure the parameters as described in the following table.

Parameter	Description
Migration Source Type	Physical servers/VMs/Cloud servers of other cloud platforms.
Import Method	Select Use Client to Import Server. You must manually download and install the SMC client on the source server.
Description	In the Description section, follow the prompts to download, install, and activate the SMC client that matches the operating system (Linux or Windows) and architecture (32-bit or 64-bit) of your source server. Click Generate and copy the activation code. You must enter the activation code when you install the client.

Import the migration source.

Important
Do not close the SMC client during the migration. Otherwise, the migration source will lose its connection to the SMC console and the migration will fail.
1. Use a remote connection tool that supports file transfer, such as WinSCP, to upload the SMC client to the Linux source server, or run the command provided in the import instructions to download the SMC client directly on the source server.
2. Remotely connect to the Linux source server and decompress the SMC client package.
  The following command uses the Linux 64-bit General-purpose Edition as an example. If you use a different version of the SMC client, replace the package name in the command with the name of the file you downloaded.
```
tar -zxvf go2aliyun_client.tar.gz
```
  Note
  The Linux 64-bit ARM Edition supports the g6r general-purpose instance family and the c6r compute-optimized instance family. Enterprise-level Arm-based compute instance families.
3. (Optional) Exclude files or directories from the migration.
  Important
  If you enable block replication for the migration, you cannot exclude files or directories.
4. Obtain an activation code or an AccessKey pair.
  - (Recommended) Obtain an activation code: In the Description section of the SMC console, click Generate and copy the activation code.
  - Obtain an AccessKey pair: An AccessKey pair consists of an AccessKey ID and an AccessKey secret. If you have not created one, see Create an AccessKey pair.
5. In the SMC client directory, run the following commands to start the SMC client.
  The go2aliyun_client2.6.5_linux_x86_64 directory is used as an example. The directory name varies based on the client version. Make sure to replace it with the name of the directory created after you download and decompress the package.
```
cd go2aliyun_client2.6.5_linux_x86_64
sudo chmod +x go2aliyun_client
sudo ./go2aliyun_client
```
6. Enter the activation code or AccessKey pair as prompted. The following example shows how to enter an activation code:
  After you enter the activation code or AccessKey pair, the following prompts may appear:
  - If a snapshot driver is not installed on the source system, the SMC client prompts you to install one. You can choose whether to install it based on your migration plan.
    - If you plan to enable block replication when you create the migration task, enter yes to automatically install the snapshot driver.
    - If you do not plan to enable block replication, enter no.
    Important
    If the snapshot driver fails to install, do not enable block replication when you create the migration task. Otherwise, the migration will fail.
  - Most mainstream source systems have rsync installed by default. If rsync is not installed, the SMC client prompts you to install it. Enter yes to automatically install rsync, as shown in the following figure.
  - If SELinux is enabled on the source system, the SMC client prompts you to disable it. Enter yes to automatically disable SELinux, as shown in the following figure.
  If a message similar to Import Source Server [s-bp11npxndknsycqj****] Successfully! is displayed, it indicates a successful import.
  Note
  If the import fails, troubleshoot the issue based on the displayed message. Then, run the following commands in sequence to exit the background process and import the migration source again. For information about common issues and solutions, see SMC FAQ and Troubleshooting.
  sudo ./go2aliyun_client --abort sudo ./go2aliyun_client
On the Containerized migration page in the SMC console, check the status of the migration source in the Real-time Migration Status column.
- A status of Source Online indicates that the migration source was imported successfully.
- If the migration source is in any other status, the import failed. Troubleshoot the issue using the following methods and then re-import the migration source.
  - Troubleshoot the issue based on the error message in the console or by checking the log file in the SMC client directory. The SMC client is installed in the /smc directory by default.
  - For information about common issues and solutions, see SMC FAQ and Troubleshoot errors.

Step 3: Migration configuration

In the Actions column of the migration source that you want to manage, click Start Migration.

Configure the parameters and click Start Migration.

Configure basic parameters.

Parameter	Description
Destination Region (Required)	The Alibaba Cloud region to which you want to migrate the server. For more information about regions, see Regions and availability zones.
Namespace (Required)	Select the namespace for the container image repository that will store the container image created by the migration. If you have not created a namespace, see Manage namespaces and quotas to create one.
Repository Name (Required)	Select the repository to store the container image created by the migration. If you have not created an image repository, see Build repositories and images to create one.
Version (Required)	Enter a version for the container image created by the migration. Example: v1. The string must be 1 to 128 characters in length. The string can contain only lowercase letters (a-z), digits (0-9), periods (.), underscores (_), or hyphens (-). The string cannot start or end with a period (.) or a hyphen (-).
Intermediate instance RAM role (Required)	Select the RAM role for the intermediate instance. If you have not created a RAM role, create one as described in Step 1: Preparations.
Migration Mode	Migrate All Instances Migrates the entire system and application data from a physical machine or virtual machine to Alibaba Cloud Container Registry (ACR) Personal Edition. This mode does not generate an analysis report. It packages the entire operating system after minimal trimming, creating a larger container image. However, the runtime environment is identical to the source system and can support multiple applications. Ideal for system-level disaster recovery. Application Migration Migrates specific applications from a physical machine or virtual machine to Alibaba Cloud Container Registry (ACR) Personal Edition. This minimizes the size of the generated container image, resulting in a smaller container image. This mode analyzes the specified application and packages only the required data based on the report, producing a smaller container image. This mode currently supports Java Tomcat, Tomee, JBoss, and ASP.NET applications. Make sure the application you want to migrate is a supported type. Ideal for containerizing microservices.
Select Applications to Be Migrated	Select the application that you want to migrate. The drop-down list displays only supported applications. If your application is not in the list, it cannot be migrated. The application ID is generated by SMC in the format `${application_id} (Process: ${pid})`. For example: `java-tomcat-5924e694(Process: 2360)`. After the analysis is completed, you need to confirm the analysis results.: Deselected: The migration runs automatically after the analysis is complete. Selected: The migration job pauses after analysis is complete. You must then confirm the results to continue the migration. The analysis report is stored on the source server at a path such as `/smc/app2container/java-tomcat-5924e694/analysis.json`.
Execution Method	Select how to run the migration job: Migrate Now: Starts the migration job immediately after it is created. Migrate Now is the default option. Create Only: Creates the migration job but does not start it. You must manually start the job by clicking Run in the Actions column.
Network Type	Select the network for transferring migration data to the intermediate instance. By default, data is transferred over the public network. The intermediate instance is created in the selected Virtual Private Cloud (VPC) and vSwitch and is assigned a public IP address. Public Network (Default) Migration data is transferred to the intermediate instance over the public network. This mode requires the source server to have public internet access. You can choose whether to specify a Virtual Private Cloud (VPC) and vSwitch. Specify a VPC and vSwitch: The migration job creates an intermediate instance in the VPC and vSwitch that you specify. Do not specify a VPC and vSwitch: The migration job creates an intermediate instance in a new VPC and vSwitch that are automatically created by the system. VPC Migration data is transferred to the intermediate instance over a private connection within a VPC. This mode requires you to connect the source server to the Alibaba Cloud VPC and specify a VPC and vSwitch. Note If you can directly access a VPC in an Alibaba Cloud region from an on-premises data center (IDC), virtual machine (VM) environment, or cloud host, we recommend that you use this method. Private network transfer is faster and more stable than public network transfer, improving migration efficiency. You can connect the source server to the cloud VPC by using a VPN gateway, an Express Connect circuit, or a Smart Access Gateway. For more information, see Connect a VPC to a data center or another cloud.

Optionally, to set parameters such as transmission speed and compression ratio, click Advanced Settings.

Parameter	Description
Migration Job Name	The name of the migration job.
Job Description	A description of the migration job.
Transmission Speed Limit	Limits the data transfer speed, in Mbit/s. If Compression Ratio is set to a value greater than 0, the actual network transfer speed for the compressed data is lower than the speed displayed in Real-time Migration Status.
Compression Ratio	Sets the data compression level for migration. In environments with limited bandwidth, a higher compression ratio can increase data transfer speed. In environments with high bandwidth, we recommend that you do not compress data to reduce CPU usage on the source server. Valid values: 0 to 10. The default value is 7. A value of 0 indicates that data is not compressed.
Checksum Verification	This feature is disabled by default. Enabling it enhances data consistency checks but may decrease transfer speed.
SSL encrypted transmission	The default value is Auto-Select. SSL encryption for data transfer improves security and data integrity.
Tag	Add tags (key-value pairs) to the migration job for easier searching and management. Use tags to manage migration sources and jobs. Implement fine-grained permission management by using tags. Note You can add a maximum of 20 tags to a single migration job.
Intermediate Instance Type	You can select an instance type for the intermediate instance. If you specify an instance type, the system creates an intermediate instance of that type. If the specified instance type is out of stock, the migration job creation fails. If you do not select an instance type, the system automatically creates the intermediate instance by selecting from a predefined list of available types. Important To prevent migration errors, do not stop, start, restart, or release the intermediate instance during the migration. The instance is automatically released after the migration is complete.
Report diagnostic logs	Automatically uploads SMC client logs to the SMC server for diagnostic analysis. This helps troubleshoot issues if a migration error occurs. This feature is enabled by default. SMC client logs are typically stored in the `/smc/go2aliyun_client*/Logs` directory within the installation path.

In the dialog box that appears, carefully read the migration notes, and then click Got It.

On the Containerized migration page, monitor the real-time status of the migration job.
The data transfer time depends on factors such as the source data size and network bandwidth.
Note
- Speed: The amount of uncompressed migration data transferred per second. If the Compression Ratio for the migration job is greater than 0, the displayed speed is higher than the actual network transfer speed of the compressed data.
- Time Remaining for Synchronization: Calculated as (Total Data Volume - Transferred Data Volume) / Speed.
- If the transfer speed is too slow, consider temporarily increasing the fixed bandwidth of the source and destination servers. Estimate migration time and test transfer speed.
Subscribe to migration error events, and modify or pause the migration
- To avoid interruptions from migration errors, you can subscribe to SMC job error notifications in CloudMonitor to receive timely SMS and email alerts.
- While the migration job status is Synchronizing, you can perform the following operations as needed:
  To edit a migration task, in the Actions column, click Modify Migration Job. You can modify parameters such as transfer throttling, compression ratio, and Checksum verification.
  Pause the migration job: In the Actions column, click Pause Migration Job to pause the migration.
In the Migration Source ID/Name column of the target migration source, click the migration source ID to view migration details.

The migration details page contains the Basic Information and Job Configuration sections. The Basic Information section displays job details such as the Job ID/Name, Job Status, Job Progress, Destination Region, and Migration Mode. The Job Configuration section shows the Network Type, Destination VPC, and Destination vSwitch.

Verify the migration results

When the Real-time Migration Status is Completed, the migration is successful.

A successful migration generates an Alibaba Cloud container image. You can use this image to deploy a container application.
1. In the Actions column for the migration source, click Deploy Application. This action redirects you to the ACK cluster list page.
2. Select an existing ACK cluster or create a new one. For more information, see Create a cluster.
3. Navigate to the cluster. In the left-side navigation pane, choose Workloads > Deployments. Click create from image to create an application. Select the container image generated by the migration. For more information, see Create a stateless workload Deployment.
  - Startup command for machine-level migration
    
    When you deploy an application on an ACK cluster, you must add the relevant scripts and development ports to the application lifecycle or the application YAML file to start the service on the source server. Add the scripts based on your actual needs. The following is an example of adding a CMD command to a YAML file:
```
spec:
      containers:
        - args:
            - |
              cd /www/server/panel &&
              chmod +x /www/server/panel/init.sh &&
              echo 3 | sh init.sh &&
              tail -f /dev/null
          command:
            - /bin/sh
            - '-c'
          image: 'registry-vpc.cn-hangzhou.aliyuncs.com/zi***h/sa***:v1'
```
  - Application migration mode
    
    Run netstat -lptn on the source server to view the application's service ports, then configure port mapping when you deploy the application in the ACK cluster.
4. After migrating the server, you must validate the data to ensure its integrity and correctness. For more information, see After migrating a Linux server, how do I check the system?.
  
  Note
  If a domain name is mapped to the source server, remap it to the new instance's public IP address. Add a website resolution.
If the Real-time Migration Status is Error, the migration has failed. You must troubleshoot the issue and then retry the migration:
1. In the Actions column, click Troubleshoot Errors. Resolve the issue based on the error code and error message. For more information, see SMC FAQ and troubleshooting.
2. After resolving the issue, in the Actions column, click Retry Migration Job. The job resumes from where it left off.
  
  Important
  If the intermediate instance has been released, you must restart the migration. For more information, see I accidentally released the intermediate instance. What should I do?.

Clean up resources

Migrate to an image

During the migration, SMC creates a temporary pay-as-you-go intermediate instance named No_Delete_SMC_Transition_Instance in your destination Alibaba Cloud account to facilitate the migration. The migration result determines whether you need to manually release the instance:

Successful migration: SMC automatically releases the intermediate instance. No manual cleanup is required.
Migration error: The intermediate instance is not released and continues to incur charges. To avoid unnecessary charges, you can release the instance in one of the following ways:
- If you no longer need the migration task, click the migration source ID. In the Actions column for the migration task, click Cancel Migration Job to delete the migration task and automatically clean up the intermediate instance.
- Manually release the intermediate instance.

Migrate to a destination instance

During the migration, SMC creates a temporary pay-as-you-go intermediate disk named SMC_Temp_Disk and attaches it to the destination instance to facilitate the migration. The migration result determines whether you need to manually release the intermediate disk:

Successful migration: SMC automatically releases the intermediate disk. No manual cleanup is required.
Migration error: The intermediate disk is not released and continues to incur charges. To avoid unnecessary charges, you can release the disk in one of the following ways:
- If you no longer need the migration task, click the migration source ID. In the Actions column for the migration task, click Cancel Migration Job to delete the migration task and automatically clean up the intermediate disk.
- Manually release the intermediate disk.

Containerized migration for servers and applications

Introduction

Migration scenarios

Limitations

Migration costs

How it works

Machine-level migration

Application migration

Migration impacts

Prerequisites

Migration actions

Step 1: Preparations

Step 2: Import a migration source

CLI import (recommended)

Automatic console import

SMC client import

Step 3: Migration configuration

Public Network (Default)

VPC

Verify the migration results

Startup command for machine-level migration

Application migration mode

Clean up resources

Migrate to an image

Migrate to a destination instance