> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-for-agents/cli/command-reference/transfer.md).

# transfer

Transfer data between warehouses. Waits for completion by default.

```bash
carto transfer --source-connection <n> --dest-connection <n> --source-table <t> --dest-table <t>
carto transfer status <jobId>                   # Fetch status of an async transfer job
```

{% hint style="info" %}
Transfer requires the DuckDB import engine to be enabled for your account.
{% endhint %}

## Options

| Option                       | Description                                                                                                                      |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `--source-connection <name>` | (Required) Source connection name.                                                                                               |
| `--dest-connection <name>`   | (Required) Destination connection name.                                                                                          |
| `--source-table <fqn>`       | (Required) Source table.                                                                                                         |
| `--dest-table <fqn>`         | (Required) Destination table.                                                                                                    |
| `--geography`                | Use geography type for spatial data.                                                                                             |
| `--overwrite`                | Replace the destination table if it already exists. The replacement is staged, so the existing table survives a failed transfer. |
| `--target-srid <epsg>`       | Reproject geometry to this EPSG code at the destination. Fails if the destination cannot store it.                               |
| `--preserve-source-crs`      | Keep the source CRS instead of applying the destination's convention. Fails if the destination cannot store it.                  |
| `--async`                    | Return job ID immediately without waiting.                                                                                       |

`--target-srid` and `--preserve-source-crs` are mutually exclusive.

## Examples

```bash
# Transfer from BigQuery to Snowflake
carto transfer \
  --source-connection bigquery-prod \
  --dest-connection snowflake-analytics \
  --source-table project.dataset.customers \
  --dest-table db.schema.customers

# With geography support, async
carto transfer \
  --source-connection bq-prod \
  --dest-connection postgres-dev \
  --source-table project.dataset.geo_data \
  --dest-table public.geo_data \
  --geography --async

# Overwrite the destination and reproject to EPSG:4326
carto transfer \
  --source-connection bq-prod \
  --dest-connection snowflake-analytics \
  --source-table project.dataset.parcels \
  --dest-table db.schema.parcels \
  --overwrite --target-srid 4326

# Poll an async transfer
carto transfer status <jobId>
```


---

# 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.carto.com/carto-for-agents/cli/command-reference/transfer.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.