What happens to my data if I leave my CRM?
What happens to your CRM data when you leave depends on tenancy and the contract. Check the export format, the retention window, and whether attachments and history are included before you sign.
The short answer
- What happens to your data after you cancel a CRM depends on the tenancy model and the contract. On a shared platform you typically get an export window followed by deletion. On a single-tenant product you can often take the whole database.
- Check three things before signing up for any CRM, not after deciding to leave. The export format. The retention period after cancellation. Whether attachments and activity history are included in the export or left out.
- A CSV-only export commonly loses the relationships between objects. A contact linked to several deals and notes exports as separate files with reference IDs you have to rebuild by hand, not as one connected record.
- Retention after cancellation is set per vendor and often per contract. The specific number of days is usually in the terms of service or a data processing agreement, not the pricing page. Ask for it in days, in writing.
Why the answer is 'it depends' and not a fixed rule
Two things decide what happens to your data on the way out. How the vendor stores it, and what the contract says about cancellation. A multi-tenant vendor stores every customer's rows in one shared database. On cancellation it can offer an export of your rows and a retention window. It cannot hand you the database itself, because the database also holds other customers. A single-tenant vendor, where each customer has a dedicated database, has more room to offer a full dump. There is nothing else in that database to protect.
The contract is the second half. Even a vendor with generous technical capability can set a short retention window or a narrow export scope in its terms. Even a well-intentioned multi-tenant vendor can offer a wide export scope within what its architecture allows. Reading the actual policy, rather than assuming it from the marketing, is the only way to know before it matters.
What to expect by vendor pattern
| Vendor pattern | Export format | Where the retention window is written | What is commonly excluded |
|---|---|---|---|
| Multi-tenant SaaS, standard | CSV files per object type | The terms of service or the data processing agreement, not the pricing page; ask for the number in days | Attachments, activity history, custom object relationships are commonly excluded or degraded |
| Multi-tenant SaaS, enterprise contract | CSV plus a data processing agreement clause | The negotiated contract, which is where a longer window can be asked for | Usually broader than the standard plan, but still object-by-object rather than a full database |
| Single-tenant, dedicated database | Full database dump plus CSVs | The contract, though the technical constraint is weaker because nothing else lives in that database | Fewer exclusions, since the whole database is available; secrets and API keys are typically not included |
| SalesCrew | Full Postgres dump plus CSVs everywhere | Read-only access first, export available, deprovisioning after 90 days as a human-triggered step | Disclosure: SalesCrew is our product. Secrets stored in the Vault are not exported as plain values. |
Patterns described in general terms because retention windows are set per contract; SalesCrew figures are our own, September 2026.
What to ask before you sign, not after you decide to leave
Ask for the export format in specific terms. Is it a database dump, or a set of CSVs? If CSVs, which objects are included? A vendor that says "you can export your data" should be able to name whether that covers attachments, email threads, call logs and custom fields, or only the standard objects like contacts and deals.
Ask for the retention window in days, in writing, not as a general assurance. "We keep your data available for a while" is not the same as "90 days". The difference matters if you need time to negotiate a new tool or reconcile a migration before the old data disappears.
Disclosure: SalesCrew is our product. Its pattern on cancellation is read-only access first, then a full export available on request, with deprovisioning after 90 days carried out as a deliberate human decision rather than an automatic timer. Because each client runs in its own Supabase project, the export is the whole database, not a curated set of CSVs.
CSV-only export loses the relationships between objects
Questions
- How long do vendors usually keep my data after I cancel?
- Retention windows vary widely by vendor. They are usually stated in the terms of service or a data processing agreement, not the pricing page. Ask for the specific number in days before you sign, not after you decide to leave.
- Does 'export available' in a sales conversation guarantee anything?
- Not on its own. What matters is the written policy: the format, the objects included, and the retention window after cancellation. A verbal assurance in a sales call is worth confirming in the contract or the vendor's published terms.
- Is a database dump always better than a CSV export?
- For most purposes yes. A database dump preserves the relationships between records. CSVs typically flatten them into separate files. A CSV export is still useful for re-importing contacts into a new tool. It is less useful for rebuilding exactly how records were connected.