Data you can leave with

Every software vendor says you own your data. It is an easy thing to say, because ownership without the ability to take delivery is a sentence rather than a right. The practical question is narrower and answerable: if you decided to leave in six months, what exactly would you walk out with, and how long would it take to get?

Three levels of export, and why the difference matters

• A list export. Any screen, to a spreadsheet, whenever you want, with the filters you applied. This is table stakes and most systems have it.

• A structured export of a whole domain. All customers with their balances, all items with their costs, all invoices with their lines. This is what a migration actually needs, because a screen export loses the relationships between records.

• A full database export. Everything, in a form another system could be loaded from. This is the one that proves ownership, and the one vendors are least likely to offer.

A vendor who offers the first and calls it data portability is not lying, but they are answering a smaller question than the one you asked.

Ask during the trial

Request the export while you are still a prospect. The answer you get then is the answer the organisation can give easily; the answer you get after two years of data is the answer under pressure, from a team with other priorities and no commercial reason to hurry.

It costs nothing to ask, and the response is informative whatever it is: an immediate yes, a yes with a process, or a change of subject. All three tell you something you cannot learn from a feature list.

What makes an export actually usable

An export that technically contains everything can still be useless. Three things separate the two.

1. Identifiers. If the export uses internal numbers with no stable codes, you cannot match customers or items to anything else, and the relationships are guesswork.

2. Documents and attachments. Scanned invoices, contracts and signed delivery notes are data too. An export of rows without files leaves the part auditors ask for behind.

3. The derivations. An exported balance is a number; an exported set of transactions is a record you can rebuild the number from. Where only the former exists, you are exporting conclusions.

Leaving is also a security question

The reverse case matters too: when you leave, what happens to the copy that stays behind? A clear answer about retention and deletion after termination is part of owning your data, and it is worth having in writing before you need it rather than after.

The cheapest insurance in software procurement

Request an export in the first week, confirm it opens and contains what you expect, and keep it. It costs an hour. Everything else in a software relationship is negotiable later; the ability to walk away with your own records is the one thing that is much harder to obtain retroactively.