Is replacing Dynamics GP with self-hosted Odoo or ERPNext cheaper than Business Central?
Dynamics GP support ends December 31, 2029, so the question for a finance leader is which path costs less over the full life of the system, not in year one. On the software license line, self-hosted Odoo Community or ERPNext costs nothing to license, since the ERPNext pricing page states self-hosting is free and Odoo Community is LGPLv3. Business Central is different: it is sold per user, and this page does not have a supplied per-user price, so you must get current figures from Microsoft or a Business Central partner and compare them against your own seat count. The real gap usually sits elsewhere, in implementation, data migration, infrastructure, backup, and the internal skills to run the system after go-live. Those costs depend on your scope, customizations and staff, so they cannot be read off a price list. If you choose self-hosting, the recurring costs are the servers, backups, monitoring, patching and the people who run them. Frappe Cloud is a managed option, not a requirement: its pricing page lists shared site hosting from 5 US dollars per month and dedicated servers from 125 US dollars per month, which gives you a reference point for a hosted alternative. Ask any implementation partner to quote these separately: the license, the infrastructure, the migration, the customizations, and the upgrade and support work that a Community deployment does not include. On the Business Central side, check the exit cost before you commit. Microsoft documents that online databases can be exported as BACPAC files only with a paid subscription, and Microsoft does not support creating a working on-premises Business Central environment from a BACPAC exported from the online service. Ask your partner in writing what a full data exit would cost and how you would retain a readable copy of history for audits.
Which cost components differ between Business Central and self-hosted Odoo or ERPNext
This table sets each cost component of a Dynamics GP replacement on the Business Central path against the self-hosted Odoo and ERPNext paths, and marks whether each is one-time or recurring. Read the recurring lines first, since they decide the five-year shape of the budget, then check the optional paid lines (Odoo Enterprise, Frappe Cloud support) against your own requirements.
| Cost component | Business Central (Microsoft cloud or on-premises) | Self-hosted Odoo or ERPNext | One-time or recurring |
|---|---|---|---|
| Software subscription or license | Per-user subscription to Business Central, priced by Microsoft and sold through partners. Confirm the user tiers and add-on licenses in the written quote. | Odoo Community and ERPNext carry no license fee. Odoo Enterprise is an optional paid subscription for features such as Odoo Studio and version upgrades. | Recurring for Business Central. Recurring for Odoo Enterprise if chosen. None for Community or ERPNext. |
| Infrastructure | Included in the subscription if you choose online. On-premises deployment means you buy and run your own servers and SQL Server licensing. | Your own servers or cloud accounts, plus PostgreSQL or MariaDB, backups and monitoring. Frappe Cloud hosting is optional and starts at a published monthly price. | Recurring for both. Hardware or initial cloud build is one-time. |
| Partner migration fees | Partner-led conversion from GP, including data mapping, configuration and cutover. Scope depends on customizations and add-ons. | Not a licensing line. Data extraction, mapping and import are paid as part of implementation work, usually to a partner or your own staff. | One-time. |
| Implementation and configuration | Partner fees for setup, extensions and integrations, often based on the written scope and the number of modules. | Partner or in-house fees for setup, chart of accounts design and module configuration. ERPNext implementation is available through certified partners. | One-time, with later change requests recurring. |
| Data migration and validation | Mapping GP segments, masters and open transactions into Business Central, then reconciling balances before cutover. | Extraction from GP SQL Server, mapping to Odoo accounts or ERPNext dimensions, importing masters with the built-in tools and reconciling trial balances. | One-time per cutover, plus any parallel month-end runs. |
| Support and upgrades | Included in the subscription for the Business Central release waves. Partner support is a separate contract if you need it. | Odoo standard support covers three years per major version, and upgrades on Odoo Online and Odoo.sh are mandatory every two years. Frappe support requires a matching Frappe Cloud plan for warranty coverage. | Recurring. Confirm support windows and upgrade effort in your own environment. |
| Internal skills and admin time | Business Central administration, release testing and extension maintenance, usually with a smaller in-house team. | Staff or a partner to run Linux servers, databases, backups, upgrades and custom modules. Server Scripts in ERPNext require explicit enabling from version 15. | Recurring. Driven by how much customization you keep. |
| Exit and data export | Online databases export as BACPAC files only with a paid subscription, up to 10 times per month per environment. Microsoft does not support restoring that BACPAC to a working on-premises environment. | Your database and file storage stay on your own infrastructure, so you control the export. Confirm the format and tooling you need for an eventual move. | One-time at exit, but the cost depends on how the data was held from the start. |
How the license and subscription lines differ
Business Central is a recurring per-user subscription, and the rate is not in the sources we used for this page. Microsoft prices Dynamics 365 Business Central per user per month through its licensing terms and through partners, and the rate depends on the user types, the edition and any partner margin. Ask for the per-user, per-month price for each user type you need, the minimum seat count, what is included in the base license, and whether the partner quote covers the first year only. Treat the subscription as a line that continues for as long as you use the product, and compare it with the other paths over the same period. Odoo Community is licensed under LGPLv3, and ERPNext is licensed under GPL-3.0, so neither core carries a license fee. The recurring cost on those paths comes from Odoo Enterprise, if you choose it, and from hosting and support, which are separate lines. Odoo's pricing page lists One App Free, Standard and Custom plans with per-user monthly prices. Standard is Odoo Online only. Only Custom can run on-premise or on Odoo.sh, and only Custom includes multi-company, Odoo Studio, external API access and custom modules. If your GP estate needs multi-company consolidation, custom modules or API access to a warehouse or payroll system, budget Enterprise as a per-user recurring line. Confirm the current per-user rates on the Odoo pricing page before you model the figure. ERPNext has no license tier that changes the core, but its warranty is tied to support. Frappe's supported versions policy says a customer must run a listed version and hold a matching Frappe Cloud support plan to receive warranty coverage from Frappe. Self-hosting ERPNext does not require that plan, so the support contract becomes optional. If you want Frappe's warranty, confirm the plan tier and cost for your version with Frappe before you sign off on a self-hosted design. If you want support from a partner or your own staff instead, record that as an internal or partner line item.
What moves the cost comparison most
The Business Central and self-hosted Odoo or ERPNext paths price differently on the same components: licenses or subscriptions, hosting, implementation, data migration and internal time. The six drivers below decide how large each component becomes, so confirm each one with the vendor or partner before comparing totals.
User count and license tier
Business Central is priced per user and per license type, so the user count and the mix of full and limited users multiply the subscription line every year. Odoo Community carries no per-user license, while Odoo Enterprise and the Odoo Online plans price per user per month. Ask Microsoft or a partner for the license mix each role needs, and ask Odoo for the plan and user count your Enterprise or Custom quote assumes.
Data volume and history loaded
The more history you load, the more time goes into extraction, mapping, validation and reconciliation, and the larger the hosting footprint. Business Central online exports to BACPAC are limited to a paid subscription and up to 10 times per month per environment, and Microsoft does not support building a working on-premises environment from that export. ERPNext's Data Import guidance recommends importing only a few thousand records at a time, so large masters and open items add batches to the internal or partner schedule.
Odoo edition and modules needed
Odoo Community is free to download under LGPLv3, but the features that many GP sites need, such as multi-company, Odoo Studio, external API access and custom modules, sit in the Custom plan. Odoo Enterprise also brings the upgrade service and standard support. List the GP modules in use, including add-on products, and map each one to a Community app, an Enterprise feature or a custom build, since custom work is often the largest unplanned line.
Hosting choice and infrastructure
Self-hosting moves the cost to your own servers, backups, monitoring and staff time, with no vendor hosting fee. Frappe Cloud and Odoo.sh replace part of that with a platform fee, and Business Central online removes it entirely while adding subscription cost. Confirm which environments you need for production, test and parallel month end, because each one is a separate infrastructure line or hosting plan.
In-house skills or partner-led implementation
Self-hosting shifts cost toward people: someone must patch, back up, upgrade and support the platform after go-live, and implementation fees are paid to a partner or internal team. ERPNext's implementation is available through certified partners, and Business Central requires a partner for migration. Ask each bidder for a fixed scope covering data mapping, the parallel run, training and the first year of support, so the comparison uses the same deliverables.
Release cadence and upgrade effort
Each path has a recurring upgrade cost. Odoo major versions are supported for three years and must be upgraded on Odoo Online and Odoo.sh every two years, and minor releases arrive about every two months. ERPNext v15 and v16 both get frequent minor releases, and Frappe support requires a listed version and a matching Frappe Cloud support plan for warranty coverage. Budget upgrade testing as a recurring line, not a one-time project.
What your own infrastructure costs for Odoo or ERPNext
The infrastructure line is the one cost you pay directly to a provider, so it is the first thing to price. Odoo runs on PostgreSQL, so a self-hosted Odoo estate needs application servers, a PostgreSQL server with its own backup and patch cycle, file storage for attachments, and a separate environment for test copies and the upgrade rehearsal described in the Odoo upgrade documentation. ERPNext can use MariaDB or PostgreSQL, and a production Docker deployment built from the frappe_docker repository runs several services: MariaDB, Redis, background workers, the scheduler, Socket.io and Nginx. Each of these is a process you must size, monitor and restart. The single-file demo setup in that repository is marked for short-lived evaluation only, so budget for the fuller Compose layout from the start and do not let a demo stack become production.
The cloud or data center bill depends on choices you make, not on the software license. Ask your team to size for peak month-end runs, not average load, and to price three things separately: compute for the application and workers, managed or self-run database storage with point-in-time backup, and off-site backup retention that meets your records policy. Backup is a recurring cost that many estimates leave out. Frappe's ERPNext pricing page lists Frappe Cloud shared site hosting from 5 US dollars per month, shared servers from 20 US dollars per month and dedicated servers from 125 US dollars per month. Use those figures only as a managed-hosting reference point. Confirm current prices with Frappe directly, then price your own cloud account or data center using the same component list, because your region, egress, storage class and support contracts will change the result.
Two cost drivers are easy to underestimate. First, the number of environments: a production system, a staging copy for the migration rehearsal and a test copy for user acceptance each carry the same server footprint, so confirm whether you need all three running at once or only during cutover. Second, staffing time to operate the stack: someone must own patching, the scheduler and worker health, database maintenance and restore tests. When you request a quote from an implementation partner, ask for the infrastructure bill of materials by component, the backup and restore test plan, the recurring operations tasks and who performs them, and which items are one-time setup versus monthly. A quote that lists only a total hides where your money goes.
How to build the comparison with your own numbers
This sequence turns a vague renewal question into a five-year total for each path, built from your own seat count, written quotes and internal time. Each step produces a figure you can defend in front of finance and the board.
Inventory current GP seats and modules
Finance operations and IT should list every active GP user by role, every installed module (general ledger, receivables, payables, inventory, purchasing, manufacturing and any third-party add-ons), and every integration that feeds or reads GP, such as banking, payroll, tax or reporting tools. Count named users separately from occasional or read-only users, because Business Central pricing is per user and the split changes the quote. Done when the inventory is signed off by the controller and each add-on has a named owner and a known replacement need.
Request a written Business Central quote
Ask your Microsoft partner for a written quote that states the per-user subscription price for each role you named, the environment count (production, sandbox, and any test copies), the licensing terms for read-only or occasional users, and any price changes scheduled during your five-year window. Separately request the migration partner fee as a fixed or estimated line item with the scope it covers, including add-on replacement and data conversion. Done when you hold two documents that can be added up without assumptions.
Price Odoo or ERPNext from written partner scopes
Ask two or three implementation partners for written scopes covering fit-gap analysis, configuration of financials and inventory, customization of any replaced add-on, data migration from GP, testing, training and cutover support. Ask each partner to separate one-time implementation work from recurring items such as hosting support, upgrades and retainers. For Odoo, ask whether the quote assumes Community or Enterprise, since Enterprise is a subscription and the upgrade service and some features depend on it. For ERPNext, confirm whether the quote assumes self-hosting or Frappe Cloud. Done when every path has a scope that a reviewer could compare line by line.
Cost infrastructure, backup and environments
Have your infrastructure team price the self-hosted option in your own cloud account or data center: database servers for PostgreSQL (Odoo) or MariaDB (ERPNext), application and worker nodes, storage, backups with tested restores, a staging environment for upgrades, monitoring and access controls such as LDAP or single sign-on. Include the cost of the people who run it. Compare this with the hosting and environment charges in the Business Central subscription and any Frappe Cloud or Odoo.sh plan you might choose instead. Done when each path has a monthly infrastructure figure and a named owner for patching and backup.
Add internal project time and an upgrade reserve
Estimate the hours your finance, IT and business teams will spend on data validation, testing, parallel month-end closes, training and change management for each path, and cost them at internal rates. Then add an upgrade reserve. Odoo's documentation states that on Odoo Online and Odoo.sh a major version upgrade is mandatory every two years, and that each major version has three years of standard support. ERPNext releases minor versions frequently, so budget regular patch testing even though major upgrades are less frequent. Done when each path has a recurring upgrade allowance with hours, a test environment cost and a named reviewer.
Check the Business Central data exit cost
Before you commit to Business Central, ask Microsoft or your partner to confirm the export limits that apply to your tenant. Microsoft Learn documents that a Business Central online database can be exported as a BACPAC file to an Azure standard storage account only with a paid subscription, and up to 10 times per month per environment. Microsoft also states it does not support creating a working on-premises Business Central environment from that BACPAC. Ask what this means for a future exit, what the storage and egress costs are, and whether your partner will extract data in another format. Done when you have a written answer on exit paths and a cost figure for a full export plan.
Model five-year totals for each path
Build one spreadsheet with three columns: stay on GP through its support end (with any extended support quote you obtain), Business Central, and self-hosted Odoo or ERPNext. Separate one-time costs (implementation, migration, add-on replacement, hardware, training) from recurring costs (subscriptions, hosting, support, upgrades, internal staff). Run each path with the same assumed user count and inflation or price-change clause, and show the result as a five-year total and a per-year figure. Label any assumed user growth as an assumption. Have finance review the model and check that every line traces to a quote, an internal estimate or a stated assumption. Done when the controller can explain each number and the decision can be taken on the totals.
Questions buyers ask about replacement cost and effort
How much does Business Central cost per user?
Business Central is sold per user per month, and the exact rate depends on the user type, the agreement you sign, your country and any partner margin, so the figure has to come from Microsoft or your Microsoft partner in writing. No per-user rate is supplied for this page, so do not budget from a list price you found elsewhere. Ask for a quote that shows each user class, the number of named users, the cost of any environments you add, and whether the price includes the support you expect. Also ask what the subscription does to your total when you add a partner migration fee and the ongoing partner work that follows go-live.
Is self-hosted Odoo or ERPNext free to use?
The software license is free in both cases, but running it is not. Odoo Community is published under LGPLv3 and ERPNext is licensed under GPL-3.0, so you can install and use the code without a license fee. Odoo Enterprise is a paid edition with a subscription, and its on-premise use and upgrade service need that subscription. Your recurring costs are the servers, backups, monitoring, storage, staff time and any support contract you buy. ERPNext's pricing page states that self-hosting is free, and Frappe Cloud is a separate paid option if you prefer managed hosting.
What drives implementation and data migration costs?
The main drivers are the number of legal entities, the volume of open and historical transactions, how many GP add-on products you rely on, and how much custom reporting or workflow you need. Each of these changes how much mapping, cleansing and testing is required. Data migration is usually the largest variable because GP account segments must be mapped to the new chart of accounts or accounting dimensions, and masters must be cleaned before they load. Ask any implementation partner for a fixed-scope proposal that lists the data objects, the number of trial balance validation cycles, the parallel month-end runs and the custom modules included. DeployOpen agrees scope, deliverables and timelines in writing before work starts.
How much internal time does each path need from our team?
Internal time is set by how many finance, IT and operations people must take part in mapping, testing and sign-off, and by how many months you need to run old and new systems in parallel. Business Central requires your team to work through partner onboarding, the configuration decisions and user training. Odoo or ERPNext requires you to decide the chart of accounts, the master data rules, the approval flows and who owns the hosting. Neither path has a duration in this page's sources, so ask each vendor or partner for a written plan with named roles and dates. Plan for your controller to review trial balances at every validation cycle, because that review cannot be delegated to a vendor.
Can our own staff migrate from Dynamics GP without a partner?
Your staff can extract, map and load data without an outside firm if they have SQL Server skills, a clear understanding of GP account segments and the time to validate results. ERPNext's Data Import tool loads CSV or Excel files using templates, and the documentation advises importing a few thousand records at a time, which means a large vendor or item list is run in batches. Odoo's import tool accepts Excel or CSV files and recommends External IDs when you bring data from another application. The harder parts are reconciling open items, rebuilding reports, replacing add-ons and signing off the opening balances. Most teams keep an outside reviewer for those steps, and a fixed-scope engagement can cover only the parts you choose.
How often do Odoo and ERPNext upgrades recur?
Upgrades recur on a fixed schedule set by each vendor, and their cost depends on who performs them. Odoo states that each major version gets three years of standard support, followed by two more years to complete the upgrade, and minor versions usually arrive about every two months. On Odoo Online and Odoo.sh, major upgrades are mandatory every two years. ERPNext's supported versions page states that version 15 is supported until the end of 2027 and version 16 until the end of 2029, and its releases ship frequently. Each upgrade should be tested on a copy before production, so budget internal testing time each cycle and ask your partner whether upgrades are included in a retainer.
What does Frappe Cloud cost as a reference point?
Frappe Cloud is an optional managed host, and its published pricing sets a reference point for what hosting alone can cost. The ERPNext pricing page lists shared site hosting from 5 US dollars per month, shared servers from 20 US dollars per month, and dedicated servers from 125 US dollars per month. These are starting prices, so confirm current rates and the support plan that matches your version with Frappe before you budget. Hosting on your own servers replaces these charges with infrastructure, backup and administration costs that you control, and it may suit regulated data that must stay in your environment.
What usually decides the five-year total
The license line is rarely what decides the five-year total. Business Central is priced per user, and Odoo's Standard plan and Custom plan are priced per user per month, but in both cases the larger costs sit in the work around the license: migrating open items and history, rebuilding the GP add-ons your finance team depends on, and the upgrade and backup routine you run for years afterward. Before comparing totals, ask each option for a written scope that names the entities, masters, open transactions, years of history, report set and every customization. A quote that does not list these items is not comparable with one that does, and the gap usually appears in the migration line after signature.
The second decider is who runs the platform. Odoo on-premise and Odoo.sh are only available on the Custom plan, and Odoo's standard support covers the first three years after a major release, with upgrades mandatory every two years on Odoo Online and Odoo.sh. ERPNext on your own servers is free to install, but Frappe's warranty depends on running a listed version with a matching Frappe Cloud support plan, and Frappe's supported versions page lists different end-of-life dates per major version. Ask whether your team or a partner will own the upgrade test cycle, the backup and restore tests, and the patch calendar, and price those as recurring items.
The third decider is edition. Odoo Community is LGPLv3 and covers a broad app set, but multi-company, Odoo Studio, external API access and custom modules sit on the Custom plan, so confirm which of your requirements depend on them before you compare. ERPNext is GPL-3.0 and does not have a separate paid edition, but Server Scripts are disabled by default from version 15 and must be enabled deliberately, and Frappe Cloud public shared benches do not allow them. Put each of these features on the scope list so the five-year figure reflects what you will actually run.
How DeployOpen scopes a fixed-price GP replacement
DeployOpen plans and implements self-hosted Odoo or ERPNext inside your own cloud account, data center or air-gapped network. We start from a written scope that compares the Business Central subscription path with the self-hosted path on the same user counts, data volumes and cutover date, so the cost comparison rests on your numbers rather than a generic estimate.
How we scope
- Inventory your GP companies, modules, third-party add-ons and integrations before agreeing any price.
- Define which open transactions, masters and history years move, and which stay in a read-only archive.
- Agree in writing the hosting target, user counts, environments and the parallel month-end test window.
How we build
- Install and harden the chosen platform in your infrastructure, including backups and database hosting.
- Map GP account segments and accounting dimensions to the target chart of accounts under your review.
- Configure authentication with your identity provider and test data migration runs until trial balances reconcile.
How we hand over
- Deliver runbooks for installation, upgrades, backups and restores, documented for your own administrators.
- Provide reconciliation reports comparing GP and the new system at each migration checkpoint.
- Train key users and confirm the cutover checklist with your finance and IT owners before go-live.
How we support
- Offer ongoing support, upgrades and continuous testing as a retainer after go-live.
- Plan version upgrades around the vendor's support windows, which you confirm with the vendor for your release.
- Scope any further customization or add-on replacement as a separate written change to the agreed scope.
