> 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/import-data.md). # Import data Fluid is designed to make switching fast while keeping your pipeline structure intact. *** ### Why import exists Most CRMs lock your data behind complex exports and fragile imports. Fluid treats importing as a first-class workflow so you can: * Move from another CRM without rebuilding everything manually * Start working immediately with real deals * Keep pipeline logic consistent from day one Imports are explicit, controlled and predictable. ### Supported import formats Fluid supports importing from: * CSV * XLS * XLSX A downloadable template is provided to ensure the correct format. You can import: * Deals (with auto-linked contacts and companies) * Contacts only Up to 10,000 rows per import. Split larger files into multiple imports. ### Import workflow The import process is the same for deals and contacts, with one extra step for deals. Step 1: Open the import page and choose what you want to import * Select Deals or Contacts * The correct template downloads automatically when you click Download import template CSV Step 2: Map your data in the sheet * Open the downloaded template in Excel or Google Sheets * Paste your existing data into the matching columns * Save the file as CSV, XLS or XLSX Step 3: Upload your file * Click Upload or drag and drop the file directly into the import area * Fluid validates the file before processing Step 4: Configure the import * **For deals:** select the target pipeline, then map each stage in your file to a stage in that pipeline, then confirm field mappings * **For contacts:** confirm field mappings only Step 5: Review the preview * Fluid shows you exactly what will be imported * Verify the row count, deal values and stage placement match expectations Step 6: Run the import * Click Import to commit the data * Deals are placed in the selected stages * Contacts and companies are auto-created and linked ### Undo an import If you made a mistake during importing, you do not need to manually delete anything. * Go back to the Import page * Undo is available for 48 hours after the import This rolls back the entire batch in one action and lets you fix the issue and re-import cleanly. ### AI-assisted field mapping During import, Fluid helps map your file's columns to Fluid fields automatically. This reduces manual setup when migrating from another CRM and lowers the risk of misaligned data. You always review and confirm mappings before the import runs. ### Pipeline and stage matching When importing deals, Fluid reads every unique stage name in your file and asks you to map each one to a stage in your pipeline. If your stage names already match, the mapping is filled in for you and you confirm it. Example: * Old CRM: Lead, Meeting, Proposal * Fluid pipeline: Lead, Meeting, Proposal If the names differ, pick the matching Fluid stage from the dropdown. You can also set a stage to Skip and those deals are left out. Nothing is created until you confirm the mapping. ### What importing does not do Importing does not: * Change existing pipeline configuration * Modify deal probabilities * Merge duplicate records automatically * Sync continuously with another CRM Imports are one-time actions you explicitly control. For ongoing sync from external tools, use the API and webhooks. ### Common import issues A few things to check if an import fails or looks off: * Column headers do not have to match the template. Fluid suggests a mapping for each column and you adjust anything that looks off. The template just makes the suggestions more accurate. * Deal values must be numbers, not text. Remove currency symbols and thousand separators. * Dates should be in YYYY-MM-DD format. Excel sometimes converts dates to formats Fluid does not recognize. * Contacts are matched by email. A typo in the email field breaks the contact link. ### Migration tips * For Pipedrive users, export "All deals" not just "open deals" so your historical data comes too * For HubSpot users, contact emails are the linking field. Make sure they export cleanly without quotes or extra spaces * For Google Sheets users, the cleanest approach is to start with Fluid's template and paste your data column by column rather than reformatting your existing sheet ### What to read next * Pipeline customization, configuring stages before importing * Customize data fields, aligning fields for clean imports * Export data, downloading your data at any time --- # 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/import-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.