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.
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.
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.
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.
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.
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.
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.
Seven building blocks shape the integration. HubSpot's app covers the standard sales records; the Dataverse Web API and change tracking carry everything else.
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.
RESTful access to every Dataverse table, standard or custom, with GET, POST, PATCH and DELETE, plus named functions and actions for other operations.
EntityDefinitionsThe 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.
Cases, the entitlements behind them, the SLA KPI instances that time each case, and the queues that route them.
Quotes, orders and invoices with their line rows, priced from Dynamics price lists and their product price list items.
Every owned row carries an owning business unit, and the application user's security role decides which rows the integration can see and change.
Where a tenant has no Sales plan, the custom build carries the account, contact and case sync on the Web API.
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.
Marketing engagement, sales activity and service history meet on one HubSpot record, whichever system created each piece.
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.
Price lists, SLA timers, entitlement terms and business unit security are calculated in Dynamics. HubSpot stores the results and never recalculates them.
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.
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.
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.
Read table, column and option set metadata for every table in scope, and enable change tracking on those tables.
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.
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.
Load current records and an agreed case and opportunity history window, then switch each table to its delta link.
Build lead handoff, service and reporting automations with sends paused, run two weeks in parallel, then switch on.
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 field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Accounts, contacts & leads | ||||
| accountid | d365_account_id | Company | D365 → HS | Primary key. Unique. |
| account.name | name | Company | ↔ Both | HubSpot's app handles the base sync. |
| account.accountnumber | d365_account_number | Company | D365 → HS | Secondary match key where used. |
| account.owningbusinessunit | d365_business_unit | Company | D365 → HS | Drives HubSpot teams and views. |
| contactid | d365_contact_id | Contact | D365 → HS | Primary key. Unique. |
| contact.emailaddress1 | Contact | ↔ Both | Match key. | |
| contact.firstname, lastname | firstname, lastname | Contact | ↔ Both | Owner set per field in the ownership table. |
| lead (new row) | Contact meeting handoff criteria | Contact | HS → D365 | HubSpot creates the Dynamics lead when a contact meets the agreed criteria. |
| Opportunities, quotes & orders | ||||
| opportunity.name, estimatedvalue | dealname, amount | Deal | ↔ Both | HubSpot's app handles the base sync where opportunities are used. |
| opportunity.estimatedclosedate | closedate | Deal | ↔ Both | |
| opportunity.salesstage | dealstage | Deal | D365 → HS | Stages map one to one in a dedicated pipeline. |
| opportunity.pricelevelid | d365_price_list | Deal | D365 → HS | Dynamics owns pricing. |
| transactioncurrencyid | deal_currency_code | Deal | D365 → HS | For multi-currency portals. |
| quote.quotenumber | d365_quote_number | Deal | D365 → HS | Latest active quote. |
| quotedetail / salesorderdetail rows | Line items | Line item | D365 → HS | Product, quantity and price per line. |
| salesorder.ordernumber, totalamount | Order name, amount | Order | D365 → HS | Read-only in HubSpot. |
| invoice.invoicenumber, totalamount | Invoice | Invoice | D365 → HS | Read-only in HubSpot. |
| Cases, SLAs & queues | ||||
| incident.ticketnumber | d365_case_number | Ticket | D365 → HS | Primary key. Unique. |
| incident.title | subject | Ticket | D365 → HS | |
| incident.statuscode | hs_pipeline_stage | Ticket | D365 → HS | Status reasons map to a dedicated ticket pipeline. |
| incident.prioritycode | hs_ticket_priority | Ticket | D365 → HS | |
| incident.caseorigincode | d365_case_origin | Ticket | D365 → HS | Phone, email, web and others, per tenant. |
| incident.customerid | Ticket associations | Ticket | D365 → HS | Customer can be an account or a contact. |
| incident.entitlementid | d365_entitlement | Ticket | D365 → HS | Entitlement name; remaining terms confirmed in discovery. |
| slakpiinstance via firstresponsebykpiid | d365_first_response_status | Ticket | D365 → HS | KPI status. Column names confirmed in discovery. |
| slakpiinstance via resolvebykpiid | d365_resolve_by | Ticket | D365 → HS | Resolve-by time. Column names confirmed in discovery. |
| queueitem.queueid | d365_queue | Ticket | D365 → HS | Current queue for the case. |
| Custom tables & marketing context | ||||
| Custom table rows | Custom object records | Custom object | ↔ Both | One HubSpot object per table in scope, defined from metadata. |
| Custom lookup columns | Association labels | Custom object | D365 → HS | Lookups become associations. |
| Custom columns for score and engagement | hubspotscore, last engagement | Contact | HS → D365 | Sellers see HubSpot's marketing context in Dynamics. Columns created in discovery. |
Values Microsoft publishes are stated; anything tenant-specific is marked for confirmation.
| Topic | Dynamics 365 | HubSpot |
|---|---|---|
| Access model | A 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. |
| Interfaces | Dataverse Web API: OData v4 over HTTPS, with functions, actions and batch requests. | REST APIs: CRM objects, associations, pipelines, imports. |
| Authentication | OAuth 2.0 tokens from Microsoft Entra ID for the application's service principal. | Bearer token on every call. |
| Change detection | Change tracking per table. Delta links return new, changed and deleted rows; tokens expire after seven days by default. | Webhooks for HubSpot-side changes. |
| Rate limits | Service 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. |
| Hosting | HubSpot'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 visibility | Business units and the security role limit what the application user reads and writes. | Teams and field-level permissions can mirror business units. |
Severity reflects impact on the SOW, not technical difficulty alone.
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.
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.
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.
The application user only sees rows its role allows. Agree which business units are in scope and test with real data before backfill.
A delta token older than the retention window fails. The integration layer alerts on lag and runs a scoped resync when needed.
Full case history can be large. Agree a history window; older closed cases stay in Dynamics.
Score and last engagement land on the Dynamics record, so sellers see what each contact has read and done before they call.
Cases with SLA status sit on the company record, so customer health, renewal and expansion workflows use real service data.
Marketing attribution, pipeline and service outcomes meet in HubSpot dashboards.
Contacts that meet agreed criteria become Dynamics leads with their source and score, and the outcome comes back to HubSpot.
Each business unit gets its own HubSpot team, lists and reports, matching how Dynamics secures the data.
With history already in HubSpot, ownership can move object by object without a second migration project.
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.
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 name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| d365_account_id | Dynamics Account ID | Company | Single-line text | accountid; unique |
| d365_account_number | Account Number | Company | Single-line text | account.accountnumber |
| d365_business_unit | Business Unit | Company | Dropdown | Owning business unit name |
| d365_contact_id | Dynamics Contact ID | Contact | Single-line text | contactid; unique |
| d365_price_list | Price List | Deal | Single-line text | Opportunity price list name |
| d365_quote_number | Quote Number | Deal | Single-line text | Latest active quote |
| d365_case_number | Case Number | Ticket | Single-line text | incident.ticketnumber; unique |
| d365_case_origin | Case Origin | Ticket | Dropdown | Case origin labels from metadata |
| d365_queue | Queue | Ticket | Dropdown | Current queue item's queue |
| d365_entitlement | Entitlement | Ticket | Single-line text | Entitlement name |
| d365_first_response_status | First Response SLA | Ticket | Dropdown | First-response KPI status |
| d365_resolve_by | Resolve By | Ticket | Date and time | Resolve-by KPI time |
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.
Based on public documentation from Microsoft and HubSpot. Each item marked for confirmation is verified with the client's Microsoft admin during discovery.
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.
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.
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.
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.
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.