Audit your data: Identify what data you want to migrate (e.g. contacts, companies, deals, activities). Cleanse data: remove duplicates, inactive records, and outdated info.
Define migration scope: Determine essential objects: contacts, companies, deals, tickets, notes, emails, custom fields. Note differences in data structures between Dynamics and HubSpot.
Set roles and responsibilities: Assign a project manager and technical owner. Involve key stakeholders from sales, marketing, and IT.
Export data from Dynamics using: Advanced Find (for filtered exports). Power Platform Admin Center or Data Export Service. Export in .csv
format per object (Contacts.csv, Accounts.csv, etc.). Store backups securely.
Review standard fields in both systems. Create a field mapping document: Match Dynamics fields to HubSpot fields (e.g., “Account Name” → “Company Name”). Identify any custom fields that need to be recreated in HubSpot.
Create custom properties in HubSpot to match Dynamics data. Set up pipelines, deal stages, ticket stages, etc. Configure user roles and permissions.
Choose your migration approach:
Use HubSpot's import tool.
Import objects in the right order:
Contacts
Companies
Deals
Tickets
Activities (notes, calls, emails – more complex, may need API)
Consider tools like:
Trujay
Data2CRM
Import2
HubSpot Migration Services
These automate object linking and handle large volumes or custom objects.
Use Dynamics and HubSpot APIs.
Script a migration using tools like Python, Zapier, or middleware platforms like Workato or Make (Integromat).
Migrate a small sample (10–50 records per object).
Verify: Field accuracy, object relationships (e.g. Contact ↔ Company), activities and notes. Get stakeholder feedback before full migration.
Perform migration in a planned downtime window. Import data in batches, maintaining object relationships. Document any issues and resolutions.
Review and validate all data: Check pipelines, workflows, and reports. Rebuild automations and workflows in HubSpot. Set up integrations (e.g., email, marketing tools).
Train teams on: HubSpot CRM usage, new workflows or pipelines, reporting and dashboards.
Monitor CRM performance and adoption, collect user feedback, refine properties, workflows, and reports as needed.
Tag imported records (e.g., “Imported from Dynamics”) to track and troubleshoot, use HubSpot's sandbox (if available) for safe testing. Engage HubSpot support or a HubSpot partner for expert guidance.