Hi @lmatheis
What you’re trying to do avoid duplicate deal entry while keeping HubSpot as the daily tool for sales is exactly the common ERP/CRM integration challenge.
In 2025 Global Shop doesn’t publish much API documentation, which is why most projects end up being custom or semi-custom. On the HubSpot side you’ll likely need custom objects for deals or invoices so they mirror the ERP structure. Without that, you’ll always hit limits with standard Deals.
(Create and edit custom objects )
If Global Shop is on-premise, the bigger hurdle is secure access. HubSpot requires an accessible API layer, so often a sync agent or intermediate database is used to bridge local ERP data into the cloud. This way you can transform Global Shop’s schema into HubSpot-ready records and maintain associations (contacts, companies, deals) without building fragile one-off scripts
The real question: do you just need ROI reporting, or true two-way sync of orders, deals, and customer updates? For reporting only, BI tools or one-way exports can work. For operational use (sales seeing ERP deals in HubSpot, updating status back), you’ll want a reliable two-way sync platform rather than a custom connector that breaks every update. If consistency between HubSpot and your ERP system is the gap, Stacksync keeps them mirrored as changes happen.