Marketo to HubSpot Migration Guide 2026: Zero Data Loss

Marketo to HubSpot Migration Guide 2026: Zero Data Loss

Migrating from Adobe Marketo Engage to HubSpot is one of the most impactful technology decisions a B2B marketing team can make — and one of the most commonly botched. The platforms look similar from a distance: both handle email marketing, lead nurturing, scoring, and automation. But they are architecturally different, they use different terminology for almost identical concepts, and data fields between them do not map neatly without deliberate planning.

Done without a structured approach, this migration results in broken workflows, corrupted lead scoring models, missing field data, and a HubSpot instance that replicates every bad habit from the Marketo environment it replaced. Done correctly, it is an opportunity to consolidate your marketing and sales stack, reduce total cost of ownership, eliminate the technical overhead that makes Marketo expensive to operate at pace, and rebuild your automation on a platform that your entire team can use without specialist support.

This guide covers the full migration process — audit, field mapping, data export and import, workflow rebuild, lead scoring translation, Salesforce sync reconfiguration, testing, and go-live — with a complete checklist at the end. It is written from the perspective of teams that have managed this migration multiple times for enterprise B2B clients across the USA, UK, Canada, Australia, and Singapore.

---

Why Teams Migrate from Marketo to HubSpot

The drivers are consistent across every organisation that makes this switch. Marketo's operational overhead — the constant reliance on a dedicated marketing operations professional, the steep learning curve for campaign managers, the SQL-adjacent complexity of Smart List filters and programme architecture — grows disproportionate to the business value extracted from the platform as marketing teams scale and evolve.

HubSpot's appeal is its unified architecture. Marketing Hub, Sales Hub, Service Hub, and CRM all share the same database. Lead lifecycle data, campaign attribution, sales pipeline, and customer service interactions all exist in one place without integration middleware. Marketing and sales teams see the same contact timeline. Revenue attribution connects marketing campaigns directly to closed deals without custom reporting.

Additional drivers include lower total cost of ownership — HubSpot typically costs 40–60% less than a comparable Marketo deployment including admin overhead — easier team adoption without specialist training, native reporting that does not require SQL or Salesforce configuration to produce meaningful insights, and the fact that HubSpot's Professional and Enterprise tiers in 2026 now support complex custom objects, ABM tooling, and multi-touch attribution that previously required Marketo for enterprise B2B teams.

One well-documented case from a Marketo customer that migrated to HubSpot demonstrates the potential: PublicRelay unified its entire tech stack onto HubSpot and achieved 340% revenue growth following full adoption. While individual results vary, the directional trend of improved team efficiency and faster campaign execution is consistent across documented migrations.

---

The Critical Difference: How Marketo and HubSpot Think About Data

Before the first task is started, understand this conceptual difference — it shapes every field mapping and workflow rebuild decision.

Marketo is programme-based and modular. Contacts live in the Marketo database and are acted upon by Smart Campaigns. Smart Lists filter contacts based on field values and activity history. Programmes are containers for campaigns, assets, and reporting. Lead scoring runs through a dedicated Marketo scoring programme. Everything is separate and explicitly connected through logic you define.

HubSpot is object-based and unified. Contacts, companies, deals, and custom objects all share a single CRM. Properties (HubSpot's term for fields) belong to objects. Workflows trigger on object property changes, timeline activities, or form submissions. Lead scoring runs through a Contact Score property or AI-powered predictive scoring. Everything shares the same data model.

The practical implication: Marketo Smart Lists that filter on programme membership, activity history, and complex field combinations need to be reimagined as HubSpot Active Lists using HubSpot's filter logic — not directly copied. Marketo Engagement Programmes (drip nurtures) need to be rebuilt as HubSpot Workflows — not migrated. Marketo custom fields need to be created as HubSpot Contact, Company, or Deal Properties before any data is imported.

The Marketo-to-HubSpot migration is a system redesign, not a data transfer. Approach it as such and the outcome will be a cleaner, more maintainable marketing automation environment on HubSpot than you had in Marketo.

---

Marketo to HubSpot: Terminology Mapping

Use this reference throughout the migration.

---

Phase 1: Audit Your Marketo Environment (Weeks 1–2)

The audit is the most important phase and the one most migration projects underfund. Inadequate auditing produces a messy HubSpot instance that replicates Marketo's accumulated technical debt in a new environment.

Database audit: Pull a full export of your Marketo contact database. Note the total record count, the number of duplicates (run Marketo's deduplication report), the percentage of records with missing key fields, and the number of records with no engagement activity in the last 12 months. Most long-running Marketo instances have 20–40% contact records that are either duplicates, invalid, or genuinely unengaged and should not be migrated.

Automation audit: List every active Smart Campaign — document the trigger or schedule, the Smart List filter conditions, the flow steps, and whether it is currently active or inactive. Marketo instances typically have dozens of Smart Campaigns that have been running for years and are no longer relevant. Use Marketo's grey icon indicators for inactive assets to identify what can be retired. Only migrate what you are actively using.

Programme audit: List every active Engagement Programme and document the stream structure, the email cadence, the entry criteria, and the stream transition logic. These become HubSpot Workflows.

Assets audit: Catalogue email templates, landing pages, and forms — note which are actively used versus inactive. Export performance data for active assets so you have benchmarks for post-migration comparison.

Integrations audit: List every LaunchPoint integration in Marketo — Salesforce, webinar platforms (Zoom, On24, GoToWebinar), enrichment tools (Clearbit, ZoomInfo), account-based marketing tools, and any custom API integrations. Each integration needs to be reconfigured or replaced in HubSpot. Some Marketo integrations have direct HubSpot equivalents in the App Marketplace. Others require middleware or custom development.

Lead scoring audit: Document your complete lead scoring model — every demographic score, every behavioural score, every recency decay rule. Marketo's scoring model is often the most complex element to translate to HubSpot because the logic is frequently undocumented and distributed across multiple scoring programmes.

---

Phase 2: Set Up Your HubSpot Environment (Weeks 2–3)

Before importing a single contact, configure HubSpot to receive your data correctly. Setting up HubSpot before importing prevents the most common data integrity problems.

Create custom properties: For every Marketo custom field that does not have a native HubSpot equivalent — custom segmentation fields, programme membership flags, partner tier values, product interest fields — create a matching HubSpot Contact or Company property. Match the field type (text, dropdown, date, number) and, for dropdowns, create matching option values. This field creation step must be completed before import or data in those fields will be lost.

Configure lifecycle stages: HubSpot's default lifecycle stages — Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer — need to be mapped to whatever lifecycle nomenclature your Marketo instance uses. If you use custom stages in Marketo, determine whether HubSpot's standard stages are sufficient or whether custom lifecycle properties are needed.

Set up teams and user permissions: Create HubSpot users, teams, and permission sets before go-live. Marketing, sales, and operations users have different access requirements. Configure these upfront rather than after migration when they become urgent.

Install HubSpot tracking code: Install HubSpot's tracking script on your website — replacing Marketo's Munchkin tracking code. Once live, HubSpot will begin recording page view activity on all contact timeline records. Do not remove the Munchkin code from your website until HubSpot's tracking code is confirmed working.

Configure email sending domain: Set up your sending domain in HubSpot under Settings, Email, Sending Domains. Add SPF and DKIM records to your DNS. Verify domain authentication before your first HubSpot email send.

---

Phase 3: Data Export from Marketo and Import to HubSpot (Weeks 3–4)

Exporting from Marketo:

Go to Marketo's Database section and export your All People smart list as a CSV with all available fields. Include email address, first name, last name, company, all lead score fields, lifecycle stage, unsubscribe status, opt-in date, and every custom field you will be migrating. Export engagement data — email opens, clicks, form submissions — if you want to seed this into HubSpot as custom properties for segmentation purposes. Full historical engagement history does not transfer natively, but seeding "last open date" and "last clicked date" as properties allows segmentation by engagement recency in HubSpot from day one.

Export your Static Lists individually as CSVs. Smart Lists cannot be directly exported — instead, run each Smart List, export the resulting contact set as a Static List export, and reimport into HubSpot as a Static List. Rebuilding the Smart List logic as a HubSpot Active List comes in Phase 4.

Cleaning before import:

Run deduplication in Marketo before exporting. Marketo allows duplicate records for the same email address — HubSpot does not. Importing duplicates into HubSpot will create merge conflicts that are laborious to resolve. Clean your database in Marketo first.

Remove unsubscribed contacts from your main import and keep them as a separate suppression file. Import them separately into HubSpot with their unsubscribed status preserved — do not skip this step. Emailing a Marketo unsubscribe from HubSpot violates CAN-SPAM, GDPR, and CASL and will generate spam complaints that damage your sender reputation.

Importing into HubSpot:

Use HubSpot's Import tool under Contacts. Upload your CSV and map each column to the corresponding HubSpot property. For columns that match native HubSpot properties (First Name, Last Name, Email, Company Name), the mapping is straightforward. For custom properties you created in Phase 2, map the CSV columns to the matching custom properties.

Review the import preview carefully before completing the import — verify that field mapping looks correct on the sample records shown. A field mapped to the wrong property creates data corruption that must be manually corrected.

After import, run a data validation check. Pull a sample of 20–30 records and compare them against the corresponding Marketo records to verify all fields transferred correctly, unsubscribe statuses are preserved, and no data corruption occurred in custom fields.

---

Phase 4: Rebuild Workflows and Lead Scoring (Weeks 4–8)

This is the largest body of work in the migration and the phase where the most meaningful improvement over your Marketo setup can be achieved.

The workflow rebuild principle: Do not attempt to replicate Marketo Smart Campaign logic directly in HubSpot Workflows. The architectures are different and a direct copy produces unnecessarily complex HubSpot automation. Use your Step 1 audit documentation as a reference for what each campaign does, then rebuild the outcome in HubSpot's workflow logic — often with fewer steps and simpler conditions.

Priority workflows to rebuild first:

Lead lifecycle management workflow — The most important automation in any B2B Marketo instance is the one that manages lifecycle stage transitions: Subscriber to Lead to MQL to SQL. In HubSpot, rebuild this as a Contact Workflow triggered on relevant engagement signals — form submissions, email engagement above a threshold, page visits on high-intent pages. Connect the workflow to your lead scoring property (see below) so lifecycle stage advances when the score threshold is reached.

Lead routing and notification workflow — If Marketo sends internal notification emails or assigns leads to sales reps based on territory, company size, or lead source, rebuild this in HubSpot using workflow branching and the Notify Owner or Assign Owner actions.

Engagement programmes → nurture workflows — Each Marketo Engagement Programme becomes a HubSpot Workflow with email send actions and time delays. For programmes with multiple streams and stream transition logic, use HubSpot's Workflow branching with If/Then branches to replicate stream eligibility conditions.

Rebuilding lead scoring in HubSpot:

HubSpot has two scoring approaches — manual Contact Score (available in all Professional tiers) and AI-powered Predictive Lead Scoring (available in Enterprise tier).

For manual scoring: Go to Contacts > Contact Score and add scoring criteria matching your Marketo demographic and behavioural scoring rules. HubSpot's scoring interface is more accessible than Marketo's — point values, positive and negative scoring, and recency-based decay can all be configured without technical support.

HubSpot does not natively support Marketo's automatic score decay for behavioural inactivity. Replicate decay logic by building a workflow that reduces the Contact Score property by a defined amount when a contact has had no email engagement in the last 30 or 60 days.

Rebuilding Smart Lists as Active Lists:

For each Marketo Smart List you need in HubSpot, create a HubSpot Active List using the same filter logic translated to HubSpot's filter interface. Most common Marketo Smart List conditions — email engagement, form submissions, page visits, lifecycle stage, lead score threshold — have direct equivalents in HubSpot's list filter builder without any technical knowledge required.

---

Phase 5: Rebuild Email Templates, Landing Pages, and Forms (Weeks 5–8)

Email templates and landing pages do not transfer from Marketo to HubSpot. They must be rebuilt.

Email templates: In Marketo, export your most-used email templates as HTML files. In HubSpot, create new emails and import the HTML as a starting point — go to Create Email, select Drag and Drop, then Code. For templates that use Marketo tokens — {{lead.First Name}} — replace every token with the HubSpot personalisation equivalent — {{ contact.firstname }}. For complex Velocity Script templates, rebuild the logic using HubSpot's personalisation token system and HubSpot's simple if/else conditional content.

This is also the right time to modernise templates. Marketo templates built years ago may not render correctly on current mobile clients. Use Marketo's performance data from your audit to identify your highest-performing email templates and invest time rebuilding those correctly. Low-performing templates are good candidates for a complete redesign rather than a careful replication.

Landing pages: Marketo landing pages need to be rebuilt in HubSpot's landing page editor. For each active landing page, note the URL, the form attached, the thank-you page redirect, and any UTM parameters. Rebuild the page in HubSpot's drag-and-drop editor, connect the HubSpot form, and set up the same thank-you page logic. Update your website navigation, CTAs, and any Google or LinkedIn ads pointing to Marketo landing page URLs to point to the new HubSpot URLs after launch.

Forms: Rebuild all active Marketo forms in HubSpot's form builder. For each form, note the fields collected, the required fields, the progressive profiling logic if any, the hidden fields, and the thank-you message. Create equivalent forms in HubSpot and embed them on your website pages, replacing the Marketo form embed codes. Connect each form to the appropriate HubSpot workflow to ensure form submission triggers the correct follow-up automation.

---

Phase 6: Reconfigure Salesforce Integration (Weeks 6–9)

If your Marketo instance is connected to Salesforce CRM — which is the case for the vast majority of enterprise B2B Marketo users — the Salesforce integration must be reconfigured through HubSpot rather than Marketo before go-live.

HubSpot has a native Salesforce integration available as a connector. It provides bidirectional sync of contacts, companies, deals, and activities between HubSpot and Salesforce. The sync configuration requires deciding which object types sync, which fields sync bidirectionally versus unidirectionally, what triggers a contact to create or update a Salesforce record, and how lifecycle stages in HubSpot map to Lead Status and Opportunity Stage in Salesforce.

Before switching the Salesforce sync from Marketo to HubSpot, run both integrations in parallel briefly — HubSpot connected but not yet the primary — to verify that HubSpot's sync behaviour matches expectations before Marketo's sync is deactivated.

Key configuration decisions for the HubSpot-Salesforce sync:

• Which HubSpot contact properties sync to which Salesforce lead or contact fields
• Whether HubSpot creates new Salesforce leads automatically or only syncs contacts that already exist in Salesforce
• How Salesforce opportunity data flows back into HubSpot for revenue attribution in HubSpot reports
• Whether the Marketo Sales Insight package in Salesforce is replaced by HubSpot's Sales Insight Salesforce app

Deactivate Marketo's Salesforce integration only after HubSpot's integration is confirmed working correctly. Running both simultaneously for more than a brief validation period creates data conflicts where both platforms are writing to Salesforce simultaneously.

---

Phase 7: Testing and Validation (Weeks 8–10)

Before any HubSpot marketing is live to real contacts, every component of the migration must be tested against real data and real scenarios.

Workflow testing: Use HubSpot's Test Workflow feature to walk each workflow through a test contact. Verify that the entry trigger fires correctly, that branching paths route correctly, that personalisation tokens resolve to actual contact data, that email sends trigger at the right step with the correct delay, and that lifecycle stage changes occur as expected.

Form and landing page testing: Submit test entries through every rebuilt form. Confirm that form submissions create or update the correct contact record in HubSpot, trigger the correct workflow, and set the correct property values. For forms connected to list enrollment, confirm the contact is added to the correct list after submission.

Lead scoring testing: Create test contact records with known property values and verify that the Contact Score property calculates the correct score based on your scoring criteria. Test both positive scoring (score increases when criteria are met) and negative scoring (score decreases for disqualifying attributes).

Salesforce sync testing: Create test contacts in HubSpot and verify they sync correctly to Salesforce with the right field values. Update a field in Salesforce and verify the change syncs back to HubSpot within the expected sync frequency.

Suppression list validation: Pull a sample of known Marketo unsubscribes and verify they are marked as opted out in HubSpot and will not receive marketing emails.

Email rendering testing: Send test emails from HubSpot to seed accounts at Gmail, Outlook, and Apple Mail. Verify rendering on desktop and mobile. Check that all personalisation tokens resolve correctly, all links work, and unsubscribe links function properly.

---

Phase 8: Team Training and Go-Live (Weeks 9–12)

HubSpot is significantly more accessible than Marketo, but teams accustomed to Marketo's interface will still need structured onboarding before they are independently productive on HubSpot.

Plan role-based training sessions: Marketing managers need training on the campaign creation, workflow, and reporting interfaces. Sales reps need training on the CRM timeline, tasks, sequences, and Sales Hub features. Operations and admin users need training on property management, import tools, and integration configuration.

HubSpot Academy provides free certification training covering HubSpot Marketing Software, HubSpot Sales Software, and platform-specific courses. Requiring relevant certifications before go-live is a practical way to ensure team members have baseline competency.

Set a go-live date and communicate it clearly to all stakeholders. On go-live day: activate all HubSpot workflows that are tested and ready, ensure all website forms are pointing to HubSpot, confirm HubSpot tracking code is live on the website, and verify the Salesforce sync is active and Marketo's Salesforce integration is deactivated.

Keep Marketo active for 30 days after go-live as a reference. Do not cancel the Marketo subscription until you have confirmed HubSpot is functioning correctly for 30 days of live operation and you have downloaded all historical Marketo data you may need for future reference.

---

Complete Migration Checklist

Audit

• Export full Marketo contact database with all fields
• Run deduplication report and clean database
• List all active Smart Campaigns with trigger, filter, and flow documentation
• List all active Engagement Programmes with stream structure and cadence
• Document complete lead scoring model — all demographic and behavioural rules
• Catalogue all active email templates and landing pages
• List all LaunchPoint integrations and confirm HubSpot equivalents
• Download historical campaign performance reports for reference

HubSpot Setup

• Create all custom Contact, Company, and Deal properties matching Marketo fields
• Configure lifecycle stage mapping
• Set up user accounts, teams, and permissions
• Install HubSpot tracking code on website
• Configure sending domain — SPF and DKIM DNS records
• Set up HubSpot-Salesforce integration (do not activate until ready to switch)

Data Migration

• Clean list — remove duplicates, hard bounces, long-term unengaged
• Export unsubscribed contacts separately as suppression import
• Import contacts into HubSpot with correct field mapping
• Import suppressed contacts with opted-out status
• Validate sample records against Marketo source data
• Import Static Lists as HubSpot Static Lists

Workflow and Scoring Rebuild

• Rebuild lifecycle management workflow
• Rebuild lead routing and notification workflows
• Rebuild all active Engagement Programmes as HubSpot Workflows
• Rebuild lead scoring in HubSpot Contact Score
• Rebuild Smart Lists as HubSpot Active Lists
• Rebuild all active email templates with updated personalisation tokens
• Rebuild all active landing pages in HubSpot editor
• Rebuild all active forms and embed on website

Integrations

• Reconfigure Salesforce sync through HubSpot
• Reconnect webinar platforms (Zoom, On24) via HubSpot App Marketplace
• Reconnect enrichment tools (Clearbit, ZoomInfo)
• Reconnect any other third-party integrations

Testing

• Test every workflow using test contact — verify all branch paths
• Test every form submission end-to-end
• Test lead scoring with test contact records
• Test Salesforce sync bidirectionally
• Validate suppression list — confirm opted-out contacts will not receive emails
• Test email rendering across Gmail, Outlook, Apple Mail, mobile
• Send test emails to confirm personalisation tokens and links work

Go-Live

• Activate all workflows
• Switch all website forms to HubSpot
• Confirm HubSpot tracking code live on all pages
• Activate HubSpot-Salesforce integration
• Deactivate Marketo-Salesforce integration
• Complete team training before first HubSpot campaign
• Keep Marketo active for 30 days as reference
• Schedule 30-day post-migration review

---

Timeline: How Long Does This Migration Take?

The most common cause of timeline overrun is the lead scoring rebuild and the Salesforce integration reconfiguration. Both deserve significantly more time than most migration plans allocate. Budget at least two weeks purely for Salesforce integration validation — it is the integration that surfaces the most unexpected edge cases.

---

Conclusion

The Marketo to HubSpot migration is a genuinely transformative project when executed well. The result is a marketing automation environment that your entire team can use, that connects marketing and sales data natively, that reports on revenue attribution without complex configuration, and that costs meaningfully less to operate than a Marketo instance maintained by specialists.

The key is approaching it as a system redesign rather than a data transfer. Audit thoroughly, clean your data, map your fields before importing, rebuild your workflows with HubSpot's architecture in mind rather than replicating Marketo logic, and validate everything before going live.

---

Work With a Certified Migration Partner

Rackwave is a certified implementation and account management partner for both Adobe Marketo Engage and HubSpot. We serve clients across the USA, UK, Canada, Australia, and Singapore — managing Marketo-to-HubSpot migrations with zero data loss and full marketing continuity throughout the transition.

Explore Our Marketo Services → Explore Our HubSpot Services →

---

Frequently Asked Questions

How long does a Marketo to HubSpot migration take?
Between six and sixteen weeks depending on account complexity. Small accounts with fewer than 50,000 contacts and ten or fewer active workflows can complete in six to eight weeks. Enterprise accounts with 500,000-plus contacts, thirty-plus workflows, and a complex Salesforce integration should plan for twelve to sixteen weeks.

Do Marketo workflows transfer to HubSpot automatically?
No. Marketo Smart Campaigns and Engagement Programmes do not transfer to HubSpot. Each automation must be rebuilt in HubSpot's Workflow builder using your existing logic documentation as a reference. This is best treated as a redesign opportunity — rebuilding with HubSpot's more accessible architecture often produces simpler, more maintainable automation than the Marketo equivalent.

Does Marketo's lead scoring transfer to HubSpot?
No. Lead scoring does not transfer. You recreate your scoring model in HubSpot's Contact Score property, translating each Marketo demographic and behavioural scoring rule into HubSpot's scoring criteria interface. The rebuild is typically faster and simpler in HubSpot's interface than the original Marketo configuration.

What happens to email and engagement history from Marketo?
Historical email engagement data does not transfer natively. You can export key engagement signals from Marketo — last open date, last click date — and import them as custom HubSpot Contact properties to preserve segmentation by engagement recency. Full send and engagement history stays in Marketo, which is why keeping your Marketo account active for 30 days post-migration as a reference is recommended.

How does the Marketo-Salesforce integration become the HubSpot-Salesforce integration?
HubSpot has a native Salesforce integration that replaces Marketo's Salesforce sync. Configure the HubSpot-Salesforce integration with your field mapping, object sync rules, and lifecycle stage mapping. Validate that it is syncing correctly before deactivating Marketo's Salesforce integration. Running both integrations simultaneously for more than a brief validation period causes data conflicts.

Do Marketo email templates transfer to HubSpot?
Not automatically. Marketo email templates can be exported as HTML files and imported into HubSpot's HTML email editor as a starting point. Templates using Marketo tokens need to have tokens replaced with HubSpot personalisation equivalents. Templates using Velocity Script need to be rebuilt using HubSpot's conditional content and personalisation token system.

What is the biggest risk in a Marketo to HubSpot migration?
Data integrity — specifically, field mapping errors during import that put data into wrong properties, and failing to migrate suppression lists before the first send. Both are preventable with thorough preparation: create all custom HubSpot properties before importing, and import unsubscribed contacts with their opted-out status as the first data migration task.

Can I run Marketo and HubSpot simultaneously during migration?
Yes — and you should. Keep Marketo fully operational and active throughout the migration. Only deactivate Marketo automation and Salesforce integration after HubSpot is fully tested and confirmed working. Cancel your Marketo subscription only after 30 days of successful live HubSpot operation.

Does HubSpot support the same ABM features as Marketo?
Yes, in 2026 HubSpot's Enterprise tier includes target account lists, buying role assignment, account-level engagement scoring, and ABM-specific workflow actions. For most mid-market B2B companies, HubSpot Enterprise's ABM capabilities are sufficient. For the most complex enterprise ABM programmes — coordinating marketing and sales across buying committees of ten-plus stakeholders — Marketo's depth remains an advantage.

Does Rackwave manage Marketo to HubSpot migrations?
Yes. Rackwave is a certified implementation partner for both Adobe Marketo Engage and HubSpot. We manage full Marketo-to-HubSpot migrations for enterprise B2B clients across the USA, UK, Canada, Australia, and Singapore — covering audit, data migration, workflow rebuild, Salesforce reconfiguration, testing, and post-migration managed services.