> ## Documentation Index
> Fetch the complete documentation index at: https://docs.condense.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Clone transform

The Clone Transform feature allows you to create a copy of an existing deployed transform within the same workspace. Instead of rebuilding transformation logic from scratch, you can duplicate an existing transform, modify its configuration if required, and deploy it as a separate transform.

The cloned transform copies the original transform configuration, including environment variables, technical settings, and deployment configuration, while remaining independent from the source transform.

## Benefits

The Clone Transform feature helps you:

* Reuse existing transformation logic without rebuilding it.
* Quickly create variations of existing transforms.
* Reduce development time and configuration effort.
* Test changes without modifying the original transform.
* Create environment-specific or use case-specific transform instances.

## Supported Resources

Currently, cloning is supported only for **deployed transforms** within the same workspace.

## Permissions

The following roles can clone deployed transforms:

| Role              | Permission  |
| :---------------- | :---------- |
| Environment Admin | Full Access |
| Maintainer        | Full Access |

## How It Works

1. Navigate to the **Transforms** page.
2. Select a deployed transform.
3. Click **Clone**.
4. Review the cloned configuration.
5. Rename the transform if required.
6. Save the cloned transform.
7. Deploy the transform when ready.

The cloned transform is created in a **Stopped** state and does not begin processing data until it is explicitly deployed.

## What Gets Cloned

When a transform is cloned, Condense copies:

* Transform configuration
* Environment variable mappings
* Technical configuration
* Transformation logic
* Deployment version (latest or selected historical version)

Sensitive values such as secrets remain securely managed and continue to be masked.

## Version Selection

While cloning a transform, you can choose to clone either:

* Latest deployed version
* A specific historical deployed version

This enables previously deployed transform versions to be reused without recreating the transformation.

## Naming Convention

By default, the cloned transform is assigned the following name:

```text theme={null}
<Original Transform Name>_Copy
```

The transform name can be modified before saving.

## Deployment

Saving the cloned transform creates a new transform configuration.

The transform is **not deployed automatically**.

To begin processing data:

1. Review the cloned configuration.
2. Update configuration values if required.
3. Click **Deploy**.

## Validation

The following validations are performed before the transform is created:

* Source transform must exist.
* Transform configuration must be valid.
* Transform name must be unique within the workspace.

## Common Errors

| Message          | Cause                                                       |
| :--------------- | :---------------------------------------------------------- |
| Cloning Failed   | Source transform no longer exists or cannot be accessed.    |
| Duplicate Name   | Another transform with the same name already exists.        |
| Clone Successful | Transform has been successfully created in a stopped state. |

## Best Practices

* Clone deployed transforms when creating similar processing pipelines.
* Rename cloned transforms using meaningful names.
* Review environment variables before deployment.
* Validate the transformation logic after cloning.
* Deploy the cloned transform only after verifying the configuration.