Your business software has an Export button. That sounds reassuring until you open the file and discover that a customer is now a row of numbers, the attachments are missing, and nobody knows what the status codes mean.
Before you rely on an export as an exit plan, follow one representative record out of the system. Can you understand it, reconnect its related information, and use it for the work it supported? A downloaded file is the beginning of that test.
Choose a record with relationships
A plain contact name and email can make an export look complete. A better test is a harmless sample record with the kinds of relationships your business needs: a company, a request, notes, an attachment, a status, and relevant dates.
Use a test account or approved sample data where possible. If production data is necessary, keep it within the business’s approved storage and access controls. Don’t upload a customer export to an unfamiliar online converter just to find out what it contains.
Write down what the record means before exporting it. Which person owns the request? Which attachment belongs to it? What does its status permit staff to do next? Those questions become the acceptance criteria.
Check meaning as well as columns
Open the export in an appropriate local tool and compare the sample against the original. Look for:
- Stable identifiers: Can you distinguish two customers with the same name and connect their related records?
- Relationships: Are companies, requests, notes, and attachments linked in a way the receiving system can use?
- Files: Are attachments included, or do you have links that depend on keeping the old account open?
- Dates and states: Can you interpret the timezone, status values, and other codes without guessing?
- Communication preferences: If the workflow relies on permission or suppression records, does the export preserve their meaning and supporting details?
A column labeled “subscribed” isn’t enough evidence to invent consent that the source record doesn’t establish. Likewise, an owner ID isn’t useful on its own if the export omits the table that identifies that owner.
Some systems provide these pieces in separate files. That’s workable when the connections are documented and tested. The problem is discovering the missing piece after access has ended.
Separate portability from a restorable backup
An export can help move information without reproducing the old application. It may leave behind layouts, automations, permissions, integrations, or settings that made the information useful.
WordPress provides a concrete example. Its Tools Export documentation describes a WXR XML file containing selected content and associated information such as comments, custom fields, and taxonomy terms. That content export is not evidence that a complete website can be restored from it. A WordPress backup test answers a different recovery question.
For business software, record the same distinction: what data you can take, what configuration must be rebuilt, and what behavior depends on the original provider.
Try the destination before canceling the source
In an isolated test environment, import the sample using the receiving system’s documented process. Disable or isolate outbound email and other actions so the test can’t contact customers or trigger live work. Confirm those controls before importing.
Now ask someone familiar with the process to locate the record, read its history, find the attachment, and identify the next appropriate action. A successful import message doesn’t prove those tasks work.
If the test fails, make a precise request to the provider: a missing attachment export, a field dictionary, a relationship mapping, or the documented retention window after cancellation. Add the responsible account and renewal details to your website and business-system ownership record where applicable.
One sample won’t prove every record will transfer cleanly; larger migrations need broader validation. It will reveal whether your exit plan has the basic ingredients. Keep access until the agreed migration and verification are complete, and keep the tested export instructions with the business records that explain how the system is operated.
TechDex Presents…
Flashback to the ’90s
Get 2026 services at 1990s prices.
For a limited time, I’m rolling prices back on six focused small-business services. Choose one service for $800, or choose two for $1,200. Nothing is purchased here—I’ll review your request and confirm the scope with you first.
For related website work, explore this Rewind service:
The campaign form lets you choose one or two services and request a follow-up. It isn’t a checkout, and you won’t be billed when you submit it.