ERP cloud vs on-premise
the real 5-year bill
Cloud ERP markedly more expensive than on-premise over 5 years. Why the gap and when cloud really wins.
The cloud vendor will show you the monthly subscription cost and a nice "zero upfront cost" chart. The on-premise vendor will show low license cost and "full data control". Both presentations skip half of the real costs. I compared both models on the same example: a 200-employee company, Microsoft Dynamics 365 Business Central. Cloud TCO turned out to be clearly higher than on-premise over a 5-year horizon (figures indicative, depend on user count, modules and current license rates; we prepare the full calculation at the consultation). Break-even: 36-48 months for a 200-user company with full customization. If you are planning a manufacturing deployment, also see our article on CMMS vs ITSM for manufacturing, which explains when ERP alone stops being enough.
Why TCO always lies - 9 hidden costs
Every model has costs that do not show up in the offer. Vendors deliberately skip these items - not because they are dishonest but because their sales model relies on a low entry cost. Here is what disappears from the deck:
Hidden cloud costs
- Internet link redundancy: Cloud ERP has a critical single point of failure - the internet link. An ISP outage is a full system outage. For a 200+ employee company, the minimum is 2 independent links from different ISPs (MPLS + xDSL or 5G). Cost: 2,400-4,800 PLN/year. Cloud offers never include this and any IT manager will ask about it.
- Data egress costs: Public clouds charge for outbound data transfer above a free quota. With regular backups and report exports outside the system these costs add up and are not visible in standard subscription offers. Current rates and quotas should be checked in the provider's price list.
- Vendor lock-in exit cost: After 5 years you want to change provider (better system, too expensive). Extracting data, rewriting integrations, testing - that is a 150-400k PLN project. On-premise has the same problem but far less often.
- Customizations via API, not code: Dynamics 365 Business Central does not allow editing source code. Every custom calculation, report or workflow has to go through REST API or Power Automate (more paid licenses). In on-premise you write directly in C/AL code at 500 PLN/hour. Via API: 1,500-2,000 PLN/hour (requires a solution architect). For a company with 5 customizations a year: +100-200k PLN of cost.
- Per-user subscription: Dynamics 365 BC Essentials in Microsoft 365 is 80 USD/user/month. For 200 active users: 192,000 PLN/year. Business logic changes, you hire +10 employees - automatically +9,600 PLN/year. No room to negotiate. At 20% growth over 5 years (200 to 240 users): +192,000 PLN of additional cost.
Hidden on-premise costs
- IT time for maintenance: The IT director must assign someone for ongoing support: OS patches, backup management, performance monitoring, incidents (where is the database during a network outage?). For an ERP serving 200 users the real cost is 0.25-0.5 FTE, or 50-100k PLN/year. Alternative: managed hosting (80-150k PLN/year) - then you do not handle it yourself.
- Hardware refresh every 5-7 years: PowerEdge or HP ProLiant servers live 5-7 years. After that failure risk grows exponentially. In year 3-4 of a five-year project you need to plan: storage expansion or disk swap (80-150k PLN). At cycle end: full server replacement (150-250k PLN). One of the reasons many companies move to cloud.
- Disaster recovery costs: A main server on-site is a risk. The minimum DR procedure is: backup to a second physical location (partner data center, cloud storage for copies) + restore testing every six months. One-off setup cost: 30-80k PLN. Annual maintenance (offsite storage + tests): 15-30k PLN. That is 225k PLN over 5 years.
- Deferred upgrades = tech debt: The vendor releases a new ERP version. The upgrade is a project: testing, data migration, user retraining (can take 3-6 months). Cost: 100-300k PLN. Many companies "wait another year" - and suddenly they have a system 3-4 versions behind. After 5 years: a major upgrade is a 200-400k PLN project you must plan, while cloud handles this (updates are automatic).
5-year cloud TCO - sample calculation
The table below is an illustrative example, not a price list. Assumptions: 200 employees, 120 active ERP users, Microsoft Dynamics 365 Business Central, Poland, 5-year horizon. All figures are estimates illustrating the cost structure - real values depend on user count, modules, exchange rates and current pricing.
| Cost item | Year 1 | Years 2-5 (total) | 5-year total |
|---|---|---|---|
| Licenses (BC Essentials subscription) | 230,400 PLN | 921,600 PLN | 1,152,000 PLN |
| Implementation and data migration | 380,000 PLN | - | 380,000 PLN |
| Customizations and API integrations | 120,000 PLN | 480,000 PLN | 600,000 PLN |
| Partner support (Annual Support) | 46,080 PLN | 184,320 PLN | 230,400 PLN |
| Training and change management | 80,000 PLN | 80,000 PLN | 160,000 PLN |
| Extra infrastructure (links, tools) | 18,000 PLN | 72,000 PLN | 90,000 PLN |
| Egress costs and data transfer | 8,000 PLN | 32,000 PLN | 40,000 PLN |
| Scaling cost (new users +20%) | - | 192,000 PLN | 192,000 PLN |
| Termination/exit costs | - | 250,000 PLN | 250,000 PLN |
| TOTAL | 882,480 PLN | 2,211,920 PLN | ~6.5M PLN (indicative, depends on user count, modules, license terms) |
Note: the figures above are assumptions. Microsoft periodically updates Business Central pricing (including a 2025 subscription price hike), so a real calculation should use current rates, exchange rates and possible future increases.
5-year on-premise TCO - sample calculation
Same illustrative example: 200 employees, 120 users, perpetual on-premise license. Note: Microsoft is moving consistently to subscription and limiting Business Central perpetual licenses for new customers - availability of this model should be confirmed with a partner. On-premise alternatives include systems like Comarch ERP XL. Figures in the table are estimates.
| Cost item | Year 1 | Years 2-5 (total) | 5-year total |
|---|---|---|---|
| Perpetual license (one-off) | 520,000 PLN | - | 520,000 PLN |
| Annual maintenance (typically low double-digit % of license value) | 104,000 PLN | 416,000 PLN | 520,000 PLN |
| Implementation and data migration | 320,000 PLN | - | 320,000 PLN |
| Hardware (servers, storage, UPS) | 280,000 PLN | 80,000 PLN | 360,000 PLN |
| Customizations and integrations (code) | 80,000 PLN | 200,000 PLN | 280,000 PLN |
| IT costs: maintenance, administration | 72,000 PLN | 288,000 PLN | 360,000 PLN |
| Training | 60,000 PLN | 40,000 PLN | 100,000 PLN |
| Backup, DR, security | 45,000 PLN | 180,000 PLN | 225,000 PLN |
| OS, database licenses | 120,000 PLN | - | 120,000 PLN |
| Power, cooling, server-room space | 36,000 PLN | 144,000 PLN | 180,000 PLN |
| TOTAL | 1,637,000 PLN | 1,348,000 PLN | ~3.5M PLN (indicative, depends on user count, modules, license terms) |
Key observation: on-premise is more expensive in year 1 (in this example ~1.6M PLN vs ~880k PLN, indicative) but cheaper from year 2 onward. A company that cannot survive year 1 financially picks cloud out of necessity, not conviction.
When cloud actually wins - 5 scenarios
Despite higher 5-year TCO, cloud ERP is the right choice in specific cases:
Scenario 1: A company with no in-house IT
A 50-80 employee trading company, one network admin (burned out, doing everything). On-premise ERP requires deployment, testing, backups, monitoring, incidents. You will quickly need to hire a specialist (+80k PLN/year) or outsource managed hosting (+100k PLN/year). Cloud is 30k PLN/year for the subscription - the rest is on the vendor. For a no-IT company cloud is more expensive by 150-200k in year 1 but cheaper by 50-100k/year from year 2.
Scenario 2: A fast-growing company
Plan: from 100 employees to 200 in 3 years. A 2-CPU, 32 GB RAM server is enough today but a bottleneck in a year. On-premise requires upfront over-provisioning (more expensive now, resources wasted) or a year 2 upgrade (another 150k PLN capex). Cloud scales smoothly: +10 users = +1,600 PLN/year. No surprises. Cloud wins for 200% user growth despite higher per-user cost because you avoid hardware refresh.
Scenario 3: Multiple locations and remote work
Distribution company: HQ + 3 regional warehouses + field reps. On-premise ERP at HQ needs: (a) VPN (30k PLN setup + 10k PLN/year), (b) deployment at every location (+80k PLN), (c) off-hours data sync (risk of inconsistencies). Cloud: everyone logs in from the browser, works in real time, online/offline transparently. Additional cost? Zero. SPOF? One - the internet link (which they need anyway). Cloud wins economically by 100-150k PLN over 5 years.
Scenario 4: Short deployment time, fast ROI
The company runs without ERP (Excel, manual processes) and loses ~5% of revenue annually to errors and lack of visibility. They need a system fast. Cloud ERP: go-live in 3-6 months. On-premise: 6-18 months. Every month without the system costs ~400k PLN of losses (at 100M revenue). Cloud TCO will be higher but at the EBITDA level cloud wins by 2-4M PLN in year 1.
Scenario 5: Industries with compliance requirements
A pharma company. Audit: "Where does our data go? What SLA do you have? What DR?" On-premise needs: ISO 27001 (80-120k PLN first year), geographic redundancy (second data center = 200-300k PLN), DR tests every six months (30-50k PLN/year). Cloud Microsoft Azure already has: EU compliance (GDPR), 99.95% SLA, audit trail, encryption at rest/in transit, DR documentation. Cost? Included in the subscription.
When on-premise wins: manufacturing company with rich, specific processes (code-level customization), stable headcount without fast-growth plans, strong in-house IT, company that already owns server infrastructure and does not plan to retire it. If you use Comarch ERP and want a detailed calculation for that system, see our Comarch ERP subscription vs perpetual license analysis.
How to calculate break-even for your company
Break-even = the point at which cumulative on-premise cost (high start, low monthly) catches up with cumulative cloud cost (low start, high monthly).
Simple formula
Break-even (months) = (Year 1 on-premise cost - Year 1 cloud cost) / (Reasonable annual difference in years 2-5)
The figures below are indicative and follow from sample assumptions, depending on current pricing, user count and company specifics.
Year 1 (capex):
On-premise: ~1,637,000 PLN (license, hardware, deployment, maintenance, estimate)
Cloud: ~882,000 PLN (subscription + deployment, no hardware, estimate)
Difference: on-premise may need ~750,000 PLN more in year 1
Years 2-5 (annual run cost):
On-premise: ~337,000 PLN/year (maintenance, hardware refresh, IT, DR)
Cloud: ~553,000 PLN/year (subscription rising + integrations)
Cloud is ~200,000 PLN more expensive every year
Break-even calculation (example):
~750,000 PLN / ~200,000 PLN = about 3.5 years = ~42 months
Meaning: if the company plans to keep the system 5+ years, on-premise will be cheaper. If 3 years or less, cloud.
Note on 18-22 months: that is break-even for a small company (80-100 users, simple ERP, infrastructure already in place). For 200 users on Dynamics 365 BC with customizations - break-even is 36-48 months. Key insight: the more users and the more complex the functionality, the faster on-premise wins economically. Reason: an on-premise license is a one-off cost (amortized). Cloud subscription is variable (linear growth).
FAQ
Is cloud ERP always more expensive than on-premise?
Over 5 years: depends on scale and licensing, but for companies over 150 users on-premise often has lower total TCO. Reason: subscription does not shrink, hardware amortizes, and maintenance costs spread over time. Exceptions: (1) companies with no in-house IT - on-premise costs go up by external support, (2) companies with existing server infrastructure, (3) companies planning the system for less than 3 years.
When is cloud ERP economically the better choice?
Cloud wins when: (1) no in-house IT, (2) fast growth - cloud scales naturally while on-premise needs hardware upgrades, (3) multiple locations - cloud eliminates VPN/WAN, (4) time-to-value critical - 3 months vs 12 months, (5) compliance mandated - cloud has built-in GDPR/ISO 27001, (6) horizon under 3 years - break-even for cloud comes earlier.
How do I calculate break-even for my specific company?
Steps: (1) Sum year 1 on-premise: license + hardware + deployment + maintenance (IT) = X. (2) Sum year 1 cloud: subscription + deployment = Y. (3) Difference = X-Y. (4) Calculate annual costs years 2-5: on-premise (maintenance+IT+upgrades) vs cloud (subscription+API customization). (5) Annual difference in favor of on-premise = Z. (6) Break-even months = ((X-Y)/Z)*12.
What if on-premise has expensive version upgrade cycles?
That changes TCO drastically. Annual support cost (Software Assurance or maintenance) for most on-premise systems is in the low double digits of license value, exact rate depending on the vendor. Major upgrades are a separate project: re-test, data migration, retraining. On-premise companies often wait 3-4 years between upgrades, deferring cost. Cloud eliminates this: updates are transparent and included in the subscription.
Calculate the real TCO for your company
In 60 minutes we will prepare a cloud vs on-premise comparison with your data: user count, customization needs and industry specifics. Zero hidden costs in the calculation.
Book a free TCO calculation →