Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP
CRM / Marketing · Two-way sync platform

HubSpot and Salesforce Marketing Cloud integration

Plan how HubSpot and Salesforce Marketing Cloud should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Set this up from Claude or ChatGPT
  • Scope your workflow with an integration engineer
  • Review the systems, records, and updates you need
Integration planning
stacksync.com
HubSpot
Salesforce Marketing Cloud
Review the integration scope

Built for teams where self-serve, reliability and scale matter

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo

Proposed workflow

Contact sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving HubSpot Contact or Salesforce Marketing Cloud Contacts / Subscribers needs a defined result in the other system.

  1. Start with HubSpot Contact and Salesforce Marketing Cloud Contacts / Subscribers. Use the record-matching and field-ownership rules from your mapping worksheet.

  2. Resolve the organization relationship and any owner or consent references required by the destination.

  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest an email change, two records sharing an email, and a person associated with multiple organizations.

Review records and field ownership

AI assistant

Set up HubSpot and Salesforce Marketing Cloud from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

  1. Open Customize → Connectors, select + Add, then Add custom connector.
  2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
  3. Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

  1. Open Settings → Apps → Advanced settings and turn on Developer mode.
  2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
  3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a sync between my HubSpot and Salesforce Marketing Cloud.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use HubSpot and Salesforce Marketing Cloud. The assistant checks what each app supports, for example:

  • “Build a workflow that messages our team in Slack when a HubSpot record changes.”
  • “Create a Genie that answers questions about our Salesforce Marketing Cloud data in Slack.”

What happens next

  • Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
  • Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
  • Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between HubSpot and Salesforce Marketing Cloud
HubSpot recordSalesforce Marketing Cloud recordRecord matchingField ownership
ContactDocumented record: SupportedRecord matchingContacts / SubscribersProposed record; confirm Stacksync object support.Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

HubSpot

Read and write support varies by record

Record types covered in the setup guide

Record typesCoverage and requirements
  • Contact
  • Company
  • Deal
  • Line Item
  • Product
  • Ticket
  • Quote
  • Goal
  • Owner
  • Pipeline
  • Stages
  • Audit
  • Subscriptions
  • HubDB
  • Forms
  • Calls
  • Communications
  • Emails
  • Meetings
  • Notes
  • Post Mail
  • Tasks
  • Marketing Emails
  • Invoices
  • Attachments
  • Custom objects (all)
  • Associations
  • Users
  • Services
  • Listings
  • Courses
  • Appointments
  • Commerce Payments
  • Email Events
  • Property History
Supported. Confirm field permissions and sync direction.
  • Campaigns
Coming soon. Confirm field permissions and sync direction.
  • Feedback Submissions
Not supported. Confirm field permissions and sync direction.

Read the HubSpot connector guide

Salesforce Marketing Cloud

Connection and object support require review

Record types to review with Stacksync

Record typesCoverage and requirements
  • Data Extensions
  • Contacts / Subscribers
  • Journeys (Journey Builder)
  • Content Assets (Content Builder)
  • Automations (Automation Studio)
  • Tracking Events
Confirm support for this record type and the direction you need.

Discuss Salesforce Marketing Cloud requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits
Connection requirementHubSpotSalesforce Marketing Cloud
Integration interfaceREST API (CRM v3)Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
AuthenticationOAuthConfirm the credentials, API plan, and permissions required for Salesforce Marketing Cloud.
Change detectionRecord updates and association changes need separate validation.Confirm how Stacksync detects changes for this connector and the objects you need.
Read accessAvailable for supported recordsConfirm with Stacksync
Write accessAvailable for supported recordsConfirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

  • SOC 2 Type II
  • ISO 27001
  • HIPAA BAA
  • GDPR
  • CCPA
  • DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

HubSpot
Integration interface
REST API (CRM v3)
Authentication
OAuth (choose HubSpot account and authorize Stacksync); requires a HubSpot 'Super Admin' to grant access; optional "Grant access to sensitive fields" checkbox for sensitive/highly sensitive fields
Change detection
Record updates and association changes need separate validation. Association detection uses full scans unless Associations CDC Boost is configured for an eligible account.
Read access
Available for supported records
Write access
Available for supported records
Setup requirements
  • Have a HubSpot Super Admin authorize Stacksync through the account connection flow.
  • Include association tables when relationships between records are needed. Configure Associations CDC Boost separately when eligible.
Limitations to check
  • Custom objects require an eligible HubSpot plan. Custom id properties that collide with native record IDs are excluded from sync.
  • Associations CDC Boost requires setup and is unavailable on Free and Starter accounts; association timing can differ from ordinary records.
Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

HubSpot setup guide
Salesforce Marketing Cloud
Integration interface
Two APIs on tenant-specific endpoints: a REST API (JSON over HTTPS) for Data Extensions, Journeys, Contacts, Content Builder, and Automations, plus a legacy SOAP API (ExactTarget WSDL) for tracking events and bulk Retrieve.
Authentication
Confirm the credentials, API plan, and permissions required for Salesforce Marketing Cloud.
Change detection
Confirm how Stacksync detects changes for this connector and the objects you need.
Read access
Confirm with Stacksync
Write access
Confirm with Stacksync
Setup requirements
  • Identify the Salesforce Marketing Cloud account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for Salesforce Marketing Cloud, including read/write support, authentication, and initial-load limits.
Limitations to check
  • Confirm Stacksync support for Salesforce Marketing Cloud and the record types your workflow needs.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare HubSpot and Salesforce Marketing Cloud access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

HubSpot setup checklist
  • Have a HubSpot Super Admin authorize Stacksync through the account connection flow.
  • Include association tables when relationships between records are needed. Configure Associations CDC Boost separately when eligible.

Setup guides: Authorize HubSpot

Salesforce Marketing Cloud setup checklist
  • Identify the Salesforce Marketing Cloud account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for Salesforce Marketing Cloud, including read/write support, authentication, and initial-load limits.
Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the HubSpot and Salesforce Marketing Cloud planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Record matching

Contact / Contacts / Subscribers

Compare whether HubSpot Contact and Salesforce Marketing Cloud Contacts / Subscribers describe the same contact in your business.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

HubSpot
Documented record · Supported
Salesforce Marketing Cloud
Object support to establish
Record identity
Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.
Field ownership
Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.

Fields to include

  • Source person ID
  • Display name
  • Email address
  • Organization reference
  • Consent state
Record dependencies
Resolve the organization relationship and any owner or consent references required by the destination.
Validation
Test an email change, two records sharing an email, and a person associated with multiple organizations.
Recovery
Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

References: HubSpot: Contact documentation

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Contact / Contacts / Subscribers to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit
Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility
Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose
Check record matching: Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit
A vendor-built integration may fit if it supports your HubSpot and Salesforce Marketing Cloud record types.
Operating responsibility
Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose
First check whether either vendor offers this integration. If available, verify Contact / Contacts / Subscribers, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit
Consider when HubSpot and Salesforce Marketing Cloud need a transformation, approval, or action outside a direct record sync.
Operating responsibility
Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose
Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit
Consider for a one-time HubSpot / Salesforce Marketing Cloud migration or a reporting need with an explicit freshness window.
Operating responsibility
Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose
Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Contact sync test

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Contact or Contacts / Subscribers record needs a defined result in the other system.

  1. Start with HubSpot Contact and Salesforce Marketing Cloud Contacts / Subscribers. Use the record-matching and field-ownership rules from your mapping worksheet.
  2. Resolve the organization relationship and any owner or consent references required by the destination.
  3. Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an email change, two records sharing an email, and a person associated with multiple organizations.

If it fails: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

Plan the customer lifecycle across HubSpot and Salesforce Marketing Cloud

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A customer-facing change in HubSpot needs operational context in Salesforce Marketing Cloud.

  1. Select the relevant Contact or Company records and identify whether the downstream relationship is a person, a company, a deal, or a reporting row.
  2. Define which lifecycle transitions are informative and which should request a downstream action. Keep conversion and merge history connected to stable IDs.
  3. Choose a representative reopened deal, changed contact identity, or reassigned account to test the handoff before expanding.

Expected result: The relationship survives a lifecycle change without creating a duplicate customer or triggering an unintended business action.

If it fails: Inspect merge/conversion history and existing destination records before replaying a lifecycle transition.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Contact / Contacts / Subscribers

Test case

Test an email change, two records sharing an email, and a person associated with multiple organizations.

Expected result

The expected contact relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated contact change

Investigate

Inspect HubSpot Contact and Salesforce Marketing Cloud Contacts / Subscribers, their IDs, and the destination error.

Next action

Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

A record type or update is unavailable

Investigate

Check the HubSpot and Salesforce Marketing Cloud connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between HubSpot and Salesforce Marketing Cloud

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

HubSpot Salesforce Marketing Cloud Direction requires confirmation

Detect changesRecord updates and association changes need separate validation. Association detection uses full scans unless Associations CDC Boost is configured for an eligible account.

Apply updatesConfirm that Stacksync can create or update the records you need in Salesforce Marketing Cloud.

Salesforce Marketing Cloud HubSpot Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in HubSpot.

Update timing and record limits
  • Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
  • Associations CDC Boost requires setup and is unavailable on Free and Starter accounts; association timing can differ from ordinary records.
  • Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ

HubSpot and Salesforce Marketing Cloud integration FAQ

Further reading

Resources for your technical review

Next step

Plan your integration with an engineer

Walk through your HubSpot and Salesforce Marketing Cloud records, field mappings, and requirements with an integration engineer.

Talk to an engineer Explore plans and pricing