Integration Products | Campaign Creators

Dynamics 365 Sales & Service HubSpot Integration

Written by Campaign Creators | Nov 17, 2026, 2:11:10 PM
Integration Assessment
Integration Assessment · CRM & Customer Service

Dynamics 365 Sales & Customer Service × HubSpot

How a business running Dynamics 365 Sales or Dynamics 365 Customer Service can connect it to HubSpot: what HubSpot's own Dynamics 365 app already syncs, what a custom build on the Dataverse Web API adds, and how HubSpot becomes the place where marketing, customer data and reporting come together.

Dataverse Web API (OData v4)Microsoft Entra IDChange trackingHubSpot's Dynamics 365 appCases, SLAs and queuesCustom Dataverse tables
Platform ownerMicrosoft
Integration typeHubSpot's app + custom Dataverse build
Primary directionTwo-way, owner set per object
FeasibilityStrong fit for cloud tenants
API accessOpen API
01 — Summary

Does Dynamics 365 Sales & Customer Service integrate with HubSpot?

Dynamics 365 Sales and Dynamics 365 Customer Service both store their data in Microsoft Dataverse. A HubSpot integration reads and writes that one data platform, whichever Dynamics apps the client licenses.

API access
Open APIOpen with conditionsGated API

Public documentation. The client's own admin issues credentials, with no vendor approval needed.

Open API. The Dataverse Web API is documented publicly. The client's Microsoft admin creates the Entra app registration and application user.

Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.

Dynamics 365 and HubSpot can run side by side, with HubSpot as the place where marketing, customer data and reporting meet.

Campaign Creators assessment

Dataverse exposes every standard and custom table through its Web API, which implements OData v4 and authenticates with Microsoft Entra ID. HubSpot's own Dynamics 365 app is the starting point: its listing covers accounts, contacts, leads, opportunities, products, sales orders, invoices, activities and cases (as tickets), one-way or two-way, for cloud tenants on dynamics.com. The custom build adds what a given tenant needs beyond that: custom tables with their own rules, case history with SLA and entitlement detail, queues, business unit rules, price list logic, and tenants that license Customer Service without a Sales plan.

Scorecard
API & docsExtensive
Data model fitHigh
App coveragePartial
Build complexityModerate

Ratings are CC judgments from Microsoft's and HubSpot's public documentation. Licensing, custom tables, business units and option set values are confirmed per tenant in discovery.

Strength

One API for every table

Sales, Customer Service and custom tables all live in Dataverse, so one authenticated Web API client reads and writes them all, with change tracking for incremental sync.

Plan for

Two syncs on one record

HubSpot's app and the custom build must never write the same field. An ownership table assigns each object and field to one sync path before the build starts.

Gate

Licensing and access first

HubSpot's listing names a Dynamics 365 Sales plan as a requirement. Customer Service-only tenants, and the Entra application user the custom build needs, are confirmed with the client's Microsoft admin first.

02 — API modules

Which Dynamics 365 Sales & Customer Service APIs does the integration use?

Seven building blocks shape the integration. HubSpot's app covers the standard sales records; the Dataverse Web API and change tracking carry everything else.

Starting point

HubSpot's Dynamics 365 app

Built by HubSpot · HubSpot Marketplace

HubSpot-built sync for standard records, one-way or two-way, for cloud tenants on dynamics.com. The custom build extends it rather than replacing it.

  • Accounts, contacts, leads, opportunities, products, sales orders, invoices, activities
  • Listing maps cases to tickets and entities to custom objects
  • Custom field mappings need Data Hub
Integration path

Dataverse Web API

OData v4 · [org].crm.dynamics.com/api/data/v9.2

RESTful access to every Dataverse table, standard or custom, with GET, POST, PATCH and DELETE, plus named functions and actions for other operations.

  • Create, read, update and upsert any row
  • Batch requests for volume
  • Table and column metadata through EntityDefinitions
Core

Change tracking

Prefer: odata.track-changes · delta links

The first request returns a delta link. Each later call to it returns only new, changed and deleted rows, so the sync reads what moved and nothing else.

  • Enabled per table, and cannot be switched off once on
  • Delta tokens expire after seven days by default
  • Full resync path for a lapsed token
Core

Customer Service tables

incident · entitlement · slakpiinstance · queueitem

Cases, the entitlements behind them, the SLA KPI instances that time each case, and the queues that route them.

  • First-response and resolve-by KPIs per case
  • Entitlement terms per customer
  • Current queue and routing state
Core

Quote-to-order tables

quote · salesorder · invoice · pricelevel

Quotes, orders and invoices with their line rows, priced from Dynamics price lists and their product price list items.

  • Price list per opportunity or account
  • Quote and order lines into HubSpot line items
  • Dynamics keeps the pricing rules
Scope rule

Business units & security roles

businessunit · owningbusinessunit

Every owned row carries an owning business unit, and the application user's security role decides which rows the integration can see and change.

  • Least-privilege custom role for the integration
  • Business unit becomes a HubSpot property and team
  • Separate rules per unit where needed
Scope decision

Customer Service-only tenants

No Dynamics 365 Sales plan

Where a tenant has no Sales plan, the custom build carries the account, contact and case sync on the Web API.

  • Confirm HubSpot app eligibility with the Microsoft admin
  • Same Dataverse tables, same HubSpot data model
  • Agree how much case history to load
03 — Framework

How does the Dynamics 365 Sales & Customer Service HubSpot integration work?

HubSpot's app handles the standard sales records. A CC-built integration layer sits beside it for everything else: it reads changes through delta links, applies the ownership rules, matches records and writes to HubSpot in batches. HubSpot-owned data travels back to Dynamics through the same Web API.

Dynamics 365 (Dataverse)
Sales tablesaccounts, contacts, leads, opportunities
Quote-to-order tablesquotes, orders, invoices, price lists
Customer Service tablescases, entitlements, SLA KPIs, queues
Custom tablesclient-specific Dataverse tables
CC integration layer
Entra-authenticated clientapplication user, least-privilege role
Change readerdelta link per table, resync fallback
Ownership rulesone sync path per object and field
Identity resolverDataverse ID · email · account number
HubSpot writerbatch upserts, error replay
HubSpot
Contacts & Companiespeople, accounts, business unit
Deals, Line items & Ordersopportunities, quotes, orders
Ticketscases with SLA and queue state
Custom objectsone per custom table in scope
Lists, workflows & reportsjourney, pipeline and service views
Dynamics 365 → HubSpot (records, cases, history)HubSpot → Dynamics 365 (leads, scores, engagement, HubSpot-owned fields)
Principle

HubSpot brings the customer view together

Marketing engagement, sales activity and service history meet on one HubSpot record, whichever system created each piece.

Principle

Extend the app, don't duplicate it

Standard records stay on HubSpot's Dynamics 365 app. The custom layer handles only what the app does not, so two syncs never write the same field.

Principle

Dynamics keeps its own rules

Price lists, SLA timers, entitlement terms and business unit security are calculated in Dynamics. HubSpot stores the results and never recalculates them.

04 — Process

What does Dynamics 365 Sales & Customer Service HubSpot integration setup involve?

Each phase ends on a gate the client signs off before the next begins. HubSpot's app is set up first, so the custom build only adds what the app does not cover.

1

Discovery & ownership

List the Dynamics apps licensed, environments, business units and custom tables. Agree the use case (side by side, by business unit, or a phased move) and which system owns each object and field.

Gate to next phaseSigned object and field ownership table
2

Access & app setup

Register the Microsoft Entra application, create the application user with a least-privilege custom security role, and install HubSpot's Dynamics 365 app for the objects it covers.

Gate to next phaseToken works against a sandbox environment; app syncing default objects
3

Metadata & change tracking

Read table, column and option set metadata for every table in scope, and enable change tracking on those tables.

Gate to next phaseSigned data dictionary with option set values
4

HubSpot data model

Create properties, custom objects for custom tables, a ticket pipeline that mirrors case statuses and a deal pipeline that mirrors sales stages, in a HubSpot sandbox.

Gate to next phaseSchema approved and created in sandbox
5

Build

Build the integration layer for custom tables, cases with SLA KPIs and entitlements, queues and price list rules, with idempotent upserts and Retry-After handling.

Gate to next phaseEvery in-scope table syncing in sandbox
6

Backfill

Load current records and an agreed case and opportunity history window, then switch each table to its delta link.

Gate to next phaseHubSpot counts reconcile to Dynamics views within an agreed tolerance
7

Workflows, parallel run & launch

Build lead handoff, service and reporting automations with sends paused, run two weeks in parallel, then switch on.

Gate to next phaseFive consecutive days with no unresolved sync errors
05 — Data mapping

What does the Dynamics 365 Sales & Customer Service HubSpot integration sync?

Dynamics column names follow the Dataverse table reference (logical names). Custom tables and columns carry a publisher prefix that differs per tenant and is read from metadata during discovery. Rows the HubSpot app covers are noted.

Dynamics 365 fieldHubSpot propertyObjectDirectionNotes
Accounts, contacts & leads
accountidd365_account_idCompanyD365 → HSPrimary key. Unique.
account.namenameCompany↔ BothHubSpot's app handles the base sync.
account.accountnumberd365_account_numberCompanyD365 → HSSecondary match key where used.
account.owningbusinessunitd365_business_unitCompanyD365 → HSDrives HubSpot teams and views.
contactidd365_contact_idContactD365 → HSPrimary key. Unique.
contact.emailaddress1emailContact↔ BothMatch key.
contact.firstname, lastnamefirstname, lastnameContact↔ BothOwner set per field in the ownership table.
lead (new row)Contact meeting handoff criteriaContactHS → D365HubSpot creates the Dynamics lead when a contact meets the agreed criteria.
Opportunities, quotes & orders
opportunity.name, estimatedvaluedealname, amountDeal↔ BothHubSpot's app handles the base sync where opportunities are used.
opportunity.estimatedclosedateclosedateDeal↔ Both
opportunity.salesstagedealstageDealD365 → HSStages map one to one in a dedicated pipeline.
opportunity.pricelevelidd365_price_listDealD365 → HSDynamics owns pricing.
transactioncurrencyiddeal_currency_codeDealD365 → HSFor multi-currency portals.
quote.quotenumberd365_quote_numberDealD365 → HSLatest active quote.
quotedetail / salesorderdetail rowsLine itemsLine itemD365 → HSProduct, quantity and price per line.
salesorder.ordernumber, totalamountOrder name, amountOrderD365 → HSRead-only in HubSpot.
invoice.invoicenumber, totalamountInvoiceInvoiceD365 → HSRead-only in HubSpot.
Cases, SLAs & queues
incident.ticketnumberd365_case_numberTicketD365 → HSPrimary key. Unique.
incident.titlesubjectTicketD365 → HS
incident.statuscodehs_pipeline_stageTicketD365 → HSStatus reasons map to a dedicated ticket pipeline.
incident.prioritycodehs_ticket_priorityTicketD365 → HS
incident.caseorigincoded365_case_originTicketD365 → HSPhone, email, web and others, per tenant.
incident.customeridTicket associationsTicketD365 → HSCustomer can be an account or a contact.
incident.entitlementidd365_entitlementTicketD365 → HSEntitlement name; remaining terms confirmed in discovery.
slakpiinstance via firstresponsebykpiidd365_first_response_statusTicketD365 → HSKPI status. Column names confirmed in discovery.
slakpiinstance via resolvebykpiidd365_resolve_byTicketD365 → HSResolve-by time. Column names confirmed in discovery.
queueitem.queueidd365_queueTicketD365 → HSCurrent queue for the case.
Custom tables & marketing context
Custom table rowsCustom object recordsCustom object↔ BothOne HubSpot object per table in scope, defined from metadata.
Custom lookup columnsAssociation labelsCustom objectD365 → HSLookups become associations.
Custom columns for score and engagementhubspotscore, last engagementContactHS → D365Sellers see HubSpot's marketing context in Dynamics. Columns created in discovery.
06 — Auth & API

How are authentication and API limits handled?

Values Microsoft publishes are stated; anything tenant-specific is marked for confirmation.

TopicDynamics 365HubSpot
Access modelA Microsoft Entra app registration plus an application user in the Dynamics environment, assigned a custom security role. Microsoft states the application user needs no paid license.Private app access token or OAuth public app, scoped per object. Custom objects need an Enterprise subscription.
InterfacesDataverse Web API: OData v4 over HTTPS, with functions, actions and batch requests.REST APIs: CRM objects, associations, pipelines, imports.
AuthenticationOAuth 2.0 tokens from Microsoft Entra ID for the application's service principal.Bearer token on every call.
Change detectionChange tracking per table. Delta links return new, changed and deleted rows; tokens expire after seven days by default.Webhooks for HubSpot-side changes.
Rate limitsService protection limits per user: 6,000 requests and 20 minutes of execution time in a five-minute sliding window, and 52 concurrent requests. Excess calls return 429 with Retry-After.Per-10-second burst and daily limits by subscription tier.
HostingHubSpot's app supports cloud tenants on dynamics.com. Confirm hosting before any build.HubSpot's app is installed by a Super Admin or a user with App Marketplace permissions.
Data visibilityBusiness units and the security role limit what the application user reads and writes.Teams and field-level permissions can mirror business units.
07 — Issues & opportunities

What should you plan for, and what does the integration unlock?

Severity reflects impact on the SOW, not technical difficulty alone.

Challenges to plan for

Two sync paths on one recordHigh

If HubSpot's app and the custom layer both map a field, they overwrite each other. The ownership table assigns every field to exactly one sync, and the app mapping is switched off where the custom build takes over.

Licensing for HubSpot's appHigh

HubSpot's listing names Sales Professional, Sales Enterprise or Sales Premium. Confirm the tenant's plans before relying on the app; the custom build covers tenants without a Sales plan.

Option sets differ per tenantMedium

Status reasons, priorities and case origins are stored as numbers with labels set per environment. The mapping is built from the tenant's metadata, not from defaults.

Business unit visibilityMedium

The application user only sees rows its role allows. Agree which business units are in scope and test with real data before backfill.

Change tokens expireMedium

A delta token older than the retention window fails. The integration layer alerts on lag and runs a scoped resync when needed.

Case history depthLow

Full case history can be large. Agree a history window; older closed cases stay in Dynamics.

Opportunities in HubSpot

Marketing context for Dynamics sellersHigh value

Score and last engagement land on the Dynamics record, so sellers see what each contact has read and done before they call.

Service history on the HubSpot recordHigh value

Cases with SLA status sit on the company record, so customer health, renewal and expansion workflows use real service data.

One reporting layerHigh value

Marketing attribution, pipeline and service outcomes meet in HubSpot dashboards.

Clear lead handoffMedium value

Contacts that meet agreed criteria become Dynamics leads with their source and score, and the outcome comes back to HubSpot.

Views per business unitMedium value

Each business unit gets its own HubSpot team, lists and reports, matching how Dynamics secures the data.

A phased move when the client is readyMedium value

With history already in HubSpot, ownership can move object by object without a second migration project.

Coexistence plan

Decide what each system owns, then set the pace.

Most clients run both systems side by side for a period. The integration is the same whether that period is permanent or the first step of a move to HubSpot; only the ownership table changes.

  1. Side by side: sales and service work in Dynamics 365, marketing works in HubSpot, and HubSpot reports on the full journey.
  2. By business unit: units that sell through HubSpot own their records there, others keep Dynamics as owner, and both meet in HubSpot reporting.
  3. Phased move: history is loaded into HubSpot first, then ownership moves object by object, sales before service.
  4. Customer Service-only tenants: start with accounts, contacts and cases on the custom build, then add HubSpot marketing on top.
08 — Property schema

Which HubSpot properties does the integration create?

All custom properties use the d365_ prefix in a Dynamics 365 property group. Records synced by HubSpot's Dynamics 365 app keep that app's own properties; these extend them.

Internal nameLabelObjectTypeSource / logic
d365_account_idDynamics Account IDCompanySingle-line textaccountid; unique
d365_account_numberAccount NumberCompanySingle-line textaccount.accountnumber
d365_business_unitBusiness UnitCompanyDropdownOwning business unit name
d365_contact_idDynamics Contact IDContactSingle-line textcontactid; unique
d365_price_listPrice ListDealSingle-line textOpportunity price list name
d365_quote_numberQuote NumberDealSingle-line textLatest active quote
d365_case_numberCase NumberTicketSingle-line textincident.ticketnumber; unique
d365_case_originCase OriginTicketDropdownCase origin labels from metadata
d365_queueQueueTicketDropdownCurrent queue item's queue
d365_entitlementEntitlementTicketSingle-line textEntitlement name
d365_first_response_statusFirst Response SLATicketDropdownFirst-response KPI status
d365_resolve_byResolve ByTicketDate and timeResolve-by KPI time
09 — Scope builder

Interactive scope builder

Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.

Scope summary

0Fields
0Inbound
0Write-back
Dynamics 365 × HubSpot Integration Assessment · Designed by Campaign Creators, Elite HubSpot Solutions Partner

Dynamics 365 Sales & Customer Service HubSpot integration FAQ

Does Dynamics 365 Sales & Customer Service integrate with HubSpot?

Yes. Campaign Creators builds a custom integration on the Dynamics 365 Web API v9.2, connecting Sales and Customer Service modules to HubSpot CRM. The build covers leads, contacts, accounts, opportunities, cases and activities, with field-level mapping and bidirectional sync rules your team controls.

What data syncs between Dynamics 365 and HubSpot?

Contacts and accounts sync bidirectionally. Dynamics 365 leads, opportunities and their stages sync to HubSpot contacts and deals. Customer Service cases sync to HubSpot tickets. Activity records (calls, emails, tasks, appointments) sync in the direction your team chooses. HubSpot form submissions and email engagement can post back to Dynamics 365 as leads or activities.

Which system owns which data?

Dynamics 365 stays the system of record for sales pipeline, customer service cases and account history. HubSpot owns marketing attribution, campaign engagement and inbound lead capture. The integration enforces those boundaries: a field updated in its owning system wins and overwrites the other, and no field moves without appearing on the agreed mapping.

What does setting up the Dynamics 365 HubSpot integration involve?

Discovery and access provisioning, field mapping review and sign-off, OAuth app registration in Azure AD, webhook and scheduled-sync configuration, UAT with a sample of live records, backfill of historical data, and a parallel-run period before the integration is switched on for the full team.

How long does the integration take and what does it cost?

Timeline and cost depend on the Dynamics 365 modules in use, the number of objects and fields in scope, custom entities, and whether a backfill is needed. Campaign Creators confirms scope in discovery and provides a fixed price before the build starts.