Marketo to HubSpot migration guide

Migrate what's running, not everything you ever built.Inventory every smart campaign by API in an afternoon, retire most of them, and cut over Salesforce and email before the Marketo renewal.

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.

1,000 Smart campaigns Status unknown until you open each one. Pulled in 5 API calls (200 per page), status included.
  • Webinar > Registered > ConfirmEvent program · batchScheduled for first run
  • Nurture > Q3 Stream 2 > AdvanceEngagement program · triggerScheduled for first run
  • OPS > Lead Router > SFDC AssignOperational · triggerScheduled for first run
  • + 997 moreOpen each one to refresh its status?
Never run214 Inactive, no sends in 12 mo398 Active trigger236 Recurring batch64 One-time batch, ran88 Of these, write to Salesforce41
652Retire
291Rebuild as 146 workflows
57Redesign as nurture
No inventory, no plan. At about 2.5 minutes per campaign, opening all 1,000 is 40+ hours of clicking.
146 of 300 workflows on Marketing Hub Professional. The rebuild fits, with room to grow.
Why migrations stall

The tool swap is easy. The inventory is not.Most Marketo to HubSpot projects stall in week two, when the team tries to list what's actually running and the UI won't tell them.

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 hrs

Open each campaign so its status refreshes, then copy it into a sheet.

1,000 campaigns × ~2.5 min each

By the Asset API

5 calls

Page 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

01

"Scheduled for first run" doesn't mean anything

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.

02

1,000 campaigns, 300 workflows

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.

03

Marketo constructs don't map 1:1

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.

04

Hidden automation does the real work

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.

05

The deadline is set by Salesforce and deliverability, not asset count

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.

What good looks like

Measure the migration, not just the launch.Four hard limits frame the plan. The table shows where teams land when they inventory first and when they don't.

300Workflows on Marketing Hub Professional (1,000 on Enterprise)HubSpot Workflows FAQ, 2026
40Days for HubSpot's managed dedicated IP warm-upHubSpot KB, 2026
30–50%Of a mid-market Marketo program library that can be retiredPedowitz Group, 2026
0.3%Gmail spam rate that triggers hard rejectionsGoogle enforcement via GMass, 2026

Benchmarks: weak, acceptable, strong

MetricWeakAcceptableStrong
Program library retired before rebuild<15% (lift-and-shift)30–50%>50%, backed by 12-month usage evidence
Person records left out of the migration0% (migrate everything)20–40% inactive, bounced or suspendedRule-based exclusion with a CSV archive outside HubSpot
Timeline, mid-market (50K–200K contacts, 20–40 active programs)>16 weeks10–16 weeks8–10 weeks with logic documented up front
Starting without documented Marketo logic+4–6 weeksDocumented during rebuildInventory and triage done in week 1–2
Parallel run (both platforms live)>4 weeks: data-quality problems2–4 weeks≤3 weeks with a hard freeze date
Dedicated IP warm-up startAfter cutover40 days before cutover6+ weeks before, engaged contacts first
Spam complaint rate (Gmail)≥0.3%: 5xx rejections0.1–0.3%: throttling risk<0.1%
Lead-score parity after rebuild>60 days, or scores reset to zero30–60 daysImported 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.

The step-by-step playbook

Ten steps from 1,000 unknowns to a clean cutover.Date math first, then the API inventory, triage, mapping, rebuild, data, Salesforce, deliverability and the cutover itself. Each step names the endpoint, object or setting.

  1. 01

    Work backward from the renewal date

    What

    Fix the latest date for each phase before anyone rebuilds an email.

    Why it matters

    IP warm-up and the parallel run are calendar time. Extra people can't shorten them.

    T−12 wksAPI inventory, triage signed off
    T−9 wksDomain auth live; dedicated IP DNS + first send
    T−5 wksMarketo SFDC sync off; HubSpot connector on
    T−4 wksParallel run: new inbound on HubSpot only
    T−1 wkFreeze, final delta, Marketo read-only
    • Ask Adobe in writing whether a 30–60 day extension or month-to-month term exists. If it does, you can phase scope instead of cutting it.
    • Budget 2 weeks of buffer before the renewal date. Exports and fixes always run long.
  2. 02

    Pull the smart campaign inventory by API

    What

    One CSV row per smart campaign with type, status and flags, without opening a single campaign.

    Why it matters

    The Asset API returns status directly, so the stale "Scheduled for first run" icon stops mattering.

    • Create an API-only user with an API role (Admin > Users & Roles), then a custom service in Admin > LaunchPoint to get a client ID and secret. The REST endpoint is under Admin > Web Services.
    • Page 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.
    • Fields returned: id, name, type (batch or trigger), status, isActive, isRequestable, isSystem, isCommunicationLimitEnabled, recurrence, folder, workspace, smartListId, flowId, computedUrl, updatedAt.
    • Need the triggers and filters? GET /rest/asset/v1/smartCampaign/{id}/smartList.json?includeRules=true. Limits: 50,000 calls a day, 100 per 20 seconds, 10 concurrent.
    Python 3 · requests · writes smart_campaigns.csv
    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")
  3. 03

    Inventory every other asset, then add usage evidence

    What

    Programs, emails, landing pages, forms, lists and tokens in the same sheet, joined to 12 months of activity.

    Why it matters

    "Active" in Marketo is a setting. "Sent mail in the last year" is evidence.

    • Same paging pattern: programs.json (type, channel, status), emails.json, landingPages.json, forms.json, smartLists.json, staticLists.json. My.tokens: folder/{id}/tokens.json?folderType=Program.
    • Join each campaign to its program with the folder ID (folder type Program).
    • Evidence: Bulk Extract activities (/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.
    • Bulk limits: 31 days per job, 500 MB a day, 2 jobs processing, 10 queued. Twelve months takes 12 jobs, so start on day one.
  4. 04

    Triage: retire, keep, rebuild or redesign

    What

    Every row gets one decision and one owner.

    Why it matters

    Each row you retire saves rebuild, QA and maintenance hours.

    • Retire if never run, no sends or members in 12 months, email open rate under 5% and clicks under 1%, or under 50 members with none new in 90 days (Pedowitz thresholds).
    • Rebuild operational logic first: form processors, routing, lifecycle, scoring, Salesforce write-backs, unsubscribe handling.
    • Redesign engagement programs and anything built on my.tokens. They change shape in HubSpot.
    • Consolidate as you go: 10 near-identical "form fill > add to list" campaigns become one workflow branched by form.
  5. 05

    Map every Marketo construct to its HubSpot equivalent

    What

    A design decision for each construct, written down before building.

    Why it matters

    Rebuild decision logic, not folder structure. If HubSpot looks exactly like Marketo, nothing improved.

    MarketoHubSpotFitDesign note
    Program + channelCampaign + folder and naming conventionRebuildChannel becomes a campaign property. Program statuses become campaign membership plus a status property.
    Smart campaign (trigger)Contact workflow with event triggersRebuildMax 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 sendRebuildRecurring batches often become real-time workflows. Check that's what sales wants.
    Smart list / static listActive / static segmentDirectHubSpot renamed lists to Segments in 2025. Smart list membership history doesn't migrate.
    Engagement programWorkflow with delays, branches and goalsRedesignNo cadence or stream engine. Use lifecycle-state branches and a goal to exit.
    My.tokens (program-scoped)Personalization tokens, snippets, modules, propertiesRedesignHubSpot tokens are contact-, company- or owner-scoped. Program values become properties set by workflow or module fields.
    Dynamic content / VelocitySmart content / HubL, programmable emailRebuildSmart content rules key off segments, lifecycle, country or device. Programmable email needs Enterprise.
    Lead scoringLead Scoring tool: fit, engagement, combinedRebuildThe legacy HubSpot Score property stopped updating Aug 31, 2025. Import a "Marketo score at migration" baseline.
    Revenue Cycle ModelerLifecycle stage + Lead object + date-entered propertiesRedesignLifecycle is linear. Multi-track models need extra properties or the Lead object (Sales Hub Pro+).
    Communication limitsSend frequency cap / suppression segmentRebuildFrequency 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 emailsTransactional email add-on, or a dedicated subscription typeRedesignHubSpot won't bypass opt-outs for marketing email. Truly transactional mail needs the add-on.
    Forms: hidden fields, progressive profilingForms with hidden fields, queued progressive fields, smart fieldsDirectConsolidate to one master form per purpose. Hidden fields carry UTMs and click IDs.
    Landing pages and email templatesTheme-based pages and drag-and-drop emailsRebuildMarketo template HTML doesn't render. 301-redirect old LP URLs to the new pages.
    Workspaces / partitionsTeams, or the Brands add-onRedesignBrands requires Enterprise. Partitions become team-based permissions.
  6. 06

    Rebuild nurtures and email ops as structure, not copies

    What

    Audit the email infrastructure, then rebuild nurture as lifecycle-driven workflows.

    Why it matters

    Marketo nurtures run on snapshots and cadence. HubSpot evaluates conditions in real time, so copied nurtures enroll people who never advance.

    • Audit first: subscription categories, operational vs. marketing flags, Communication Limits settings ("Block non-operational emails" must be checked), and which campaigns had isCommunicationLimitEnabled off.
    • One workflow per nurture track. Enroll on lifecycle plus fit. Delays between sends, if/then branches on engagement, a goal segment that removes converters. Example: "Lifecycle = MQL for 3 days > send email 2."
    • Replace stream transitions with branches on a property such as nurture_track, set by the same workflow.
    • Subscription types by category: newsletter, product updates, events, nurture. Map Marketo unsubscribed to "opt out of all email."
  7. 07

    Move people, consent and the history you can keep

    What

    Clean person records, consent and a deliberate slice of history.

    Why it matters

    Opens, clicks and visits don't become native HubSpot engagement events. Plan for that before access ends.

    • Import suppression and opt-outs first, before any contact can be emailed.
    • Migrate fields populated on more than ~10% of records. Exclude bounced, suspended and long-inactive records (typically 20–40%), but archive them as a CSV.
    • Set marketing contact status on import. Customers-only and ex-customers can be non-marketing; switching existing ones takes effect at your next update date.
    • History: store 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.
  8. 08

    Cut over Salesforce so only one platform writes at a time

    What

    A fixed order for turning one sync off and the other on.

    Why it matters

    Two marketing platforms writing to the same leads cause field loops, duplicates and routing errors.

    1. 1 · ListEvery SFDC field and campaign the Marketo sync user writes
    2. 2 · SandboxHubSpot connector tested against a Salesforce sandbox
    3. 3 · InstallProduction install with a near-empty inclusion segment
    4. 4 · StopMarketo sync off (Admin > CRM > Salesforce); SFDC-writing campaigns deactivated
    5. 5 · ExpandWiden the inclusion segment in waves; watch sync errors
    6. 6 · CampaignsMap member statuses; use the "Set Salesforce campaign" action
    7. 7 · UsersDeactivate the Marketo sync user and remove its packages last
    8. 8 · CertifyCreate a lead, change lifecycle, fire an alert: all three pass
    • The connected Salesforce user must be a system admin with API Enabled, View Setup and Modify All on synced objects. Use a dedicated integration user.
    • The inclusion segment must be an active segment. Records outside it don't sync to Salesforce, but anything already paired can update on its first sync.
    • Budget API calls: one contact sync can use up to 4 Salesforce API calls. Details in our HubSpot Salesforce integration guide.
  9. 09

    Authenticate, warm and protect deliverability

    What

    Domain auth and IP warm-up running weeks before the first real campaign.

    Why it matters

    New infrastructure has no reputation. Since November 2025, Gmail rejects non-compliant bulk mail outright.

    • Connect the sending domain: SPF include, DKIM CNAMEs, DMARC at p=none or stronger with alignment. Add one-click unsubscribe and honor unsubscribes within 2 days.
    • Dedicated IP only for high, steady volume (a common rule of thumb is 50K–100K+ emails a month). It's an add-on on Pro or Enterprise, needs A, MX (priority 0), TXT and CNAME records, and warms over 40 days. The warm-up pauses after 7 days with no sends.
    • Otherwise stay on HubSpot's shared IPs and warm the domain: send to the last 90 days' engaged contacts first, then widen weekly.
    • Targets: spam complaints under 0.1%, never 0.3%. Run an email deliverability audit before the first big send.
  10. 10

    Run in parallel, freeze, cut over, then hypercare

    What

    A 2–4 week overlap with a hard freeze date and a rollback plan.

    Why it matters

    Overlaps longer than 4 weeks almost always create data-quality problems and double sends.

    • Route new inbound to HubSpot first. Suppress HubSpot-mailed segments in Marketo so nobody gets both.
    • Swap Munchkin for the HubSpot tracking code, repoint form embeds, and 301-redirect Marketo landing page URLs.
    • Freeze, run a final delta import, then set Marketo to read-only. Export activity logs, program members and reports before access ends.
    • Hypercare for 30–60 days. Review workflow error logs weekly (kept 90 days) and calibrate scores against known MQLs.

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.

Best practices

Twelve rules that keep the deadline honest.If you adopt only one, make it the first: never open campaigns by hand to build the inventory.

  1. 1

    Inventory by API in week one. Smart campaigns, programs, emails, pages, forms, lists and tokens in one sheet.

  2. 2

    Join evidence before you triage. Last send date and 12-month members beat any "active" flag.

  3. 3

    Default to retire. Every keep needs an owner and a reason.

  4. 4

    Rebuild decision logic first: lifecycle, routing, scoring and sync write-backs, then content.

  5. 5

    Move suppression and opt-outs before any contact. Compliance first, not last.

  6. 6

    Only one platform writes to Salesforce at a time. Marketo sync off, then widen HubSpot's inclusion segment.

  7. 7

    Start domain auth and IP warm-up 6+ weeks before cutover. It's calendar time.

  8. 8

    Carry a score baseline and decay it over 30 days while the new model learns.

  9. 9

    Consolidate forms to one master form per purpose with hidden fields and smart fields.

  10. 10

    Cap the parallel run at 4 weeks and publish the freeze date to every team.

  11. 11

    Certify every integration: create a contact, change lifecycle, trigger an alert.

  12. 12

    Export everything before access ends: activity logs, program members and reports.

Common mistakes

Six shortcuts that cost you the deadline.Each looks faster in week one and costs more after go-live.

Lift-and-shift every campaign

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.

Two platforms syncing to Salesforce

Marketo's sync left on "just in case" while HubSpot starts writing.

CostDuplicate leads, fields overwriting each other, and reps routed the wrong records.

Migrating every person record

Bounced, suspended and five-year-inactive records imported as marketing contacts.

CostA higher contact tier and worse engagement rates on new infrastructure.

Warm-up after cutover

The dedicated IP is connected the week the first newsletter goes out.

CostThrottling and spam-folder placement in launch month, when leadership is watching.

Copying nurtures stream for stream

Engagement programs rebuilt as snapshot-enrolled workflows.

CostContacts enroll and never advance. Nurture goes quiet with no errors.

Letting scores reset to zero

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.

Interactive estimator

Will it fit before the renewal?Enter your Marketo counts and capacity. The estimator converts them into rebuild hours and weeks, then checks both against your deadline and HubSpot's workflow limit.

Migration scope & deadline estimator

Change any input; every output updates.

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.

Verdict

At risk: cut scope or add capacity

  • Calculating…
0total migration hours
0weeks needed at your capacity
0hours per week to hit the deadline
0%retire rate that fits your current capacity

HubSpot workflows after consolidation0 of 300

Weeks needed, by phase0 weeks

Weeks you have10 weeks

Inventory & triageRebuild & QAData, Salesforce & email setupParallel run & cutover

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.

Copyable templates

Copy the inventory sheet and cutover runbook.Three tables, tab-separated, ready to paste into Google Sheets or Excel.

Copies all three tables as tab-separated text.

AMigration inventory column spec

ColumnSourceExampleUsed for
asset_typeWhich endpointsmart_campaign, program, email, landing_page, form, smart_list, static_list, tokenFiltering and effort rates
marketo_id / nameAPI id, name4821 / OPS > Lead Router > SFDC AssignTraceability
program_id / program_type / channelfolder.id > programs.json1093 / event / WebinarGrouping into HubSpot campaigns
workspaceworkspaceDefaultTeams or Brands design
campaign_type / statustype, statustrigger / ActiveTriage rules
is_active / is_requestable / comm_limitsisActive, isRequestable, isCommunicationLimitEnabledTRUE / FALSE / TRUEDependencies and email-ops audit
recurrencerecurrenceweekly, weekdayOnlyBatch vs. real-time decision
last_updatedupdatedAt2024-03-11Staleness
last_activity_date / sends_12mo / members_12moBulk Extract activities2025-12-02 / 14,300 / 2,140Usage evidence
writes_to_sfdcFlow steps (Sync to SFDC, Change Owner, SFDC campaign)TRUESalesforce cutover list
depends_on / used_byManual + smart list rulesRequested by: Webinar ConfirmDon't retire a dependency
business_ownerManualDemand gen leadSign-off
triage_decisionRules in table BRetire / Keep / Rebuild / RedesignScope
hubspot_targetMapping in step 5Workflow: Lead routing (branch by region)Build list
effort_hrs / wave / statusEstimate1.25 / Wave 1 / Built, QA passedPlan and burn-down

BTriage rules

DecisionRule (first match wins)HubSpot outcome
Keep (operational)Writes to Salesforce, routes leads, processes forms, sets lifecycle or score, handles unsubscribesRebuild first, in Wave 1, with QA tests
RetireStatus Never Run, or no sends or members in 12 monthsNot built; listed in the archive tab
RetireEmail open rate under 5% and click rate under 1% over 12 monthsNot built
RetireUnder 50 members and no new members in 90 daysNot built
RetireLanding page under 50 visits in 12 months301 redirect to the closest live page
RedesignEngagement program, my.tokens-driven program or dynamic contentNew workflow or module design
RebuildEverything else with evidence of useConsolidated workflow, segment, email or page

CCutover runbook

WhenTaskOwnerDone when
T−12 wksAPI inventory and usage evidence; triage signed offMOPs leadEvery row has a decision and an owner
T−10 wksProperties, subscription types, lifecycle and lead scoring designedRevOpsMapping doc approved
T−9 wksSending domain authenticated; dedicated IP DNS live and first sendMOPs + ITSPF, DKIM and DMARC pass; warm-up started
T−8 wksSuppression lists and opt-outs importedMOPsCounts match Marketo
T−7 wksWave 1 operational workflows built and testedHubSpot devTest contacts pass every branch
T−6 wksHubSpot connector tested in a Salesforce sandboxSalesforce adminNo sync errors on test set
T−5 wksPerson records imported; Marketo SFDC sync off; HubSpot inclusion segment widenedSalesforce adminOne platform writing to Salesforce
T−4 wksParallel run: new inbound to HubSpot, Marketo suppressed for the same segmentsMOPsNo double sends
T−2 wksTracking code swap, form embeds repointed, LP redirects liveWebForms submit to HubSpot only
T−1 wkFreeze, final delta import, Marketo read-only, full exports savedMOPs leadExports stored outside both platforms
T+30 daysHypercare: workflow errors, sync errors, score calibration, spam rateRevOpsSpam rate under 0.1%; MQL volume within 15% of baseline
FAQ

What marketing ops teams ask mid-migration.Direct answers, current as of October 2026. Click a question to open it.

Campaign Inspector shows hundreds of campaigns as "Scheduled for First Run" and won't refresh until I open each one. How do I get a real inventory?

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.

Can we finish a Marketo to HubSpot migration before a December renewal?

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.

What can't we migrate from Marketo?

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.

How do engagement programs translate to HubSpot?

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.

When do we turn off the Marketo Salesforce sync?

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.

Do we need a dedicated IP in HubSpot?

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.

We have 80–120 contractor hours. What should they go to?

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.

How JayOh does it

We migrate the system, not the folders.A JayOh pod of a RevOps consultant, a HubSpot developer and a Salesforce developer runs the migration in weekly sprints, with the inventory done in week one.

01

API inventory in week one

Every smart campaign, program, email, page, form and token pulled by API and joined to 12 months of activity. Nobody opens 1,000 campaigns.

02

Evidence-based triage

Rules-first triage with a named owner for every keep. Most mature instances retire well over half the library.

03

Decision logic before content

Lifecycle, routing, scoring and Salesforce write-backs are rebuilt and tested first, then nurtures, emails and pages.

04

One writer to Salesforce at a time

A sequenced connector cutover with a sandbox test, inclusion-segment waves and a certification test for every integration.

05

Deliverability from day one

Domain auth, warm-up and suppression start in week one, so launch-month sends land in the inbox.

06

A short parallel run with a freeze

Two to three weeks of overlap, a published freeze date, full exports, then 30–60 days of hypercare.

40+Marketing automation migrations
60–90Day go-lives on complex migrations
90%Fewer data errors
4→2Platforms consolidated post-merger in 90 days

Related: HubSpot migration services · Marketo consulting · Migration cost & timeline · HubSpot Salesforce integration

Get your migration plan checked before the renewal date is locked.

Send us your counts. We'll review the inventory, triage, Salesforce cutover order and warm-up plan, and tell you what fits your deadline.

Get in touch