> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/copying-transformations.md).

# Copying transformations

### Introduction

You can copy a set of transformations to another transformation mapping. You can then edit the transformations, if required.

Transformations must be copied from the same Gallagher Command Centre field type, (e.g. a set of Personal Data Field transformations, can only be copied from another Personal Data Field transformation mapping).

### Procedure

1. Select the map you wish to copy transformations into.
2. Click the **Copy from...** button. The Copy From Transformation window displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c9107453e4fd3fd392b1d40de8ae7b888ac40ec8%2Fcopytransformations.png?alt=media)
3. Click the drop-down arrow and select the map you wish to copy transformations from.
4. Click the **OK** button. The transformations are displayed in the Transformations grid.

   **Note:** If this transformation map already contains one or more transformations, a dialog box displays. Click **Yes** to clear the existing transformations. Click **No** to retain the existing transformations. The copied transformations will be added to the Transformations grid.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/copying-transformations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
