The vast majority of mid-sized family businesses — what European business research refers to as owner-managed SMEs or “Mittelstand-equivalent” firms — form the backbone of national economies well beyond what aggregate statistics typically reveal. According to the European Family Businesses federation, family firms represent more than 60% of all companies across Europe. Yet their relationship with ERP systems is paradoxical. Many have been slow to digitalise their processes, convinced that their informal, fast-moving, well-worn ways of working do not need a structured tool.
When they finally take the plunge, the reality is often striking. The particular structure of family business groups — multiple legal entities created for tax or governance reasons, processes driven by the instincts of founders, minimal documentation of institutional know-how — generates specific challenges that ERP vendors rarely mention in their sales brochures.
This paradox has a name: the family business group has an exceptionally strong operational culture (client loyalty, rapid decision-making, adaptability) but almost no traceability of the very processes that drive it. The ERP will surface and formalise what has worked until now on instinct. That transition is demanding. It is also usually triggered by a specific catalyst: a generational handover, an external acquisition, a banking audit, or simply growth that makes the shared spreadsheet impossible to maintain.
This guide is aimed at CFOs and CEOs of family business groups with 50 to 500 employees, 2 to 8 legal entities, and annual revenue between €15 million and €200 million. No IT jargon: concrete criteria for choosing an ERP suited to your governance, and five golden rules drawn from projects that actually succeeded.
What Sets a Family Business Group Apart from a Corporate Group: 6 ERP Specificities
Standard ERP methodologies were designed for corporate groups with dedicated IT departments, project teams of five to ten people, and already-formalised processes. In a family business group, none of those assumptions hold.
1. The CFO Is Buyer, Project Manager, and End User
In a large corporate, the ERP is driven by an autonomous IT department that liaises with business units. In a family business group, the CFO often plays all three roles simultaneously: writing the brief, running vendor demos, overseeing deployment, and becoming the solution’s first power user. This concentration of responsibility is a strength (fast decisions) but also a risk: the same actor cannot evaluate the tool critically while championing it to the rest of the team.
Practical implication: plan for a neutral external resource during the selection phase, even a lightweight one. A structured scoring framework for evaluating an integrator helps you structure that effort without hiring a full-time consultancy.
2. Multiple Legal Entities, Often Created for Tax Reasons
A family group with four entities is not necessarily a complex industrial conglomerate. Property holding companies, animating parent entities, regional subsidiaries created to ring-fence an activity or optimise succession planning: these structures are common in entrepreneurial families. These entities sometimes have very few transactions between them, or conversely have undocumented intercompany flows (management fee recharges, intra-group loans, implicit transfer margins).
The ERP must handle multi-entity consolidation without making day-to-day management burdensome. If each entity is forced to re-enter the same data manually, the tool will be rejected within the first three months.
3. Management Accounting Driven by the Founder’s Intuition
In many family business groups, the founder has a precise mental picture of profitability by product line, key account, and region. But that picture exists only in their head. There is no formalised cost centre plan, no documented profit centres, no allocation rules for shared overhead.
The ERP will force this formalisation. That is both its value and the first point of resistance. The pragmatic response: start with a minimal management accounting structure (three to five dimensions) and refine after go-live, rather than trying to model all the complexity upfront.
4. Succession and Handover as an Overlooked Catalyst
The ERP conversation often surfaces when the founding owner starts thinking about succession. An acquisition due diligence or generational transfer reveals that a significant portion of key processes lives in the heads of one or two people. The buyer or successor wants traceability, documented processes, reliable data. The ERP then becomes not just a management tool but an asset that enhances enterprise value.
Yet waiting for the moment of succession to deploy an ERP is the worst possible strategy: the succession process and the IT project overlap and interfere with each other. The rule is to plan three to five years ahead.
5. Resistance from “Old Guard” Employees to Having Their Practices Tracked
The teams who built the business often have informal practices that are effective but undocumented. The ERP imposes a traceability that some experience as a challenge to their autonomy: “Someone will be watching what I do.” This resistance is stronger in family business groups than in corporate groups, because informal hierarchies are more entangled and long-standing employees sometimes have a direct personal relationship with the founding family.
The solution is not technical — it is relational. The internal ERP champion must be chosen from within those teams, not appointed by management decree.
6. A Constrained Budget, Without an Internal IT Department
A family business group of 80 employees typically has no CIO. At best, it has an IT manager who also handles phones, printers, and cybersecurity. The ERP budget is therefore arbitrated directly between licence costs, integrator costs, and other operational investments. Pressure on the integrator budget is intense — and that is often where projects go off the rails: the integration cost is under-budgeted to get past the decision hurdle, and the overruns surface mid-project.
Ground rule: in a family business group, integrator costs typically represent 1.5 to 2.5 times the licence cost in the first year. That is predictable. What is not predictable is failing to plan for it.
Which ERP Modules Should a Family Business Group Prioritise?
Before choosing a tool, you need to decide the functional scope of your initial rollout. The temptation is to be exhaustive to “get full value for money.” That is the classic mistake.
Priority modules for Phase 1:
- Intercompany consolidation and group reporting: essential as soon as you have two entities. Manual consolidation on spreadsheets is a source of errors and significant time at every monthly close.
- Multi-dimensional management accounting: by site, product family, project, cost centre. Without it, the CFO continues to manage on instinct.
- Purchase and supplier management: centralising supplier master data is often the first concrete gain, especially when multiple entities order from the same suppliers without coordination.
- Basic commercial management: quotes, customer orders, invoicing. A full CRM can wait for Phase 2.
- Expense management and multi-level approvals: in a family business group, approval workflows are often informal. The ERP formalises them without making them cumbersome.
What to avoid in Phase 1 for a family business group:
MES (production floor control) and WMS (warehouse management) modules are too complex to start with: they require process maturity that Phase 1 is precisely meant to build. PLM (product lifecycle management) is similar, unless you are in manufacturing and it is the core of your differentiation. Advanced collaboration portals are pointless without solid adoption of the core modules first.
The guiding principle: deploy fewer functions but use them at 100%, rather than deploying everything and using none of it properly.
What ERP Architecture for a Family Business Group with 2 to 8 Entities?
Three architectures are viable, depending on your number of entities and the coherence of your activities.
Option A — Recommended: Single ERP with multi-entity management
One tool manages the entire group, with a parent company and subsidiaries configured as child companies. Intercompany flows are automated, consolidation is native, and group reporting is produced in a few clicks. This is the optimal choice for family business groups with up to five or six entities operating in similar sectors. Complexity: moderate. Cost: controlled. Low risk if entities share common processes.
Option B: Group ERP at the parent + lightweight tools at subsidiaries
The holding company runs the main ERP; subsidiaries use simple invoicing tools connected by API. This is a transitional solution, often adopted by default because a subsidiary already had its own tool. It generates technical debt and data consistency problems in the medium term. Acceptable temporarily if a subsidiary is too small to justify the main ERP. Not recommended as a target architecture.
Option C: Orchestrated multi-ERP
Multiple different ERPs across entities, connected by an integration layer (middleware, ETL). Reserved for groups whose entities operate in very different sectors (wholesale distribution + real estate + hospitality, for instance) with incompatible business logic. This architecture is costly to maintain and fragile. Avoid it if you have the option of a full overhaul.
| Option A | Option B | Option C | |
|---|---|---|---|
| Complexity | Moderate | Low initially | High |
| Total cost | Controlled | Low but growing | High |
| Technical debt risk | Low | High | Very high |
| Relevance for family groups | High | Transitional | Exceptional cases only |
The 4 Most Deployed Solutions in European Family Business Groups
The ERP market for family business groups is dominated by four vendors with distinct positioning.
Sage X3 (known as Sage 200 or Sage 300 in some markets) is historically the reference choice for mid-market manufacturing businesses. Strong functional coverage on finance and production, mature multi-entity management. Its integrator ecosystem is broad across Europe. Main limitation: configuration costs can be significant, and the interface modernisation has lagged some competitors.
Odoo has seen notable growth in recent years that now makes it a serious contender in the mid-market segment. Its strengths: parameterisation flexibility, modularity (deploy only what you need), native multi-company support, and a features-to-price ratio that is hard to beat. Its limitation: integrator quality is decisive, and the Odoo market is heterogeneous. Integrator selection is even more critical here than with other solutions.
Microsoft Dynamics 365 Business Central is the natural choice if your business is already in the Microsoft ecosystem (Microsoft 365, Teams, Azure). Integration with productivity tools is a concrete advantage for teams with low technology affinity. Good multi-entity coverage. Licence cost is higher but often offset by reduced interfaces between tools.
Access Group / Sage UK / SAP Business One are worth evaluating depending on your sector and geography. If your group has a strong retail, distribution, or professional services component, and you work with an accounting firm already on a compatible platform, the consistency of the accounting reference framework between the group and its external auditor is an underestimated argument: monthly closes are faster and file exchanges disappear.
None of these four solution categories is objectively superior in all cases. The decisive criterion remains the quality of the local integrator and their experience on family business group projects similar to yours — sector, number of entities, size. Always ask for references on comparable projects, not generic testimonials.
Five Golden Rules for a Successful ERP Project in a Family Business Group
These rules come from field feedback on family business group projects — both the ones that succeeded and the ones that did not.
Rule 1: Involve the owner-director from the design phase
Not just the CFO. The owner. If the founder or principal shareholder does not understand why the ERP changes how a purchase order is approved or how profitability by subsidiary is reported, they will delegate and then block the project mid-way. Their involvement in the first three parameter workshops is non-negotiable. An owner who says “handle it among yourselves” after two weeks of the project is a warning sign.
Rule 2: Map intercompany flows before choosing the tool
Management fee recharges between the holding company and its subsidiaries, transfer margins, intra-group loans, shared services: these flows must be documented on paper before touching the ERP. A group of four entities that discovers after migration that its intercompany flows were undocumented will spend the first six months post go-live catching up on accounting discrepancies. That is not an ERP problem — it is a preparation problem.
Rule 3: Appoint a credible internal champion, not an external consultant
The client-side project lead must be a company veteran, respected by the teams, and freed from at least 50% of their operational responsibilities during the deployment phase. An external consultant can help with methodology and functional expertise, but cannot be the change champion. Internal legitimacy is non-transferable.
Rule 4: Do not wait for the succession to migrate
Deploying an ERP during a business transfer means running two transformation projects simultaneously: organisational and cultural. That is twice the risk, twice the management burden at a time when leadership already has other strategic priorities. Plan the ERP project three to five years ahead of any succession milestone.
Rule 5: Budget 20 to 30% extra for non-standard specificities
Unusual consolidation structures, complex intercompany flows, tax rules specific to family holding companies, data migration from heterogeneous systems: all of this has an integration cost not covered by the vendor’s standard quote. Build it in from the start, and you will avoid the change orders that derail projects mid-stream.
Pre-Project Checklist for a Family Business Group: 10 Points
Before launching your vendor selection, verify these ten points. Every unchecked box is a risk of cost overrun or project derailment.
- Up-to-date legal structure chart with documented financial flows between entities
- Formalised intercompany flows (management fee recharges, transfer margins, shared services, intra-group loans)
- Chart of accounts for each entity reviewed to identify divergences across companies
- Formalised purchase approval process (who approves what, up to which amount, in which entity)
- Formalised commercial process (from order to invoicing in each subsidiary)
- Clean master data (customer, supplier, product reference lists) in current systems
- Internal champion identified and available at 50% capacity during deployment
- Integrator budget calculated separately from the licence budget (and no less than 1.5x the licence cost)
- CEO and principal shareholder committed to attending the first three scoping workshops
- Internal communication plan in place before announcing the project to operational teams
That tenth point is often the first one forgotten. Teams learn about the ERP project through the grapevine, which generates unnecessary anxiety. A clear statement from leadership — explaining why and giving a timeline, before the tool is even chosen — eliminates the majority of initial resistance.
Conclusion
An ERP in a family business group is not an IT project. It is a project to document and transmit the company’s operational culture. The owner who decides to deploy an ERP is accepting, implicitly, that their processes will be formalised, that their decisions will be traceable, and that their organisation will be able to function without them. That is a far deeper transformation than a tool change.
Family business groups that succeed at this project share one common trait: they treated it as a strategic decision owned by the founder and the principal shareholder, not as a technical project delegated to the CFO or outsourced to a consultant.
For further reading, see our complete guide on multi-entity consolidation with an ERP — a direct complement to this article — our analysis of cloud vs on-premise architectural choices for mid-market firms, and our practical guide on negotiating your ERP contract without an internal IT team.
