DataWorks:Create and view import tasks

Limits

Edition limits

Each successful export task generates one package. If you reach your edition's package limit, upgrade your DataWorks edition — you cannot pay to bypass the limit.

Access control

Only an Alibaba Cloud account or a RAM user assigned the Workspace Administrator role can create import or export tasks. RAM users without this role can only view tasks.

Data Quality monitoring rules

• Alert configurations attached to monitoring rules are not exported with the package.

• If the table associated with an imported monitoring rule does not exist in the destination workspace, the rule does not appear on the Monitoring Rules page in Data Quality. Create the table and associate it with the rule after import — the rule then appears on the table's rule details page.

• If the package contains monitoring rules and auto triggered nodes, the monitoring rules can only be imported after the auto triggered nodes are imported, committed, and deployed. This ensures the auto triggered nodes can be associated with the correct monitoring rules.

• If the package contains monitoring rules but no auto triggered nodes, the monitoring rules can be imported, but the workspace does not contain information about the auto triggered nodes. If the package contains both monitoring rules and auto triggered nodes, the system imports, commits, and deploys the auto triggered nodes, updates the existing monitoring rules, and then associates the auto triggered nodes with the monitoring rules.

Other limits

• Import and export of tasks created in new-version Data Studio are not supported.

Prerequisites

Before you begin, make sure that you have:

• An export task created in Migration Assistant. For details, see Create and view export tasks.

• A package ready to import, based on your upload method:

  • Local upload: Download the package from the export task to your on-premises machine. See the Create a custom export task section.

  • OSS upload: Download the package, then upload it to Object Storage Service (OSS). See Simple upload.

Go to Migration Assistant

1. Log on to the DataWorks console. In the top navigation bar, select a region. In the left-side navigation pane, choose Data Development and O&M > Data Development. Select your workspace from the drop-down list and click Go to Data Development.

2. Click the icon in the upper-left corner, then choose All Products > More > Migration Assistant.

Create an import task

1. In the left-side navigation pane of Migration Assistant, choose Migration in DataWorks > DataWorks import.

2. On the Import Task List page, click Create Import Task in the upper-right corner.

3. In the Create Import Task dialog box, configure the following parameters.

   Parameter	Description
   Import Package Name	The name of the import task. Allowed characters: letters, digits, underscores (_), and periods (.).
   Upload Method	The source of the package: <br>• Local Upload: Click Upload File to upload from your on-premises machine. The system automatically verifies the package. Size limit: 30 MB. <br>• OSS Object: Enter the OSS endpoint in the OSS Endpoint field and click Check. Log on to the OSS console to get the package URL. After The verification succeeded appears, click Preview File to inspect the package.
   Remarks	An optional description for the import task.

   

4. Verify the package format and contents, then click OK. The Import Task Settings page opens.

5. Configure the import task. Computing Resource Mapping is required; all other sections are optional.

   • Computing Resource Mapping (required): Map each computing resource in the source workspace to a computing resource in the destination workspace. The Computing Resources in Destination Workspace column shows display names, not the project names used when the resources were created. To find display names, go to DataStudio, click the icon in the left-side navigation pane, and open the Computing Resource page. > Important: If the source workspace uses multiple computing resource types but the destination workspace has only one, the import task fails — the destination workspace lacks permission to create nodes for the missing resource types.

   • Resource Group Mapping (optional): Map resource groups between the source and destination workspaces so that imported nodes have the correct resource groups available.

   • Dependency Mapping (optional): Configure workspace mappings for related nodes. If any tasks to import reference the source workspace name in their code, input parameters, or output names, set New Project Name to the destination workspace name. The system replaces all occurrences of the source workspace name in the imported tasks.

   • Dry-run Property (optional): Mark specific nodes as dry-run nodes. Click Set to Dry-run in the Actions column for a single node, or select multiple nodes and click Batch Set to Dry-run. A dry-run node returns a success response without running or generating data — useful for configuring time properties on auto triggered nodes without triggering execution.

   • DataService Studio Settings (optional): Click Specify Mappings for DataService Studio Business Processes to configure DataService Studio mappings.

   • Committing Rule (optional): Configure committing rules for resources, functions, and tables, and set the Change Owner parameter.

     • If the destination workspace already contains an object with the same name as an object in the package, the incoming object cannot be committed.

     • If you select Not Modify for Change Owner and the node has no owner, you are automatically assigned as the owner after import.

   If you are migrating objects between workspaces in the same region under the same tenant, configuring computing resource mappings is sufficient.

   

6. In the lower-left corner, click Start Import.

7. In the Confirm dialog box, click OK.

View and manage import tasks

On the Import Task List page, available actions depend on the task status.

Task status	Available actions
Completed	Click View Import Report in the Actions column to open the report. The report includes Basic Information, Import Results, Details, and Import Settings sections.
Editing	Continue to Edit: Modify the task configuration. Preview: View task details in the Basic Information, Overview, and Details sections. Delete: Remove the task. Click OK in the confirmation dialog box.
Import Failed	Click Import Again in the Actions column. After the task completes, click Return to Import Task List in the Import Progress dialog box.

What's next

• To export objects from a workspace, see Create and view export tasks.

• To upload files to OSS, see Simple upload.