Open-source ERP: the main systems, their licences and how to implement one
An open-source ERP is business management software for accounting, sales, purchasing, stock, production and projects whose source code is published under an open-source licence. Open-source ERP gives a small or midsize business full control: no per-user licence fees for the open edition, freedom to change the code, and freedom to choose who implements and hosts it. This guide compares the best-known open-source ERP systems by licence and fit, explains what an open-source ERP really costs to run, and sets out how to implement one without disrupting the business.
Licence facts come from each project's own licence page or licence file, read on 12 November 2026, and the definition of open source from the Open Source Initiative, read the same day. We name products neutrally; none of them is ours.
What makes an ERP open source
The Open Source Initiative's Open Source Definition sets ten criteria a licence must meet, among them free redistribution, access to source code, permission for derived works, and no discrimination against persons, groups or fields of endeavour. In practice, the licence decides what you may do with the code:
- Copyleft licences such as the GNU GPL version 3 require that if you convey a modified version to others, you make its source available under the same licence. Section 2 of the GPL version 3 states that you may make, run and propagate covered works that you do not convey, without conditions, so running and changing the software for your own company does not by itself trigger the sharing duty.
- The GNU LGPL version 3 is a weaker copyleft, commonly used so that separate modules can have their own terms.
- Permissive licences such as Apache 2.0 allow almost any use, including in closed products, with attribution.
Watch for "open core" models: an open-source community edition and a proprietary edition with more features, sold by subscription. Both can be good choices, but you should know which features you are planning on.
The main open-source ERP systems
| System | Licence (as read 12 November 2026) | Typical fit |
|---|---|---|
| Odoo Community Edition | Odoo 19 Community Edition: LGPL version 3. Odoo Enterprise Edition: Odoo's own proprietary licence, valid subscription required | Wide range of modules (sales, CRM, stock, accounting, website, manufacturing) and a large partner network; check which modules are Community and which are Enterprise |
| ERPNext | GNU GPL version 3 (licence file in the project's repository) | Accounting, stock, manufacturing, projects and HR in one system, built on the Frappe framework; suits companies that want one fully open system |
| Dolibarr | GNU GPL version 3 (licence file in the project's repository) | Light, modular ERP and CRM for small companies and associations with simpler needs |
| Apache OFBiz | Apache License 2.0 (licence file in the project's repository) | A framework of ERP components for companies that plan to build substantially on top of it |
Other projects exist, including ERP systems for specific industries. The list above covers the ones most small and midsize companies shortlist. For an overview of what any ERP does, see our page on ERP systems for small business.
What an open-source ERP really costs
The licence of the open edition costs nothing; everything else does. Plan for these cost lines, which apply to any ERP:
- Implementation: process mapping, configuration, chart of accounts, tax rules, users and permissions.
- Data migration: customers, suppliers, products, open orders, balances and history from the old system. See our data migration service.
- Customisation and integrations: your own workflows, reports, and connections to the webshop, bank, e-invoicing network, payroll or production machines.
- Hosting and operation: servers or managed hosting, backups, monitoring, security updates.
- Upgrades: major versions every year or two in most projects. Every customisation must be tested and sometimes rewritten on upgrade.
- Training and support: internal key users and an external partner for problems.
The difference from proprietary ERP is not that these costs disappear, but that you control them: you can change partners, host where you want and keep the system running without a vendor's permission. Our custom software development cost guide explains how to compare quotes for this kind of work.
Open-source, proprietary or custom ERP?
| Situation | Often the best fit |
|---|---|
| Standard processes, small team, no IT staff, want everything handled | A hosted proprietary or open-core ERP with a subscription |
| Standard core, some own processes, want control over data and partners | Open-source ERP, implemented and hosted by a partner of your choice |
| Core processes that are your competitive advantage, or industry needs no ERP covers well | A standard ERP for finance plus custom modules, or a custom system |
| Strict hosting rules, for example data must stay in specific EU regions | Open-source or custom, self-hosted in those regions |
How to implement an open-source ERP
- Map the processes that the ERP will run: order to cash, purchase to pay, stock, production, month-end close. Our process mapping guide shows how.
- Shortlist two or three systems and test them with your own data and real cases, not a vendor demo.
- Prefer configuration to code. Every change to the core makes upgrades harder. Put your own logic in separate modules that can be maintained.
- Clean the data before migrating it. Duplicates and outdated records are cheaper to fix before go-live than after.
- Go live in stages, for example finance and sales first, then stock and purchasing, then production, rather than everything on one weekend.
- Run old and new in parallel for at least one month-end close to compare results.
- Plan upgrades from day one, with a test environment and a yearly upgrade window.
What to test before you choose
A demo shows what a system can do; a test with your own data shows what it does for you. For each shortlisted system, set up a trial with a copy of real master data and run five or six real cases end to end: a typical customer order from quote to invoice, a purchase with a partial delivery, a stock count, a production order if you make things, a credit note and a month-end close. Note every workaround. Check the reports your managers read every week, the user interface on the devices your staff use, the speed with your data volume, the maintenance activity of the modules you need, and how much the partner had to change in code to make the cases work. The system that needs the fewest changes to the core is usually the one that stays upgradeable.
EU requirements to check
- E-invoicing: structured electronic invoices are becoming mandatory between companies in more EU countries. Check that the ERP supports the format and network your country requires; see our e-invoicing guide.
- GDPR: customer, supplier contact and employee data need access control, retention rules and deletion. When a partner hosts the ERP, you need a data processing agreement.
- Local accounting and tax rules: chart of accounts, VAT reporting and audit trail requirements differ by country. Check the localisation for your country is maintained.
Risks and how to manage them
- Customisation lock-in: heavy changes to the core tie you to one version. Keep changes in modules.
- Community modules of uneven quality: check maintenance activity and test before relying on one.
- Edition confusion: in open-core systems, confirm that every planned feature is in the edition you will run.
- Partner dependency: keep the code, the configuration and the hosting accounts in your company's name.
How we help
We implement, extend and integrate ERP systems, and build custom modules where a standard ERP does not fit, such as manufacturing ERP processes. We host in EU regions, in accounts in your company's name, and keep customisations in separate modules so upgrades stay possible. You own the code and the data.
Questions people ask
What is an open-source ERP?
An open-source ERP is enterprise resource planning software whose source code is published under a licence that lets anyone use, study, change and distribute it. Companies can run it themselves, adapt it or have a partner do so, without per-user licence fees for the open-source edition. Well-known examples are Odoo Community, ERPNext, Dolibarr and Apache OFBiz.
Is open-source ERP free?
The licence for the open-source edition is free of charge, but running an ERP is not. Implementation, data migration, configuration, customisation, hosting, updates, support and training are real costs, and for most companies they are larger than licence fees would have been. The advantage is control: you choose who does the work and you are not tied to one vendor's prices.
Is Odoo open source?
Partly. Odoo has two editions. According to Odoo's licence page for version 19, Odoo 19 Community Edition is licensed under the LGPL version 3, while the Enterprise Edition is under Odoo's own proprietary licence and requires a valid subscription. Many features, and many hosted Odoo offers, belong to the Enterprise Edition.
Which open-source ERP is best for a small business?
It depends on the business. Dolibarr is light and modular for small companies with simple needs. ERPNext covers accounting, stock, manufacturing and projects in one system. Odoo Community has the widest range of modules and partners. Apache OFBiz is a framework for companies that want to build heavily on top. Test the two or three that fit with your own data before deciding.
Can an open-source ERP handle EU e-invoicing?
The systems offer e-invoicing modules or community extensions for many countries, but coverage of national formats and networks varies by system, edition and country. Check that the exact format and network your country requires, for example Peppol or a national platform, is supported and maintained before you choose.
Sources
- Odoo, Licenses (Odoo 19 Community and Enterprise Editions) (read 12 November 2026)
- ERPNext, licence file (GNU GPL version 3) (read 12 November 2026)
- Dolibarr, COPYING file (GNU GPL version 3) (read 12 November 2026)
- Apache OFBiz, LICENSE file (Apache License 2.0) (read 12 November 2026)
- Open Source Initiative, The Open Source Definition (read 12 November 2026)