3 min read

How to Export HubSpot Contacts, Clean Them and Import Into Another CRM

A practical checklist for moving contacts and deals out of HubSpot: what to export, how to clean the CSV with free tools, and how to test an import before you cut over.

UrwaTools Editorial Published
Contents

Switching CRMs is rarely blocked by the new tool. It is blocked by the data: duplicate contacts, half-filled columns, dates in three formats and owner names that no longer match any user. This checklist walks through a clean move out of HubSpot, and the same steps work for most CRM exports.

Do not export everything by reflex. Make three lists before you touch a file: records you need to keep working (open deals, active contacts), records you need only for history (closed deals, old notes), and records you can leave behind (unsubscribed or bounced contacts, test data). A smaller, cleaner import is easier to check than a full copy of a messy database.

Export contacts, companies and deals as separate CSV files, and keep the record ID column in each file. The ID is what lets you re-link a deal to its company later. Save the raw exports untouched in a folder called "original" so you can always start again.

Most failed imports are caused by a handful of problems. Work through them in this order:

  • Duplicates. Paste a single column of emails into the duplicate lines remover to see how many repeats you have. Decide which record wins before you delete anything.
  • Bad email addresses. Run suspicious addresses through the email validator, and use the email extractor when addresses are buried in notes columns.
  • Dates and numbers. Pick one date format and one currency format and apply it to every row. Importers often reject mixed formats or silently turn them into blanks.
  • Stray columns. Remove columns the new CRM has no field for, or map them to custom properties on purpose.

UrwaTools also has a longer guide to cleaning a lead list before a CRM import, and a similar checklist for moving support data between help desks.

Most CRM importers take CSV. If a tool or script hands you JSON, the JSON to CSV converter flattens it into rows, and the CSV to JSON converter goes the other way when you are loading data through an API. Check that nested fields such as address blocks came out as separate columns.

Write a two-column table: the old field name and the new field name. Pay special attention to deal stages (the new CRM will have its own stage names), record owners (they must exist as users before import) and lifecycle or status fields, which rarely match one to one. Some CRMs ship importers for popular sources. For example, ProductListo's profile of Close says it has built-in importers for HubSpot, Pipedrive and HighLevel, which removes much of the manual mapping.

Take a sample of ten contacts and five deals, import them, and open each record. Check that the owner, dates, notes and linked company arrived correctly. Fix the mapping, then import the full file. If the importer reports skipped rows, download the error file and look for the pattern instead of fixing rows one by one.

Do not cancel the old plan the day you import. Run both for a few weeks, compare record counts and pipeline totals, and only then close the old account. Export a final backup before you do.

If you are still deciding on the destination, ProductListo's comparison of the best HubSpot alternatives in 2026 covers Pipedrive, Close, Attio and others on price and fit, and its CRM & Sales guide lists more. Makers of CRM and sales tools can submit a tool to the ProductListo directory or read the write for us page for sponsored options.

Frequently asked questions

Should I export HubSpot contacts and deals in one file?
No. Export contacts, companies and deals as separate CSV files and keep the record ID column in each so deals can be re-linked to companies after import.
How do I find duplicate contacts in a CSV?
Copy the email column into a duplicate lines remover to count repeats, then decide which record to keep before deleting. Merge notes first if the duplicates hold different history.
Why do CRM imports skip rows?
Common causes are invalid emails, mixed date formats, owners that do not exist as users in the new CRM and required fields left blank. Download the importer's error file and look for the pattern.
Do I need to convert my export to JSON?
Usually not. Most CRM importers accept CSV. Convert to JSON only if you are loading data through an API or script.
How long should I keep the old CRM after switching?
Keep it read-only for a few weeks, compare record counts and pipeline totals against the new system, and export a final backup before cancelling.
Written by UrwaTools Editorial

The UrwaTools Editorial Team delivers clear, practical, and trustworthy content designed to help users solve problems efficiently. Our articles focus on accurac...