Every piece of business software looks portable on the day you buy it. There is an export button somewhere in the settings, a page in the help center about downloading your records, and a salesperson who says the word open more than once. None of that is a lie. It is just a description of the product in week one, under no pressure, with a small amount of data in it.
The question worth answering is what happens in year eight. You have four hundred thousand records, a custom field structure nobody documented, two integrations wired in by a contractor who left, and a reason to move. That is when export stops being a feature and starts being a load-bearing part of your business. Here is what to check, and roughly when to check it.
1. Run the export now, while nothing is at stake
The single most useful thing you can do is pull a full export on an ordinary Tuesday and open the files. Not a sample. Everything the system will give you.
You are looking for three things. How long it took. Whether it arrived as one file or as a job you had to request and wait on. And whether the contents match what you see on screen.
That last one catches more problems than the other two combined. Plenty of systems export the records but not the attachments, or the records but not the comment threads, or the current state of a record but not the history of who changed what and when. If your industry has any retention obligation, the history is often the part that matters and the part most likely to be missing.
Do this during a trial if you can. If you are already five years in, do it this month. An export you have personally opened is worth more than any contract clause promising one.
2. Look at the format, then ask what can actually read it
A CSV file is not automatically portable. It is a grid of text. Whether it is useful depends on whether the relationships between your records survived the trip.
Say you keep customers, jobs, invoices and notes. In the application, a note belongs to a job and a job belongs to a customer. In the export, you may get four separate files with identifier columns that stitch them back together. Fine. Or you may get four files where the identifiers are internal and meaningless, which means a migration becomes a reconstruction project billed by the hour.
Ask the vendor directly, in writing, whether the export preserves record identifiers, custom field definitions, file attachments, and user-level activity history. Keep the answer. If the format is something proprietary with a vendor-specific extension, ask what third-party tools read it. Sometimes the answer is good. Sometimes the answer is that the only tool that reads it is the product you are leaving.
There is a middle path worth knowing about. Many systems have an application programming interface, a structured way for outside software to pull records on request, and the interface often returns more complete data than the download button does. If the interface is open to you and documented, your portability is in decent shape even when the export file is thin. Check whether access to it is included in your tier or sold separately, and check whether there is a cap on how many records you can pull per hour. A cap matters a great deal when you are trying to pull four hundred thousand records inside a thirty-day window.
3. Find the clock that starts when you give notice
This is the part people discover too late. Somewhere in the agreement is a sentence about what happens to your data after termination: how long you keep access, in what mode, and when it is deleted.
The shapes vary. Some vendors give you a read-only period of thirty or sixty days. Some cut access on the final day of the paid term and will restore it only as a paid reactivation. Some keep backups for a defined window and then purge, which is reasonable practice but means a request made late gets nothing.
Go find that sentence before you need it. Then work backward. If the window is thirty days and your export job takes four days to run and two weeks to validate, you have very little slack. Negotiating a longer transition period is far easier at renewal, when you have leverage, than during the notice period, when you do not.
A related clause worth asking for by name is termination assistance: a commitment that the vendor will provide the data in an agreed format within an agreed time, at a stated price or at no charge. Vendors who intend to behave well have usually seen the request before and say yes without much fuss.
4. Count everyone else who is holding a copy
Your records are rarely in one place. The vendor runs on somebody's cloud infrastructure. It may use a separate provider for email delivery, another for document storage, another for search. In the contract these are sub-processors, and most agreements list them or link to a page that does.
This matters on the way out for a practical reason. If a service was bolted on through an integration, the copy sitting in that other system may not come down in the main export at all. Invoices synced to an accounting package, files pushed to a storage service, call recordings held by a phone vendor: each one is its own export, its own format, its own window.
Write the list down while you still have admin access and can see what is connected. A one-page inventory of every system holding a piece of your operation is the cheapest insurance in this whole exercise, and it tends to be useful for security reviews and insurance questionnaires too.
5. Know which protections are law and which are only your contract
There are real statutory portability rights in the United States, most visibly in the state consumer privacy laws that have passed over the past several years. They give individuals the ability to get a copy of personal information a company holds about them, often in a portable, machine-readable form.
Read that carefully, because the right belongs to the individual. It generally does not give your company a legal claim to pull your own business records out of a vendor. That claim comes from your contract and almost nowhere else. The Federal Trade Commission oversees unfair and deceptive business practices, which is why the promises a vendor publishes about data handling are worth capturing and keeping rather than skimming.
So the practical protection stack, in order: a contract clause naming format, timing and cost; a documented interface you have tested; an export you have personally opened; and a written answer from the vendor on anything the first three leave ambiguous. Build that during purchasing and renewal, and the exit, whenever it comes, is an ordinary project instead of an emergency.
Software choices are long-lived. The thing that determines how a system behaves in year eight is not the interface you were shown at the demo; it is the plumbing underneath and the paperwork around it. Ten minutes with the termination clause and one afternoon spent opening export files will tell you more about a vendor's durability than any feature list.