SAP Business One or Dolibarr: which fits a small company's ERP switch
If a renewal, a licensing change or residency pressure has pushed you to re-evaluate SAP Business One, the choice for a small company comes down to how much process depth you need and how much you are willing to build yourself. SAP Business One fits when a partner will deliver the implementation and you want to standardize on SAP HANA or Microsoft SQL Server, especially where manufacturing and inventory logic must be deep. SAP states it is deployable on premises or in the cloud and is backed by over 850 local partners, so partner availability is rarely the constraint. Dolibarr fits when you want a lighter footprint: a modular PHP application on MySQL, MariaDB or PostgreSQL that you enable one module at a time. Its catalog covers invoicing, stock, manufacturing (MRP), point of sale and CRM, which is often enough for a trading or small production business.
Dolibarr also brings a clear hosting profile for a small IT team. The prerequisites page lists MySQL 5.7.7 or newer, MariaDB 10.3 or newer or PostgreSQL 9.1.0 or newer, on any web server that runs PHP, and the Dolibarr website describes on-premises, virtual machine, Docker and SaaS options. Confirm with your own team whether Microsoft SQL Server support, which Dolibarr lists as experimental, would be a blocker. For accounting, the Double Entry Accounting module (module ID 50400) exports in formats such as CSV, FEC, Sage, Cegid, Quadratus and EBP, so check that your external accountant accepts one of them before you commit. Dolibarr is GPL-3.0 licensed, but the add-ons you need may come from DoliStore, so review each one's license and maintenance status.
The decision turns on four questions. First, process depth: list your manufacturing, costing and multi-warehouse rules and test them against the Dolibarr modules. Second, add-on dependence: count the SAP Business One add-ons you run today, because each one must be replaced, rebuilt or dropped. Third, internal skills: Dolibarr can be administered by a small team, but customization through the Module Builder or PHP work needs someone who can own it after go-live. Fourth, accounting export needs: confirm the format, period close and audit trail your accountant requires. Ask a partner or DeployOpen for a written scope that covers these checks before you choose a direction.
Which option fits which buying scenario
This table maps common buying scenarios for small companies to the option that usually fits better, with the reason tied to documented capabilities and requirements. Read each row against your own processes, database standards and team skills. The main takeaway: Dolibarr suits lean teams comfortable with PHP and MySQL, MariaDB or PostgreSQL, while SAP Business One suits organizations already committed to SAP HANA or SQL Server and a partner relationship.
| Scenario | Better fit | Reason |
|---|---|---|
| Manufacturer with BOMs and multi-warehouse stock | Test Dolibarr MRP first | Dolibarr lists stock and manufacturing (MRP) modules. Confirm warehouse, costing and BOM depth in a trial before committing. |
| Service firm needing invoicing and CRM | Dolibarr | Invoicing, proposals, orders, contracts and help desk sit in one modular PHP application with a small footprint. |
| Company with an existing SQL Server estate | SAP Business One | SAP Business One runs on Microsoft SQL Server. Dolibarr's SQL Server support is listed as experimental, so MySQL, MariaDB or PostgreSQL is the established path. |
| External accountant expecting FEC or Sage exports | Dolibarr | Double Entry Accounting exports CSV, FEC, Sage, Cegid, Quadratus and EBP. Agree the export format with your accountant before go-live. |
| Company that wants a large partner ecosystem | SAP Business One | SAP states Business One is backed by over 850 local partners. Ask any partner for references in your sector and country. |
| No in-house PHP or database administration | Dolibarr through a hosted provider, or SAP Business One through a partner | Dolibarr needs a PHP web server and database. Confirm who patches, backs up and upgrades it, or choose a SaaS provider such as DoliCloud. |
| Small team with modest hardware | Dolibarr | Dolibarr's prerequisites suggest at least a 1 GHz CPU for 30 or more users, plus storage for uploaded and generated documents. |
Where the data sits and who can run it
SAP Business One and Dolibarr both can run inside your own infrastructure, but the work of hosting, access control and evidence falls to different parties in each case. The cards below set out the decisions that connect deployment, identity and compliance for a small company weighing the two.
SAP Business One deployment model
SAP states that Business One is deployable on-premise or in the cloud and runs on SAP HANA or Microsoft SQL Server. The partner who installs it usually sets the database, the server sizing and the hosting arrangement, so the choice of database and host often comes with the partner's contract. Ask who holds the database administrator credentials, where backups are stored and who patches the database engine and the operating system.
Self-hosting Dolibarr on your own servers
Dolibarr runs as a PHP application on any web server that runs PHP, such as Apache, Nginx, Lighttpd or IIS, with MySQL, MariaDB or PostgreSQL as the database. Your team owns the web server, the PHP version, the database and the document storage. Confirm the database version against the prerequisites page, since experimental Microsoft SQL Server support is not the same as a supported production path.
Virtual machines, Docker or cloud hosting
Dolibarr can run on premises, on virtual or dedicated machines, or with Docker, and it can also be hosted by cloud providers and partners. For a small company, a virtual machine with a nightly database dump is simpler to audit than a container stack. Decide early whether the database and uploaded documents will sit in the same region and under the same backup policy as the rest of your records.
DoliCloud as a managed option
DoliCloud describes itself as the official Dolibarr preferred partner and hosts Dolibarr as SaaS. It offers a Basic plan at 14 euros per user per month and a Premium plan from 45 euros per month, each with a 30-day free trial. Read its data location, backup, export and exit terms in writing, because a managed host changes who holds the database and who can restore it.
Identity and access controls
Both systems rely on named user accounts, role permissions and the ability to remove leavers quickly. Dolibarr permissions are set per module and per user group, so review who can edit invoices, change bank details and export ledgers. Confirm whether your identity provider can federate sign-in to Dolibarr or whether accounts will be managed locally, and document the review cycle.
Compliance evidence you produce
Whichever platform you choose, the controls and the records that show them are your responsibility. Keep change logs for module and database updates, access review records, backup restore tests and the accounting exports you rely on. DeployOpen can prepare these controls and evidence for an assessment, but independent auditors issue any report, and the evidence must be collected and kept by your own team.
How a Dolibarr deployment is built and what it needs from the server
Dolibarr is a PHP application that runs on any web server able to execute PHP, such as Apache, Nginx, Lighttpd or IIS, and stores its data in a relational database. The supported engines are MySQL 5.7.7 or newer, MariaDB 10.3 or newer, and PostgreSQL 9.1.0 or newer. Experimental Microsoft SQL Server support is also listed. For a team already operating MariaDB or PostgreSQL, the database layer is familiar territory, while an SAP Business One shop running on SQL Server should treat that engine as experimental and ask the Dolibarr Association or a tested integrator to confirm it for the intended version before committing. Confirm the exact versions against the Dolibarr prerequisites page when you size the server.
Dolibarr is modular, so you enable only the modules a business uses, such as invoicing, stock, manufacturing, point of sale or CRM, and leave HR or project modules off until someone needs them. This keeps the attack surface, the configuration review and the upgrade testing smaller. Plan the enabled-module list as a written document, because each module adds menus, permissions and data that must be backed up and tested. The prerequisites page estimates about 150 MB for program files and 35 MB for an initial database, and recommends at least a 1 GHz CPU for 30 or more users. Those figures are a starting point, not a capacity plan. Document storage grows with use, since uploaded invoices, scanned supplier documents and generated PDFs accumulate in the file store alongside the database. Estimate that growth from your own document volume and retention rules, then load test the workload you expect at month-end close in your own environment.
What each option costs to own, by component
SAP Business One is sold through SAP's partner channel, and the license and maintenance terms are set in the quote from your SAP partner rather than published as a list you can compare directly. Licenses are usually counted per user, and the price you pay depends on user types, modules and the partner's contract. Dolibarr is free open source software under GPL-3.0, so there is no license fee to the software publisher. The recurring cost on the Dolibarr side appears only if you buy a hosted plan or a paid add-on.
- SAP Business One licenses: Ask the partner to itemize user licenses by user type, plus any add-ons, and whether maintenance is charged per year.
- Dolibarr core: No license fee. Modules are enabled from the same distribution, so the core itself is a one-time download and setup cost.
- DoliStore add-ons: Some add-ons are paid. Check the price, the license terms and whether updates are included before you rely on them.
- Hosted Dolibarr (DoliCloud): The DoliCloud website lists a Basic plan at 14 euros per user per month and a Premium plan from 45 euros per month, each with a 30-day free trial.
Check whether a quote includes the first year of maintenance, renewal uplift and any user-type changes you expect in the next three years.
Implementation work for SAP Business One is typically delivered by a partner, who configures the system, sets up the database platform and migrates master data. Dolibarr setup is lighter because the application is PHP with a choice of MySQL, MariaDB or PostgreSQL, but moving accounting history, customers, products and open documents still takes planned work. DeployOpen plans, implements and migrates self-hosted platforms in your own infrastructure under a fixed scope agreed in writing before work starts.
- Partner implementation (SAP): Billed by the partner, often by consultant time. Ask for the number of consultant days, the scope of configuration and who owns the test plan.
- Dolibarr installation and configuration: Covers the web server, PHP, database, module selection and chart of accounts. Ask for this as a fixed-scope line item.
- Data migration: Extracting and cleaning customers, products, stock and open invoices is usually the largest variable. The effort rises with data quality, history length and the number of entities.
- Accounting setup: Map the chart of accounts and confirm the double entry accounting module setup and exports against your accountant's requirements.
Specify in the quote who validates migrated balances, because that check drives how much rework remains after go-live.
Hosting costs depend on where you run the system. SAP Business One runs on SAP HANA or Microsoft SQL Server, which means the database platform carries its own license and administration costs. Dolibarr needs only a PHP-capable web server and MySQL 5.7.7 or newer, MariaDB 10.3 or newer, or PostgreSQL 9.1.0 or newer, and the Dolibarr prerequisites page estimates about 150 MB for program files and 35 MB for an initial database, plus space for documents.
- SAP database platform: SAP HANA or SQL Server licensing and administration are separate from the Business One license. Ask the partner which database edition is quoted.
- Dolibarr servers: Can run on premises, on virtual or dedicated machines, or with Docker. Infrastructure is a recurring cost whether you own the hardware or rent it.
- Document storage: Uploaded and generated documents grow over time, so plan storage growth for scanned invoices and attachments.
- Sizing: The prerequisites page recommends at least a 1 GHz CPU for 30 or more users, which is a starting point, not a substitute for load testing.
Confirm with your infrastructure team whether the hosting cost sits in an existing budget or needs a new line item.
Support is the recurring component most often underestimated. With SAP Business One, support runs through the partner's maintenance and help desk agreement, and changes to add-ons or reports usually go back to the partner. With Dolibarr, support can come from the community, the Dolibarr Association, a hosting provider or an implementation partner, and the cost depends on which of these you contract. Dolibarr maintenance releases are published on GitHub, and older lines still received maintenance releases in 2026, so upgrade planning is a recurring task either way.
- SAP support: Usually bundled with maintenance and billed for changes beyond the agreed scope. Ask for the response expectations written into the contract.
- Dolibarr upgrades: Plan a test environment, module compatibility checks and a rollback path for each upgrade you adopt.
- Backup and recovery: You own backup scheduling, retention and restore testing on the Dolibarr side unless a hosting provider contracts it.
- Retainers: DeployOpen offers ongoing support, upgrades and continuous testing as retainers, quoted from the written scope.
Ask each vendor and partner for the support hours, escalation path and who pays for emergency fixes.
What moving from SAP Business One to Dolibarr involves
The sequence turns a live SAP Business One company into a tested Dolibarr instance with reconciled masters, balances and open documents, so the cutover date is a checked decision rather than a guess. Each step ends with an output the finance and operations leads can sign off.
Scope the process map and reports
Document how the company buys, stocks, sells, produces and closes its books today, and list every report, form and add-on that staff rely on. Decide which SAP Business One functions Dolibarr must cover with its standard modules, which need configuration, and which need custom work. Agree this scope in writing with the business owners before any data moves. Done when each process has a named owner and a yes, configure or rebuild decision.
Extract masters and open documents
Pull business partners, items, warehouses, price lists, chart of accounts, opening balances and open sales and purchase documents out of the SAP Business One database or through its supported export path. The routes and their limits are covered in the sibling page on exporting data from SAP Business One, so this step follows that plan. Record row counts per object and keep the untouched extracts as a fixed reference. Done when every object in scope has an extract and a count that the source system confirms.
Map items, partners, warehouses and accounts
Translate SAP Business One codes into Dolibarr equivalents: item types and categories, third-party roles for customers and suppliers, warehouse locations, tax rates and the chart of accounts used by the double entry accounting module. Confirm with the company's accountant how each ledger account and journal will be used before loading. Keep the mapping in a shared table with a reviewer for each object. Done when the mapping table is approved and every source code has a target.
Load and reconcile in a test instance
Install Dolibarr on a test server in your own infrastructure, load the mapped masters and balances, then import open documents. Compare totals, counts and balances in Dolibarr against the SAP Business One reference extracts, and log every difference with its cause. Repeat the load until the differences are zero or explained and accepted. Done when the reconciliation report shows agreed variances and the finance lead has signed it.
Configure enabled modules and rebuild add-on behavior
Enable only the Dolibarr modules the process map requires, such as invoicing, stock, manufacturing, point of sale or CRM, and configure numbering, document templates, user rights and tax settings. For each SAP Business One add-on or custom screen that the business still needs, decide whether a configuration setting, a DoliStore add-on or a custom Dolibarr module covers it, and assess that code's support terms. Done when every in-scope workflow runs end to end in the test instance and each add-on decision is documented.
Run parallel period-end checks
Run at least one full period-end close in parallel, processing the same transactions in SAP Business One and Dolibarr, and compare ledger balances, stock valuation, receivables and payables. Test the accounting exports your external software needs, such as the formats Dolibarr supports, against what that software accepts. Check user access, backups and restore before go-live. Done when the parallel results match or the variances are approved and the restore test succeeds.
Cut over and confirm the handover
Freeze transactions in SAP Business One, run the final delta extract, load it into the production Dolibarr instance, and repeat the reconciliation on the final figures. Switch users over, keep SAP Business One read-only for an agreed period, and document the runbook and rollback decision. Confirm ownership of hosting, backups and upgrades with the internal team or your support provider. Done when the reconciliation is signed, users work in Dolibarr and the runbook is accepted.
Questions buyers ask before a Dolibarr move
How much does moving from SAP Business One to Dolibarr cost?
The cost is driven by the work around the software, not by the Dolibarr license, which is free under GPL-3.0. Dolibarr itself carries no license fee, so the one-time costs are migration, configuration, data extraction and cleansing, testing, training and any add-on work. The recurring costs are hosting, backups, maintenance of the PHP and database stack, and any support retainer you choose. Ask any quote to split these components, and to state which SAP Business One licenses, maintenance and partner fees end, and when. The DoliCloud SaaS plans show one hosted option: a Basic plan at 14 euros per user per month and a Premium plan from 45 euros per month, according to the DoliCloud website, with a 30-day free trial. Your own hosting cost will differ from that.
How long does a Dolibarr migration take?
Timing depends on the volume and quality of your master data, how many open documents move across, how many customizations you rely on, and how many people must test. Companies with a clean item list and few add-ons generally move faster than those with years of custom fields and partner-built reports. No duration figure is supplied here, so ask any implementation partner for a timeline in the written scope, with milestones for data extraction, a trial load, reconciliation of balances, user acceptance testing and cutover. Plan a parallel run of the old and new systems for at least one closing period so accounting totals can be compared.
What does our internal team need to provide during the project?
Your team must supply decisions and knowledge that no installer can infer. That includes a named business owner for each module, the chart of accounts and tax rules, item and pricing rules, approval workflows, and the list of SAP Business One reports and add-ons that finance and operations actually use. Someone must also confirm which open transactions must move and which can be closed in SAP Business One before cutover. Expect to allocate time from finance, sales, warehouse and the person who will administer the system after go-live. Without these inputs, the schedule and the cost estimate become unreliable.
Can one in-house administrator run Dolibarr alone?
A single administrator can run a small Dolibarr instance if they are comfortable with Linux, a PHP web server, a MySQL, MariaDB or PostgreSQL database, backups, and module configuration. The Dolibarr prerequisites page lists MySQL 5.7.7 or newer, MariaDB 10.3 or newer, or PostgreSQL 9.1.0 or newer, on a web server that runs PHP. Plan for a second person who can cover patching, restores and user support, because a single point of knowledge is a continuity risk. Upgrades should be tested on a copy of production, and the Dolibarr GitHub releases page shows that maintenance releases continue on several version lines. Ask a partner for a written runbook, if you want one.
Does Dolibarr cover manufacturing depth and accounting exports to our accountant?
Dolibarr includes a manufacturing module (MRP) and stock modules, so it can support bills of materials and production orders, but depth should be tested against your own routings, lots, serials and costing method before you commit. Confirm this with a scripted trial using your real products. On accounting, the Double Entry Accounting module (module ID 50400) groups transactions in journals, posts them to the general ledger and exports in formats including CSV, FEC, Sage, Cegid, Quadratus and EBP, according to the Dolibarr wiki. Ask your external accountant which format and which account mapping they need, and reconcile exports against SAP Business One totals for the same period.
How do add-ons on SAP Business One compare with DoliStore modules?
SAP Business One add-ons are typically sold and supported through SAP's partner channel, while Dolibarr extensions come from the DoliStore marketplace, and organizations can also build their own with the low-code Module Builder. Map each SAP add-on to a function: a Dolibarr module, a standard feature, a custom module, or retirement. Check each DoliStore module's license, update history and support terms before relying on it, because quality varies. Custom modules must be upgraded as Dolibarr changes, so budget for that maintenance. Treat any add-on you cannot replace as a scope item in the written agreement.
Can DeployOpen run a Dolibarr migration under a fixed-scope written agreement?
Yes. DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure, and most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts. DeployOpen does not publish a price list, so a quote follows from the written scope. Ongoing support, upgrades and continuous testing are available as retainers. DeployOpen prepares systems, controls and evidence for compliance assessments, but it does not issue audit reports or certifications, which independent auditors and certification bodies do. Ask for the scope to list each module, data source, add-on, environment and acceptance test.
Questions to answer before you pick a side
The choice between SAP Business One and Dolibarr turns on a short list of conditions, and each one changes which product is the better fit. Start with SAP add-on dependence: list every add-on, report and integration your team uses today, and for each one ask whether it is an SAP-certified add-on, a partner-built extension or a custom report. Partner-built components will need either a Dolibarr module from DoliStore, a custom module written with the Module Builder, or a rebuild in your own PHP code. If most of your daily work depends on one or two add-ons with no equivalent, the migration cost moves from the ERP itself to those components, and that should weigh heavily in the decision.
Next, test warehouse and bill of materials complexity. Dolibarr covers stock and manufacturing (MRP), but a business with several warehouses, lot or serial tracking rules, multi-level BOMs or subcontracted production should run a realistic sample of those flows in a Dolibarr test instance before committing. Reporting and audit requirements come next. Dolibarr's Double Entry Accounting module (module ID 50400) exports to formats such as CSV and FEC, so confirm with your accountant which export format your tax authority and external auditor accept and whether your month-end close fits that path. Also check user count and server skills. Dolibarr's prerequisites page recommends at least a 1 GHz CPU for 30 or more users, and a team without PHP or database administration staff should price in that gap before choosing self-hosting.
How DeployOpen works on this
DeployOpen plans, implements, customizes, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms inside your own infrastructure. For SAP Business One vs Dolibarr, we start with a written scope that tests whether Dolibarr fits your invoicing, stock, accounting and point of sale needs before any migration work begins.
How we scope
- Map your current SAP Business One modules, add-ons and partner-built reports against Dolibarr's modules and DoliStore extensions.
- Confirm the database choice (MySQL, MariaDB or PostgreSQL), web server and hosting location within your own infrastructure.
- Agree deliverables, timelines and fees in writing before work starts, since most engagements are fixed-scope.
How we build
- Install and configure only the Dolibarr modules your processes need, with the double entry accounting module set up if required.
- Test exports to your external accounting software in the formats you use, such as CSV or FEC, against sample entries.
- Document configuration, security hardening and test results so your team and auditors can review how the system was set up.
How we hand over
- Deliver runbooks for backups, restores, upgrades and user administration, with the evidence your compliance team will need.
- Walk your staff through daily invoicing, stock and point of sale tasks in the built system before cutover.
- Hand over documented add-on decisions, including any custom Module Builder work and its maintenance owner.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer, so your team does not carry every patch alone.
- Plan Dolibarr version upgrades against your own test environment before each move to production.
- Ask for a quote built from the written scope, including what recurs (hosting, support, upgrades) and what is one-time (migration, setup).
