Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
24 commits
Select commit Hold shift + click to select a range
263e1a5
first version for the draft
koletzilla Mar 18, 2026
a87c1d9
Improve index.html, fix links, fix lint
koletzilla Mar 19, 2026
601afc5
lint
koletzilla Mar 19, 2026
4310b97
Finish docs. Remove setup-guide to let that live in Fivetran side
koletzilla Mar 20, 2026
bcc8e6e
lint
koletzilla Mar 20, 2026
00576dc
Fix links
koletzilla Mar 23, 2026
de0d5ff
link
koletzilla Mar 23, 2026
98aeca6
Update docs/integrations/data-ingestion/etl-tools/fivetran/index.md
koletzilla Mar 24, 2026
e66bbb9
Update docs/integrations/data-ingestion/etl-tools/fivetran/reference.md
koletzilla Mar 24, 2026
cbaac14
Update docs/integrations/data-ingestion/etl-tools/fivetran/index.md
koletzilla Mar 24, 2026
793d0f2
Update docs/integrations/data-ingestion/etl-tools/fivetran/troublesho…
koletzilla Mar 24, 2026
2c933ba
Clarify date and type mappings
koletzilla Mar 26, 2026
b45fbcf
lint
koletzilla Mar 26, 2026
625b755
lint
koletzilla Mar 26, 2026
53bb2c7
Improve explanations for query optimizations changes.
koletzilla Mar 27, 2026
08bc7df
Remove: "Ensure cluster health during syncs". It's not applying anymo…
koletzilla Mar 27, 2026
cbac2ea
lint
koletzilla Mar 27, 2026
e615e18
lint
koletzilla Mar 27, 2026
1421ea2
Add more possible errors
koletzilla Mar 27, 2026
4b1403e
lint + message clarification
koletzilla Mar 27, 2026
49b7eae
Include in reference.md the explanation of the schema for the tables …
koletzilla Mar 31, 2026
b24030a
Update docs/integrations/data-ingestion/etl-tools/fivetran/reference.md
koletzilla Mar 31, 2026
d1b88c6
Update docs/integrations/data-ingestion/etl-tools/fivetran/troublesho…
koletzilla Mar 31, 2026
1b4186f
Update docs/integrations/data-ingestion/etl-tools/fivetran/troublesho…
koletzilla Mar 31, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 32 additions & 10 deletions docs/integrations/data-ingestion/etl-tools/fivetran/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,13 +2,14 @@
sidebar_label: 'Fivetran'
slug: /integrations/fivetran
sidebar_position: 2
description: 'You can transform and model your data in ClickHouse using dbt'
description: 'Use Fivetran to move data from any source into ClickHouse Cloud with automated schema creation, deduplication, and History Mode (SCD Type 2).'

Check notice on line 5 in docs/integrations/data-ingestion/etl-tools/fivetran/index.md

View workflow job for this annotation

GitHub Actions / vale

ClickHouse.Uppercase

Suggestion: Instead of uppercase for 'SCD', use lowercase or backticks (`) if possible. Otherwise, ask a Technical Writer to add this word or acronym to the rule's exception list.
title: 'Fivetran and ClickHouse Cloud'
doc_type: 'guide'
integration:
- support_level: 'core'
- category: 'data_ingestion'
keywords: ['fivetran', 'data movement', 'etl', 'clickhouse destination', 'automated data platform']
- website: 'https://github.com/ClickHouse/clickhouse-fivetran-destination'
keywords: ['fivetran', 'data movement', 'etl', 'clickhouse destination', 'automated data platform', 'history mode', 'SCD Type 2']
---

import ClickHouseSupportedBadge from '@theme/badges/ClickHouseSupported';
Expand All @@ -21,10 +22,12 @@

[Fivetran](https://www.fivetran.com) is the automated data movement platform moving data out of, into and across your cloud data platforms.

[ClickHouse Cloud](https://clickhouse.com/cloud) is supported as a [Fivetran destination](https://fivetran.com/docs/destinations/clickhouse), allowing users to load data from various sources into ClickHouse.
[ClickHouse Cloud](https://clickhouse.com/cloud) is supported as a [Fivetran destination](https://fivetran.com/docs/destinations/clickhouse), allowing you to load data from various sources into ClickHouse. Open Source ClickHouse version isn't supported as a destination.

The destination connector is developed and maintained together by ClickHouse and Fivetran. The source code is available on [GitHub](https://github.com/ClickHouse/clickhouse-fivetran-destination).

:::note
[ClickHouse Cloud destination](https://fivetran.com/docs/destinations/clickhouse) is currently in private preview, please contact ClickHouse support in the case of any problems.
[ClickHouse Cloud destination](https://fivetran.com/docs/destinations/clickhouse) is currently in **Beta** but we are working to make it generally available soon.

Check notice on line 30 in docs/integrations/data-ingestion/etl-tools/fivetran/index.md

View workflow job for this annotation

GitHub Actions / vale

ClickHouse.Contractions

Suggestion: Use 'we're' instead of 'we are'.

Check warning on line 30 in docs/integrations/data-ingestion/etl-tools/fivetran/index.md

View workflow job for this annotation

GitHub Actions / vale

ClickHouse.CurrentStatus

Remove 'currently'. The documentation reflects the current state of the product.
:::

<div class='vimeo-container'>
Expand All @@ -39,13 +42,32 @@
</iframe>
</div>

## ClickHouse Cloud destination {#clickhouse-cloud-destination}
## Key features {#key-features}
- **ClickHouse Cloud compatible**: use your ClickHouse Cloud database as a Fivetran destination.
- **SaaS deployment model**: fully managed by Fivetran, no need to manage your own infrastructure.
- **History Mode (SCD Type 2)**: preserves complete history of all record versions for point-in-time analysis and audit trails.
- **Configurable batch sizes**: You can adapt Fivetran to your particular use case by tuning write, select, mutation, and hard delete batch sizes via a JSON configuration file.

## Limitations {#limitations}
- Schema migrations are not supported yet, but we are working on it.
- Adding, removing, or modifying primary key columns is not supported.
- Custom ClickHouse settings on `CREATE TABLE` statements are not supported.
- Role-based grants are not fully supported. The connector's grants check only queries direct user grants. Use [direct grants](/integrations/fivetran/troubleshooting#role-based-grants) instead.

## Related pages {#related-pages}
- [Technical Reference](/integrations/fivetran/reference): type mappings, table engines, metadata columns and advanced configurations
- [Troubleshooting & Best Practices](/integrations/fivetran/troubleshooting): common errors and optimization tips and debugging queries
- [ClickHouse Fivetran destination on GitHub](https://github.com/ClickHouse/clickhouse-fivetran-destination)

## Setup guide {#setup-guide}
- If you're looking for configurations and general technical details, please refer to the [technical reference](/integrations/fivetran/reference).
- For a comprehensive guide, check the [setup guide](https://fivetran.com/docs/destinations/clickhouse/setup-guide) in the Fivetran documentation.

See the official documentation on the Fivetran website:
## Contact and support {#contact-us}

- [ClickHouse destination overview](https://fivetran.com/docs/destinations/clickhouse)
- [ClickHouse destination setup guide](https://fivetran.com/docs/destinations/clickhouse/setup-guide)
The ClickHouse Fivetran destination has a split ownership model:

## Contact us {#contact-us}
- **ClickHouse** develops and maintains the destination connector code.
- **Fivetran** hosts the connector and is responsible for data movement, pipeline scheduling, and source connectors.

If you have any questions, or if you have a feature request, please open a [support ticket](/about-us/support).
Both Fivetran and ClickHouse provide support for the Fivetran ClickHouse destination. For general inquiries, we recommend reaching out to Fivetran, as they are the experts on the Fivetran platform. For any ClickHouse-specific questions or issues, our support team is happy to help. Create a [support ticket](/about-us/support) to ask a question or report an issue.

Check notice on line 73 in docs/integrations/data-ingestion/etl-tools/fivetran/index.md

View workflow job for this annotation

GitHub Actions / vale

ClickHouse.Contractions

Suggestion: Use 'they're' instead of 'they are'.
Loading
Loading