All Products
Search

This Product

    DataWorks:Create and view export tasks

    Document Center

    DataWorks:Create and view export tasks

    Last Updated:Mar 27, 2026

    Migration Assistant lets you export data objects from a DataWorks workspace — including auto triggered nodes, manually triggered nodes, resources, functions, tables, data sources, script templates, ad hoc queries, data services, and data quality monitoring rules.

    Common use cases include:

    • Workspace backup: Export all node code to create a workspace snapshot.

    • Environment cloning: Clone a workspace for use as a test environment.

    • Cross-workspace migration: Extract a workflow and import it into another workspace.

    • Dev-to-prod promotion: Export nodes from the development environment and import them into the production environment for deployment.

    Prerequisites

    Before you begin, ensure that you have:

    • An Alibaba Cloud account or a RAM user with the Workspace Administrator role assigned

    RAM users without the Workspace Administrator role can only view export and import tasks, not create them.

    Choose an export mode

    Migration Assistant supports three export modes. Choose based on what you need to export:

    Mode What it exports Blacklist support Typical use case
    Full export All or selected object types in the workspace, at the latest version Yes Workspace backup, environment cloning
    Incremental export Objects modified after a specific date No Syncing changes since the last export
    Custom export Individually selected data objects N/A Extracting a specific workflow or node set
    Tasks created in new-version Data Studio cannot be exported or imported.

    Limitations

    Item Basic Edition Standard Edition Professional Edition Enterprise Edition
    Max packages per tenant (cumulative) 10 30 100 No limit
    Max import package size — on-premises — 30 MB 30 MB 30 MB
    Max import package size — OSS Not supported Not supported No limit No limit
    Auto commit and deploy during import Not supported Not supported Supported Supported

    Each successful export creates one package. If you reach the package limit for your edition, upgrade DataWorks — you cannot pay to export additional packages.

    Data Quality export constraints

    When exporting or importing Data Quality monitoring rules:

    • Alert configurations linked to monitoring rules are not exported.

    • If the associated table doesn't exist in the destination workspace, the imported rule won't appear on the Monitoring Rules page. Create the table and associate it with the rule after import.

    • If the package contains both monitoring rules and auto triggered nodes, the system imports, commits, and deploys the nodes first, then updates and associates the monitoring rules.

    • If the package contains monitoring rules but no auto triggered nodes, the rules are imported without node associations.

    Go to Migration Assistant

    1. Log on to the DataWorks console. In the top navigation bar, select the 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 and choose All Products > More > Migration Assistant.

    Create a full export task

    Use a full export task to export all or selected object types at their latest saved, committed, or deployed versions.

    1. On the Export Tasks page, click Create Export Task.

    2. In the Create Export Task dialog box, set Type to Full export and configure the following parameters:

      Parameter Description
      Name The task name. Allowed characters: letters, digits, underscores (_), and periods (.).
      Export scope All Objects: exports auto triggered nodes, manually triggered nodes, resources, functions, table DDL statements, data sources, data services, ad hoc queries, script templates, and monitoring rules. Selected Objects: choose specific object types from the Export Object drop-down list.
      Export object status Save: exports saved objects. Submit: exports committed objects.
      Blacklist Select Add to Blacklist to exclude specific nodes and resources from the export.
      Export version The DataWorks version that determines the export format. Options: Standard, Private Cloud (>=V3.12), Private Cloud (V3.6.1–V3.1.1). Check your workspace version before selecting.
      Remarks An optional description of the task.

      导出

    3. To exclude objects from the export, select Add to Blacklist and click OK. Then:

      1. On the Set Blacklist page, select the objects to exclude.

      2. Click Add Selected to Blacklist.

      3. Click Export in the upper-right corner, then click OK in the confirmation dialog.

    4. If you don't need a blacklist, click Export directly, then click OK.

    5. In the Export Progress dialog box, monitor the task. After it completes, click Back to Export Tasks.

    Create an incremental export task

    Use an incremental export task to export objects modified after a specific date. The data objects that you want to export must be saved, committed, or deployed.

    Incremental export tasks do not support blacklists.

    1. On the Export Tasks page, click Create Export Task.

    2. In the Create Export Task dialog box, set Type to Incremental and configure the following parameters:

      Parameter Description
      Name The task name. Allowed characters: letters, digits, underscores (_), and periods (.).
      Export scope All Objects or Selected Objects. See full export parameter descriptions for details.
      Export object status Save (saved objects) or Submit (committed objects).
      Modified at The cutoff date. Objects modified after this date are treated as incremental data objects.
      Export version The DataWorks version. Options: Standard, Private Cloud (>=V3.12), Private Cloud (V3.6.1–V3.1.1).
      Remarks An optional description of the task.

      增量导出

    3. Click Export, then click OK.

    Create a custom export task

    Use a custom export task to select individual data objects to export — for example, to extract a specific workflow or a set of nodes.

    1. On the Export Tasks page, click Create Export Task.

    2. In the Create Export Task dialog box, set Type to Custom and configure the following parameters:

      Parameter Description
      Name The task name. Allowed characters: letters, digits, underscores (_), and periods (.).
      Export version The DataWorks version. Options: Standard, Private Cloud (>=V3.12), Private Cloud (V3.6.1–V3.1.1).
      Remarks An optional description of the task.

      自选导出

    3. Click Select Export Objects, then click OK.

    4. On the Export Objects page, select an object type from the Export Object drop-down list. Supported types: Table, Periodic tasks, Resources, Manual tasks, Function, Data Quality, DATA_SERVICE, Data source, Components, Temporary query.

      导出对象

    5. Select the objects to export and click Add Selected to Export Package. Alternatively, use the Export Object, Object Type, and Object Name filters to search, then click Add All to Export Package.

    6. Click Export in the upper-right corner, then click OK in the confirmation dialog.

    View and manage export tasks

    The Export Tasks page lists all tasks with their Name, Type, Created By, Status, Updated At, and Remarks.

    The available actions depend on the task status:

    When the status is Successful

    • View Export Report: Click View Export Report to see task details in the Basic Information, Overview, and Details sections.

      查看导出报告

    • Download Export Package: Click Download Export Package to save the package locally.

      The download link is valid for 30 days. If it expires, re-run the export task to generate a new package.

    • Clone Export Task: Create a new export task based on an existing one. The steps vary by task type:

      • Full export (no blacklist): Click Clone Export Task, enter a name in the Export Package Name field, and click Start Export.

      • Full export (with blacklist): Click Clone Export Task, enter a name, and click Add to Blacklist. On the Set Blacklist page, select objects to exclude, click Add Selected to Blacklist, then click Export.

      • Custom export: Click Clone Export Task, enter a name, and click Select Export Content. On the Export Objects page, select objects, click Add Selected to Export Package, then click Export.

    When the status is Export failed

    Click Re-export in the Actions column to retry. You can also click View Export Package or Download Export Package if a partial package was created.

    When the status is Editing (custom export)

    • Continue to Edit: Click Continue to Edit to return to the Custom Export List page and modify your selection.

    • View Export Package: Click View Export Package to review the Basic Information, Overview, and Details of the current package.

    • Delete: Click Delete, then click OK to remove the task.

    When the status is Editing (full export)

    Click Continue to Edit to resume configuration, View Blacklist to review or update the blacklist and start the export, or Delete to remove the task.

    What's next

    After exporting, download the package and create an import task to migrate the data objects to the destination workspace.

    FAQ

    An auto triggered node is missing after export. What should I do?

    Check whether the node was accidentally deleted or the export wasn't saved or committed. If deleted, go to the recycle bin to find and restore it.