A 1,000-campaign instance won't fit a 300-workflow HubSpot portal. The fix is a real inventory, ruthless triage, and a cutover plan built backward from your deadline.
Start here: step 2 has the API script.
Smart campaign inventoryNorthwind · Marketo Engage · renewal Dec 31
Toggle to compare the UI view with an inventory pulled from the Asset API.
You can't triage what you can't see.
Campaign Inspector was never built to count 1,000 campaigns.
By hand in the UI
42 hrsOpen each campaign so its status refreshes, then copy it into a sheet.
1,000 campaigns × ~2.5 min each
By the Asset API
5 callsPage through smartCampaigns.json 200 at a time with type, status and flags.
1,000 ÷ 200 per page = 5 requests, well under the 50,000/day quota
Campaign Inspector status icons go stale for timed, run-once campaigns. Marketo's own ideas board confirms they keep the "pending execution" icon after they've run. So the list says hundreds are scheduled when most are dead.
Marketing Hub Professional allows up to 300 workflows; Enterprise allows 1,000. A lift-and-shift of a mature Marketo instance doesn't fit, so triage is mandatory, not a nice-to-have.
Program-scoped my.tokens, engagement streams, program statuses, Revenue Cycle Modeler and communication limits all change shape in HubSpot. Each needs a design decision, not an export.
A triggered campaign that bumps priority after webinar attendance, or writes a Salesforce field that drives routing, breaks silently weeks after go-live if nobody listed it.
A dedicated IP takes 40 days to warm in HubSpot. Two marketing platforms can't safely write to Salesforce at once. Those two constraints fix your latest start date, however fast you rebuild emails.
Benchmarks: weak, acceptable, strong
| Metric | Weak | Acceptable | Strong |
|---|---|---|---|
| Program library retired before rebuild | <15% (lift-and-shift) | 30–50% | >50%, backed by 12-month usage evidence |
| Person records left out of the migration | 0% (migrate everything) | 20–40% inactive, bounced or suspended | Rule-based exclusion with a CSV archive outside HubSpot |
| Timeline, mid-market (50K–200K contacts, 20–40 active programs) | >16 weeks | 10–16 weeks | 8–10 weeks with logic documented up front |
| Starting without documented Marketo logic | +4–6 weeks | Documented during rebuild | Inventory and triage done in week 1–2 |
| Parallel run (both platforms live) | >4 weeks: data-quality problems | 2–4 weeks | ≤3 weeks with a hard freeze date |
| Dedicated IP warm-up start | After cutover | 40 days before cutover | 6+ weeks before, engaged contacts first |
| Spam complaint rate (Gmail) | ≥0.3%: 5xx rejections | 0.1–0.3%: throttling risk | <0.1% |
| Lead-score parity after rebuild | >60 days, or scores reset to zero | 30–60 days | Imported baseline that decays over 30 days |
| Workflows used vs. tier limit after consolidation | >90% | 50–80% | <50% |
Sources: Pedowitz Group, Marketo to HubSpot Migration: What to Preserve, Rebuild and Leave Behind (2026); SyncMatters, Marketo to HubSpot Migration (2026); Meticulosity, Marketo to HubSpot mapping (2026); RevOps Global, Migrating 500K Contacts (2025); HubSpot Knowledge Base: dedicated IP and Workflows FAQ (2026); GMass summary of Google bulk-sender enforcement, Nov 2025 (2026). "Workflows used vs. tier limit" bands are JayOh practitioner guidance, not a published study.
Fix the latest date for each phase before anyone rebuilds an email.
IP warm-up and the parallel run are calendar time. Extra people can't shorten them.
One CSV row per smart campaign with type, status and flags, without opening a single campaign.
The Asset API returns status directly, so the stale "Scheduled for first run" icon stops mattering.
GET /rest/asset/v1/smartCampaigns.json?maxReturn=200&offset=0 until a page returns fewer than 200 rows. Send the token in an Authorization: Bearer header.id, name, type (batch or trigger), status, isActive, isRequestable, isSystem, isCommunicationLimitEnabled, recurrence, folder, workspace, smartListId, flowId, computedUrl, updatedAt.GET /rest/asset/v1/smartCampaign/{id}/smartList.json?includeRules=true. Limits: 50,000 calls a day, 100 per 20 seconds, 10 concurrent.import csv, requests
BASE = "https://123-ABC-456.mktorest.com" # Admin > Web Services > REST API endpoint
tok = requests.get(BASE + "/identity/oauth/token", params={
"grant_type": "client_credentials",
"client_id": "YOUR_CLIENT_ID", "client_secret": "YOUR_CLIENT_SECRET"}).json()["access_token"]
H = {"Authorization": "Bearer " + tok}
rows, offset = [], 0
while True:
r = requests.get(BASE + "/rest/asset/v1/smartCampaigns.json", headers=H,
params={"maxReturn": 200, "offset": offset}).json()
batch = r.get("result", []) # empty when no more assets
rows += batch
if len(batch) < 200:
break
offset += 200
cols = ["id", "name", "type", "status", "isActive", "isRequestable",
"isCommunicationLimitEnabled", "updatedAt", "computedUrl"]
with open("smart_campaigns.csv", "w", newline="") as f:
w = csv.writer(f)
w.writerow(cols + ["folderId", "folderType", "recurrence"])
for c in rows:
fo = c.get("folder") or {}
w.writerow([c.get(k) for k in cols] + [fo.get("id"), fo.get("type"), c.get("recurrence")])
print(len(rows), "smart campaigns exported")
Programs, emails, landing pages, forms, lists and tokens in the same sheet, joined to 12 months of activity.
"Active" in Marketo is a setting. "Sent mail in the last year" is evidence.
programs.json (type, channel, status), emails.json, landingPages.json, forms.json, smartLists.json, staticLists.json. My.tokens: folder/{id}/tokens.json?folderType=Program.Program)./bulk/v1/activities/export/create.json) for Send Email, Fill Out Form and Visit Web Page. Confirm type IDs with /rest/v1/activities/types.json.Every row gets one decision and one owner.
Each row you retire saves rebuild, QA and maintenance hours.
A design decision for each construct, written down before building.
Rebuild decision logic, not folder structure. If HubSpot looks exactly like Marketo, nothing improved.
| Marketo | HubSpot | Fit | Design note |
|---|---|---|---|
| Program + channel | Campaign + folder and naming convention | Rebuild | Channel becomes a campaign property. Program statuses become campaign membership plus a status property. |
| Smart campaign (trigger) | Contact workflow with event triggers | Rebuild | Max 250 triggers per workflow. Turn on re-enrollment deliberately; it's off by default. |
| Smart campaign (batch / recurring) | Workflow on filter criteria, or a segment send | Rebuild | Recurring batches often become real-time workflows. Check that's what sales wants. |
| Smart list / static list | Active / static segment | Direct | HubSpot renamed lists to Segments in 2025. Smart list membership history doesn't migrate. |
| Engagement program | Workflow with delays, branches and goals | Redesign | No cadence or stream engine. Use lifecycle-state branches and a goal to exit. |
| My.tokens (program-scoped) | Personalization tokens, snippets, modules, properties | Redesign | HubSpot tokens are contact-, company- or owner-scoped. Program values become properties set by workflow or module fields. |
| Dynamic content / Velocity | Smart content / HubL, programmable email | Rebuild | Smart content rules key off segments, lifecycle, country or device. Programmable email needs Enterprise. |
| Lead scoring | Lead Scoring tool: fit, engagement, combined | Rebuild | The legacy HubSpot Score property stopped updating Aug 31, 2025. Import a "Marketo score at migration" baseline. |
| Revenue Cycle Modeler | Lifecycle stage + Lead object + date-entered properties | Redesign | Lifecycle is linear. Multi-track models need extra properties or the Lead object (Sales Hub Pro+). |
| Communication limits | Send frequency cap / suppression segment | Rebuild | Frequency cap is Enterprise-only (Settings > Marketing > Email > Send Frequency), rolling per contact. On Pro, use a "marketing email in last N days" suppression segment. |
| Operational emails | Transactional email add-on, or a dedicated subscription type | Redesign | HubSpot won't bypass opt-outs for marketing email. Truly transactional mail needs the add-on. |
| Forms: hidden fields, progressive profiling | Forms with hidden fields, queued progressive fields, smart fields | Direct | Consolidate to one master form per purpose. Hidden fields carry UTMs and click IDs. |
| Landing pages and email templates | Theme-based pages and drag-and-drop emails | Rebuild | Marketo template HTML doesn't render. 301-redirect old LP URLs to the new pages. |
| Workspaces / partitions | Teams, or the Brands add-on | Redesign | Brands requires Enterprise. Partitions become team-based permissions. |
Audit the email infrastructure, then rebuild nurture as lifecycle-driven workflows.
Marketo nurtures run on snapshots and cadence. HubSpot evaluates conditions in real time, so copied nurtures enroll people who never advance.
isCommunicationLimitEnabled off.nurture_track, set by the same workflow.Clean person records, consent and a deliberate slice of history.
Opens, clicks and visits don't become native HubSpot engagement events. Plan for that before access ends.
mkto_last_engagement_date, mkto_score_at_migration and mkto_program_history. For customers, open opportunities and recent MQLs, import 12 months of milestones as notes or custom events.A fixed order for turning one sync off and the other on.
Two marketing platforms writing to the same leads cause field loops, duplicates and routing errors.
Domain auth and IP warm-up running weeks before the first real campaign.
New infrastructure has no reputation. Since November 2025, Gmail rejects non-compliant bulk mail outright.
p=none or stronger with alignment. Add one-click unsubscribe and honor unsubscribes within 2 days.A 2–4 week overlap with a hard freeze date and a rollback plan.
Overlaps longer than 4 weeks almost always create data-quality problems and double sends.
Coming from Pardot instead? The sequence is the same, but the asset map differs. See the Pardot to HubSpot migration guide. For budget ranges by instance size, see CRM migration cost and timeline.
Inventory by API in week one. Smart campaigns, programs, emails, pages, forms, lists and tokens in one sheet.
Join evidence before you triage. Last send date and 12-month members beat any "active" flag.
Default to retire. Every keep needs an owner and a reason.
Rebuild decision logic first: lifecycle, routing, scoring and sync write-backs, then content.
Move suppression and opt-outs before any contact. Compliance first, not last.
Only one platform writes to Salesforce at a time. Marketo sync off, then widen HubSpot's inclusion segment.
Start domain auth and IP warm-up 6+ weeks before cutover. It's calendar time.
Carry a score baseline and decay it over 30 days while the new model learns.
Consolidate forms to one master form per purpose with hidden fields and smart fields.
Cap the parallel run at 4 weeks and publish the freeze date to every team.
Certify every integration: create a contact, change lifecycle, trigger an alert.
Export everything before access ends: activity logs, program members and reports.
All 1,000 campaigns treated as in scope because nobody could prove which were dead.
CostBlows past the 300-workflow Pro limit and spends weeks rebuilding logic nobody uses.
Marketo's sync left on "just in case" while HubSpot starts writing.
CostDuplicate leads, fields overwriting each other, and reps routed the wrong records.
Bounced, suspended and five-year-inactive records imported as marketing contacts.
CostA higher contact tier and worse engagement rates on new infrastructure.
The dedicated IP is connected the week the first newsletter goes out.
CostThrottling and spam-folder placement in launch month, when leadership is watching.
Engagement programs rebuilt as snapshot-enrolled workflows.
CostContacts enroll and never advance. Nurture goes quiet with no errors.
The new HubSpot model starts from nothing the morning after cutover.
CostAn MQL drought, or a flood, and a sales team that stops trusting marketing.
30–50% is typical; mature instances often retire more.
Everyone working on the migration combined.
HubSpot tier
Sets the workflow limit: 300 or 1,000.
Dedicated IP?
Dedicated adds a fixed 40-day warm-up.
At risk: cut scope or add capacity
HubSpot workflows after consolidation0 of 300
Weeks needed, by phase0 weeks
Weeks you have10 weeks
Illustrative planning math (JayOh practitioner guidance, not a quote). Kept smart campaigns consolidate 2:1 into workflows at 1.25 h each; programs 0.5 h; emails 0.5 h; landing pages 1.5 h; forms consolidate 3:1 at 1 h; QA adds 25% of rebuild. Fixed work: inventory 16 h + 1 h per 100 campaigns, templates and theme 24 h, data and consent 16 h + 4 h per 25K records, Salesforce cutover 32 h, deliverability 8 h, scoring and lifecycle 16 h. Parallel run and cutover take 3 calendar weeks; a dedicated IP adds a 40-day warm-up that must start 6 weeks before cutover.
Copies all three tables as tab-separated text.
AMigration inventory column spec
| Column | Source | Example | Used for |
|---|---|---|---|
| asset_type | Which endpoint | smart_campaign, program, email, landing_page, form, smart_list, static_list, token | Filtering and effort rates |
| marketo_id / name | API id, name | 4821 / OPS > Lead Router > SFDC Assign | Traceability |
| program_id / program_type / channel | folder.id > programs.json | 1093 / event / Webinar | Grouping into HubSpot campaigns |
| workspace | workspace | Default | Teams or Brands design |
| campaign_type / status | type, status | trigger / Active | Triage rules |
| is_active / is_requestable / comm_limits | isActive, isRequestable, isCommunicationLimitEnabled | TRUE / FALSE / TRUE | Dependencies and email-ops audit |
| recurrence | recurrence | weekly, weekdayOnly | Batch vs. real-time decision |
| last_updated | updatedAt | 2024-03-11 | Staleness |
| last_activity_date / sends_12mo / members_12mo | Bulk Extract activities | 2025-12-02 / 14,300 / 2,140 | Usage evidence |
| writes_to_sfdc | Flow steps (Sync to SFDC, Change Owner, SFDC campaign) | TRUE | Salesforce cutover list |
| depends_on / used_by | Manual + smart list rules | Requested by: Webinar Confirm | Don't retire a dependency |
| business_owner | Manual | Demand gen lead | Sign-off |
| triage_decision | Rules in table B | Retire / Keep / Rebuild / Redesign | Scope |
| hubspot_target | Mapping in step 5 | Workflow: Lead routing (branch by region) | Build list |
| effort_hrs / wave / status | Estimate | 1.25 / Wave 1 / Built, QA passed | Plan and burn-down |
BTriage rules
| Decision | Rule (first match wins) | HubSpot outcome |
|---|---|---|
| Keep (operational) | Writes to Salesforce, routes leads, processes forms, sets lifecycle or score, handles unsubscribes | Rebuild first, in Wave 1, with QA tests |
| Retire | Status Never Run, or no sends or members in 12 months | Not built; listed in the archive tab |
| Retire | Email open rate under 5% and click rate under 1% over 12 months | Not built |
| Retire | Under 50 members and no new members in 90 days | Not built |
| Retire | Landing page under 50 visits in 12 months | 301 redirect to the closest live page |
| Redesign | Engagement program, my.tokens-driven program or dynamic content | New workflow or module design |
| Rebuild | Everything else with evidence of use | Consolidated workflow, segment, email or page |
CCutover runbook
| When | Task | Owner | Done when |
|---|---|---|---|
| T−12 wks | API inventory and usage evidence; triage signed off | MOPs lead | Every row has a decision and an owner |
| T−10 wks | Properties, subscription types, lifecycle and lead scoring designed | RevOps | Mapping doc approved |
| T−9 wks | Sending domain authenticated; dedicated IP DNS live and first send | MOPs + IT | SPF, DKIM and DMARC pass; warm-up started |
| T−8 wks | Suppression lists and opt-outs imported | MOPs | Counts match Marketo |
| T−7 wks | Wave 1 operational workflows built and tested | HubSpot dev | Test contacts pass every branch |
| T−6 wks | HubSpot connector tested in a Salesforce sandbox | Salesforce admin | No sync errors on test set |
| T−5 wks | Person records imported; Marketo SFDC sync off; HubSpot inclusion segment widened | Salesforce admin | One platform writing to Salesforce |
| T−4 wks | Parallel run: new inbound to HubSpot, Marketo suppressed for the same segments | MOPs | No double sends |
| T−2 wks | Tracking code swap, form embeds repointed, LP redirects live | Web | Forms submit to HubSpot only |
| T−1 wk | Freeze, final delta import, Marketo read-only, full exports saved | MOPs lead | Exports stored outside both platforms |
| T+30 days | Hypercare: workflow errors, sync errors, score calibration, spam rate | RevOps | Spam rate under 0.1%; MQL volume within 15% of baseline |
Skip the UI. Call GET /rest/asset/v1/smartCampaigns.json with maxReturn=200 and page by offset. You get type, status, isActive, isRequestable and recurrence for every campaign, so 1,000 campaigns take 5 calls. Then join 12 months of Bulk Extract activity to see what actually sent.
Usually, if you start 10–12 weeks out and retire most of the library. Mid-market migrations take 10–16 weeks per Pedowitz Group (2026). The fixed constraints are a 40-day dedicated IP warm-up and a 2–4 week parallel run. Ask Adobe early about a short extension, and use the estimator above to test your numbers.
Opens, clicks and web visits don't become native HubSpot engagement events. Smart list membership history, Revenue Cycle Analytics, program performance and score history don't move either. Keep summary properties and key milestones, and export the raw activity log before your access ends.
As workflows with delays, if/then branches and a goal segment that removes people who convert. There's no stream or cadence engine, so model tracks with a property such as nurture_track and enroll on lifecycle stage plus fit. Don't copy streams one-for-one.
Right before HubSpot starts writing to Salesforce at scale. Install HubSpot with a near-empty inclusion segment, turn off Marketo's sync and its Salesforce-writing campaigns, then widen the segment in waves. Never let both platforms update the same leads.
Only with high, consistent volume; many practitioners use 50K–100K+ emails a month as the line. It's an add-on with a 40-day managed warm-up. Below that, HubSpot's shared IPs plus properly authenticated SPF, DKIM and DMARC usually perform better.
Inventory and triage (about 20 hours), the email-ops audit and subscription design (about 20), rebuilding operational workflows and scoring (about 40), and the first nurture tracks (the rest). Asset-heavy rebuilds of pages and templates usually need more hours or a second wave.
Every smart campaign, program, email, page, form and token pulled by API and joined to 12 months of activity. Nobody opens 1,000 campaigns.
Rules-first triage with a named owner for every keep. Most mature instances retire well over half the library.
Lifecycle, routing, scoring and Salesforce write-backs are rebuilt and tested first, then nurtures, emails and pages.
A sequenced connector cutover with a sandbox test, inclusion-segment waves and a certification test for every integration.
Domain auth, warm-up and suppression start in week one, so launch-month sends land in the inbox.
Two to three weeks of overlap, a published freeze date, full exports, then 30–60 days of hypercare.
Related: HubSpot migration services · Marketo consulting · Migration cost & timeline · HubSpot Salesforce integration
Send us your counts. We'll review the inventory, triage, Salesforce cutover order and warm-up plan, and tell you what fits your deadline.
We engineer growth systems. JayOh builds the RevOps architecture, GTM execution and data infrastructure that turn messy revenue operations into predictable pipeline for B2B SaaS and PE-backed teams.