> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/pipeline-designer/managing-transformations-and-jobs/export-a-transformation-or-job.md).

# Export a transformation or job

Export transformations and jobs to save backup copies, migrate them to other systems, share them with other users, or use them in other tools. You can export a transformation as a  `.ktr` file or a job as a `.kjb` files.&#x20;

To export a transformation or job, complete the following steps:

1. Log into the Pentaho User Console.
2. Open **Pipeline Designer**:&#x20;

   * If you are using the **Modern Design**, in the menu on the left side of the page, click **Pipeline Designer**.&#x20;
   * If you are using the **Classic Design**, click **Switch to the Modern Design,** and then in the menu on the left side of the page, click **Pipeline Designer**.&#x20;

   **Pipeline Designer** opens with the **Quick Access** section expanded.
3. In the table at the bottom of the screen, select either the **Recently opened** or **Favorites** tab.
4. Open a transformation or job:&#x20;
   1. Search for or browse to the transformation or job, and then click **Open**.
   2. Click **Open files**, and then in the **Select File or Directory** dialog box, search for or browse to the transformation or job and click **Open**.
5. In the **Canvas Action** toolbar, click the **Export** icon. The transformation or job downloads to your default download folder as either a `.ktr` file or `.kjb` file, respectively.


---

# 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://docs.pentaho.com/pba/pipeline-designer/managing-transformations-and-jobs/export-a-transformation-or-job.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.
