Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.
Set up MCP
Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Give marketing and sales the same customer context. Sync supported HubSpot and Salesforce records with field mappings your team controls and record errors you can resolve in one place.
Set this up from Claude or ChatGPT
Example workflow based on connector documentation
Start with a company and its contacts. Stacksync connects the two CRMs, maps selected fields, and carries changes between supported records so teams can work in the system they already use.
Pair a HubSpot Company with the corresponding Salesforce Account, then pair their Contact records. Retain both systems’ record IDs and resolve existing duplicates before the first load.
For this example, sales maintains contact phone and job title in Salesforce. Map those values to the matching HubSpot Contact properties; keep marketing consent separate from ordinary contact details.
Update the selected contact, check the matched HubSpot record, and inspect any rejected field in the Issues dashboard. After correcting the cause, retry reads the latest source values.
AI assistant
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.
Server URL
https://mcp.stacksync.com/mcp codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksyncComplete the browser sign-in with your Stacksync account, then start a new Codex session.
claude mcp add --transport http stacksync https://mcp.stacksync.com/mcpOpen 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.
Create a two-way sync between my HubSpot and Salesforce.
You can also ask for workflows and AI agents (Genies) that use HubSpot and Salesforce. The assistant checks what each app supports, for example:
New to Stacksync? Create an account first, then sign in from your assistant.
Example mapping
A contact update reaches the right customer record
Download the mapping worksheetCSV · No email required
The workflow shows a mapping design, not an account-tested configuration. HubSpot documents Company, Contact, and associations; Salesforce object availability depends on writability and the configured change-detection method. Field labels here describe business values, not a universal API schema.
| Source | Target | Field owner | Mapping notes |
|---|---|---|---|
| HubSpot Company record ID | Linked Salesforce Account record ID | Integration owner | Keep an explicit ID link. A company name or website domain alone is not a universal matching key. |
| Salesforce Contact phone and title | HubSpot Contact phone and job title | Salesforce in this example | Use the writable fields exposed by your connected accounts and compatible field types. |
| HubSpot Contact → Company association | Salesforce Contact → Account relationship | CRM administrators | Resolve the company/account ID link before linking the contact. Define relationship handling separately from copying scalar fields. |
Expected result: Marketing sees the current contact details maintained by sales, and both teams retain the link to the same company.
HubSpot data without a HubSpot SDK in the product codebase
Related customer story: HubSpot–MySQL. Eko uses Stacksync to connect HubSpot with MySQL while retaining its database-based development and testing workflow. Read the Eko story.
Start with the records your workflow needs. Check each system’s read and write requirements before mapping fields.
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| Supported. Confirm field permissions and sync direction. |
| Coming soon. Confirm field permissions and sync direction. |
| Not supported. Confirm field permissions and sync direction. |
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| See connector requirements. Confirm field permissions and sync direction. |
Review how each system connects, detects changes, and permits access to your records.
View setup requirements and limits| Connection requirement | HubSpot | Salesforce |
|---|---|---|
| Integration interface | REST API (CRM v3) | REST, SOAP, and Bulk APIs |
| Authentication | OAuth | OAuth login via a Salesforce user |
| Change detection | Record updates and association changes need separate validation. | Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. |
| Read access | Available for supported records | Available for supported records |
| Write access | Available for supported records | Available for supported records |
Architecture
Choose the approach that fits your record model, field ownership, and connected systems.
Use HubSpot’s built-in integration for CRM-to-CRM workflows covered by its contact, company, deal, ticket, activity, and custom-object sync settings.
Considerations: The required HubSpot subscription, object sync rules, and property mapping behavior must fit your workflow.
Configure ongoing record sync in Stacksync: select objects and direction, edit field mappings, and inspect or retry rejected records in one dashboard.
Considerations: Your team defines record identity and business ownership. Supported objects, writable fields, and account permissions determine the available configuration.
Enterprise controls
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Review setup, record relationships, testing, and recovery for your implementation.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
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.
Setup guides: Authorize HubSpot
Setup guides: Authorize Salesforce
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 planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Keep each record tied to its source ID. Use the references below to choose field owners and preserve relationships between records.
Download the mapping worksheet · CSV, no email required
Record matching
Compare whether HubSpot Company and Salesforce Accounts describe the same company in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: HubSpot: Company documentationSalesforce: Accounts documentation
Record matching
Compare whether HubSpot Contact and Salesforce Contacts describe the same contact in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: HubSpot: Contact documentationSalesforce: Contacts documentation
Record matching
Compare whether HubSpot Deal and Salesforce Opportunities describe the same deal or opportunity in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: HubSpot: Deal documentationSalesforce: Opportunities documentation
Business process
Support-to-work-item handoff: HubSpot Ticket provides context for Salesforce Tasks and Events. These are related records, not equivalent entities.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: HubSpot: Ticket documentationSalesforce: Tasks and Events documentation
Record matching
Compare whether HubSpot Ticket and Salesforce Cases describe the same support case or ticket in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: HubSpot: Ticket documentationSalesforce: Cases documentation
Record matching
Compare whether HubSpot Product and Salesforce Products and Price Books describe the same product or catalog item in your business.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Fields to include
References: HubSpot: Product documentationSalesforce: Products and Price Books documentation
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Company or Accounts record needs a defined result in the other system.
Expected result: Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
If it fails: Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Contact or Contacts record needs a defined result in the other system.
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.
Object-specific availability and field permissions determine this mapping. Use the restrictions shown for each record type.
Starting event: A change to the selected Deal or Opportunities record needs a defined result in the other system.
Expected result: Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
If it fails: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.
Validate the selected objects and operations even where connector-level direction is documented.
Starting event: A customer-facing change in HubSpot needs operational context in Salesforce.
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.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.
The expected company relationship is preserved with no duplicate action or unintended write.
Test an email change, two records sharing an email, and a person associated with multiple organizations.
The expected contact relationship is preserved with no duplicate action or unintended write.
Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
The expected deal or opportunity relationship is preserved with no duplicate action or unintended write.
Escalate the same ticket twice, close one of several tasks, and verify that private ticket content is not copied into a public work item.
The expected support case or ticket relationship is preserved with no duplicate action or unintended write.
Check that each connected account can read and write the chosen objects. Exercise both directions with a test record before enabling production changes.
Only an approved, supported direction and permitted fields are written.
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.
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Inspect HubSpot Company and Salesforce Accounts, their IDs, and the destination error.
Repair the cross-system ID relationship before retrying dependent records; do not merge companies solely to remove a sync error.
Inspect HubSpot Contact and Salesforce Contacts, their IDs, and the destination error.
Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.
Inspect HubSpot Deal and Salesforce Opportunities, their IDs, and the destination error.
Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.
Check the HubSpot and Salesforce connector guides, account permissions, and any operations marked On Request.
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Compare current source values, destination validation, identity mappings, and any side effects already completed.
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.
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
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 updatesSelected writable fields update in Salesforce. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Detect changesStacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.
Apply updatesSelected writable fields update in HubSpot. Its permissions and validation rules still apply; rejected records can be inspected in the Issues dashboard.
Stacksync connects HubSpot and Salesforce with two-way sync for supported records. Authorize the accounts, select the record types, and map compatible fields. Both connectors support reading and writing; object permissions determine the available fields. Use the Issues dashboard to inspect and resolve rejected updates.
Stacksync supports two-way sync between writable records in both systems. The chosen objects and fields must permit updates in both directions. Read-only fields can supply values but cannot receive updates. Stacksync can read database views; it does not write back to the view.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Have a HubSpot Super Admin authorize Stacksync through the account connection flow. Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
This pair can involve both record sync and process handoffs. Keep the Ticket / Tasks and Events relationship explicit: copying fields and creating a downstream business transaction require different validation.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Start by reviewing Company in HubSpot and Accounts in Salesforce. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 567 integrations listed for HubSpot and Salesforce.
Popular · 8 of 567
HubSpot and Nutshell 
HubSpot and Oracle CX Sales 
HubSpot and Outreach 
HubSpot and Salesloft 
Salesforce and Gorgias 
Salesforce and Infor CRM 
Salesforce and Insightly 
Salesforce and Intercom Next step
Walk through your HubSpot and Salesforce records, field mappings, and requirements with an integration engineer.
