Microsoft Dynamics 365 F&O and HubSpot integration

What moves between them

Master data flows from Microsoft Dynamics 365 F&O into HubSpot: customers become HubSpot companies and contacts, and released products become HubSpot products, so sales teams quote against records that exist in the ERP. Closed-won deals flow the other way, where ml-connector creates or updates the matching customer in Dynamics and opens a sales order for fulfillment and invoicing. Product and customer references are aligned on both sides so each deal line resolves to a real Dynamics product number and customer account. The general ledger and posted invoices stay in Dynamics, since HubSpot has no GL, so ml-connector never writes ledger entries into the CRM.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Dynamics side it requests an Entra ID bearer token with the client credentials flow against the tenant-specific scope and refreshes it when a call returns 401, and it fully specifies entity keys including dataAreaId, adding cross-company for multi-entity reads. On the HubSpot side it sends the Private App token as a Bearer header and writes companies, contacts, and products through the batch upsert endpoint, matching on a stable external id such as the Dynamics customer account so a re-read does not create duplicates. It polls Dynamics customers and products on a schedule and can take a Dynamics Business Event over HTTPS as a trigger, deduping on the ControlNumber and then calling back to OData for the full record because the event is only a stub. Both APIs return HTTP 429 with Retry-After, so ml-connector backs off and retries, and a HubSpot Private App alone cannot receive webhooks, so HubSpot-side change capture is handled by polling or a separate Public app. Financial dimensions are passed as the formatted display string Dynamics expects, mapped from the deal context first so postings land on valid accounts. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized industrial equipment distributor, around 300 employees, runs Microsoft Dynamics 365 F&O for finance and order processing and HubSpot as the CRM for its sales reps. Before the integration, a rep closed a deal in HubSpot and then a finance clerk re-keyed the customer and order into Dynamics by hand, so customers were entered twice with mismatched names, product codes were sometimes wrong, and orders sat for a day before fulfillment saw them. With Microsoft Dynamics 365 F&O and HubSpot connected, the ERP customer and product masters sync into HubSpot so reps quote against real records, and each closed-won deal opens a Dynamics customer and sales order within the polling window. The duplicate-entry and miskeyed-product problems are gone, and orders reach fulfillment the same day they close.

What you can do

• •Sync Microsoft Dynamics 365 F&O customers and products into HubSpot companies, contacts, and products.
• •Turn closed-won HubSpot deals into Dynamics customer and sales order records for fulfillment.
• •Match HubSpot upserts on a stable external id so a re-read never creates duplicate companies or products.
• •Bridge Entra ID OAuth client credentials on Dynamics with the HubSpot Private App access token.
• •Poll on a schedule with Business Event triggers, 429 backoff, and a full audit trail on every record.

Questions

Which direction does data move between Microsoft Dynamics 365 F&O and HubSpot?

Master data moves from Dynamics into HubSpot, where customers become companies and contacts and products become HubSpot products. Closed-won deals move the other way and create a customer and sales order in Dynamics. HubSpot has no general ledger, so posted invoices and GL entries stay in Dynamics and ml-connector never writes ledger data into the CRM.

Does Dynamics push changes, or does ml-connector poll for them?

Both are supported. ml-connector polls Dynamics customers and products on a schedule, and where Business Events are activated it can take an HTTPS push as a trigger. Because a Business Event payload carries only identifiers and a ControlNumber, ml-connector dedupes on that number and then calls back to the OData service to retrieve the full record before syncing.

How does the integration avoid duplicate records in HubSpot?

HubSpot has no universal idempotency header, so ml-connector writes companies, contacts, and products through the batch upsert endpoint, which matches on an idProperty. It keys that match on a stable external id such as the Dynamics customer account, so re-reading the same Dynamics record updates the existing HubSpot record instead of creating a second one.