> 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/pdc-admin/pdc-10.2-admin/ldc-manage-data-sources-cp/pdc-export-data-connections.md).

# Export data connections

In Data Catalog, you can export data connection details of all connected data sources in CSV format to create a backup of all data connection settings and use it for migrating connections from one instance to another, ensuring consistency and reducing manual errors.

Perform the following steps to export data connection details in Data Catalog:

1. Click **Management** in the left navigation menu.

   The Manage Your Environment page opens.
2. In the **Resources** card, click **Data Sources**.

   The Manage Data Sources and Data Centers page opens.
3. Click **Export**.

   This downloads the file containing the data connection details in CSV format.

You have successfully exported the data connection details of all connected data sources in CSV format from Data Catalog.

You can also import the data connections into Data Catalog. See [Import data connections](/pdc-admin/pdc-10.2-admin/ldc-manage-data-sources-cp/pdc-import-data-connections.md) for more information.


---

# 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/pdc-admin/pdc-10.2-admin/ldc-manage-data-sources-cp/pdc-export-data-connections.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.