ActiveCampaign to HubSpot migration.
Automations rebuilt to a model, not transliterated. ActiveCampaign encodes everything in tags because tags are where there is room. Carrying four hundred of them into HubSpot carries the problem with them. The migration is the moment to turn tags back into properties, lifecycle stages and lists.
Four hundred tags doing the job of a schema.
Source, interest, product, stage, event attendance, whether somebody once clicked a link in 2021 — all tags. It works until you need to report on it, at which point there is no way to ask how many customers in a segment bought a product, because neither of those is a field.
A tag is not a field.
ActiveCampaign — the tag sprawlWhat the tags were standing in for.
Tags become several different things
Read properly, a tag list sorts into properties, list membership, lifecycle stages and dead weight. Each group maps somewhere different, and the sorting is the intellectual work of the project.
Automations encode branching in tags
ActiveCampaign automations add a tag, then branch on it. HubSpot workflows can branch on properties and enrolment directly, so the rebuild simplifies the logic rather than copying it.
Deal pipelines were an afterthought
The CRM side of ActiveCampaign is usually lightly used and lightly modelled. Rather than import the pipeline as-is, this is the point to design one that produces a forecast.
Site tracking and event data
Site tracking, event tracking and the conditional content built on them have HubSpot equivalents but different identifiers. Anything personalised on those signals gets rebuilt and retested.
Custom fields per list
Fields scoped to particular lists collapse into one contact property set, which surfaces the same conflicts a Mailchimp audience merge does.
Sending reputation and consent
Domain authentication, unsubscribe state and any regional consent records carry explicitly. A large list moving to a cold sending domain needs a warming plan.
The sequence, start to cutover.
Discovery
Object counts, custom fields, automation and the integrations that will break on the way out, read from the source system rather than from a questionnaire.
Mapping
Field by field, including what will not carry across, agreed and signed before anyone exports anything.
Dry run
A complete rehearsal into a sandbox portal, reconciled against source counts so the gaps surface a month early rather than on cutover night.
Automation rebuild
Workflows, sequences and routing rebuilt to the new model rather than transliterated from the old one, which is how a migration inherits a decade of workarounds nobody remembers writing.
Cutover
A dated switch with the legacy system read-only for a defined window, and a rollback that was tested rather than assumed.
Post-migration support
A named engineer through the first full reporting cycle, which is when the questions actually arrive.
The tags come across intact.
It is the fastest migration to run and the one that wastes the most money. Six months later the portal has four hundred tags, no properties worth reporting on, and a team wondering why HubSpot feels the same as the thing they left. The re-model is not the optional part.
What people ask before they commit.
Do we have to give up our tags?
Not entirely. Some tags are genuinely list membership and stay that way. The ones encoding a fact about the person become properties, because that is the only form you can report on and segment reliably.
How long does it take?
Three to six weeks. Automation count drives the timeline, and the tag audit is the part worth not rushing.
Will our automations work the same way?
They will do the same job, usually with fewer steps. Enrolment and re-enrolment semantics differ between the platforms, so each automation gets tested rather than assumed.
What about our deals and pipeline?
They migrate, but we will push back on copying the pipeline as it stands. ActiveCampaign pipelines are rarely designed for forecasting and the migration is the cheapest moment to fix that.
Is HubSpot more expensive?
On licence, generally yes. HubSpot bills on marketing contacts, so the migration includes deciding who is actually marketable — which usually removes a meaningful slice of the list.
Where people go from here.
Turn the tags back into a model.
Tell us what you are running
What the system does today, where it breaks, and when it has to work. An engineer reads it — you get an answer inside one business day, not a sequence.