Migration
Migrating from HubSpot: an honest checklist.
What moves cleanly, what does not, and how to plan the cutover so nothing slips through.
A
AutomatticCRM team
·
·
8 min read
Most HubSpot migrations slip not because the data is hard, but because the process around the data is unspecified. Here is the checklist we use with every migrating customer.
What moves cleanly
- Contacts, Companies, Deals, Pipelines, Stages
- Notes, Tasks, Activities
- Email histories (the most recent 90 days, then asynchronously)
- Custom properties (1:1 mapped to AutomatticCRM custom fields)
What needs decisions
- **Workflows.** HubSpot workflows do not map 1:1 — every workflow needs a quick review and an AutomatticCRM equivalent.
- **Marketing emails.** Templates port; lists need to be re-segmented because AutomatticCRM is contact-centric, not list-centric.
- **Sales sequences.** AutomatticCRM AI Agent often replaces them entirely. Decide which sequences to port vs. retire.
What does not move
- HubSpot's Marketing Hub-only social / ads tooling. AutomatticCRM is not a marketing automation platform; pair it with a tool like Beehiiv or Loops if needed.
Cutover plan
- **Week -2:** dry-run import into a sandbox. Validate counts.
- **Week -1:** freeze HubSpot writes for non-essential records.
- **Day 0:** full re-import + email sync.
- **Day +1 to +14:** parallel-run in HubSpot read-only.
- **Day +14:** turn HubSpot off.