A new tool makes it easy to import a spreadsheet. Six months later, your team wants to move, but the export contains contact names without their notes, files, or activity history. The import demo never answered the question that matters now: can you reconstruct your work somewhere else?

Test that before choosing a tool, using sample records instead of real customer data.

Make the sample represent a real workflow

Create a few fictional records that exercise the parts your team needs: one company with two contacts, two linked requests, a note with multiple languages, a date with a time zone, and an attachment. Include an empty field and a custom field, too.

Write down what must survive a migration. A directory may only need names and emails. A support workflow may need message order, assignment history, and files attached to the correct conversation.

Open the export outside the original tool

Check whether a record has a stable identifier and whether linked records reference it. Identical names are not reliable join keys. Open the files in a spreadsheet or a local test database and try rebuilding one complete record.

For attachments, check whether you receive actual files or just links. If you receive links, find out whether those links require an active account or expire. Check whether exported dates retain enough information to interpret them correctly.

Separate portability from completeness

One successful CSV export does not mean everything can move. Rules, forms, dashboards, and permissions may have to be rebuilt even when the underlying data is available. Keep a short inventory with three categories: exportable, reconstructable, and missing.

Ask the vendor to confirm any restriction that matters to your decision, such as who can export, whether exports cover archived records, and how access works after account closure. Test the answers you can verify in a trial.

Put an exit test in the acceptance checklist

  • Can another person export without relying on the original setup owner?
  • Can they match notes and files to the right records?
  • Can they reconstruct one representative case outside the tool?
  • Are gaps and rebuilding costs recorded?
  • Is there a protected location for authorized exports?

A good export test does not require planning a full migration. It makes the cost of leaving visible while the team can still choose.

For a related starting point, see our guide on moving from a spreadsheet to an internal tool or ask about migration planning.