Most CRM migrations to HubSpot do not fail because of the tool. They fail because of the data. Dirty records, wrong import order, missing field mappings, and no validation step are the four most common ways a migration creates more problems than it solves. This checklist covers every phase, in sequence, so you can move to HubSpot without losing a contact or breaking an association.
Phase 1: Pre-Migration Audit and Preparation
Everything that happens before the first export determines the quality of what lands in HubSpot. Skipping pre-migration preparation is the fastest path to a broken CRM.
Phase 1 Checklist
Pre-Migration
Audit your current CRM data. Count records by object type: how many contacts, companies, deals, activities. Identify the last active/updated date per record type to determine what is worth migrating versus archiving.
Deduplicate contacts and companies. Run a deduplication pass before exporting. Duplicates that migrate into HubSpot are harder to merge at volume than duplicates cleaned in the source system first.
Validate email addresses. HubSpot uses email as the primary contact identifier. Invalid or malformed emails create orphaned records on import. Clean them before you export.
Create a field mapping document. List every field in your source CRM and map it to the corresponding HubSpot property. Note fields that have no direct equivalent and decide whether to create a custom property in HubSpot or drop the field.
Define your HubSpot data model before importing anything. Decide on lifecycle stage definitions, deal stage criteria, and required properties. Importing into a model that is not yet designed means reconfiguring records after the fact.
Decide what not to migrate. Not all historical data is worth bringing over. Contacts who have been inactive for 3 or more years, bounced emails, and junk records that accumulated in the old system should be archived, not migrated.
Phase 2: Migration Execution
The order of import is non-negotiable. HubSpot creates associations by referencing records that must already exist in the system. Import in the wrong order and you break every association in your data.
The correct import order is always: Companies, then Contacts, then Deals, then Activities. Every other sequence breaks associations.
Phase 2 Checklist
Migration Execution
Export all objects from your current CRM in CSV format. Export by object type: a companies file, a contacts file, a deals file, and an activities file. Keep them separate.
Import Companies first. This creates the anchor records that contacts and deals will associate to. Include a unique identifier column (domain or internal ID) so HubSpot can match associations on subsequent imports.
Import Contacts and associate them to Companies. Use the Company domain or HubSpot Company ID (from the Companies import result) to set the association. Contacts without a company association can be imported cleanly and associated afterward if necessary.
Import Deals and associate to Contacts and Companies. Deals require at least one contact or company association to be meaningful. Include both Contact email and Company domain columns in your Deals import file.
Import Activities (Tasks, Calls, Emails, Notes) last. Use the HubSpot Contact ID or Deal ID from prior imports to associate activities correctly. Note: email activity history from Salesforce does not import directly and typically requires manual reconstruction or third-party migration tools.
Keep a rollback file. Before going live, export a snapshot of HubSpot immediately after the migration completes. If something is wrong, you want a clean restore point rather than attempting to delete and reimport selectively.
Phase 3: Validation
Validation is the step most teams skip because they are eager to go live. It is also the step that catches the problems that would otherwise show up as missing deals, broken associations, or lost contacts three months after go-live.
Phase 3 Checklist
Post-Import Validation
Compare record counts against the source. The number of contacts, companies, and deals in HubSpot should match the number exported from your source CRM, minus any records intentionally excluded.
Spot-check 10 to 20 records from each object type. Pull specific contacts, companies, and deals from your source CRM and find them in HubSpot. Verify that properties migrated correctly, associations are intact, and activities are present.
Check for orphaned contacts (no company association). Run a HubSpot list of contacts with no associated company and compare against your source data. Unexpected orphans indicate a mapping failure during the companies import.
Check for orphaned deals (no contact or company association). Deals with no associations are invisible to your sales team and will not appear in pipeline reports. Fix these before go-live.
Review import error logs. Every HubSpot import generates a results file listing rows that failed to import and why. Review it completely, not just the first few errors. A 1% error rate on 100,000 records is 1,000 missing contacts.
Phase 4: Post-Migration Setup
A successful data migration gets your records into HubSpot. The post-migration phase turns that data into a working revenue system.
Phase 4 Checklist
Post-Migration
Configure your pipelines and deal stages. Map your sales stages to HubSpot deal stages. Set win probability for each stage, define entry and exit criteria, and configure required properties for stage transitions.
Set up workflow automation. Build the automations that make HubSpot active: lead assignment, lifecycle stage progression, deal rotation, follow-up task creation, and internal notification workflows.
Connect your tool integrations. Link your email client (Gmail or Outlook), connect your calendar for meeting scheduling, set up your marketing tools, and configure any third-party integrations required by your stack.
Configure user permissions. Set up HubSpot users with appropriate roles and property-level permissions. Decide which users can edit, delete, or export records based on their function.
Run team training before turning off the old CRM. Your team needs at least one live training session on the new HubSpot setup before their old system is decommissioned. Train on the workflows and views that match how they actually work, not just on generic HubSpot features.
Set a decommission date for the old CRM. Running two CRMs in parallel creates data drift. Set a firm cutover date and stick to it. Give your team 1 to 2 weeks to adjust, then turn off the old system.
The Most Common Mistakes in a CRM Migration
- Migrating dirty data. Duplicates and invalid emails that exist in the source system will exist in HubSpot. Clean before you move, not after.
- Wrong import order. Importing contacts before companies breaks every company association and requires a full re-import to fix.
- Skipping the field mapping document. Importing without a field map means some data lands in the wrong property or does not land at all. You typically do not discover this until a rep cannot find a key piece of information months later.
- No validation step. Import error logs are easy to ignore when you are eager to finish. A 2% error rate on a large database is thousands of missing or broken records.
- Running two CRMs too long. The longer you run the old system in parallel, the more your data diverges and the harder the final cutover becomes. Set a firm date and enforce it.
Moving from Salesforce or Pipedrive?
Pixiu X has run CRM migrations from Salesforce, Pipedrive, Zoho, and spreadsheets into HubSpot. We handle the full process: audit, cleaning, mapping, import, validation, and post-migration setup. Fixed scope, no data loss.
Get a Migration Quote
Frequently Asked Questions
How long does a CRM migration to HubSpot take?
A clean migration with under 50,000 records takes 2 to 3 weeks when handled by an experienced partner. Larger migrations with complex field mappings and activity history typically take 4 to 6 weeks. The biggest variable is the quality of data in the source system.
What data can be migrated from Salesforce to HubSpot?
Most standard Salesforce objects migrate: Contacts, Accounts (Companies), Opportunities (Deals), Activities, and Notes. Custom objects can often be migrated to HubSpot Custom Objects. Reports and dashboards do not migrate directly and need to be rebuilt in HubSpot.
What is the correct import order for a HubSpot migration?
Companies first, then Contacts (associated to Companies), then Deals (associated to Companies and Contacts), then Activities and Notes. Importing in the wrong order breaks associations and requires a full re-import to fix.
What are the most common mistakes in a CRM migration to HubSpot?
Migrating dirty data without cleaning first, importing in the wrong order, skipping the field mapping document, not running a validation pass against the source, and running two CRMs in parallel for too long after go-live.
Do I need a partner to migrate my CRM data to HubSpot?
For under 5,000 records with a simple structure, a careful DIY migration using HubSpot's import tool is feasible. For migrations above 10,000 records, or any migration involving Salesforce or Pipedrive with complex field mappings and activity history, working with a certified partner significantly reduces the risk of data loss.
Ready to migrate to HubSpot the right way?
Pixiu X specializes in CRM migrations from Salesforce, Pipedrive, and Zoho to HubSpot. Fixed scope, full validation, clean data on go-live.
See Our Migration Service