To integrate a multi-entity setup, build a single integration with entity routing, then reuse it across all legal entities. You do not need a separate project per company. A platform like Rapidi identifies which legal entity each record belongs to and automatically routes deals, quotes, orders, customers, and invoices to the correct company in your ERP, adjusting only the company, currency, and item codes per entity. This eliminates misrouted records, duplicate customers, and the month-end intercompany reconciliation that drains finance teams.
This guide is based on the Rapidi Live webinar "How Rapidi Handles Global Operations," presented by Sirine Touihri (Sales Consultant) and Andreea Arseni (Senior Data Integration Consultant) at Rapidi.
Native connector vs multi-entity integration: a quick comparison
| Capability |
Native CRM-ERP connector |
Rapidi multi-entity integration |
| Routing to the correct legal entity |
None or basic; records land in one hardcoded company |
Identifies the entity and routes each record automatically |
| Adding a new legal entity |
New project, rebuild from scratch |
Add the entity's settings, reuse the same integration |
| Shared customer across entities |
Duplicated once per legal entity |
One master record linked to each company, no duplicates |
| Multi-currency |
Not handled per entity |
Each entity's own currency and item codes; consolidate to group currency |
| Build effort |
Custom development |
Pre-built mapping templates, configured by your team |
| Monitoring |
Fragmented per connector |
One place for logs, errors, and schedules |
| Support |
Varies |
In-house consultants, 97% support satisfaction |
What is multi-entity CRM and ERP integration?
Multi-entity CRM and ERP integration connects one shared CRM, such as Salesforce or HubSpot, to several legal entities running in an ERP, such as Microsoft Dynamics 365 Business Central or Dynamics 365 Finance. Instead of a one-to-one link between one ERP company and one CRM, it uses entity routing to maintain a one-to-many relationship: contacts, orders, products, and invoices flow between the single CRM and the correct company in the ERP, in both directions.
Why do deals and orders land in the wrong legal entity?
Because most native connectors have no routing logic. They assume one ERP company per CRM, so when a group runs multiple legal entities, records are pushed into a single hardcoded company. The symptoms are familiar to any global finance team:
- Deals, quotes, and orders land in the wrong legal entity.
- The group P&L and the CRM forecast tell different stories at every month-end.
- Intercompany reconciliation eats finance hours chasing misrouted records.
- Every new legal entity means rebuilding the integration from scratch.
A typical example: a multinational on Dynamics 365 pushes every subsidiary's deals into one hardcoded company, then fixes misrouted orders by hand at every quarter-end. After connecting their systems to Rapidi, every deal automatically routes to the correct legal entity, and intercompany reconciliation goes from days to clean.
Do you need a separate integration project for every legal entity?
No. Build the integration once with routing logic in place, and you reuse the same logic across every legal entity, each with its own settings. Adding a company means expanding what you already have, not launching a new project.
Can a native CRM-ERP connector handle multiple companies?
Usually not cleanly. Native connectors have no routing logic, or only a basic one, so they default to a one-to-one relationship. Rapidi identifies which legal entity a record belongs to and routes it to the right company, so the same customer or order reaches the correct entity every time.
Does routing records to the right entity need custom developers?
No. Rapidi uses pre-built mapping templates plus entity routing that your team configures. There is no programming required to set up entity-specific routing, and you reuse the same setup for future legal entities.
How are duplicate customers prevented across entities?
With a native connector, a customer who trades with five companies is created five times in the CRM. Rapidi creates one master customer record and links the related records to the right company, so you keep a single customer view and avoid duplicates across legal entities.
How does Rapidi connect a multi-entity setup without rebuilding?
The principle is one service, multiple connections. Each company has its own connection inside a single Rapidi integration, with its own parameters.
- Reuse your transfers. Field mappings, filters, and table links are configured once for the first entity and reused for the second, third, and beyond.
- Per-entity scheduling and filtering. Sync one entity every 10 minutes and another every 2 hours, and apply country-specific filters for each entity, all from the same setup.
- One place to monitor. Logs, errors, and schedules for every legal entity sit in one view inside MyRapidi, whether you run one entity or ten.
What should you look for in a multi-entity integration platform?
- Built-in entity routing. The platform should identify the right legal entity and route each record there automatically, configured by your team rather than developers.
- Scales to new entities without rebuilding. Adding a legal entity should mean adding settings, reusing one integration definition with its own company, currency, and item codes.
- Connects every entity, with real support. Regional or acquired entities often run different or legacy ERPs. Rapidi connects cloud, on-premise, direct SQL, and legacy Microsoft Dynamics NAV and AX, backed by in-house consultants at 97% support satisfaction.
What do real multi-entity integrations look like?
These patterns are common in manufacturing, wholesale distribution, and retail groups, and in mid-market and European companies that run several legal entities across countries and currencies.
- Salesforce Dynamics 365 Finance integration (RMA cases). An approved return in Salesforce becomes a return order in the Finance entity that made the original sale, with status written back to the Salesforce case.
- Salesforce CPQ Business Central integration (quotes). An approved CPQ quote becomes a sales order in the correct Business Central company, with the right currency and item codes.
- Salesforce Business Central integration (closed-won opportunities). Closed deals are recognized as revenue in the correct company, so the group P&L matches the Salesforce forecast.
- HubSpot Business Central integration (deals). Closed HubSpot deals land in the correct Business Central company, and new entities are added without rebuilding.
- HubSpot Dynamics 365 Finance integration (selective customer creation). A master customer lives as a Company in HubSpot, with a linked child record per trading entity, so customers are created in Finance only where there is real business intent.
- CRM-to-CRM consolidation. Regional CRMs in Germany, Spain, and the UK sync into a master Salesforce org every 15 minutes, matched on a key to prevent duplicates, with amounts converted to group currency.
See each of these scenarios walked through live in the full webinar recording.
How do you roll out multi-entity integration in 5 steps?
- Map your entities and systems. List your companies, currencies, and which ERP and CRM instances each one runs.
- Find the duplicated work. Spot where the same data is re-entered per entity or consolidated by hand in spreadsheets.
- Configure your first entity. Set up connections and transfers for one company, including the routing logic, so it becomes your template.
- Replicate to the next entity. Add a connection, reuse the transfers, and adjust currency and filters. No new project.
- Scale and monitor centrally. Roll out the remaining entities and track every sync from one place.
Frequently asked questions
What systems does Rapidi integrate for multi-entity setups? Salesforce, HubSpot, Microsoft Dynamics 365 Business Central, Dynamics 365 Finance, legacy Microsoft Dynamics NAV and AX, NetSuite, direct SQL databases, and more, in cloud, on-premise, or hybrid deployments.
Can one CRM serve multiple legal entities? Yes. One Salesforce or HubSpot instance can serve every legal entity. With routing logic in place, you have a one-to-many relationship, so data flows from all your ERP companies to the single CRM and back.
Does Rapidi support custom objects and custom fields? Yes. Custom fields, custom objects, and custom tables all work the same as standard ones, as long as the connection has access to them.
What happens when we upgrade Dynamics or change a process? A process change may mean adjusting the field mappings within the same integration. Moving from Microsoft Dynamics NAV to Business Central is a separate project, but you still reuse the existing setup.
Is the sync bidirectional, and which system wins on a conflict? Sync runs in both directions. Choose a main source of truth, sync each system's relevant fields in the right direction, and always match records on a unique key rather than an email address.
Can Rapidi migrate or backfill historical data? Yes. Rapidi can backfill historical records, for example every customer since January 2025, then continue with day-to-day syncing. Full migration is supported when needed.
How does Rapidi handle multiple currencies? Each legal entity keeps its own currency and item codes, and amounts can be converted to a single group currency when consolidating into a master org for reporting.
Is multi-entity sync real-time or scheduled? It is scheduled per entity, and you control the frequency. One entity can sync every 10 minutes, and another every 2 hours, independently within the same setup.
How long does it take to add a new legal entity? Because the transfers are reused, adding a new entity is a matter of adding a connection and adjusting settings, not running a fresh implementation project.
Does Rapidi work with on-premise and legacy ERPs? Yes. Rapidi connects cloud systems, on-premise databases via direct SQL, and legacy Microsoft Dynamics NAV and AX.
Who maintains the integration day-to-day? Your team configures and maintains it through MyRapidi without programming, and Rapidi's in-house consultants support you throughout, included in the subscription.
What data can Rapidi sync between CRM and ERP? Contacts, accounts, customers, products, quotes, opportunities, sales orders, return orders, and invoices, routed to the correct legal entity.
Can Rapidi route quotes and orders to different companies in the same ERP? Yes. The routing logic sends each quote or order to the correct legal entity within the same Business Central or Dynamics 365 Finance instance, based on the entity it belongs to.
How does multi-entity integration stop subsidiaries chasing the same accounts? In a CRM-to-CRM setup, Rapidi syncs each regional CRM into a master Salesforce org every 15 minutes and matches accounts on a defined key, so every team sees the same up-to-date pipeline instead of duplicating outreach.
What is the difference between a native connector and an iPaaS for multi-entity integration? A native connector links one ERP company to one CRM with no routing logic. An iPaaS like Rapidi adds entity routing, reusable transfers, multi-currency handling, and one place to monitor every legal entity.
Is Rapidi a good fit for mid-market and European companies? Yes. Rapidi is built for mid-market and enterprise groups, including companies with 200 to 500 employees and multinationals operating across Europe. As a European data integration provider with worldwide coverage, Rapidi connects multi-entity setups for organizations spanning multiple countries and currencies.
Does multi-entity integration work for manufacturing and distribution companies? Yes. Multi-entity setups are common in manufacturing, wholesale distribution, and retail groups running several legal entities. Rapidi routes orders, returns, customers, and invoices to the correct company across Salesforce, HubSpot, Business Central, and Dynamics 365 Finance.
How do I eliminate duplicate customer records between Salesforce or HubSpot and Dynamics 365? Use a single master customer record linked to each legal entity, rather than letting the connector create a copy per company. Rapidi keeps a single master record and links the entity-specific records, so customers are not duplicated across companies.
Get started with multi-entity data integration
A multi-entity setup does not have to mean a project per company. With entity routing configured once and reused, you connect every legal entity to your CRM and ERP, maintain a single customer view, and trust your numbers at month-end.
Download the free Multi-Entity Data Integration Checklist, or book a free demo to see Rapidi route records to the right entity in your own systems.
