> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/primer-support-legacy/learn-more/upload-people-and-companies-to-primer-via-s3-beta/export-data-from-fivetran-to-primer-via-s3.md).

# Export Data from Fivetran to Primer via S3

Fivetran Activations can generate recurring CSV snapshots using its Amazon S3 destination.

To maintain one current dataset in Primer, configure the sync with:

* **Replace** as the sync behavior
* A fixed filename
* CSV format
* A comma delimiter
* A header row
* No PGP encryption
* The complete source dataset on every run

> **Use Replace only**
>
> Do not use **Update or Create**. Fivetran adds timestamps to files generated by incremental Update or Create runs. Because Primer uses each filename as a dataset name, this would create multiple datasets instead of updating one dataset.

Direct integration with Primer’s S3 access points is subject to compatibility validation. Fivetran’s documentation describes standard S3 bucket connections but does not explicitly document S3 access-point aliases.

Fivetran also requires an external ID and role permissions configured by Primer. Contact your Primer representative before creating the destination. Primer will provide the access-point alias, AWS Region, role ARN, upload path, and validated authentication instructions.

For additional information, see:

* [Fivetran Activations](https://fivetran.com/docs/activations)
* [Fivetran Amazon S3 destination](https://fivetran.com/docs/activations/destinations/available-destinations/s3)
* [Fivetran Activations syncs](https://fivetran.com/docs/activations/syncs/overview)
* [Amazon S3 access-point aliases](https://docs.aws.amazon.com/AmazonS3/latest/userguide/access-points-naming.html)


---

# 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://support.sayprimer.com/primer/primer-support-legacy/learn-more/upload-people-and-companies-to-primer-via-s3-beta/export-data-from-fivetran-to-primer-via-s3.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.