Large enterprises rarely replace their headquarters ERP in one go. Instead they run a cloud system such as NetSuite at subsidiaries and satellite operations, then synchronise it with the on-premise system at head office. This article sets out the evaluation criteria that matter and how the two-tier model actually works.
What a Two-Tier ERP Model Actually Is
Criterion 1: Can the Vendor Handle Your Entity and Currency Structure?
Criterion 2: How Does the Vendor Handle Upgrades?
Criterion 3: What Are the Capacity Limits?
Criterion 4: How Well Does It Integrate With Headquarters?
Criterion 5: Does the Suite Cover the Operational Modules You Need?
Criterion 6: Can the Partner Deliver in Your Regions?
How to Sequence a Two-Tier Rollout
This paper proposes several evaluation criteria as a starting point for what you, as a business leader, should be looking for in a cloud ERP vendor. It also highlights some examples of companies that have achieved success by deploying NetSuite for ERP/financials, CRM, ecommerce, supply chain and more at their satellite operations, and synching with on-premise ERP at headquarters
In a two-tier model, headquarters keeps the ERP it already runs. Subsidiaries or newly acquired operations run a cloud ERP that reports up into it.
The two tiers have different needs. Head office wants stability and the deep customisation built up over years. A subsidiary needs to be operational quickly, in its own currency and tax regime, without waiting for a global rollout.
Companies have used this approach successfully: NetSuite for ERP and financials, CRM, ecommerce and supply chain at the satellite operations, synchronising with the on-premise ERP at headquarters.
This is the first question because it is the hardest to fix later. A subsidiary system has to post in local currency, meet local tax rules and still consolidate cleanly into the group.
Ask to see consolidation across entities demonstrated, not just described. The difference between native consolidation and an export-and-combine process is the difference between a close that takes days and one that takes weeks.
On-premise upgrades are projects. Cloud upgrades should not be.
Find out who performs the upgrade, how often it happens, and what it does to your customisations. Oracle publishes the contractual framework for its NetSuite cloud services. It is worth reading those terms alongside any quote rather than after you have signed.
Every cloud system has ceilings. You should know yours before you sign rather than when you hit them.
Oracle documents NetSuite service tiers that cover the maximum number of users, file storage and monthly transaction lines. The Standard tier starts at up to 100 users, 100 GB of storage and 200,000 monthly transaction lines. The Ultimate tier scales to 4,000 users and 50 million monthly transaction lines.
Match those figures against your transaction volume and your growth plan, not against today’s numbers alone.
In a two-tier model the integration is the product. If the subsidiary system cannot pass a trial balance up to head office cleanly, the model does not work.
Ask specifically what is synchronised, how often, and what happens when a record fails to post. The error handling matters more than the happy path.
Financials alone rarely justify the move. The subsidiaries usually need inventory, order management, CRM or ecommerce alongside the ledger.
Oracle documents the inventory capability in detail, covering real-time quantities, costs and asset values across locations. Check that the modules you need form part of the suite rather than a third-party addition you will have to maintain separately.
The software is the same everywhere. The implementation is not.
A partner has to understand local tax, local reporting and the operating reality of the countries where your subsidiaries sit. Softype has delivered more than 600 NetSuite implementations over 25 years across multiple regions. In a two-tier rollout that regional experience usually shapes the timeline more than the software itself does.
Start with one subsidiary rather than several. The first deployment is where you discover what the integration with headquarters actually requires, and it is far cheaper to learn that once.
Choose a subsidiary that is representative but not critical. A site with real operational complexity teaches you something useful. The largest revenue-generating entity is the wrong place to learn those lessons.
Then treat the first rollout as the template. Once the entity structure, the chart of accounts and the synchronisation to head office are settled, subsequent subsidiaries become configuration rather than fresh projects.
A two-tier model keeps headquarters ERP in place and runs cloud ERP at subsidiaries.
The two tiers have genuinely different needs: stability at head office, speed at the subsidiary.
Entity and currency structure is the first evaluation criterion because it is hardest to retrofit.
Establish who performs upgrades, how often, and what happens to your customisations.
Know your capacity ceilings for users, storage and monthly transaction lines before signing.
In a two-tier rollout the integration with headquarters is effectively the product.
Regional partner experience usually drives the timeline more than the software does.
Headquarters keeps its existing ERP while subsidiaries and satellite operations run a cloud ERP that synchronises with it. It lets a group modernise at the edges without replacing the head-office system in one move.
Subsidiaries need to be operational quickly, in their own currency and tax regime, without waiting for a global rollout. A cloud system can be deployed at that pace where a full headquarters replacement cannot.
Whether they can handle your entity and currency structure. It is the hardest thing to retrofit later. Ask to see consolidation across entities demonstrated rather than simply described.
Oracle documents service tiers that set maximum users, file storage and monthly transaction lines. The Standard tier covers up to 100 users, 100 GB and 200,000 monthly transaction lines. The Ultimate tier scales to 4,000 users and 50 million monthly transaction lines.
The integration with headquarters, and the partner’s experience in the regions where your subsidiaries operate. The software is identical everywhere; the local tax, reporting and operating knowledge is not.
Oracle publishes the documentation behind the capabilities described above:
Softype is an Oracle NetSuite solution provider with more than 25 years of experience and over 600 implementations. To talk through what this would look like for your business, book a meeting or contact us.
Helping businesses thrive with integrated ERP solutions.
NetSuite
Service
Company
Contact Us
Copyright © 2026
