Rebuilding Marketo's MQL Orchestrator as Chained HubSpot Workflows
Marketo ran the whole inbound MQL flow as one orchestrator campaign: enrichment, segmentation, scoring, a five-minute wait, then a stamp marking the record marketing-qualified. HubSpot doesn't have a single-campaign equivalent, so the chain became a suite of separate workflows. The stamp fires once inbound type reads MQL, after the same five-minute wait.
Executive Summary
Context
A global enterprise SaaS company rebuilding its Marketo instance on HubSpot depended on the process that marks a record marketing-qualified before Salesforce routing acts on it. That process had to carry over without the single campaign that used to run every step.
What We Built
We rebuilt Marketo's single orchestrator campaign as a chained suite of HubSpot workflows ending in the same MQL stamp. The stamp checks that inbound type reads MQL and that merge and test records are excluded, and fires as the orchestrator's last step after the same five-minute wait Marketo used.
Tech Stack
- HubSpot
- Salesforce
- LeanData
Not a fit if your qualification logic already runs as separate workflows rather than one orchestrator campaign.
The Challenge
Marketo held every step of MQL qualification inside one orchestrator campaign: enrichment, segmentation, scoring, a five-minute wait and the stamp itself. A separate sync step, controlled by a marketer, held the record back from Salesforce until that chain finished.
HubSpot's native Salesforce connector removes that held-back step. It syncs field by field, close to real time, the moment a field changes. So a record can reach Salesforce routing and the MQL History object before every field is populated, which the old platform's single manual sync step didn't allow.
Our Approach
We split Marketo's one campaign into a chained suite of HubSpot workflows ending in the same mql_date stamp.
The stamp fires as the last step, after the same five-minute wait, once inbound type reads MQL and merge or test records are excluded.
LeanData, the routing tool on the Salesforce side, reads mql_date and the segmentation fields HubSpot writes in order to route the lead. Because the sync runs in near real time, LeanData reads whatever the record holds at the moment it syncs.
Impact
One orchestrator campaign becomes an inspectable suite
Marketo's single campaign, which was hard to read outside its own canvas, is now a set of discrete HubSpot workflows, each holding a named piece of the enrichment-to-stamp chain.
The five-minute wait carried over unchanged
The wait step Marketo used before scoring settled carried into the HubSpot rebuild unchanged, so a timing behaviour marketers already knew didn't shift with the platform.
The stamp conditions are explicit
The stamp fires once inbound type reads MQL and merge or test records are excluded, so the conditions that qualify a record are explicit.
The sync model changes how routing sees a record
Because HubSpot's sync moves field by field in near-real time, a downstream system such as Salesforce routing can act on a record before every field is populated.
One campaign chained enrichment, segmentation, scoring, a five-minute wait and the MQL stamp, held back from Salesforce by a marketer-controlled sync step until the chain finished.
HubSpot's native connector syncs field by field in near real time, where Marketo held the record back behind a marketer-controlled sync step until the chain finished.
The rebuild stamps mql_date as the last step, after the same five-minute wait, once inbound type reads MQL and merge or test records are excluded.
LeanData, the routing tool on the Salesforce side, reads mql_date and the segmentation fields HubSpot writes in order to route the lead.
Marketo held MQL qualification in one orchestrator campaign, and a manual sync step kept the record from Salesforce until it finished. HubSpot's connector syncs field by field in near real time. Now the "mql_date" stamp fires once inbound type reads MQL and merge and test records are excluded. LeanData reads that stamp to route the lead.
FAQ
The stamp firing on time is a different question from whether every field a downstream system expects is populated when it fires. HubSpot's Salesforce sync moves field by field in near-real time, so a record can reach routing before every field is set, which the old platform's held-back sync step did not allow.
The wait sits before scoring settles, so carrying it over kept a known timing behaviour in place.
