What you actually take with you when you leave a platform

The decision is made. The tool is too expensive, or it stopped fitting, and you are moving. Somebody says "we'll export the data first", everyone nods, and the assumption underneath — that an export contains your business — goes unexamined until the week after you cancel.

Exports are real and usually generous about data. They are silent about everything else.

What a full export actually contains

Mailchimp is a good example to look at, because it documents its account export in detail rather than in principle.

An account export gives you your audiences, split into separate files for subscribed, unsubscribed, transactional and cleaned contacts. It gives you your emails: a CSV of every regular campaign, plus a folder of HTML and TXT files with the content. It gives you reports — aggregate opens, clicks and unsubscribes, geographic data, and per-contact open and click activity. It gives you your templates as HTML. If you send SMS, it gives you the source of each contact, the time consent was given, the time it was revoked where applicable, the subscription status and the phone number.

That is a lot, and it is more than many people expect. If your worry was "will I lose my list", the answer is no.

The things that stay behind

The same documentation is equally specific about what an export does not include, and the list is instructive.

Deleted audiences. Deletion is permanent and the deleted data is not held for you. If somebody tidied up last year, that tidying is final.

Billing statements. Current and past invoices are not part of the export. If you need them for your accounts, get them before you close the account, not after.

Landing pages, website content and ad content. The pages you built inside the platform are not in the export.

Notice what that last one means. Anything you made inside the tool, as opposed to data you brought into it, is the most likely thing to be missing. Which is also, usually, the thing that took the most work.

And then the limit that catches people

One more line in that documentation is worth knowing before the day you need it: you are allowed one account export per 24-hour period, only one export can be generated at a time, and the same limit applies whether you use the interface or the API.

So the plan of "we'll pull everything on the last evening" does not survive a mistake. If the export you generate turns out to be missing something, or was generated with the wrong settings, your next attempt is tomorrow. Start the week before you cancel, not the night before.

The other half: how it was set up

Data is the part that exports. Configuration is the part that does not, and Shopify's documentation for duplicating a store puts it plainly: some kinds of store information can be moved with CSV files and a copy of the theme, while other kinds have to be entered manually in the admin.

The same page is worth reading for a second reason. If you want a backup of your store at all, it points you at an app from the App Store — the platform is not quietly keeping a copy for you to restore from.

Extend that to whatever you are leaving, and the questions become concrete. Your automations, segments, tags, custom fields, form logic, user permissions, email sequences and the conditions that decide who receives what — which of those come out in a file, and which exist only as screens somebody once filled in?

Usually: none of them come out. You are exporting the contents of the building, not the building.

Do this before you cancel, not after

Export while the account is still paid. Access usually ends with the subscription, and support has much less appetite for helping a former customer. Give yourself a week of overlap.

Open the export before you trust it. Not just check it downloaded — open the files, look for the fields you actually use, and confirm the ones that matter survived. Custom fields and tags are the usual casualties.

Screenshot the configuration. Unglamorous and effective. Every automation, every segment definition, every settings page. Ten minutes of screenshots replaces a week of trying to remember what the rules were.

Collect the invoices separately. They are frequently outside the export.

Write down what the tool was actually doing. Not the settings — the behaviour. "Anyone who books twice in a month gets the follow-up sequence" is the thing you need to rebuild. A CSV of contacts does not contain it.

Keep the old account alive for a month if the plan allows. Downgrading rather than deleting buys you the ability to check something you forgot, which you will.

What this costs, honestly

The reason platforms feel sticky is not the export button. It is that the export gives you a pile of data and nothing that explains how it was working, so "moving" is really "rebuilding, from a pile of data".

That is worth knowing in advance for two reasons. It changes the arithmetic — the cost of moving is the rebuild, not the transfer. And it changes what you should do while you are still happily using the tool, which is to keep some description of how your processes work somewhere outside the tool that runs them.

The businesses that move platforms easily are not the ones with better exports. They are the ones who could still explain their own process if the software vanished.

When it is worth planning properly

For one tool holding a contact list, the checklist above covers it.

It changes when several tools are joined together and the thing you would be moving is the arrangement rather than any single account — the booking system that feeds the CRM that triggers the invoices. Then the question of what leaves with you has a different answer for every link, and the honest cost of switching one of them is the cost of re-establishing every connection it sits in.

Working out what you would actually have to rebuild, before the renewal date forces the question, is one of the things a process audit produces: $299, three business days, and a written description of your process that does not live inside any vendor's account.

Sources

I read these pages in August 2026. Vendor documentation moves; check the vendor's own page before acting on it. These are two vendors' policies rather than an industry standard.

What an account export contains, what it excludes, and the one-per-24-hours limit: Mailchimp on exporting and backing up account data.

What moves with CSV files and what must be re-entered by hand, and who is responsible for backups: Shopify on backups and duplication.