Hi experts and HubSpot team,
We’re currently working on an integration between HubSpot Data Hub and Microsoft Dynamics 365, and have run into a limitation we’re hoping to get clarity on.
Scenario:
We have a single contact in HubSpot who can generate multiple leads over time. Our goal is to allow that one contact to create multiple corresponding “lead” records in Dynamics CRM.
Challenge:
From what we understand, the sync only occurs once per record. This means we’re unable to sync the same HubSpot contact to new, future lead records in Dynamics after the initial sync.
Alternative considered:
We explored syncing HubSpot’s Lead object directly to Dynamics CRM Leads. However, since the HubSpot Lead object is relatively new, it doesn’t currently support this type of integration/sync.
Questions:
- Has anyone successfully handled a one-to-many (contact → multiple leads) sync between HubSpot and Dynamics?
- Are there recommended workarounds or best practices (e.g., custom objects, workflows, third-party connectors)?
- Is this a known limitation, or are there updates/roadmap items that address this?
Appreciate any insights or suggestions, thanks in advance!
Hey @Marketer_Kerry,
Thanks for posting in the Community!
I’d like to tag in some Community experts to see what insight they might have for us. @TomM2, @franksteiner79, and @RomyFuchs1 - any thoughts on @Marketer_Kerry’s inquiries?
Shane, Senior Community Moderator
@Marketer_Kerry
Have worked with a client on solving just this!
I would not recommend setting up a HubSpot Contact → D365 Lead sync personally, as the data model doesn’t align it becomes very problematic from a duplicate / sync error perspective.
The approach we moved forward with is a HS Contact → D365 Contact sync with a custom-coded workflow action to create a D365 Lead against the relevant D365 Contact for each qualified conversion - if you do not have Data Hub in your HS subscription this can also be achieved via Zapier.
We also set up D365 Opportunity → HS Deals to enable Marketing ROI reporting too.
@Marketer_Kerry
This is a genuine limitation of the native HubSpot and Dynamics sync and you have understood it correctly. The native connector is built around a one-to-one record sync model, so a single HubSpot contact generating multiple Dynamics leads is not something it handles out of the box.
The most reliable workaround teams use for this is a middleware layer rather than relying on the native connector for this specific flow. Tools like n8n, Make, or Power Automate sit between HubSpot and Dynamics and give you full control over the logic. You can trigger a new Dynamics lead creation based on a HubSpot event, a deal stage change, a form submission, or whatever signals a new lead in your process, without being constrained by the one-to-one sync limitation.
The custom object route is worth exploring if you want to stay within the native sync. You could create a HubSpot custom object to represent each discrete lead event, sync that object to Dynamics leads, and associate it back to the contact. It is more setup upfront but keeps the architecture cleaner long term.
On the HubSpot Lead object point, you are right that it does not currently support direct sync to Dynamics. Given how recently it was introduced I would not expect that to change quickly, and I would not build your architecture around waiting for it.
If you are already using or open to Power Automate given you are in the Microsoft ecosystem, that is probably the path of least resistance here. It has solid HubSpot connectors and native Dynamics support.
What middleware or integration tooling do you currently have available? That would help narrow down the most practical route for your setup.