> For the complete documentation index, see [llms.txt](https://fluid-crm.gitbook.io/fluid-crm-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fluid-crm.gitbook.io/fluid-crm-docs/data-and-imports/export-data.md). # Export data Your data is always accessible and never locked inside the product. *** ### Why export exists Fluid is built on the principle that you own your data. Exporting allows you to: * Create backups * Run external analysis or reporting * Share data with other systems * Move away from Fluid if needed There are no export limits or plan-based restrictions. *** ### Available exports You can export: * Contacts * Deals Each export generates a structured file you can store or reuse elsewhere. *** ### Export behavior Exports: * Reflect the current state of your data * Include all visible fields * Do not modify records in Fluid Exports are read-only actions. *** ### Common export use cases Exporting is commonly used for: * Financial or sales reporting * Compliance and audits * Data backups * Migration to another system Fluid does not watermark, restrict, or alter exported data. *** ### What exporting does not do Exporting does not: * Remove data from Fluid * Change deal status or history * Affect other users It simply creates a copy of your data. *** ### What to read next * **Import data** – moving data into Fluid * **API settings** – automated data syncs and integrations * **Contacts overview** – how contacts are structured --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://fluid-crm.gitbook.io/fluid-crm-docs/data-and-imports/export-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.