Cross-workspace cloning is retiring and merging into Deploy Center, which provides a unified place to manage cross-workspace deployments. DataWorks automatically migrates your historical data — deployment environments and clone packages — based on the default logic described on this page. Review these details to determine whether any manual adjustments are needed after migration.
For the retirement timeline, see DataWorks Cross-workspace Cloning Deprecation Announcement.
How migration works
The migration covers two types of data:
-
Deployment environments — created automatically in Deploy Center based on your existing compute engine mappings in Cross-workspace cloning
-
Deployment packages — all historical clone packages from the Clone Package List are migrated to
Default deployment environment migration logic
DataWorks automatically creates a deployment environment for each source-destination workspace pair that has historical clone packages. The generated environment reuses your existing compute engine mappings from Cross-workspace cloning. You can use it directly in Deploy Center or modify it as needed.
DataWorks does not create or overwrite a deployment environment if one already exists for the same source and destination workspaces.
Conditions for environment generation:
-
A deployment environment is generated only if the source workspace has historical clone packages that were deployed to a destination workspace.
-
If a source workspace has no historical clone packages, no deployment environment is generated.
-
If a source workspace maps to multiple destination workspaces, multiple deployment environments may be generated.
Generated environment parameters:
| Parameter | Value |
|---|---|
| Environment name | Cross-workspace cloning migration_${SourceWorkspaceName}_to_${DestinationWorkspaceName} |
| Deployment type | Cross-workspace Deployment |
| Destination workspace | The original destination workspace from Cross-workspace cloning |
| Deployment object owner | Default |
| Compute engine instance mappings | Reuses mappings from the original compute engine mappings settings. If no mappings were configured, this setting is ignored. |
| Resource group mappings | Only shared resource groups for scheduling and public resource groups for DataService are mapped. All other resource group mappings are not carried over. |
| Dependency mappings | For DataWorks projects: uses the mappings defined in the target deployment environment. For MaxCompute projects: reuses configured engine mappings and ignores all others. Only MaxCompute is supported — E-MapReduce (EMR) and Hologres are not yet supported. |
| Data source mappings | Reuses mappings from the original compute engine mappings settings. If no mappings were configured, this setting is ignored. |
| Parameter mappings | Empty by default |
| Remarks | This deployment environment was automatically migrated from Cross-workspace cloning. Source: ${source_workspace_display_name} (${source_workspace_name}) to Destination: ${destination_workspace_display_name} (${destination_workspace_name}) |
What is not automatically migrated:
The following settings require manual configuration in Deploy Center after migration:
-
Resource group mappings other than shared resource groups for scheduling and public resource groups for DataService
-
Parameter mappings (empty by default)
-
Dependency mappings for E-MapReduce (EMR) and Hologres engines
Default clone package migration logic
All historical clone packages from the Clone Package List to the . The table below shows how each field maps from the clone package to the deployment package.
| Parameter | Clone package | Deployment package |
|---|---|---|
| Package ID | Clone package ID | A new deployment package ID is generated |
| Package name | Clone package name | Reuses the clone package name |
| Deployment environment | Not applicable | Cross-workspace cloning migration_${SourceWorkspaceName}_to_${DestinationWorkspaceName} |
| Deployment type | Not applicable | Cross-workspace Deployment |
| Applicant | Applicant | Reuses the applicant from the clone package |
| Application time | Application time | Reuses the application time from the clone package |
| Published By | Published By | Reuses the publisher from the clone package |
| Deployment time | Cloning time | Reuses the cloning time |
| Progress | Progress | Not applicable |
| Status | Clone status | Deployment status |
After migration
After migration, manage all packages — deploy, redeploy, or cancel deployments — directly in Deploy Center according to its rules.
Check the following after migration completes:
-
Verify that the automatically generated deployment environments match your intended source-destination workspace pairs.
-
Reconfigure any resource group mappings (other than shared scheduling groups and DataService public groups) that were not carried over.
-
Add parameter mappings if your workflows require them — these are empty by default.
-
If your pipelines use E-MapReduce (EMR) or Hologres engines, reconfigure the dependency mappings manually, as these are not supported in automatic migration.