Create and view DataWorks export tasks - DataWorks - Alibaba Cloud Documentation Center

Migration Assistant lets you export objects such as scheduled tasks, manual tasks, resources, functions, table metadata, data sources, and components. You can create and view export tasks, with some differences between Data Studio and legacy Data Studio.

Background

Migration Assistant supports three export types: Full Export, Incremental Export, and Custom Export:

Full Export creates a complete backup of all tasks in a workspace, useful for backing up code or quickly cloning a test environment. This option exports the latest saved version from the development environment.

Full Export exports only successfully saved objects. If a task has multiple versions, such as development and production versions, the development version takes precedence. For detailed instructions, see Create a full export task.
Incremental Export filters and exports objects based on their last modification time. For detailed instructions, see Create an incremental export task.

Note
You cannot configure a blacklist for an incremental export.
Custom Export lets you select specific business workflows for easy replication. In an environment with fully isolated development and production clusters, you can use Custom Export to simulate task deployment. For detailed instructions, see Create a custom export task.

Limitations

The following table lists the DataWorks migration features supported by each edition.

DataWorks migration feature		Basic Edition	Standard Edition	Professional Edition	Enterprise Edition
Number of DataWorks export packages supported per tenant Note When you create an export task and the export succeeds, an export package is generated. If the number of export packages exceeds the limit of your edition, upgrade your edition to obtain more export packages. You cannot purchase additional export packages separately.		Up to 10 (cumulative)	Up to 30 (cumulative)	Up to 100 (cumulative)	Unlimited
DataWorks import package size limit	Local file upload	30 MB	30 MB	30 MB	30 MB
DataWorks import package size limit	OSS file upload	Not supported	Not supported	Unlimited	Unlimited
Whether auto-commit and auto-deploy are supported during DataWorks import		Not supported	Not supported	Supported	Supported

Only Alibaba Cloud accounts and workspace administrators can perform import and export operations. Members with other roles can only view the import and export task lists and do not have operation permissions.
When you export and import Data Quality rules (supported only in legacy Data Studio), take note of the following points:
- When you export Data Quality rules, subscription management (alert-related configurations) is not exported.
- If the table associated with an imported Data Quality rule does not exist in the destination workspace, the imported rule is not displayed on the Data Quality rules page. If you create the destination table after importing the Data Quality rule, the imported rule is displayed on the rule details page of the table.
- The Data Quality import step depends on the successful completion of the scheduled task import step. If an import package contains both Data Quality rules and associated scheduling node information, you must first import the associated nodes to the destination workspace and successfully commit and deploy them before the scheduling nodes can be correctly associated with the Data Quality rules.
- If you import only Data Quality rules without importing the associated scheduling nodes, the Data Quality rules are still imported successfully, but without the associated scheduling node information. After you import and commit and deploy the associated scheduling node information, you can re-import the Data Quality rules, and DataWorks updates the rules and associates them with the scheduling nodes.
Data Studio and legacy Data Studio have differences in Migration Assistant features. For details, see the notes in each operation section below.

Go to Migration Assistant

Log on to the DataWorks console, switch to the target region, and then click More > Migration Assistant in the left-side navigation pane to go to the Migration Assistant Homepage page.

Create a full export task

On the DataWorks export page, click Create Export Task in the upper-right corner.
In the Create Export Task dialog box, configure the parameters.

Data Studio

Parameter	Description
Export Package Name	The export name can contain only letters, Chinese characters, digits, underscores (_), and periods (.).
Export Type	When you select Full Export, you can configure Export Scope below to export the full content of the selected objects.
Export Scope and Export Object	Export Scope supports: All Objects: If you select this option, all objects in the current workspace are exported. The objects include scheduled tasks, manual tasks, resources, functions, table DDL statements (MaxCompute only), data sources, and components. Selected Objects: If you select this option, you can select the objects that you want to fully export from the Export Object drop-down list below, such as scheduled tasks, resources, and DataService Studio.
Export Object Status	You can select the state of the objects to export: Saved: Exports the saved content of the export objects. Deployed: Exports the deployed content of the export objects.
Remarks	Enter a brief description of the export task.

Legacy Data Studio

Parameter	Description
Export Package Name	The export name can contain only letters, Chinese characters, digits, underscores (_), and periods (.).
Export Type	When you select Full Export, you can configure Export Scope below to export the full content of the selected objects.
Export Scope and Export Object	Export Scope supports: All Objects: If you select this option, all objects in the current workspace are exported. In legacy Data Studio, the objects include scheduled tasks, manual tasks, resources, functions, table DDL statements (MaxCompute only), data sources, DataService Studio, ad hoc queries, components, and Data Quality rules. Selected Objects: If you select this option, you can select the objects that you want to fully export from the Export Object drop-down list below, such as scheduled tasks, resources, and DataService Studio.
Export Object Status	You can select the state of the objects to export: Saved: Exports the saved content of the export objects. Committed: Exports the committed content of the export objects.
Blacklist	You can determine whether to select Add to Blacklist based on your business requirements to filter out tasks and resources that do not need to be exported.
Export Package Version and Format of Files in Export Package	Options include Standard Format, Apsara Stack (V3.12 and later), and Apsara Stack (V3.6.1 to V3.11). Data formats vary across DataWorks versions. Confirm the DataWorks version in the destination import environment before selecting a format.
Remarks	Enter a brief description of the export task.

Click Start Export.
In the Export Progress dialog box, view the export progress. After the export succeeds, click Return to Export Task List.

Create an incremental export task

On the DataWorks export page, click Create Export Task in the upper-right corner.

In the Create Export Task dialog box, configure the parameters.

Data Studio

Parameter	Description
Export Package Name	The export name can contain only letters, Chinese characters, digits, underscores (_), and periods (.).
Export Type	When you select Incremental Export, files that were modified after the specified date are exported, including saved and committed scheduled tasks, manual tasks, table metadata, and data sources.
Export Scope and Export Object	All Objects: If you select this option, all objects in the current workspace are exported. The objects include scheduled tasks, manual tasks, resources, functions, table DDL statements (MaxCompute only), data sources, and components. Selected Objects: If you select this option, you can select the objects that you want to fully export from the Export Object drop-down list below, such as scheduled tasks, resources, and DataService Studio.
Export Object Status	You can select the state of the objects to export: Saved: Exports the saved content of the export objects. Deployed: Exports the deployed content of the export objects.
Modified At	The incremental export is based on the last modification time.
Remarks	Enter a brief description of the export task.

Legacy Data Studio

Parameter	Description
Export Package Name	The export name can contain only letters, Chinese characters, digits, underscores (_), and periods (.).
Export Type	When you select Incremental Export, files that were modified after the specified date are exported, including saved and committed scheduled tasks, manual tasks, table metadata, and data sources.
Export Scope and Export Object	All Objects: If you select this option, all objects in the current workspace are exported. In legacy Data Studio, the objects include scheduled tasks, manual tasks, resources, functions, table DDL statements (MaxCompute only), data sources, DataService Studio, ad hoc queries, components, and Data Quality rules. Selected Objects: If you select this option, you can select the objects that you want to fully export from the Export Object drop-down list below, such as scheduled tasks, resources, and DataService Studio.
Export Object Status	You can select the state of the objects to export: Saved: Exports the saved content of the export objects. Committed: Exports the committed content of the export objects.
Modified At	The incremental export is based on the last modification time.
Export Package Version and Format of Files in Export Package	Options include Standard Format, Apsara Stack (V3.12 and later), and Apsara Stack (V3.6.1 to V3.11). Note This parameter is supported only in legacy Data Studio. Data Studio uses a unified Spec format and does not require you to select an export version format.
Remarks	Enter a brief description of the export task.

Click Start Export.

Create a custom export task

On the DataWorks export page, click Create Export Task in the upper-right corner.

In the Create Export Task dialog box, configure the parameters.

Data Studio

Parameter	Description
Export Package Name	The export name can contain only letters, Chinese characters, digits, underscores (_), and periods (.).
Export Type	When you select Custom Export, you can freely select the files that you want to export, including saved and committed scheduled tasks, manual tasks, table metadata, and data sources.
Remarks	Enter a brief description of the export task.

Legacy Data Studio

Parameter	Description
Export Package Name	The export name can contain only letters, Chinese characters, digits, underscores (_), and periods (.).
Export Type	When you select Custom Export, you can freely select the files that you want to export, including saved and committed scheduled tasks, manual tasks, table metadata, and data sources.
Export Package Version and Format of Files in Export Package	Options include Standard Format, Apsara Stack (V3.12 and later), and Apsara Stack (V3.6.1 to V3.11). Note This parameter is supported only in legacy Data Studio. Data Studio uses a unified Spec format and does not require you to select an export version format.
Remarks	Enter a brief description of the export task.

Click Select Export Content.
On the Custom Export List page, filter the objects to export by Export Object type.

The Export Object types supported by Migration Assistant include: Table, Auto Triggered Task, Resource, Manually Triggered Task, Function, Data Quality, DataService Studio, Data Source, Component, and Ad Hoc Query. Among these, Data Quality, DataService Studio, and Ad Hoc Query are supported only in legacy Data Studio. Data Studio does not support exporting these three types of objects.
After you select the objects to export, click Add to Export Package.

You can also filter objects by Export Object, Object Type, Object Name, and other conditions, and then click Add Filter Results to Export Package to add all filtered results.
Click Start Export in the upper-right corner of the page.

Task status

On the Export Task List page, you can view the Export Task Name, Export Type, Task Creator, Status, Update Time, and Remarks of export tasks. You can perform different operations on tasks in different statuses:

Note

Data Studio introduces two new task statuses: Partially Succeeded and Canceled, and supports canceling export tasks that are in progress.

When the Status of an export task is Exported, you can:
- Click View Export Report to view the Basic Information, Overview, and Details of the export task.
- Click Download Export Package to download the export package to your local machine.
  
  Note
  The download link is valid for 30 days. We recommend that you download the package before the validity period ends. After the validity period ends, you need to re-export the project if you want to download the package.
- Clone Export Task (supported only in legacy Data Studio; Data Studio does not support cloning and requires you to create a new task):
  - Click Clone Export Task for a task whose Export Type is Full Export and has no blacklist configured. In the Clone Export Task dialog box, enter the Export Package Name and click Start Export.
  - Click Clone Export Task for a task whose Export Type is Full Export and has a blacklist configured. In the Clone Export Task dialog box, enter the Export Package Name and click Add to Blacklist.
    
    On the Select Blacklist page, select the objects that do not need to be exported, click Add to Blacklist, and then click Start Export in the upper-right corner of the page.
  - Click Clone Export Task for a task whose Export Type is Custom Export. In the Clone Export Task dialog box, enter the Export Package Name and click Select Export Content.
    
    On the Custom Export List page, select the objects to export, click Add to Export Package, and then click Start Export in the upper-right corner of the page.
When the Status of an export task is Export Failed, in addition to View Export Report and Download Export Package, you can click Retry to re-export the task (supported only in legacy Data Studio; Data Studio does not support retrying and requires you to create a new task).
When the Export Type of an export task is Custom Export and the Status is Editing, you can:
- Click Continue to Edit to go to the editing page and perform operations based on the export task type.
- Click View Export Package to view the Basic Information, Overview, and Details of the export task on the Export Package Details page.
- Click Delete. In the Delete dialog box, click OK.
When the Export Type of an export task is Full Export and the Status is Editing, in addition to Continue to Edit and Delete, you can click View Blacklist (supported only in legacy Data Studio). In the blacklist preview dialog box, confirm the blacklist entries and click Start Export or Close.

Next step

To migrate tasks across workspaces, Download Export Package to your local machine from the Export Task List page, and then create a DataWorks import task to import them to the destination workspace.

FAQ

If the exported task does not exist, go to the corresponding workspace to check whether the task was accidentally deleted or not saved and committed. If the task was deleted, go to Recycle bin to check whether the task exists and restore it.