Rebuilding your CRM automations in HubSpot
Your old CRM’s automations don’t migrate. How to inventory them, rebuild them as HubSpot workflows and test them before go-live.
The short answer: CRM automations don’t migrate. Salesforce Flows, Pipedrive automations, Zoho Blueprints and Dynamics Power Automate flows must be listed, understood and rebuilt as HubSpot workflows, available on Professional and Enterprise. Write test cases, test in a test portal and switch automations on only after data loads, starting with lead routing.
Records are the visible part of a CRM. Automations are the invisible part, and they’re where most migrations quietly fail. Your old system routes leads, assigns owners, creates follow-up tasks, updates statuses and sends alerts. None of that moves to HubSpot by itself. Every automation has to be found, understood and rebuilt.
Why automations don’t migrate
Every CRM builds automation differently: Salesforce Flows and Apex, Pipedrive automations, Zoho workflows and Blueprints, Dynamics Power Automate flows. HubSpot uses workflows, which are available in its Professional and Enterprise subscriptions. The logic can usually be reproduced, but no tool converts one system’s automation into another’s. It’s rebuilt by hand.
The automations that break most often
Lead routing
If routing isn’t rebuilt and tested before cutover, new leads arrive in HubSpot unassigned and sit there. It’s the most business-critical automation and the first to check.
Follow-up tasks and sequences
Reps who relied on automatic reminders lose them on day one unless replacements are ready. In HubSpot these are task-creating workflows and sequences.
Status and stage updates
Automations that moved a lead to a new status or updated a field when something happened. Lose these and your reports start drifting.
Internal alerts
Small automations that tell a manager about a large deal or tell customer success that a deal closed. Easy to forget, noticed only when someone misses something important.
Automations nobody knew about
Systems accumulate automation over years. Some is still running long after its owner left. An inventory always finds a few surprises.
How to rebuild them safely
- Inventory every active automation with its trigger, actions and an owner who can explain why it exists.
- Decide for each one: rebuild as a HubSpot workflow, replace with a standard HubSpot feature, move to another tool, or retire it.
- Write test cases first: “a lead from this form in this region is assigned to this rep and gets this task.”
- Build and test in a test portal during both rehearsals.
- Switch on after the data loads, so automations don’t fire on migrated history. Emailing ten thousand old customers a welcome message is a classic migration accident.
- Watch routing closely for the first weeks after go-live.
Working automations are part of our 30-day guarantee. For the wider setup, see setting up HubSpot for your sales team.
Sources and further reading
- Create workflows, HubSpot Knowledge Base
- Getting started with the HubSpot CRM Data Migration Service, HubSpot Academy
Platform features and policies change. Check the vendor’s current documentation before acting on any detail in this article. This article is general information, not legal advice.