Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Plan how HubSpot and Dynamics 365 Business Central should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
Proposed workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving HubSpot Company or Dynamics 365 Business Central Customers needs a defined result in the other system.
Start with HubSpot Company and Dynamics 365 Business Central Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
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 individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Review records and field ownershipProposed record relationships
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| HubSpot record | Dynamics 365 Business Central record | Record matching | Field ownership |
|---|---|---|---|
| CompanyDocumented record: SupportedCustomer identity assessment | CustomersProposed record; confirm Stacksync object support. | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
| ContactDocumented record: SupportedCustomer identity assessment | CustomersProposed record; confirm Stacksync object support. | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
| InvoicesDocumented record: SupportedRecord matching | Sales InvoicesProposed record; confirm Stacksync object support. | Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap. | The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.
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. |
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.
View setup requirements and limits| Connection requirement | HubSpot | Dynamics 365 Business Central |
|---|---|---|
| Integration interface | REST API (CRM v3) | REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL |
| Authentication | OAuth | Confirm the credentials, API plan, and permissions required for Dynamics 365 Business Central. |
| Change detection | Record updates and association changes need separate validation. | Confirm how Stacksync detects changes for this connector and the objects you need. |
| Read access | Available for supported records | Confirm with Stacksync |
| Write access | Available for supported records | Confirm with Stacksync |
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.
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
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 Dynamics 365 Business Central planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
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
Customer identity
Before linking HubSpot Company to Dynamics 365 Business Central Customers, check whether the customer is an individual or a company. Match the correct record type in each system.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: HubSpot: Company documentation
Customer identity
Before linking HubSpot Contact to Dynamics 365 Business Central Customers, check whether the customer is an individual or a company. Match the correct record type in each system.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: HubSpot: Contact documentation
Record matching
Compare whether HubSpot Invoices and Dynamics 365 Business Central Sales Invoices describe the same customer invoice in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: HubSpot: Invoices documentation
Business process
Approved sales handoff: HubSpot Deal provides context for Dynamics 365 Business Central Sales Orders. These are related records, not equivalent entities.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: HubSpot: Deal documentation
Business process
Order-to-invoice handoff: Dynamics 365 Business Central Sales Orders provides context for HubSpot Invoices. These are related records, not equivalent entities.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: HubSpot: Invoices documentation
Record matching
Compare whether HubSpot Commerce Payments and Dynamics 365 Business Central Payments describe the same payment or settlement in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: HubSpot: Commerce Payments documentation
Choose a method around one example record and the update your business needs. Use Company / Customers 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.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Company or Customers record needs a defined result in the other system.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Contact or Customers record needs a defined result in the other system.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Invoices or Sales Invoices record needs a defined result in the other system.
Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in Dynamics 365 Business Central needs operational visibility through Contact or Company.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
The expected customer relationship is preserved with no duplicate action or unintended write.
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
The expected customer relationship is preserved with no duplicate action or unintended write.
Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
The expected customer invoice relationship is preserved with no duplicate action or unintended write.
Repeat the approved handoff and verify that it locates the existing order; test a reopened deal without silently cancelling fulfillment.
The expected deal or opportunity relationship is preserved with no duplicate action or unintended write.
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
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 Dynamics 365 Business Central Customers, their IDs, and the destination error.
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Inspect HubSpot Contact and Dynamics 365 Business Central Customers, their IDs, and the destination error.
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Inspect HubSpot Invoices and Dynamics 365 Business Central Sales Invoices, their IDs, and the destination error.
Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.
Check the HubSpot and Dynamics 365 Business Central 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 updatesConfirm that Stacksync can create or update the records you need in Dynamics 365 Business Central.
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.
Explore a HubSpot and Dynamics 365 Business Central integration with a Stacksync engineer. Stacksync support for Dynamics 365 Business Central is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
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. Identify the Dynamics 365 Business Central account, edition, environment, and business objects the integration must access. 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.
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 Customers in Dynamics 365 Business Central. 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.
Choose a method around one example record and the update your business needs. Use Company / Customers 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.
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 539 integrations listed for HubSpot and Dynamics 365 Business Central.
Next step
Walk through your HubSpot and Dynamics 365 Business Central records, field mappings, and requirements with an integration engineer.
