Data Export Drills: Testing Whether You Can Leave a SMB Software Vendor
Most small businesses discover how hard it is to leave a software vendor only when they try. The contract is renewed, the team has built habits around the tool, and the data sits in a format nobody has looked at closely. A data export drill is a deliberate test, run before you need it, that shows whether your records can actually move somewhere else. This guide sets out how UK founders and operators can run that test without buying anything new or assuming the vendor's marketing answers the question for them.
Why exporting is different from owning your data
Many operators assume that because the records were entered by their team, they can take them wherever they like. In practice, a platform decides what can be exported, in which formats, with which relationships intact, and how long that takes. A customer list may come out as a flat spreadsheet while the notes, attachments, approval history and links between invoices and projects stay behind. Ownership is a legal and commercial question. Portability is a technical one, and it is the one that matters when you want to switch.
The gap between the two is where switching projects stall. A founder who believes the data is theirs may only discover in month eleven of a migration that the reporting history cannot be reconstructed. A drill exposes that gap early, while the cost of finding it is still low.
Designing a simple export drill
Pick one system that holds business-critical records, such as customer contacts, invoices, job tracking or stock levels. Choose a single recent period, perhaps the last ninety days, so the test is realistic but contained. Then ask someone other than the usual administrator to perform the export using only the vendor's standard tools and documentation. The point is to find out what a competent person can do without special help.
Record the steps, the time taken, and every point where the process required guessing, a support ticket, or a workaround. Export the same records in every format the vendor offers, then open each file in a neutral tool and check whether it is readable without the original software. Confirm that record counts match what the interface shows. Finally, check whether attachments and comments came out at all, and whether they can be linked back to their parent records.
Questions to put to the vendor before you test
Before running the drill, write down what you need the vendor to answer in writing. Useful questions include: which export formats are offered, and whether any are machine-readable with a documented structure; whether exports include relationships between records, or only individual tables; whether there is a limit on volume or frequency; whether historical records and audit trails are included; and what the process and any fees are when you request a complete extract at contract end. Where the answers are vague, record that vagueness as a finding in itself.
Ask also how your data would be returned if the relationship ended unexpectedly, and who in the vendor's organisation is responsible for that process. You are not looking for promises that go beyond the contract. You are establishing what the vendor has actually committed to, so you can compare it with what the drill shows.
A practical checklist for UK operators
Work through the following after each drill and keep the answers with your software records:
First, can the export be produced by a non-specialist within a reasonable working session? Second, do the files open without the original application? Third, do record counts and key totals reconcile with the source screens? Fourth, are relationships preserved, such as customers to invoices and jobs to notes? Fifth, are attachments and comments included, and can they be matched to their records? Sixth, is the date and time format consistent and unambiguous? Seventh, is personal data handled in line with the data protection arrangements you already have, and is the export stored in a location you control?
Score each item plainly as yes, partly or no. Any no on the first four questions should trigger a conversation with the vendor and a decision about whether the risk is acceptable before the next renewal date. Keep the drill results alongside your contract review notes so that the information is available when a renewal or change decision is due, rather than being rediscovered under pressure.
Repeat the drill periodically, especially after the vendor changes plans, adds integrations or updates the product. A tool that exported cleanly two years ago may behave differently now, and a short annual drill is far cheaper than discovering that a change has made your records hard to move.