Every SaaS tool has an export button. Almost none of them export everything, and the parts they quietly drop are usually the parts that took you years to accumulate. This guide covers where the export lives in the tools small businesses most often leave, and — more importantly — what each one loses on the way out.
Do this before you decide to leave, not after. An export you can't reassemble is a fact worth knowing while you still have a working account.
Export while your subscription is active. Most vendors restrict or delete data shortly after cancellation — commonly 30 to 90 days, sometimes immediately on downgrade. Never cancel first and export second.
What exports lose, in general
Before the tool-by-tool detail, these are the five things that go missing almost everywhere. Check for each one whatever you're leaving.
- Attachments and files. CSV exports reference file names or URLs that stop working when the account closes. Files are nearly always a separate export, and often only via API.
- Relationships between records. A flat CSV per table loses which contact belongs to which company unless internal IDs are included in both files. Check for an ID column; without it, you have lists, not a database.
- History and audit trail. Comments, status changes and "who edited what when" are rarely exportable. If you have compliance reasons to keep them, verify this early.
- Automations and configuration. Your workflows, templates and permission rules are the product's configuration, not your data. They almost never export, and rebuilding them is real work.
- Formatting and rich text. Notes with formatting, embedded images or mentions come out as HTML fragments or plain text, depending on the vendor's mood.
Tool by tool
Monday.com
Where: per-board, via the board menu → Export to Excel. Account-level exports are available on higher plans.
What you lose: updates and comments on items, file attachments, automations, and board structure. Each board exports separately, so cross-board links become dead text. Budget time for a board-by-board pass rather than one big download.
Airtable
Where: per-table CSV from the view menu; the API gives much better results.
What you lose: the CSV export gives you what the view shows — filtered and hidden fields are silently excluded. Linked records come out as human-readable names rather than IDs, which breaks the moment two records share a name. Attachments export as URLs that expire. If the base matters, use the API and pull record IDs.
QuickBooks (and its add-ons)
Where: reports export to CSV/Excel individually; lists (customers, vendors, items) export separately. Desktop offers a fuller company-file export than Online.
What you lose: there's no single "everything" export from Online. Transaction detail, attachments and the audit log come out separately if at all. The paid add-ons bolted onto QuickBooks are usually worse: many have no export at all. Check the add-on before you check QuickBooks.
HubSpot / Salesforce
Where: object-by-object export from the settings area; Salesforce also offers a weekly full data export.
What you lose: the standard export covers records well but treats activity history, email threads and file attachments separately, and some of it needs API access. Custom field definitions export as values without their configuration, so you'll be rebuilding picklists by hand. Always take the IDs — without them, re-linking contacts to companies is guesswork.
Scheduling, dispatch and field-service tools
Where: varies enormously; usually a reports section rather than a settings one.
What you lose: this category is the worst offender. Photos attached to jobs, signatures, GPS/timestamp records and customer communication history are frequently unexportable — and they're often the records you're legally required to keep. Test this specifically.
Toast, Square and POS add-ons
Where: sales and transaction reports export readily; menu, catalogue and customer data are separate.
What you lose: item-level modifiers, historical menu versions and loyalty balances are the usual casualties. Sales totals come out fine, which makes the export look more complete than it is.
A procedure that actually works
- Export everything once, today, while you're a customer. Even if you're not leaving. It's a free backup and an honest test of how locked in you are.
- Open the files. Not "check they downloaded" — open them and look for the ID columns, the attachment references and the fields you care about.
- Try to answer one real question using only the export. "Which customers bought twice last year?" If you can't, the export is incomplete.
- Export the files separately, via API if that's the only way. This is usually the largest hidden task in a migration.
- Screenshot the configuration — automations, permissions, templates. It doesn't export, and you'll need to rebuild it from something.
- Run both systems in parallel for at least one full billing or reporting cycle before cancelling. Month-end is when you find out what's missing.
The point of doing this early
A tool you can leave is a tool you can negotiate with. A tool you can't leave sets its own prices, and the ones that make exports awkward generally know exactly what they're doing.
Whatever replaces it should be judged the same way. Anything I build keeps your data in a standard SQL database with a schema you can read, and exports that include the IDs — because ownership that you can't verify isn't ownership. If you're weighing that up, the build-vs-buy checklist scores exportability for exactly this reason.