Hi,
We’re in the process of implementing Scoro and want to integrate same with our HubSpot CRM platform. In particular, we’re looking to sync HubSpot Deals with Scoro Quotes. I’ve managed to setup the sync, but the sync fails due to a missing record - ’ Company ID’. I’ve tried to map the Primary Company ID - but these fields are grey’d out in the mapping setup.
this is a one-way sync from Hubspot to Scoro.
Anyone had a similar challenge or succesfully integrated Scoro with Hubspot for deal sync that can point me in the right direction.
Hey, @CvanLoggerenb 
Can you post any screenshots or additional details? The app listing page shows for Quotes > Deals (HubSpot) = Client
Associated Company (Primary).
Best,
Jaycee
Hi @CvanLoggerenb
You’re hitting a common limitation: HubSpot won’t let you map the Primary Company ID field in custom syncs because it’s a system field, not exposed for mapping.
The way HubSpot handles associations is that a Deal always links to a Company via association, not by copying the ID into a property. That’s why the mapping option is greyed out. HubSpot’s docs on CRM associations explain the difference pretty well.
(Accounts Dashboard | HubSpot )
(Connect and use HubSpot data sync )
To get around this, the usual route is:
- Make sure each Deal in HubSpot is associated with a Company (using the Primary Company association)
- Configure your Scoro integration to use this association rather than a raw Company ID field. If the Scoro connector doesn’t expose this directly, the fallback is creating a custom field in HubSpot to hold the Company external ID (from Scoro) and then populating it via workflow or API. That custom property can be mapped across systems.
For syncing Deals to Scoro Quotes specifically, you may need to add a workflow in HubSpot that copies the associated Company’s Scoro ID into a custom Deal property before the sync runs. This way Scoro gets the identifier it needs without relying on the greyed-out system ID.
Now, connecting to your value point: handling record associations across systems is usually where integrations break down. Scoro wants a “Company ID” to anchor the Quote, HubSpot hides it behind associations, and developers end up patching with scripts.
That’s actually the exact kind of challenge we solve at Stacksync. The platform maintains association logic automatically and translates IDs between systems in real time, so you don’t need custom fields or fragile workflows to keep Deals linked to the right Company.
Teams using this cut engineering time on integrations by 40% and avoid sync failures at scale. If you want, I can share how it would look with a HubSpot–Scoro setup.
Hope this helps.