Who keeps your data when you cancel a software subscription?

A building materials distributor switches sales software after six years. The vendor sends an export: a file with current customer records and open orders. Six years of call history, follow-ups and notes left by the sales team are nowhere in that file. They stay in the tool that just got switched off.

What the contract promises, and what it leaves out#

Most SaaS contracts mention a right to export data "in a standard format", often in a short clause, far from the pricing terms. Three things are almost always missing:

• The scope of the export. Active records, yes. Change history, attachments, internal comments, activity logs: rarely.
• The deadline. Some contracts give 30 days after cancellation to request the export, after which the data is deleted.
• The format. A CSV of raw columns is not the same thing as a dataset you can load into another tool without retyping everything.

A rented piece of software gives you access to a screen, not to what you built inside it. The difference only shows up the day you leave, never before.

What disappears in practice, even with an export#

For a distributor of several dozen people who built their follow-up routines, quote templates and discount rules inside a rented tool over the years, this table comes down to one simple fact: anything that is not a raw record stays with the vendor. It is the same pattern as taking stock of your software subscriptions: you find out what you have accumulated the day you need to add it up, or the day you need to leave it.

The method: three checks, now#

No need to wait for a cancellation to run them.

1. Re-read the export clause of your current contract, before it becomes an urgent matter. Look for the word "export", the deadline after cancellation, and the format promised.
2. Ask for a test export, even with no intention to leave. Many vendors allow it on request. Open the file you receive and compare it with what the screen shows.
3. List what should never depend on a single rented tool: customer history, the templates that save time, the business rules. Those are what needs to be portable, not the fields you could retype in an hour.

When I go on holiday, I'm the one who handles all the paperwork.

That sentence usually describes a person. It applies to tools too: when a subscription ends, whatever the company built inside it ends with it, unless someone checked beforehand.

What changes with an application you own#

An application built for the company runs on a database that belongs to you, from day one. In practice:

• The database is readable at any time, with no request and no deadline: you can pull out whatever you need, whenever you need it.
• The history of exchanges, changes and attachments is part of the same database as the records, not a separate module that can be switched off.
• Changing provider, the day you decide to, does not mean starting over: the database keeps existing, with everything it holds.

This is not an argument against off-the-shelf software, which works well for plenty of needs. It is a question worth asking before you build six years of customer history on top of one: who keeps what, the day it stops. An application built around the way you work answers that question before it comes up, and its price is reasoned the same way as any custom business application.

What not to do#

Don't wait for the notice period to read the contract: by then, the balance of power has shifted, and the vendor has no reason to make the export easy. Don't settle for a demo export provided by the vendor without opening it: a file nobody looks at proves nothing.

Who keeps your data: the key takeaways#

A software subscription grants a right to use, not ownership of what you build inside it. The gap between the two costs nothing while everything runs smoothly, and costs the entire history the day you leave.

The check takes an hour: re-read the export clause, ask for a test, list what should never depend on a single rented tool. It is worth doing before you need it, not on cancellation day.