Audit a HubSpot export before deleting the old account
Treat the export as unproven until you can find representative records, their matching keys and the associations your destination needs.
Keep the old account available until a separate migration audit is complete; this guide does not recommend deleting anything.
Work through the setup
- Write a coverage inventory. List CRM objects, properties, associations, activities and files. Mark each as exported, not exported or still uncertain.
- Check the files rather than the email. Open the downloaded files with a tool that preserves IDs. Confirm the requested view and all necessary columns are present, including associated IDs where required.
- Test edge cases. Inspect a contact with several email addresses, a deal with a company relationship and a record with an unusual character in its name. Count rows without assuming that count proves completeness.
- Keep an exception list. Record missing values, truncated relationships or activities that require a different export. Do not cancel the source on the strength of a successful download alone.
A worked example
An audit can use ten deliberately varied records rather than ten adjacent rows. For each, record whether the ID, owner, stage and needed relationships survive. If a critical association is absent for one of those records, enlarge that check before making a cutover decision. Ten is an illustrative sample, not a statistical assurance.
What to watch out for
- Records and activities have different export paths.
- A filtered view can make a complete-looking file incomplete.
- Export links expire; store the actual downloaded evidence securely.
Use a recovery checklist, not a row total
Open the saved file in a separate reader and check several known records by Record ID. Look for expected associations and properties, then record which content needs a separate export or manual copy. A file that downloads successfully can still omit a view, a field or an associated object. Do not delete the old account merely because the exported row count looks plausible. Keep the source until you have checked what the destination actually restored.
Sources and evidence
- Export your records (read November 7, 2026)
- Deduplicate records in HubSpot (read November 7, 2026)
Common checks
Is a row-count match enough?
No. The right number of rows can still contain wrong IDs, missing properties or broken associations.
Published November 7, 2026. Sources last read November 7, 2026. Send a correction.