HubSpot

HubSpot consultants for the portal, the migration and the operations after

The InHouse Marketers is a B2B marketing operations consultancy that implements HubSpot, migrates companies into and out of it, and runs the operations afterwards for the team that inherits the portal. Of its nine published migrations, five have HubSpot on one side of the move, three leaving it and two arriving in it.

What does a HubSpot consultant do?

A HubSpot consultant configures the portal, builds and repairs the workflows, forms, properties and CRM sync inside it, and runs the operations that follow. five of the nine migrations The InHouse Marketers has published have HubSpot on one side of the move: three leaving HubSpot and two arriving in it. Clean-up on a portal that grew faster than its admin is part of the same work.

Delivered work

The HubSpot migrations on the record

Every row is an engagement our consultants ran, described by sector because clients are never named. Each write-up link reads as the pair a buyer searches for. The full list of 15 engagements sits on the migrations track record.

five published migrations with HubSpot on one side
Move	Sector	What it involved
HubSpottoPardot	Security services	System analysis first, then a written plan of exactly what needed migrating. The operational programs were the work; HubSpot workflows split across automation rules, completion actions and Engagement Studio. HubSpot to Pardot migration
HubSpottoOdoo	Authentication software	A platform with almost no marketing operations community behind it. Learning Odoo well enough to teach it came before any migration, and program logic ended up encoded in regular expressions. HubSpot to Odoo migration
MarketotoHubSpot	sector not published	Moving from a granular platform to a more opinionated one. Marketo smart campaigns do not collapse into HubSpot workflows one-for-one, so some logic consolidates, some is deliberately dropped, and the decision about which is a conversation, not a mapping exercise. Marketo to HubSpot migration
HubSpottoMarketo	sector not published	Usually a move made because scale or complexity outgrew the original platform. Workflows become smart campaigns, and the programme, channel and token structure Marketo expects has to be designed up front — HubSpot has no equivalent to inherit. HubSpot to Marketo migration
SalesforcetoHubSpot	sector not published	Mostly a question of ownership rather than transfer: which system is master for which object and field, which direction each one syncs, and what happens to the reports built on the fields that move. Salesforce to HubSpot migration

HubSpot wired to the systems around it

Two published integrations have HubSpot at one end: one writing enrichment into it, one putting two HubSpot databases behind a single CRM.

two published integrations with HubSpot at one end
Move	Sector	What it involved
Two HubSpot instancestoOne Salesforce	sector not published	Two marketing databases writing into a single CRM without overwriting each other: field-level ownership, deduplication across both sources, and sync rules that make it obvious which instance a record came from.
ClaytoHubSpot	sector not published	Enrichment that writes back safely — only filling fields that are empty, holding a record of where each value came from, and never letting an enrichment run overwrite something a human entered.

Moving off HubSpot

The workflow is the whole problem

HubSpot puts enrolment, branching, delays, actions and re-enrolment inside a single object. No other platform on our track record has that object, so every move off HubSpot turns one workflow into several things in the destination.

HubSpot to Pardot · security services

One workflow becomes four or five constructs

In Account Engagement a workflow lands as some combination of an automation rule, a completion action attached to the asset, a page action on a URL, a dynamic list and an Engagement Studio program. There is no single screen where the logic is visible afterwards. Account Engagement also caps the number of active automation rules, so a one-for-one rebuild hits that cap under time pressure. On this engagement the system analysis and a written plan came first, naming what moved as-is, what was rebuilt differently and what was left behind.

Why the two automation models differ Account Engagement (Pardot) consultancy

HubSpot to Marketo

Smart campaigns, inside a structure you design first

Marketo hands over an empty instance, so the structure every later object depends on gets designed before the first asset lands. This is usually a move made because scale or complexity outgrew the original platform, and it comes with database restructuring attached.

What has to be decided before the build Marketo consultancy

HubSpot to Odoo · authentication software

No equivalent object at all

Odoo has marketing automation campaigns with activities and filter-based entry, which covers ordinary nurture. It is not an equivalent of the workflow editor for branching or lifecycle. Anything conditional beyond a straightforward filter ends up in server actions or encoded expressions, and on this engagement the program logic ended up written in regular expressions. Learning the platform well enough to teach it came before any migration. Where nobody on a project has shipped in Odoo before, that learning gets its own dates in the plan.

HubSpot to Odoo migration

Moving onto HubSpot

What consolidates, and what gets dropped on purpose

From Marketo

Write the list of what is being abandoned and have it signed, because that column is the one that saves the project. It gets longest around reporting: program status and channel success are the objects Marketo numbers are built on, and HubSpot holds neither.

Marketo to HubSpot migration

From Salesforce

Mostly a question of ownership instead of transfer: which system is master for which object and field, which direction each one syncs, and what happens to the reports built on the fields that move. The audit check that catches this is the one on fields with two writers.

Salesforce to HubSpot migration

Either direction moves the website with it. Forms, the tracking code and every hidden field behind them are their own workstream, with a repointing register and a daily zero-submission alert, as set out in the hidden-field inventory.

Before anything changes

What the audit opens in a HubSpot portal

A different eight checks from the ones we open first in Marketo, because a HubSpot portal fails differently: the platform keeps the contact list looking tidy while the damage collects in workflows and forms nobody has counted. The wording is from the marketing automation audit checklist, and each check names the object to open.

Field fill ratesFor every field (Marketo field, HubSpot property, Pardot prospect field), count the records holding a value and note when it was last written. Few values and no recent writes make a field a candidate to retire. Database health
Duplicate person recordsIn Marketo and Account Engagement, count duplicates by email address, including the same address in different casing, and note which system created each copy. HubSpot keeps one contact per email address, so there, look for the same person under a second address. Database health
Last-run datesPull the last-run date for every smart campaign, workflow, automation rule and Engagement Studio program. Anything that has not sent an email or written to a field in two quarters goes on the archive list. Programme structure
Form submissions by monthCount submissions per form by month. Lifetime totals hide forms that stopped taking submissions years ago. Programme structure
Fields with two writersFor every field more than one system writes, Lead Source included, record which system wins and in which direction it syncs. Sync integrity
Enrichment write-backCheck that enrichment only fills empty fields and records where each value came from, so an enrichment run cannot overwrite a value a person entered. Sync integrity
Form endpointsFor each form, note whether it is a native form or a site form posting to a form handler or API endpoint, and whether that endpoint still exists. Old form handlers keep accepting posts long after they were meant to be switched off. Reporting accuracy
The tracking scriptConfirm Munchkin, the HubSpot tracking code or the Account Engagement tracking code is on every page, including pages built outside the CMS. Pages without it drop out of source data while every report still runs. Reporting accuracy

Boundaries

What we will not do in a HubSpot engagement

Each line below gets promised in sales conversations and then found to be untrue during the build, so each is said here first.

Convert workflows automatically. There is no export format another platform can consume. A HubSpot workflow holds enrolment, branching, delays, actions and re-enrolment in one object, and the mapping out of it is one-to-many. The rebuild is done by hand and treated as a redesign.
Rebuild HubSpot scoring as it stands. Scoring models are not portable between platforms: a two-dimensional profile and engagement grid does not map onto a single score field, and behavioural decay is modelled differently in each platform. HubSpot holds one score property covering behaviour and fit together, so the criteria get split before anything is built, and the thresholds are agreed with sales.
Carry email engagement history out of the portal. Activity history mostly stays behind: opens, clicks, form fills and page views remain in the old platform, so every report or scoring rule with a lookback window restarts at cutover. Plan for a reporting gap at the cutover date and keep the portal readable for a defined period if the contract allows.
Recover anonymous browsing history. Anonymous web history restarts at cutover: the old platform’s visitor cookie and the new one’s are unrelated, so a known person’s pre-cutover browsing does not follow them and their behaviour history starts the day the new tracking script goes live. No connector recovers it, so the baseline reports come out of HubSpot before it is switched off.
Treat one contact per email address as a clean database. HubSpot keeps a single contact per email address, which hides the duplicate a person creates under a second address. The audit looks for the same person under another address instead of counting matching ones.
Claim a platform nobody here is certified in. The certifications are Adobe Marketo Engage, HubSpot, Salesforce, Account Engagement (Pardot), Salesforce Marketing Cloud and Oracle Eloqua. If you run Dynamics 365, Klaviyo or anything else, say so on the first call and we will tell you whether we have worked in it.

Questions

About HubSpot engagements

Can HubSpot workflows be migrated to another platform automatically?

No. There is no export format another marketing platform can consume, and the mapping is one-to-many. In Account Engagement a single workflow becomes some combination of an automation rule, a completion action on the asset, a page action, a dynamic list and an Engagement Studio program. In Marketo it becomes smart campaigns inside a programme, channel and token structure designed up front. The rebuild is manual and it should be a redesign.

Does HubSpot allow duplicate contacts?

HubSpot keeps one contact per email address, so the database looks cleaner than it is. The duplicate to look for is the same person under a second address, which is why the audit counts duplicates by email address in Marketo and Account Engagement and searches for second addresses in HubSpot. Note which system created each copy while you are there.

Does activity history migrate between marketing automation platforms?

People, field values and list membership come across with an export and a field map. Activity history mostly stays behind: opens, clicks, form fills and page views remain in the old platform, so every report or scoring rule with a lookback window restarts at cutover. Export the history your reports depend on to a warehouse or the CRM, keep the old instance readable until they are rebuilt, and warn whoever owns the dashboards before the first report lands.

Should we move from HubSpot to Marketo, or from Marketo to HubSpot?

Both moves are on our track record and the reasons differ. HubSpot to Marketo is usually made because scale or complexity outgrew the original platform, and it needs the programme, channel and token structure designed up front. Marketo to HubSpot is a move to a more opinionated platform, where some logic consolidates and some is deliberately dropped, and deciding which is a conversation with the people who own the programmes.

Can two HubSpot portals feed one Salesforce org?

Yes, and we have built it. Two marketing databases writing into a single CRM without overwriting each other needs field-level ownership, deduplication across both sources, and sync rules that make it obvious which instance a record came from. Record which system wins for every field more than one of them writes, Lead Source included.

How is HubSpot work priced?

One of four ways: a fixed price for a defined scope, hourly for consultative or variable work, a monthly retainer for ongoing operations support, or a quarterly retainer for strategic programmes. Discovery calls and the initial system audit are free. How many workflows are still live and how many forms still take submissions set most of the scope.

Last updated 24 October 2026

Running HubSpot?

Count the live workflows first

Pull the last-run date for every workflow and the submissions per form by month. Those two lists tell you what you are keeping, and they are the first thing we ask for.

Discuss a HubSpot project Use the audit checklist

Marketo consultancy Account Engagement (Pardot) consultancy HubSpot to Pardot migration How we run a migration