Post-M&A ERP consolidation is one of the highest-friction problems in operations. Generic options force a winner-loser choice between legacy ERPs; framework-based options pile customization on a base that fits neither company. Custom ERP designed around the combined entity unifies operations without legacy debt — typical Indian projects: ₹25L–₹50L+, 6–10 months.
Why M&A ERP consolidation is its own category
Most ERP projects optimize a single existing operation. Post-M&A ERP consolidation does something harder: it has to model an operation that doesn't exist yet — the combined entity that the merger will create over the next 12–24 months. The ERP has to fit that future operation, not the legacy operations it is replacing.
Three structural problems make this hard:
- Neither legacy ERP fits the combined entity. Each was configured for one side's operation. The combined entity has new flows — consolidated procurement, unified sales channels, shared service functions — that neither ERP models.
- Forcing a winner is operationally expensive. The losing side rebuilds every workflow on the winning side's system. This typically means months of friction and often blocks the operational integration that justified the deal.
- Going to SAP / Oracle is too slow. Multi-quarter enterprise implementations are not compatible with the operational urgency that follows a deal close.
“Post-merger, the right ERP is not whichever side's system you can extend. It is the system that fits the company you are becoming. Custom is the only option that actually models the future operation rather than retrofitting a legacy one.”
What post-M&A ERP consolidation covers
| Area | What the system handles |
|---|---|
| Master data unification | Deduplicated products, vendors, customers across legacy entities |
| Multi-entity structure | Each legacy entity preserved as a legal entity; new shared functions added |
| Consolidated procurement | Group-level vendor relationships, shared sourcing, per-entity allocation |
| Unified inventory | Multi-warehouse, multi-entity stock with inter-entity transfers |
| Shared services | Cross-charged group functions (IT, HR, finance shared services) |
| Per-entity statutory | GST, TDS, ROC compliance per entity |
| Consolidated reporting | Group P&L with intercompany eliminations |
| Audit trail | Full per-entity and cross-entity history for due-diligence and audit |
| Phased migration | Legacy ERPs run in parallel during cutover; phased data migration |
How the project typically runs
Phase 1: discovery and target operating model (weeks 0–4)
On-site discovery across both legacy operations. The deliverable is the target operating model for the combined entity — what flows are unified, what stays per-entity, what new shared functions emerge.
Phase 2: schema and first useful module (weeks 4–10)
Multi-entity schema designed around the target operating model. First useful module typically targets the highest-friction post-merger flow — often consolidated procurement or unified inventory.
Phase 3: remaining modules and migration (weeks 10–24)
Remaining modules ship in sequence. Master data deduplication and migration runs in parallel. Each entity's legacy ERP is decommissioned after its operations have been validated on the new system for at least one operational cycle.
Phase 4: consolidation reporting and decommission (weeks 24–32)
Group-level consolidated reporting goes live. Legacy ERPs are fully decommissioned. The new ERP becomes the system of record for the combined entity.
What custom delivers that the alternatives cannot
| Option | Pros | Cons |
|---|---|---|
| Force loser onto winner's ERP | Cheapest in the short term | Half the team rebuilds workflows; merger value gets blocked |
| Replace both with SAP / Oracle | Vendor brand recognition for due diligence | Multi-quarter implementation; operational momentum lost |
| Replace both with Odoo / NetSuite | Faster than SAP | Customization tax on framework; future migrations expensive |
| Custom ERP designed around the combined entity | Fits the future operation; client owns IP; phased delivery | Requires honest target-operating-model exercise |
For the broader TCO comparison, see Custom ERP vs SAP / Oracle / NetSuite: 5-year TCO.
What drives post-M&A ERP cost
- Number of legacy entities — 2 vs 4+ legal entities to consolidate
- Operational complexity overlap — clean combination vs heavy operational divergence
- Master data dedup scope — small vs large overlap in vendor / customer / product masters
- Statutory scope — entities in different states, schedules, regulatory regimes
- Consolidated reporting depth — basic group P&L vs investor-grade reporting with KPIs
- Migration depth — operational data only vs full historical migration
Mid-deal or post-close, ERP integration on the critical path?
If the deal's value depends on operational integration and neither legacy ERP fits the combined entity, custom is usually the right answer. 30-minute call to walk through scope and timeline.