Migration Assistant quickly copies development assets across DataWorks versions, Alibaba Cloud accounts, regions, and workspaces. It supports three export methods — Full Export, Incremental Export, and Custom Export — for the following asset types:
-
Auto Triggered Task
-
Manually Triggered Task
-
Resource
-
Function
-
Data Source
-
Table Metadata
-
Ad Hoc Query
-
Component
Migration Assistant moves development assets only, not data. To migrate data between storage systems, use the batch synchronization feature instead.
Limitations
DataStudio (legacy version) support only
Migration Assistant imports and exports tasks from DataStudio (legacy version) only. Data Quality nodes, composite nodes, and data push nodes in DataStudio (legacy version) are not supported. If you need to migrate these node types, consider rebuilding them manually in the target workspace.
Edition-based quotas
All DataWorks editions support migrating jobs from open-source scheduling engines (Oozie, Azkaban, and Airflow). For DataWorks-to-DataWorks migrations using Migration Assistant, the following edition-specific limits apply:
|
Item |
Basic Edition |
Standard Edition |
Professional Edition |
Enterprise Edition |
|
|
Maximum number of packages that can be exported within a tenant Note
|
Cumulative quantity: 10 |
Cumulative quantity: 30 |
Cumulative quantity: 100 |
No upper limit |
|
|
Maximum size of a package that you want to import |
On-premises files |
30 M |
30 M |
30 M |
30 M |
|
OSS files |
Not supported |
Not supported |
No limit |
No limit |
|
|
Support for automatic commit and deployment during data import |
Not supported |
Not supported |
Supported |
Supported |
|
Permission requirements
Only workspace administrators and Alibaba Cloud account owners can perform import and export operations. Members with other roles can view the lists of import and export tasks but cannot perform the operations.
Browser requirements
Migration Assistant runs only on the desktop version of Chrome 69 or later.
Use cases
Back up jobs
Set Export Type to Full Export to back up task code and protect against data loss from accidental project deletion.
Copy business flows
Set Export Type to Custom Export to extract and replicate common business flows across workspaces.
Set up a staging environment
Set Export Type to Full Export or Custom Export to copy all task code into a new workspace, then switch the data source from production data to test data.
Hybrid cloud development
Set Export Type to Custom Export to move code from the public cloud to Apsara Stack for data development across both environments.
Isolate development and production environments
When development and production environments are on separate networks, export completed tasks from the development environment and import them into the production environment.