Help Center/ Migration Center/ User Guide/ New Edition/ Migration Workflows (New)/ Creating a Batch Object Storage Migration Workflow
Updated on 2025-08-19 GMT+08:00

Creating a Batch Object Storage Migration Workflow

This section describes how to create a workflow to efficiently migrate buckets in batches.

Constraints

  • For more information, see What Are the Restrictions on Using MgC for Storage Migration?
  • Data in the Deep Cold Archive storage of Alibaba Cloud OSS cannot be restored using the restoration function of MgC. You need to manually restore the data before migration.
  • Microsoft Azure Blob does not support automatic archiving of restored data. If needed, you can manually archive the data after the migration is complete.

Prerequisites

A batch object storage migration plan has been created for the source buckets to be migrated.

Procedure

  1. Sign in to the MgC console. In the navigation pane, under Project, select an application migration project from the drop-down list.
  2. In the navigation pane, choose Migration Workflows (NEW).
  3. On the Workflows tab, click Create Workflow to open the Select Creation Method page.
  4. Select the created batch object storage migration plan from the Migration Plan drop-down list. Then click OK. Incomplete migration plans cannot be selected. For details about how to create a migration plan, see Creating a Batch Object Storage Migration Plan.
  5. In the Basic Information area, enter a name and description for the workflow.
  6. In the Resource Settings and Migration Settings areas, check whether the resource and migration settings inherited from the selected migration plan meet your requirements. If you need to modify these settings, click Modify Migration Plan in the lower right corner of the page and update the migration plan settings.
  7. Confirm the settings and click Create Workflow in the lower right corner of the page. The Start Workflow dialog box is displayed, which indicates that the workflow has been created.

    • If you want to start the migration immediately, click Confirm to run the workflow.
    • If you want to save the migration workflow without starting the migration, click Cancel. The migration workflow will move to a Waiting status, and the migration has not started yet. To run the workflow, click Run in the Operation column to manually start the migration. If you need to add checkpoints to the workflow to control the migration process, see Adding a Stage or Step.

  8. In the workflow list, click the workflow name. On the Workflow Details page, you can review the workflow status, progress, and migration progress of the resources contained in the workflow.

    When the workflow on a resource reaches a step requiring manual confirmation, choose More > Confirm in the Operation column, or click the resource name. In the displayed page, click Confirm. The workflow will then continue with the remaining migration steps.

    In the resource list, click More > View Target Resource in the Operation column to view details about the target bucket.

  9. Click a resource name. On the page displayed on the right, you can view the Migration Progress and Historical Tasks tabs. You can also perform the following operations:

    Operation

    Description

    Modifying the migration schedule

    1. In the Overview area, click Modify next to Schedule Migration.
    2. Set Start Time and End Time, and click Confirm.

    Modifying the number of concurrent subtasks

    1. In the Progress area, under Expected Concurrent Subtasks, click Modify to change the expected number of concurrent subtasks. There cannot be more than 10 concurrent subtasks for each online migration node. For example, if there are 2 online migration nodes, the maximum number of subtasks can be 20 or any number below.
    2. Click Confirm.

    Adding traffic limiting rules

    1. In the Migration Speed area, click Add to add a rule to limit the bandwidth the migration can use in a specified period.
      NOTICE:
      • The bandwidth limit ranges from 1 MB to 1,024 GB.
      • Time periods in different rules cannot overlap.

        For example, if there is a rule added for the period from 8:00 to 12:00, you cannot configure rules for any overlapped periods, such as from 7:00 to 13:00, 7:00 to 8:00, and 9:00 to 12:00.

      • The start time in a rule cannot be later than the end time.

        For example, the time period from 23:00 to 01:00 is not allowed.

    2. Click Save.

    Obtaining the lists of migrated, skipped, or failed files

    In the File Statistics area, view the paths of the lists of migrated, skipped, or failed files. Click a file path, and it will take you to the OBS bucket where the list is stored. You can download the list from the bucket.

    Viewing traffic statistics

    In the Traffic Statistics area, view the migration traffic in the last 1 hour, last 6 hours, last 24 hours, or the entire migration period.