A multi-country integration between HubSpot and NAV

This Manufacturer of Luxury Faucets needed to make HubSpot and Microsoft Dynamics NAV work together in a much more coordinated way across different functions and geographies.
The project was not limited to a single synchronization flow.

Over time, the scope involved several operational areas, including customer and company ownership assignment, customer service mapping, agent management, offer and order visibility, post-sales processes, price list alignment, and the management of country-specific activities for markets such as Italy, USA, UK and China.

The complexity was increased by the fact that the integration had to support different business rules depending on the process and the market involved. Fantini needed a flexible architecture able to connect HubSpot with NAV without forcing teams to rely on spreadsheets, manual updates or disconnected workflows.

At the same time, the company needed to preserve internal control over which data had to be synchronized, how records had to be associated, and which information had to remain visible and actionable inside HubSpot for commercial and service teams.

HubSpot was already a central operational environment for CRM activities, while Microsoft Dynamics NAV remained the core business system for customer, commercial and service data.

Manufacturer of Luxury Faucets therefore needed an integration framework able to support multiple use cases, including:

• synchronization of companies and contacts between NAV and HubSpot

• mapping of agents, customer service contacts and company owners

• country-specific management for international organizations such as Manufacturer of Luxury Faucets USA and Manufacturer of Luxury Faucets UK

• visibility in HubSpot of offers and shipping-related information coming from NAV

• support for post-sales and ticket-related processes

• support for data normalization and datatype compatibility

• controlled synchronization of fields such as price lists, destinations, brands and additional business attributes

• the possibility to extend the integration progressively, without redesigning the entire architecture every time a new requirement emerged

A key requirement was flexibility. The integration could not be limited to a single one-way sync, but had to evolve into a modular connection between HubSpot and NAV, capable of supporting operational exceptions, local variations and new data points over time.

With ERP Bridge, Manufacturer of Luxury Faucets implemented a flexible integration layer between HubSpot and Microsoft Dynamics NAV, designed to support multiple departments and multiple countries within the same project framework.

Rather than limiting the project to a basic synchronization of contacts and companies, the integration was extended to cover a broader operational perimeter. 

Manufacturer of Luxury Faucets was able to connect CRM activities with ERP data across sales, customer service and post-sales workflows, while progressively introducing new synchronization rules whenever business needs evolved.

With ERP Bridge, Manufacturer of Luxury Faucets implemented a flexible integration layer between HubSpot and Microsoft Dynamics NAV, designed to support multiple departments and multiple countries within the same project framework.

Rather than limiting the project to a basic synchronization of contacts and companies, the integration was extended to cover a broader operational perimeter. 

Manufacturer of Luxury Faucets was able to connect CRM activities with ERP data across sales, customer service and post-sales workflows, while progressively introducing new synchronization rules whenever business needs evolved.

This approach made it possible to:

• centralize relevant ERP information inside HubSpot
  
  
• reduce manual activities related to mapping, ownership assignment and field updates
  
  
• support international operations with country-specific logic
  
  
• improve alignment between commercial data in NAV and operational visibility in HubSpot
  
  
• build an integration architecture that could grow over time instead of being replaced whenever a new requirement appeared