Data Portability Checks for UK Founders: Who Actually Owns Your Records?
Most founders think about software in terms of features and price. Far fewer think about what happens to their records when the relationship ends. A customer list, a project history, invoices and support threads accumulate quietly inside tools, and over time they become the operating memory of the business. Data portability is the question of whether that memory can be taken out in a usable form, on a timeline you control, without depending on goodwill. This article sets out a practical way for UK founders and operators to check portability before they sign, renew or migrate, using general methods rather than assumptions about any particular vendor.
Separate the three kinds of data
Start by dividing the data a tool holds into three categories. The first is primary records: the things the business created, such as contacts, orders, documents and tickets. The second is configuration: workflows, custom fields, templates, permissions and automations. The third is derived data: reports, scores, analytics and anything generated from the first two. Each category behaves differently on export. Primary records are usually the easiest to get out, configuration is often partly locked to the vendor's format, and derived data is frequently not exportable at all because it is recalculated on the platform.
Writing these three categories down for each tool gives you a realistic map. A tool that exports contacts as CSV but has no way to export automation logic has a portability gap that matters if you ever need to rebuild a workflow elsewhere.
Ask specific questions before you sign
Vague reassurances about data ownership are common, and they rarely answer the practical question. Put concrete questions to the vendor in writing. Which formats can each category be exported in? Is the export self-service or does it require a support request? Are attachments and file histories included, or only record metadata? Are there limits on volume, frequency or export size? What fields are omitted from the export, such as internal IDs needed to rebuild relationships between records? How long does a full export take for a business of your size?
Also ask what happens to your data after cancellation, and over what period. Get the answer in the contract or order terms rather than from a sales conversation, because the written terms are what you will rely on later. If a vendor cannot answer these questions plainly, treat that as information in itself.
Run a small export drill
Reading documentation is not the same as testing. Before committing, or during a trial, run an export drill. Choose a representative slice of real data, such as twenty contacts with their notes, one project with its files and comments, and one report. Export it using the method the vendor describes. Then try to make sense of the result without the vendor's interface. Can you identify which note belongs to which contact? Are dates in a readable format? Do file names survive? Are links between records preserved as IDs that map to something, or are they opaque strings?
Record how long the drill took and what manual cleanup it needed. Multiply that effort by the size of your full dataset to estimate what a real exit would cost in time. A drill that takes ten minutes on twenty records may take days on twenty thousand, and that scaling is exactly what you need to understand before you depend on the tool.
A checklist for renewal and migration
Use the following checklist when a contract is due for renewal or you are considering a move. Confirm which data categories you hold in the tool and where each lives. Check whether export is self-service, and note the formats offered for each category. Verify that attachments and history are included or know what is excluded. Record any limits on volume or frequency. Identify the fields needed to reconstruct relationships between records. Find the written post-cancellation retention period and who to contact to request deletion or return. Schedule a drill at least once a year, and after any major change to the tool's plan or data model.
Keep the results in a short document alongside your vendor register. When renewal comes around, you will be comparing the current position against a known baseline rather than trying to remember what was promised.
Reduce the cost of leaving
Portability is partly a property of the vendor and partly a property of how you use the tool. Keep a copy of important records in a format you control on a regular schedule, especially for data that would be painful to lose or reconstruct. Avoid storing the only copy of a process in a tool's automation logic without documenting the steps in plain language. Where possible, use standard formats and identifiers that other systems can read, and prefer tools that let you export configuration as well as content.
None of this requires a large budget or a dedicated team. It requires treating your records as an asset the business owns, and checking regularly that the tools holding them still let you take them with you. For a founder, that check is one of the cheapest forms of risk management available, and it is most valuable exactly when a vendor changes terms, raises prices, or stops being the right fit.