On-premise ERP: costs, control, and when to stay
On-premise ERP means the application and database run on servers your company controls.
On-premise ERP means the application and database run on servers your company controls. For a US or Canadian firm of about 20 to 100 people, decide whether to stay, move to cloud, or run hybrid, and what the licence floor costs over five years. Assume 25 users on Dynamics 365 Business Central Essentials. At the US list price of USD 80 per user per month, paid yearly, five years of subscription is USD 120,000 before implementation, apps, and extra environments, as of October 2026. The Canada list for the same mix is CAD 108.50 per user per month, or CAD 162,750 over five years before tax.
Those totals are a licence floor from Microsoft's pages as of October 2026. Servers, SQL, backups, and an administrator sit outside them. On-premise still fits when you already own Dynamics GP on the Modern Lifecycle Policy (or you moved a GP 2018 or 2018 R2 install there with a compatible tax release or hotfix) and you can live with enhancements and tax updates through 31 December 2029 and security updates through 30 April 2031. GP 2016 and 2016 R2 are already past extended support, which ended 14 July 2026.
The rest of this page is the decision matrix: which products still install on your servers, what five years of list price includes, where a Canadian database sits, and how a cutover behaves when history and open orders move on different dates.
What on-premise ERP means next to cloud
An on premise ERP install is the copy you patch, back up, and upgrade on hardware you operate or rent as a virtual machine. Cloud ERP, in the sense buyers use on an erp on premise vs cloud shortlist, is a subscription the vendor hosts, updates, and restores. The same brand can sit on both sides. Odoo Standard is Odoo Online only. The Odoo Custom plan is the one that includes Odoo Online, Odoo.sh, or on-premise. Business Central is sold as a cloud subscription at the prices below, and Microsoft still documents an on-premises product that can migrate online once it meets a version gate.
Hosted is the middle. Your database runs in a cloud region, often as a private instance, and your team or a host still owns upgrades. On premise vs cloud erp turns on who owns the upgrade. A buyer comparing erp cloud vs on premise should separate that private instance from multi-tenant Business Central online, because the country you pick for the online environment chooses both the localization and the Azure geography. Definitions of SaaS, single-tenant hosted, and on-premises architecture sit in our ERP deployment models guide. This page stays on the stay, move, or hybrid choice.
ERP Research, citing Panorama Consulting's 2025 ERP Report, says about 79% of organizations deploying a new ERP chose cloud, up from about 65% the year before, and puts on-premise near 30% of the installed base from a 2024 Fortune Business Insights figure. Both figures are secondary citations with medium confidence, because the underlying Panorama and Fortune pages were not checked. Your renewal still has to be priced on your licences and your servers.
Cloud versus on premise ERP cost comparison
Microsoft's US pricing page lists Business Central Essentials at USD 80.00 per user per month, Premium at USD 110.00, and Team Members at USD 8.00, each paid yearly, as of October 2026. Microsoft says displayed prices are informational and can differ by currency, country, and region. The Canada pricing page lists Essentials at CAD 108.50, Premium at CAD 149.20, and Team Members at CAD 10.90 per user per month, paid yearly, plus applicable tax.
- Business Central Essentials (US list per user per month: USD 80.00 · Canada list per user per month: CAD 108.50 plus tax)
- Business Central Premium (US list per user per month: USD 110.00 · Canada list per user per month: CAD 149.20 plus tax)
- Business Central Team Members (US list per user per month: USD 8.00 · Canada list per user per month: CAD 10.90 plus tax)
Sources for the table: US pricing and Canada pricing, Microsoft, October 2026.
A 25-user licence floor, subscription only
Assume 25 named users, all on Essentials, for five years. The arithmetic covers licences only. Extra environments, ISV apps, and implementation sit outside it. US arithmetic is 25 times USD 80 times 12 times 5, which is USD 120,000. Canada arithmetic is 25 times CAD 108.50 times 12 times 5, which is CAD 162,750 before tax.
Change the mix and the floor moves with it. Assume 17 Essentials users and 8 Team Members, same five years, US list: 17 times USD 80 times 60 is USD 81,600, and 8 times USD 8 times 60 is USD 3,840, so USD 85,440. The same mix in Canada is 17 times CAD 108.50 times 60, which is CAD 110,670, plus 8 times CAD 10.90 times 60, which is CAD 5,232, so CAD 115,902 before tax. All 25 on Premium is 25 times USD 110 times 60, which is USD 165,000, or 25 times CAD 149.20 times 60, which is CAD 223,800 before tax.
This cloud versus on premise ERP cost comparison stops at the cloud subscription. Price any on-premises Business Central licence or enhancement, SQL, backup, and the person who applies them as separate bidder lines beside that subscription.
Odoo, for one discount year only
Odoo's pricing card, as of October 2026, shows Standard (Odoo Online only) at US$31.10 and US$38.90 per user per month, and Custom at US$61.00 and US$76.20 per user per month. A note says the discount is valid for 12 months for the initial users ordered. Odoo.sh hosting is not included in the licence. The card also lists a Light User at US$8.90. Odoo shows these rates in US dollars. Apply them to a Canadian budget only after Odoo confirms the currency on your order.
Assume the same 25 full users on Custom, which is the plan required for on-premise or Odoo.sh. At the lower displayed rate, year one is 25 times USD 61 times 12, which is USD 18,300. At the higher displayed rate, year one is 25 times USD 76.20 times 12, which is USD 22,860. Keep USD 61 inside that first year. After month 12 the stated discount ends, so ask Odoo for the renewal rate before you extend the model. Hosting for custom work on Odoo.sh, and maintenance of custom code, are extra. Ask the host to price Odoo.sh workers and storage on their own lines.
What the licence floor leaves out
Subscription list price is the part a CFO can see. An on-premise ERP still needs servers, SQL Server, backups, a recovery test, and an administrator. Those lines sit outside the tables above. Add them before you compare a subscription with a server you already operate.
On Business Central online, Essentials and Premium each include one production environment and three sandbox environments at no extra charge, as of October 2026. Each extra production environment, bought through a CSP partner, includes three more sandboxes and 4 GB of extra tenant-wide database capacity. A company that needs a second company database, or a long-lived training copy beyond the three sandboxes, should price that capacity before calling the subscription complete. Details are on Microsoft's environment administration page.
Odoo says hosting, maintenance, and upgrades are included in its plans, with two exclusions that matter if you self-host or use Odoo.sh for custom developments: Odoo.sh hosting for that custom work is not included, and maintenance of custom code is not included. On-premise users must run the latest stable version. Budget the upgrade as a yearly task, because staying current is a licence condition.
Implementation is a separate cheque. Odoo Success Packs for new customers, with 15% off the first pack, list as of October 2026 at USD 493 for 4 hours (Starter), USD 3,060 for 25 hours (Basic), USD 5,950 for 50 hours (Standard), USD 10,625 for 100 hours (Custom), and USD 21,250 for 200 hours (Pro). Returning-customer prices are USD 580, USD 3,600, USD 7,000, USD 12,500, and USD 25,000. Odoo says 80% of projects in the estimator's scope go to production in 200 hours or less, and claims a 98% implementation success rate with a pack versus 65% without. Those rates are Odoo's own figures for Odoo's pack scope. A GP database with years of history needs its own quote. A Dynamics move should be quoted as its own line: version upgrade, data migration, integrations, and training. Ask each bidder to price data migration as its own line.
Buyers leaving GP describe the services bill in blunt terms. One wrote of "All of this costing well into six-figures, many using it for 5-figure A MONTH subscriptions." That comment is on a GP end-of-support thread, Treat it as a budget warning from that thread. Insist on a written split between licences and services.
A sizing comment from operators who still run servers belongs in the same worksheet. On an on-premises or AWS thread, one administrator wrote: "The software requires about 1GB per user on the server side... Storage... 2TB storage is a good starting point for approximately 90 users and should last 3-5 years." Treat that as one system's experience. Have your vendor measure your database and growth, then put hardware refresh inside the five-year column for any option that stays on servers you operate.
Which on-premise ERP options still exist
For a company in the 20 to 100 person range, the products you can still place on servers you control cluster around three situations.
You already run Dynamics GP. You own the licences. A user on the support thread put the attraction plainly: "we own the licenses, and they're good forever." The dates in the next section are the constraint on that licence.
You run Dynamics NAV or Business Central on-premises. Microsoft's cloud migration tool accepts Business Central on-premises version 25 and later directly. Versions 15 through 24 must be upgraded to at least version 25 on-premises first. Version 14 can take a full upgrade path, or a reimplementation tool that moves master data, opening balances, and setup only. NAV has no direct cloud-migration path. Microsoft says a NAV database must be upgraded to Business Central on-premises and then switched to Business Central online. The migration rules are on Migrate on-premises data to Business Central online.
You want Odoo on hardware you control. That choice is the Custom plan. Standard stays on Odoo Online. Odoo Online can be downloaded as a backup and moved to on-premise, and Odoo says the best time is right after a new stable release. Odoo Community self-host is a different product and is outside the prices on this page. Hosting shapes for Online, Odoo.sh, and self-host are compared in Odoo hosting options compared.
How long Dynamics GP on-premise support lasts
Staying on GP is a dated decision. Microsoft will end Dynamics GP product enhancements, regulatory (tax) updates, and technical support on 31 December 2029. That date was previously announced as 30 September 2029. Security updates, if needed, continue until 30 April 2031. Understand the Lifecycle Policies records a retirement of 1 January 2030 at 6:59:59 a.m. Pacific, the same instant as the end of 31 December 2029 Pacific. The Dynamics GP lifecycle product page lists a start date of 7 October 2019, a retirement date of 1 January 2030, and states that Dynamics GP follows the Modern Lifecycle Policy.
Version rows are tighter than the product headline.
- GP 2016 and 2016 R2 (What the lifecycle page says: Extended support ends · Date: 14 July 2026)
- GP 2018 and 2018 R2 (What the lifecycle page says: Extended support ends · Date: 11 January 2028)
- GP on the Modern Lifecycle Policy (What the lifecycle page says: Enhancements, tax updates, and technical support end · Date: 31 December 2029)
- GP on the Modern Lifecycle Policy (What the lifecycle page says: Security updates, if needed, continue until · Date: 30 April 2031)
As of October 2026, GP 2016 and 2016 R2 are already past extended support. Staying on that build means running without that support. GP 2018 and 2018 R2 still have extended support through 11 January 2028. Installing a compatible tax release or hotfix on GP 2018 or 2018 R2 moves the install to version 18.5 or later and onto the Modern Lifecycle Policy. Customers on that policy stay current by taking at least one of three yearly updates, typically June, October, and December.
Read that as a stay-for-now window. A company that is stable on 18.x, current on tax updates, and unwilling to fund a new subscription this year can keep operating inside those dates. The same company should put 31 December 2029 on the finance calendar, because enhancements and tax updates stop then, even though security updates can run to 30 April 2031. Perpetual licences you already paid for do not extend those dates.
What a move does to cutover and history
Microsoft's cloud migration path is a data migration with version gates. The migration page gives those gates and the supported sources. Ask the implementer to test a copy of your database and tell you what moved and how long the load took.
Built-in cloud migration to Business Central online requires SQL Server 2016 or later and database compatibility level 130 or higher. Business Central on-premises version 25 and later can migrate directly. Versions 15 through 24 stop at an on-premises upgrade to version 25 before the cloud tool will take them. Dynamics GP 2015 and later, and Dynamics SL 2015 and later, are supported migration sources. NAV is the longer road: Business Central on-premises first, then online.
History is the point that surprises finance teams. A GP user on the support thread wrote: "Moving transaction data from GP to BC (or F&O) is basically not going to happen." Microsoft listing GP 2015 and later as a supported source tells you a path exists. It does not, on that page, itemize years of posted invoices. The version 14 reimplementation option is explicit and narrower: master data, opening balances, and setup only. Have the bidder show, on a copy of your company, which tables land in Business Central and which stay behind in GP for audit.
The operating pattern buyers already use is a parallel run. The same thread describes it this way: "It's setup a whole new system, copy your customer data/addresses, and some of your inventory. Run both systems side-by-side until all GP transactions are closed (months to a year)." Budget people and licences for both systems across that overlap. Close purchase orders, shipments, and open invoices in the system that created them. Start new orders in the new system on a posted cut date. Months to a year is a practitioner's range for GP. Microsoft's migration page does not set that span as a service level.
Do not confuse that cutover with Business Central's update window. A new Business Central online environment gets a default update window that keeps updates out of 8:00 p.m. to 6:00 a.m. local time for the environment's country or region. Admins can change that window. Time the data load from a test on your database, then confirm the window in the tenant admin center so you know which hours stay clear of updates.
Where a Canadian company's data is stored
The country you select for a Business Central online environment sets the localization and the Azure geography where the database is created and stored. Canada (Microsoft localization, base app NA, abbreviation CA) deploys to the Canada Azure geography. The United States deploys to the United States geography. Mexico, also base app NA, deploys to the United States geography. Choosing Canada is the setting that places the environment database in Canada. Choosing United States places it in the United States, including for a Canadian company that picks the US environment by mistake. English (Canada) and French (Canada) application translations are provided by Microsoft and are available on Marketplace. The country and language matrix is on Country/regional availability and supported languages.
Privacy law is a separate question from the Azure region. PIPEDA sets rules for how private-sector organizations collect, use, and disclose personal information in commercial activity in Canada. Organizations in Alberta, British Columbia, and Quebec are generally exempt from PIPEDA for personal information handled inside the province, because those provinces have substantially similar private-sector laws. Personal information that crosses a provincial or national border in a commercial activity is still subject to PIPEDA. The Office of the Privacy Commissioner of Canada explains that scope in PIPEDA in brief.
A Canada Azure geography can satisfy a residency preference your contract or your customers require. It does not retire PIPEDA when personal information still crosses a border, for example when a US parent opens the same customer records. Put the environment country, the list of people who can export data, and any cross-border processing into the same decision note. Have counsel read your customer contracts. Do not treat a cloud region as a substitute for that reading.
When hybrid beats a full move
Hybrid, for this size of company, is usually one of three patterns. Each one is a phase plan with an owner. A pile of disconnected apps around an old server is a different, more expensive outcome.
Business Central on-premises below version 25. The cloud tool waits until that database is on version 25. The practical hybrid is to upgrade on-premises first, prove month-end on the new version, then migrate. Companies on version 14 who only need masters, opening balances, and setup can reimplement and leave history where it is.
Odoo Custom on your servers, with a later move to Odoo.sh or Odoo Online. You pay the Custom rate because on-premise requires it, you run the latest stable version, and you schedule the download-and-move for the window right after a new stable release. Odoo.sh remains available on the same Custom plan when you want the vendor to host, and you still add hosting for custom developments on top of the user fee.
GP kept as the book of record for closed years, with new transactions starting in Business Central. That matches the parallel-run description above. It also matches the licence math: you keep paying GP infrastructure until the last open document is closed, and you start Business Central subscriptions when the new users go live. Dynamics SL 2015 and later can be a migration source on the same Microsoft tool if that is the ledger you have.
One performance limit shows up whenever the client and the database are far apart. The same operations thread warned: "If you split the client from the DB either via regions or on-prem client and cloud DB your overall end user performance will drop." If warehouse scanners or order entry sit in one region and the database in another, test a realistic order, pick, and invoice on that split before you call the hybrid finished.
How to choose stay, cloud, or hybrid
Score the choice in the order that changes the cash, then the calendar.
- Write the five-year licence floor with your real mix. Use Essentials, Premium, and Team Members counts, US or Canada list, as of October 2026, and state that prices can differ by region. For Odoo, show year one at both displayed Custom rates and refuse a five-year extension of the discount.
- Add the lines the list price skips: SQL and servers if you stay, extra Business Central environments if you need more than one production database, Odoo.sh or custom-code maintenance if you leave pure Odoo Online, and a named administrator either way.
- Match the product to a clock. GP 2016 is already outside extended support. GP on the modern policy has enhancements through 31 December 2029 and security updates to 30 April 2031. Business Central versions 15 to 24 need version 25 before cloud migration. NAV needs a Business Central on-premises step first.
- Pick the geography on purpose. Canada for a Canada Azure database, United States for a United States database, and a PIPEDA note if personal information crosses a border.
- Decide what history is worth. If open items and masters are enough, a reimplementation can be shorter. If auditors expect drill-back to posted GP documents, keep GP online for inquiry and accept the parallel cost.
- Buy the first phase as a scoped project. The written scope sets its timeline and price before work starts. A bounded first phase can sit beside your version upgrade or parallel close when the database requires that work.
ERP implementation services are how we run that choice with you: discovery, a phase plan, data migration, and the weeks after go-live. A Business Central path, including the version gate and the US or Canada licence mix, is scoped on our Business Central implementation page. An Odoo path that starts from Custom, because on-premise and Odoo.sh require it, is scoped on our Odoo implementation page.
Bring the version you run, a user count split by role, and whether the database must stay in Canada. The first working session should end with a stay, move, or hybrid recommendation and a licence floor you can take to finance.
How Flectic can help
At Flectic, we help companies of 20 to 100 people in the US and Canada choose between staying on-premise, moving to cloud or running hybrid, then implement the choice on Odoo or Dynamics 365. Flectic sends a written proposal with a fixed price for each phase before work starts. See the ERP implementation service for how that scope is set. The next step is to book a free discovery call with Flectic.
Sources
- Dynamics 365 Business Central pricing (United States), Microsoft, October 2026.
- Dynamics 365 Business Central pricing (Canada), Microsoft, October 2026.
- Managing Production and Sandbox Environments, Microsoft Learn, October 2026.
- Country/Regional Availability and Supported Languages, Microsoft Learn, October 2026.
- Migrate on-premises data to Business Central online, Microsoft Learn, October 2026.
- Understand the Lifecycle Policies - Dynamics GP, Microsoft Learn, October 2026.
- Dynamics GP lifecycle product page, Microsoft, October 2026.
- Odoo Pricing, Odoo, October 2026.
- Odoo Success Packs, Odoo, October 2026.
- PIPEDA requirements in brief, Office of the Privacy Commissioner of Canada, October 2026.
- On-Premise ERP Software 2026, ERP Research, October 2026.
- Support for Microsoft Dynamics GP is ending, Reddit, October 2026.
- ERP software on-premises or AWS, Reddit, October 2026.
Frequently asked questions
Is cloud ERP more cost-effective than on-premise ERP?
A cloud subscription can show a lower year-one cheque and a higher five-year licence line than a perpetual product you already own. Compare them only after you add servers, SQL, backups, administration, implementation, and any parallel run. For 25 Business Central Essentials users the US list floor is USD 120,000 over five years as of October 2026, and that figure still excludes those other lines. The cheaper side depends on your user mix and on how long the current support window still runs.
What are the main differences between cloud ERP and on-premise ERP?
On-premise ERP runs on servers you patch, back up, and upgrade. Cloud ERP is a subscription the vendor hosts and updates, and you choose settings such as Business Central's country, which also picks the Azure geography. Odoo Standard is online only. On-premise or Odoo.sh requires the Custom plan, and on-premise users must run the latest stable version. The same brand can therefore be a subscription, a hosted private instance, or a server you operate.
Does anyone still use on-premise ERP in 2026?
Yes. ERP Research, citing Panorama Consulting's 2025 ERP Report, says about 79% of new ERP deployments chose cloud, up from about 65% the year before, and puts on-premise near 30% of the installed base from a 2024 Fortune Business Insights figure. Both figures are secondary citations with medium confidence, because the underlying Panorama and Fortune pages were not checked. Dynamics GP on the Modern Lifecycle Policy still has enhancements through 31 December 2029, and GP 2016 extended support has already ended.
Which ERP vendors still offer an on-premise option?
Odoo sells on-premise on the Custom plan, which also covers Odoo Online and Odoo.sh. Business Central still has an on-premises product that Microsoft will migrate online once it is on version 25, with older versions upgraded first. Dynamics NAV reaches the cloud only after an upgrade to Business Central on-premises. Dynamics GP and Dynamics SL 2015 and later are supported migration sources, and many companies still run GP on the licences they already own.
Is on-premise ERP more secure than cloud?
On-premise ERP puts patching, backups, and physical access on your team. Business Central online lets you place the database in the Canada or United States Azure geography by choosing that country, and Microsoft applies updates inside a window you can change. PIPEDA still applies when personal information crosses a provincial or national border, including when the database itself sits in Canada. Security here is who operates the controls, plus where personal information travels.
How long does an on-premise ERP implementation take?
Odoo says 80% of projects inside its estimator's scope go to production in 200 hours or less, which is its own claim for a Success Pack, up to the Pro pack at 200 hours. A GP replacement often runs both systems until open transactions close, and buyers on GP describe that overlap as months to a year. A version upgrade to Business Central 25, required before some cloud migrations, adds a project of its own before the new system takes live orders.
What does end of life mean for Microsoft Dynamics GP?
For GP on the Modern Lifecycle Policy, product enhancements, tax updates, and technical support end on 31 December 2029. Security updates, if needed, continue until 30 April 2031. Understand the Lifecycle Policies records retirement at 1 January 2030, 6:59:59 a.m. Pacific, the same instant as the end of 31 December 2029 Pacific. The Dynamics GP lifecycle product page lists a start date of 7 October 2019, a retirement date of 1 January 2030, and the Modern Lifecycle Policy. GP 2016 extended support ended 14 July 2026, and GP 2018 extended support ends 11 January 2028 unless a tax release moves the install onto the modern policy.
Can I add new users to my existing Dynamics GP license after support ends?
Your licence agreement is what allows or blocks new users, and that term is separate from the support calendar. Before you hire against GP, ask Microsoft or your reseller to confirm in writing whether new users can be added after enhancements stop on 31 December 2029 and after security updates stop on 30 April 2031. If the answer is no, price Business Central Team Members and Essentials for the new seats instead of assuming the old licence stretches.