Moving your CRM data into HubSpot from another platform – Salesforce, Pipedrive, Zoho, Dynamics, or even a spreadsheet – requires careful planning. Data migration is one of the most common sources of CRM implementation failures: contacts arrive with missing fields, deals lose their history, duplicate records proliferate, and teams end up trusting the new CRM less than the old one. This guide covers how to migrate data into HubSpot correctly, what to clean before you migrate, and the mistakes that create months of cleanup work afterwards.
That makes migration planning a critical part of the rollout, not a task to rush through at the end.
HubSpot data migration is useful when a business needs to move contacts, deals, and history from another CRM without breaking the structure of the new system. The goal is not just to import data, but to import it in a way that supports clean reporting and early adoption.
What Can Be Migrated to HubSpot
HubSpot can receive:
- Contacts: All contact properties, including custom fields mapped to HubSpot custom properties.
- Companies: Company records with all properties.
- Deals: Deal records with amounts, stages, close dates, and associated contacts and companies.
- Notes and activities: Call logs, meeting notes, emails (as notes, not as actual tracked emails).
- Custom objects (Enterprise): Custom data that doesn’t fit standard CRM objects.
What typically does NOT migrate cleanly:
- Email conversation history – most platforms can export email logs as notes, but the formatted email threads don’t migrate into HubSpot’s email activity view
- Automation workflows – these must be rebuilt in HubSpot’s workflow builder
- Custom-coded functionality – any custom triggers or integrations in the old system need to be rebuilt for HubSpot
- File attachments on contact records – require manual re-attachment or a separate document management solution
Step 2: Map Your Fields
Create a field mapping document before importing. For each field in your source system, determine: (1) the equivalent HubSpot property, or (2) whether a custom property needs to be created. Common mapping considerations:
- Lead Status in Salesforce ? Lifecycle Stage in HubSpot (or create a custom Lead Status property if they don’t map cleanly)
- Account in Salesforce ? Company in HubSpot
- Opportunity Stage values ? HubSpot Deal Stage values (map each value explicitly – don’t assume they’ll match)
- Custom fields ? Create corresponding custom properties in HubSpot before importing
Step 3: Import Contacts and Companies
Import via CSV: Contacts ? Import ? File from computer. HubSpot’s import tool maps CSV columns to contact properties. Email is the deduplication key – if a contact with the same email already exists, the import will update (not duplicate) that record. Import companies separately if you want company records to exist independently from contacts.
For large imports (100,000+ records), split into batches of 50,000-100,000 and monitor each batch for errors before proceeding to the next. Review the import error log after each batch – HubSpot generates a detailed error file showing which rows failed and why.
Step 4: Import Deals with Associations
Deals require a separate import with association columns: include contact email and/or company name columns in your deals CSV to link deals to existing contact/company records during import. Map deal stage values to your HubSpot pipeline stages. Import deals after contacts and companies so the association records already exist.
Step 5: Import Activity History
Activities (calls, notes, meetings) can be imported as Notes via the Engagements API – but this requires developer work unless your source system exports notes in a format that maps to HubSpot’s note import. For most organisations, the practical approach is to import only recent activity history (last 12-18 months) and archive older history in a separate document or spreadsheet rather than attempting a complete activity log migration.
Native Migration Tools
HubSpot offers native migration assistance for specific platforms:
- Salesforce to HubSpot: HubSpot’s Import from Salesforce tool syncs contacts, companies, deals, and activities directly from a connected Salesforce org – without manual CSV exports. Available in the Salesforce integration settings.
- Pipedrive, Zoho, and others: Migration partner services and third-party tools (MigrationService, Trujay) offer automated migration with field mapping and validation.
Post-Migration Validation Checklist
- ? Verify total record counts match source system (within acceptable tolerance for excluded records)
- ? Spot-check 20-30 individual records across different segments for accuracy
- ? Verify deal amounts and stages are correct on a sample of deals
- ? Confirm associations (contacts linked to correct companies, deals linked to correct contacts)
- ? Check that custom property values imported correctly
- ? Run HubSpot’s duplicate detection tool and merge any duplicates created during import
Getting your team to consistently use HubSpot
Adoption gaps occur when teams revert to old habits after initial training. Fix: Identify the 2-3 daily workflows where HubSpot adds the most value for your specific role. Focus training on those workflows first. Use HubSpot in-app guidance to provide contextual help at the moment of need rather than relying solely on one-time classroom training.
CRM data quality degrading over time
CRM data decays at approximately 30% per year as contacts change roles and companies. Fix: Schedule a quarterly data quality audit. Use HubSpot deduplication tools to merge duplicate records. Establish data entry standards enforced through validation rules. Consider a data enrichment tool like Clearbit or ZoomInfo to update stale records automatically.
HubSpot reports not matching actual business results
Reports are only as accurate as the data entered. Discrepancies between CRM reports and actual revenue indicate data entry gaps. Fix: Audit closed-won records against actual invoices monthly. Make CRM data the source of truth for commission calculations so reps have a direct incentive to enter accurate data.
Is HubSpot easy to learn for beginners?
HubSpot has a learning curve, but its official free training platform HubSpot Academy provides structured paths from beginner to advanced. Most users handle day-to-day tasks within 2-4 weeks. Admin and developer skills take 3-6 months to develop proficiently.
What are the biggest HubSpot mistakes to avoid?
Top mistakes include: over-customizing before understanding your process, skipping user training, importing dirty data without cleansing, and not establishing naming conventions. Avoid these four and your implementation will be significantly more successful.
How often does HubSpot release new features?
HubSpot releases major updates quarterly and ships smaller updates continuously to all tiers.
Does HubSpot offer customer support?
Yes. Support is available via chat, email, and phone depending on your plan tier. Enterprise plans include dedicated customer success managers. HubSpot Academy and the HubSpot Community are also excellent free support resources.
Can HubSpot integrate with other business tools?
Yes. HubSpot App Marketplace has 1,500+ integrations including Gmail, Slack, Zoom, Shopify, and WordPress.
The strongest migration process is the one that preserves useful history while cleaning up what should not be carried over. If the import is messy, the new CRM starts with the same problems as the old one.
Common Problems and Fixes
Frequently Asked Questions
Step 1: Audit and Clean Your Source Data
The most important step in any CRM migration is cleaning your data before importing it – not after. Problems to address in your source data:
- Duplicate records: Remove duplicate contacts (same email address, same phone and name) before import. Importing duplicates into HubSpot creates cleanup work that’s harder to do than cleaning in your familiar source system.
- Invalid emails: Remove or fix invalid email addresses – HubSpot uses email as the primary deduplication key. Invalid emails cause contacts to be created without email (reducing their usefulness) or to match incorrectly.
- Incomplete records: Decide which incomplete records are worth migrating. Contacts with only a first name and no company, email, or phone number may not justify the noise they add to your new CRM.
- Outdated records: Consider not migrating contacts with no activity in 3+ years. An import of 50,000 contacts sounds better than it is if 30,000 are unengaged records from years ago.