What Happens to Your Data When You Leave

Software evaluations are almost entirely about arrival. Can it do this, does it integrate with that, how long is the setup. Departure barely comes up, which is odd, because every platform you have ever used you will eventually stop using, and the terms of that departure were fixed on the day you signed up.

This is not a pessimistic way to buy software. It is the same reasoning that makes people read a lease before moving in.

Three different questions that get confused

"Can I get my data out" is really three questions with different answers.

Can I export it? Almost always yes, in some form. The form is where the difficulty hides.

Can I export it in a shape that another system can read? Often no. A PDF of your invoices is an export. It is not data. A CSV per screen, with the relationships between screens expressed only by the fact that they were next to each other in the interface, is barely better.

Can I export the parts that were generated by using the product? This is the one that catches people. Your customer list is obviously yours. The message history, the activity timeline, the notes people wrote, the audit trail — these are also records of your business, and they are the parts most likely to be unavailable or to come out in a format that only made sense inside the product.

The legal framing is useful here even outside its jurisdiction, because it names the standard well: the right to receive personal data "in a structured, commonly used and machine-readable format and have the right to transmit those data to another controller without hindrance" [1]. Three requirements, all load-bearing. Structured rules out a screenshot. Machine-readable rules out a PDF. Without hindrance rules out a support ticket, a fee, and a two-week wait.

Held to that standard, our own answer is a JSON export of all your records, which is the shape a receiving system can actually read.

The questions to ask before you sign

What exactly is in the export, field by field? Not "you can export your data" — an inventory. If a vendor cannot produce one, that is the answer.

Can I run it myself, today, without asking anyone? An export that requires a support request is an export that is available at someone else's convenience, which is precisely not what you need on the day relations have soured.

How long do you keep it after I leave, and when is it actually gone? Vagueness here is common and worth pressing on. Deletion is rarely instantaneous, and it should not be — an accidental deletion needs a window in which it can be undone, and there are usually legal reasons to hold some records briefly. What matters is that the schedule is stated. Ours is a 30-day recoverable window, then 60-day retention for legal and forensic needs, then hard-purge [2]. You do not have to like a particular schedule; you do need one to exist, in writing.

What happens the moment I stop paying? There is a meaningful difference between an account that becomes read-only and one that becomes inaccessible. If cancellation immediately locks you out, then your notice period is also your entire migration window. Cancellation taking effect at the end of the current billing period [3] is the ordinary and reasonable version of this, and it is worth confirming rather than assuming.

Lock-in is not usually deliberate

It is tempting to read all of this as vendors trapping customers on purpose. Occasionally true, mostly not.

The common cause is that export is a feature nobody demands during a sale, so it gets built late, thinly, and by whoever is free. It handles the main records because those were easy and skips the relationships because those were hard. It is not malice; it is prioritisation, and it produces the same outcome.

The second cause is genuinely difficult. Some of what a platform holds only makes sense inside it. A workflow you configured is not a portable artefact — nothing else has that concept. Custom fields, permissions, automations: these are shaped by the product, and no export format will carry them to a competitor. That is a real cost of adopting any system, and it is worth counting honestly rather than pretending it away.

What you can insist on is that the facts are portable even when the configuration is not. Customers, conversations, transactions, documents, and history are records of your business that happened to be stored somewhere. The automation that filed them is the platform's. The records are yours.

The attachments problem

One category deserves separate mention because it is almost always handled badly: files.

Contracts, signed quotes, identity documents, photographs of completed work — these are often the records with the longest legal life and the least portable storage. A typical export gives you a spreadsheet of records in which the file column contains a link, and the link points back into the platform you are leaving. On the day the account closes, every one of those links becomes a dead end, and the spreadsheet you carefully exported now documents the existence of documents you no longer have.

Ask specifically whether files come out as files, in a folder, with names that let you match them back to the records they belong to. It is a narrow question and the answer is rarely in any documentation.

The test that takes an hour

Do not evaluate this from documentation. Run the export during the trial, on real data, before you have committed anything.

Open the file. Look for the customer you know has a long history and check whether the history came with them. Look for a note someone wrote and see whether the author and date survived. Try to reconstruct one relationship end to end using only what is in the file.

Whatever you find is what you will get on the worst possible day, when you have less time and less goodwill. An hour spent on it during a trial is the cheapest hour in the whole evaluation, and it tells you something no feature list will: whether the company you are about to depend on treats your data as yours.