Updated on 2026-11-13 GMT+08:00

Migrating Data Between FlexusL Instances

Scenarios

If you need to migrate workloads from one FlexusL instance to another under the same account, follow the instructions in this section. Data on FlexusL instances can be migrated within a region or across regions.

  • Within a region: You can migrate workloads between FlexusL instances within a given region. This is for scenarios such as instance specification changes and workload restructuring.
  • Across regions: You can migrate workloads from a FlexusL instance in one region to an instance in another region. This is for scenarios such as remote disaster recovery and nearby service access.

This section describes how to migrate workloads deployed on one instance to another. In this example, the source instance uses the BT panel (a visualized server management platform for Linux) application image, and the destination instance uses the Portainer (a visualized Docker management platform) application image.

  • The source and destination instances can be any FlexusL instances that support image creation and changes.
  • For some application images (such as OpenClaw, Dify, and Hermes), the FlexusL console provides application details and application templates. After the migration, the disk of the destination instance will contain the application details and template data (snapshot data during migration) of the source image. However, because the product metadata of the destination instance does not match that of the source image, the destination instance cannot use the application details page provided by FlexusL to manage applications or use the templates.

Migration Type

Source Instance

Destination Instance

Key Operations

Intra-region migration

FlexusL instance with Linux BT panel

Another FlexusL instance in the same region (for example, FlexusL instance with Docker Portainer)

Creating a private image from the source instance → Changing the image of the destination instance

Cross-region migration

FlexusL instance with Linux BT panel

Another FlexusL instance in a different region (for example, FlexusL instance with Docker Portainer)

Creating a private image from the source instance → Replicating the image to the destination region → Changing the image of the destination instance

Constraints

  • In the migration example described in this section, only a system disk image can be changed.
  • The system disk capacity of the destination instance must be greater than or equal to the minimum required by the private image. If the destination instance does not meet this requirement, upgrade the instance to a larger specification before changing the image.
  • The boot mode (BIOS/UEFI) of the destination instance must be the same as that of the private image. Otherwise, the image change will fail.
  • The Dify application image does not support image change, so a Dify instance cannot be used as the destination instance.

Prerequisites

  • You have created a FlexusL instance running the Linux BT panel application image as the source instance, and the instance is running properly.
  • You have created a FlexusL instance running another application image, such as the Docker Portainer application image, as the destination instance, and the instance is running or stopped.
  • The system disk capacity of the destination instance is greater than or equal to the minimum required by the private image.
  • The source and destination instances are in the same region (for intra-region migration) or in different regions (for cross-region migration).
  • For cross-region migration, ensure that the destination region supports FlexusL instances.
  • You have permission to create and manage private images in Image Management Service (IMS).
  • You have backed up important data of the source and destination instances using Cloud Backup and Recovery (CBR).

    Image changes will clear all data on the system disk. Back up important data in advance. Data on data disks is not affected.

Procedure

Select intra-region or cross-region data migration as needed.

  1. Create a private image from the source instance.

    1. Log in to the FlexusL console.
    2. Click on the card of the source instance and click Create Image.
    3. On the Create Image page, set parameters in the Image Type and Source area.

      Table 1 Image type and source

      Parameter

      Example

      Description

      Region

      CN-Hong Kong

      The FlexusL instance and the image created from it must be in the same region.

      Type

      Create Image

      Retain the default setting: Create Image.

      Image Type

      System disk image

      A private image will be created from the system disk. The image will contain the BT panel application and the service data on the system disk. Ensure that you select System disk image for Image Type. Otherwise, the image cannot be used for image change.

      Source

      hcss_ecs_xxxx

      Select the FlexusL instance that will be used to create an image. The system automatically selects the required instance. Retain the default selection.

    4. In the Image Information area, set the following parameters.

      Table 2 Image information

      Parameter

      Example

      Description

      Encryption

      Unencrypted

      Determines whether the image is encrypted. The setting cannot be changed.

      • Images created using an unencrypted cloud server will not be encrypted.
      • Images created using an encrypted cloud server will automatically be encrypted.

      Name

      bt_test

      Set a name for the image.

      • A name can contain 1 to 128 characters.
      • The name cannot start or end with a space.
      • The name can contain the following characters:
        • Uppercase letters
        • Lowercase letters
        • Digits
        • Special characters: hyphens (-), periods (.), underscores (_), and spaces.

      Enterprise Project

      default

      Select an enterprise project from the drop-down list. This parameter is available only if you have enabled Enterprise Project or your account is an enterprise account. To enable this function, contact your customer manager.

      An enterprise project can be used to centrally manage cloud resources and members by project.

      Tag

      -

      (Optional) Set a tag key and a tag value for the image to make identification and management of your images easier.

      Description

      -

      (Optional) Enter a description of the image.

      For details about how to create a private image, see Creating a Private Image from a FlexusL Instance.

    5. Read and agree to the agreement, click Next, and complete the operation as prompted.

      You can view the image creation progress in the private image list. When the image status becomes Normal, the image creation is complete.

      The time required for creating a system disk image depends on the amount of data on the system disk. Do not restart or stop the source instance during the creation.

  2. Change the image on the destination instance.

    1. Log in to the FlexusL console.
    2. On the card of the destination FlexusL instance (for example, an instance with Docker Portainer) where you want to change the image, click and then click Change OS.
    3. On the displayed page, click the Private Images tab in the image selection area.
    4. Select the created BT panel private image from the drop-down list.

      If the private image is displayed in gray in the drop-down list, move the cursor to the image name to view prompt details. For details about the causes and solutions, see FAQs.

    5. Confirm the image charge information, and read and agree to the related agreements.
    6. Click Submit. In the displayed dialog box, enter YES to confirm the change.

      The system will redirect you to the payment page (if any charge is incurred). After the payment is completed, the change will start. During the change, the instance will automatically stop and then restart. Ensure that no ongoing service operations are in progress.

    7. Check the instance card. If the instance status is Running and the image is the BT panel private image, the image has been successfully changed.

  3. Verify the migration result.

    Log in to BT panel and check whether the created website and database are available and can be accessed.
    • If your BT panel image is the old version (purchased before August 28, 2026), use http://EIP-of-the-destination-instance:8888 to access BT panel.
    • If your BT panel image is the new version, remotely log in to the destination instance and run the following command to obtain the BT panel access address:
      bt default
    • After the image is changed, the original login password of the destination instance becomes invalid. Reset the password before logging in to the instance.
    • For some application images (such as OpenClaw, Dify, and Hermes), the FlexusL console provides application details and application templates. After the migration, the disk of the destination instance will contain the application details and template data (snapshot data during migration) of the source image. However, because the product metadata of the destination instance does not match that of the source image, the destination instance cannot use the application details page provided by FlexusL to manage applications or use the templates.

  1. Create a private image from the source instance.

    1. Log in to the FlexusL console.
    2. Click on the card of the source instance and click Create Image.
    3. On the Create Image page, set parameters in the Image Type and Source area.

      Table 3 Image type and source

      Parameter

      Example

      Description

      Region

      CN-Hong Kong

      The FlexusL instance and the image created from it must be in the same region.

      Type

      Create Image

      Retain the default setting: Create Image.

      Image Type

      System disk image

      A private image will be created from the system disk. The image will contain the BT panel application and the service data on the system disk. Ensure that you select System disk image for Image Type. Otherwise, the image cannot be used for image change.

      Source

      hcss_ecs_xxxx

      Select the FlexusL instance that will be used to create an image. The system automatically selects the required instance. Retain the default selection.

    4. In the Image Information area, set the following parameters.

      Table 4 Image information

      Parameter

      Example

      Description

      Encryption

      Unencrypted

      Determines whether the image is encrypted. The setting cannot be changed.

      • Images created using an unencrypted cloud server will not be encrypted.
      • Images created using an encrypted cloud server will automatically be encrypted.

      Name

      bt_test

      Set a name for the image.

      • A name can contain 1 to 128 characters.
      • The name cannot start or end with a space.
      • The name can contain the following characters:
        • Uppercase letters
        • Lowercase letters
        • Digits
        • Special characters: hyphens (-), periods (.), underscores (_), and spaces.

      Enterprise Project

      default

      Select an enterprise project from the drop-down list. This parameter is available only if you have enabled Enterprise Project or your account is an enterprise account. To enable this function, contact your customer manager.

      An enterprise project can be used to centrally manage cloud resources and members by project.

      Tag

      -

      (Optional) Set a tag key and a tag value for the image to make identification and management of your images easier.

      Description

      -

      (Optional) Enter a description of the image.

      For details about how to create a private image, see Creating a Private Image from a FlexusL Instance.

    5. Read and agree to the agreement, click Next, and complete the operation as prompted.

      You can view the image creation progress in the private image list. When the image status becomes Normal, the image creation is complete.

      The time required for creating a system disk image depends on the amount of data on the system disk. Do not restart or stop the source instance during the creation.

  2. Replicate the image to the destination region.

    Replicate the private image created in the previous step from the source region to the destination region so that the FlexusL instance in the destination region can use the image. For details about the regions supported by cross-region image replication and operation constraints, see Replicating Images Across Regions.

    1. Log in to the IMS console.
    2. Locate the image to be replicated and choose More > Replicate in the Operation column.

    3. In the displayed dialog box, select Across Regions for Replication Mode, set Destination Region to the region where the destination FlexusL instance is located, and set other parameters as needed.

    4. Click OK. Switch to the private image page of the destination region. When the image status changes to Normal, the replication is successful.

      The time required for cross-region image replication depends on the image capacity and network bandwidth. Perform the replication during off-peak hours.

  3. Change the image on the destination instance.

    1. Log in to the FlexusL console.
    2. On the card of the destination FlexusL instance (for example, an instance with Docker Portainer) where you want to change the image, click and then click Change OS.
    3. On the displayed page, click the Private Images tab in the image selection area.
    4. Select the created BT panel private image from the drop-down list.

      If the private image is displayed in gray in the drop-down list, move the cursor to the image name to view prompt details. For details about the causes and solutions, see FAQs.

    5. Confirm the image charge information, and read and agree to the related agreements.
    6. Click Submit. In the displayed dialog box, enter YES to confirm the change.

      The system will redirect you to the payment page (if any charge is incurred). After the payment is completed, the change will start. During the change, the instance will automatically stop and then restart. Ensure that no ongoing service operations are in progress.

    7. Check the instance card. If the instance status is Running and the image is the BT panel private image, the image has been successfully changed.

  4. Verify the migration result.

    Log in to BT panel and check whether the created website and database are available and can be accessed.
    • If your BT panel image is the old version (purchased before August 28, 2026), use http://EIP-of-the-destination-instance:8888 to access BT panel.
    • If your BT panel image is the new version, remotely log in to the destination instance and run the following command to obtain the BT panel access address:
      bt default
    • After the image is changed, the original login password of the destination instance becomes invalid. Reset the password before logging in to the instance.
    • For some application images (such as OpenClaw, Dify, and Hermes), the FlexusL console provides application details and application templates. After the migration, the disk of the destination instance will contain the application details and template data (snapshot data during migration) of the source image. However, because the product metadata of the destination instance does not match that of the source image, the destination instance cannot use the application details page provided by FlexusL to manage applications or use the templates.

Helpful Links

  • After the image is changed, the original password becomes invalid. To log in to the FlexusL instance, reset its password first. For details, see Resetting the Password for a FlexusL Instance.
  • For details about how to log in to a FlexusL instance, see Login Modes.
  • After the migration is complete, the EIP used by BT panel is changed from the source instance's EIP to the destination instance's EIP. If a domain name was added and resolved for the EIP of the source instance, add and resolve the domain name for the destination instance. For more information, see Adding and Resolving a Domain Name for a FlexusL Instance.

FAQs

Why Is the "Change OS" Option Not Available for Dify Instances?

Symptom

In the operation menu of a FlexusL instance with the Dify application image, the Change OS option is unavailable or does not exist.

Possible causes

Currently, the image of an instance cannot be changed from a Dify application image to another image. So a Dify instance can only be used as the source for data migration (image creation is supported) and cannot be used as the destination (image change is not supported).

Solution

Perform the image change on another FlexusL instance that is not using a Dify image and change the image of the instance to the Dify private image.

Why Is the Created Private Image Displayed in Gray and Cannot Be Selected When I Change an Image?

Symptom

On the image change page, the created image is displayed in gray in the private image drop-down list and cannot be selected.

Causes and solution

Error Message

Cause

Solution

Full-ECS images are not supported. You are advised to use SMS for migration.

When creating an image, you selected Full-ECS image instead of System disk image for Image Type.

Create a private image again and select System disk image for Image Type.

This charged image cannot be selected. You are advised to use SMS for migration.

The private image is from KooGallery.

Use a non-charged image as the base to create a private image, or use SMS for migration.

The Windows private image is not created from a KooGallery Windows image and cannot be selected. You are advised to use SMS for migration.

The source of the Windows private image does not meet requirements.

Use a KooGallery Windows image to create a private image.

The password reset plug-in is not installed in the image or the onekey_resetpasswd tag is missing.

The password reset plug-in is not installed in the private image.

Install the password reset plug-in for the image by referring to the IMS documentation and try again.

The system disk capacity (X GiB) of the instance is less than that (Y GiB) of the image. Upgrade the instance to a higher specification and try again.

The system disk capacity of the destination instance is less than the minimum capacity (min_disk) required by the private image.

Upgrade the destination instance to a higher specification (increase the system disk capacity) and then change the image.

What Do I Do If the Image Fails to Be Changed?

Symptom

When you change an image, a message is displayed indicating that the current instance does not support image change and you need to contact customer service.

Possible causes

Possible causes include a boot mode mismatch or an abnormal instance status.

Solution

1. Check whether the instance is running or stopped. If the instance is in another state (for example, migrating), wait until the status is restored and try again.

2. Check whether the boot mode (BIOS/UEFI) of the private image is the same as that of the destination instance. If they are different, use an image with the same boot mode.

3. If the problem persists, submit a service ticket.

What Do I Do If I Cannot Log In to an Instance After Changing Its Image?

Symptom

After the image is changed, the original password cannot be used to log in to the destination instance through SSH.

Possible causes

After the image is changed, the original login password becomes invalid. You need to manually reset the password before logging in to the instance.

Solution

Reset the password of the FlexusL instance. For details, see Resetting the Password for a FlexusL Instance.

Are Application Details and Application Templates of the Source Instance Available on the Destination Instance After Migration?

Symptom

After the migration is complete, application details and application templates are unavailable on the destination instance.

Possible causes

For some application images (such as OpenClaw, Dify, and Hermes), the FlexusL console provides application details and application templates. After the migration, the disk of the destination instance will contain the application details and template data (snapshot data during migration) of the source image. However, because the product metadata of the destination instance does not match that of the source image, the destination instance cannot use the application details page provided by FlexusL to manage applications or use the templates.

Solution

The application details and template data after the migration are snapshot data. To manage application details and templates, perform operations on the source instance.