Skip to main content
The Clone Workspace feature allows you to create a complete copy of an existing workspace. Instead of manually recreating the workspace structure, users can duplicate an existing workspace along with its supported resources and configurations. Cloning a workspace is useful for creating development, testing, staging, customer-specific, or regional environments while preserving the original workspace. The cloned workspace is created independently, allowing changes to be made without affecting the source workspace.

​
Benefits

The Clone Workspace feature helps you:
  • Create new environments quickly.
  • Reuse an existing workspace configuration.
  • Reduce manual setup effort.
  • Accelerate onboarding for new customers or teams.
  • Maintain consistency across environments.

​
Supported Resources

Workspace cloning creates a new workspace and copies supported resources from the source workspace. Depending on the selected options, the cloned workspace can include:
  • Connectors
  • Transforms
  • Utilities
  • Kafka Topics
  • Environment Variables
  • Applications
  • Workspace settings
Each cloned resource is created independently within the new workspace.

​
Permissions

The following roles can clone workspaces:

​
How It Works

  1. Navigate to the Workspaces page.
  2. Select the workspace to clone.
  3. Click Clone Workspace.
  4. Enter a name for the new workspace.
  5. Select the resources to include.
  6. Review the configuration.
  7. Click Create Workspace.
The cloned workspace is created with all selected resources and is immediately available for further configuration and deployment.

​
Resources Included

Users can choose which resources should be copied into the new workspace. Supported resources include:
  • Connectors
  • Transforms
  • Utilities
  • Topics
  • Environment Variables
  • Applications
Only the selected resources are cloned.

​
Workspace Naming

By default, the cloned workspace is assigned the following name:
The workspace name can be modified before creation.

​
Validation

Before creating the workspace, Condense validates:
  • Workspace name uniqueness.
  • User permissions.
  • Availability of the source workspace.
  • Resource compatibility.

​
Common Errors

​
Best Practices

  • Use workspace cloning to create development, staging, or production environments.
  • Rename the cloned workspace using a meaningful name before creation.
  • Review environment variables after cloning.
  • Verify connectors, transforms, and utilities before deployment.
  • Remove unused resources from cloned workspaces to keep environments organized.