Skip to content

Migration guide · Marketing Automation

Salesforce Marketing Cloud to HubSpot migration

Salesforce Marketing Cloud EngagementHubSpot Marketing Hub

Short answer

Migrating from Salesforce Marketing Cloud Engagement to HubSpot Marketing Hub moves subscribers, preferences, lists, templates and journeys into HubSpot contacts, subscription types, lists, email templates and workflows, often keeping Salesforce as the CRM through the native connector.

Why firms make this move

Firms with moderate send volumes often find Marketing Cloud more complex and costly than they need. HubSpot offers easier campaign building, website and content tools, and integrated reporting.

What moves

  • Subscribers and preferences
  • Lists and segments
  • Email templates
  • Journeys as workflows
  • Suppression lists

How the data maps

FromTo
SubscriberContact (marketing contact)
Publication listSubscription type
JourneyWorkflow
Data extensionProperties or custom objects

See the field-by-field map ↓

What to watch out for

  • Marketing contact tiers affecting HubSpot cost
  • AMPscript personalization to rebuild
  • Opt-out carry-over
  • Sending domain authentication

How Vantage Point runs the migration

  1. Inventory and simplify
  2. Configure HubSpot and the Salesforce connector
  3. Migrate contacts and preferences
  4. Rebuild templates and workflows
  5. Authenticate domains and cut over

Typical timeline

Typically 6 to 10 weeks.

Frequently asked questions

Is HubSpot suitable for high-volume sending?

For most mid-sized programs, yes. Very high-volume consumer senders may be better served by Marketing Cloud or Braze.

What happens to our Salesforce data?

It syncs to HubSpot through the native connector, so marketing can segment on CRM data.

Last reviewed October 2, 2026 by the Vantage Point team. Browse all migration paths →

Field-level map

Salesforce Marketing Cloud to HubSpot: field by field

8 mappings we start from on this migration, 5 of which need a transform, a lookup or a decision. Every project gets its own signed-off version; this is the baseline.

FromToHowNotes
SubscriberSubscriber Key / email Contactemail + custom ID property req direct
All SubscribersStatus ContactSubscription status req manual review
Publication listMembership Subscription typeOpt-in status direct
Data extensionProfile fields ContactCustom properties direct
Data extensionNon-profile rows Custom object or custom events— manual review
Journey Builder journeySteps WorkflowActions rebuild
AMPscriptPersonalization logic Personalization tokens / programmable email— rebuild
Content Builder assetEmails Marketing email template— rebuild

Field names are the platforms' standard API names; your org's custom fields are mapped during discovery. What the "How" labels mean

How labels
direct
Value copies across unchanged.
picklist map
Each source value is mapped to a target value.
lookup
Matched to an existing record, such as a user by email.
association
Becomes a relationship between records, loaded in a later pass.
derive
Calculated or cleaned during the load.
split / concat
One field becomes several, or several become one.
rebuild
Configuration or automation that is rebuilt rather than moved.
drop
Not migrated, deliberately.
manual review
Needs a decision with your team before the load.