After a merger, keep the ERP that runs your revenue, not the newest one
Two software companies merged with two ERPs. An independent review chose the older, customized, on-premises Business Central over cloud-based NetSuite, and Cateran moved the merged business onto it.
Direction of the move: from cloud NetSuite to on-premises Business Central. Retired: NetSuite, a Salesforce org, a licensing platform, an EDI channel and several point tools.
Executive summary
- The question. After the merger, finance had two ERPs and had to choose one. The newer, cloud-based NetSuite looked like the obvious answer.
- The answer. An independent post-merger review recommended Business Central instead, even though it ran on-premises and the other company's users would be moving out of the cloud. Licensing, channel ordering and usage billing already ran end to end in Business Central, so replacing it would have cost more and carried more risk than extending it. The move to the cloud could wait. Consolidation could not.
- The delivery. Cateran, the partner that had supported and extended the system for years, supplied the full team: lead architect, project manager, integration developers and functional consultants. Because one team owned both the ERP and its integrations, the hand-offs where consolidations usually break had a single owner.
- The result. Every NetSuite user, including an Asia-Pacific subsidiary that was brought live on site, now works in Business Central. NetSuite and the systems around it have been retired, and the client still works with Cateran.
1. The choice: which system becomes the system of record?
A merger leaves finance with two charts of accounts, two close calendars and two versions of the truth. Until the ERPs are consolidated, group reporting is stitched together by hand, and every integration has to be maintained twice.
The instinctive answer is to standardize on the newer, cloud-native platform. Here, that would have meant NetSuite. The case for it looked even stronger because the client ran Business Central on-premises, and had been preparing to move it to Business Central online when the merger happened. The question that actually mattered was different: which system would cost less, and carry less risk, to make the system of record for the combined business?
2. The deciding factor was where the revenue logic lived
On paper, the two companies were alike. Both were software vendors of similar size, together forming a business of roughly $200 million in annual revenue, selling through distributors, resellers and managed service providers worldwide. Both had major subsidiaries in Europe, the Middle East and Africa (EMEA), both ran Salesforce as their CRM, and both combined perpetual licences, multi-year subscriptions and monthly usage billing. Behind the CRM, their systems were very different:
| Area | Client (Business Central) | Merger partner (NetSuite) |
|---|---|---|
| Licensing | Licences generated from the sales order. The ERP is the system of record for entitlements | A separate third-party licensing platform |
| Channel orders | Distributor EDI and webstore orders arrive as sales orders | EDI plus manual order entry |
| Usage billing | Usage imported and invoiced automatically | A subscription billing add-on |
| Salesforce to ERP | Sales and order processes automated and integrated with the ERP | Largely manual, including spreadsheet quoting |
An independent management consulting firm compared the two during post-merger technology due diligence. It concluded that moving the NetSuite processes onto Business Central was the most cost-effective and efficient option. Neither Business Central's age nor its on-premises deployment was the deciding factor. Its customizations held the company's revenue model, and rebuilding them elsewhere would have cost more and put billing at risk. So consolidation came first: the merged business moved onto the on-premises system, and the cloud move waited.
3. The complexity was in the finance requirements
A five-week fit-gap assessment documented every NetSuite process. Working alongside the consulting firm, Cateran classified each gap as configuration, customization or third-party add-on. The requirements a controller would recognize were the hard part:
- Entity structure: more than 30 legal entities and branches, about 30 currencies, and multi-currency consolidation
- Revenue recognition: ratable recognition by exact days, fair-value allocation by item and currency, and reporting in two currencies
- Contract billing: multi-year subscriptions, billing on contract dates, usage at base and overage rates, evergreen renewals, and co-terming
- Channel transactions: an end user, reseller and distributor on one order, each with its own purchase order
- Licence control: licences issued when an order is created, and revoked when a product is returned
- An Asia-Pacific subsidiary: a significant operation reporting in its local currency as well as dollars, working in a different language and time zone
The ERP was also one of about 30 IT workstreams running at the same time, including merging the two Salesforce orgs into one, portal consolidation, a new entitlement service and a new subscription billing platform. Every one of them touched order-to-cash.
4. One team owned the ERP and every integration around it
Consolidations often split the work: one firm configures the ERP and others build the integrations. That's where things break: orders that don't arrive, licences that don't match invoices, revenue that doesn't reconcile.
Cateran supplied the whole delivery team, so the ERP and its integrations were run as one project with one plan and one accountable owner. Cateran had also supported and extended this Business Central system for years before the merger. The people extending it were the people who knew why it worked the way it did.
| Role | Responsibility |
|---|---|
| Lead architect | End-to-end design across Business Central and the surrounding systems |
| Project manager | One plan covering both the ERP and the integration work |
| Developers | New order and entitlement APIs linking Business Central to the unified entitlement service, the order fulfilment system and the subscription billing platform |
| Functional consultants | Setting up the merger partner's legal entities, currencies and consolidation, and migrating its data and processes from NetSuite |
The custom licensing and entitlement tables were extended to cover the merger partner's products and licence models, so Business Central stayed the single system of record for every licence. The team then planned and ran the cutover and trained about 70 people who had only ever used NetSuite.
The Asia-Pacific subsidiary needed more than remote support. The team made several on-site trips to finish the implementation and train users in person, so the subsidiary went live on the same programme as the rest of the business.
5. The result: one platform, fewer systems, a lasting relationship
- NetSuite switched off about 21 months after the assessment began
- Every NetSuite user migrated, about 70 people including the Asia-Pacific subsidiary. About 130 people now work in Business Central
- Systems retired: NetSuite, the merger partner's Salesforce org, its third-party licensing platform, its EDI channel, and several point tools
- End state: one ERP platform, Business Central on-premises, with a US database and a UK database for the combined EMEA subsidiaries, plus one entitlement service and one Salesforce org
- Relationship: the client still works with Cateran
What finance leaders can take from this
- Judge each ERP by what it runs, not when it was built. The system that already automates licensing, billing and revenue is often the cheaper and safer one to keep, even if it's older.
- Treat customization as an asset until proven otherwise. Customizations that encode the revenue model are years of know-how. Replacing them costs money and puts billing at risk.
- Give one team ownership of order-to-cash. Reconciliation problems after cutover usually come from hand-offs between systems, not from the ERP itself.
- Consolidate first, move to the cloud second. Changing platform and merging two businesses at the same time doubles the risk. One stable system of record makes the later cloud move a cleaner, single-company project.
- Plan for the regions in person. Remote rollouts work for head office. International subsidiaries, with their own language, currency and time zone, often need people on the ground.
Five questions to ask before you choose which ERP to keep
- Which system is the system of record for licences, subscriptions or contracts today?
- Where do your revenue recognition and billing rules actually live: in the ERP, in add-ons, or in spreadsheets?
- How many integrations would each option force you to rebuild?
- Which option keeps month-end close and consolidation under control during the transition?
- Who will own the integrations, and not only the ERP configuration?
Client details are withheld at Cateran's discretion. Figures are approximate.
