Which ERP fits a small business that wants only some modules?
A small business that wants only some of an ERP's modules will usually find Dolibarr the closer fit, while Business Central fits a business that wants one integrated suite tied to Microsoft 365 and is willing to buy a partner-led implementation. Renewals, per-user price changes and forced updates often trigger the comparison, so the first question is not which product has more features but which modules you will actually run. Business Central is sold as a full suite on Microsoft's per-user plans, and its strengths are the Microsoft 365 integration, a broad feature set and a partner ecosystem to implement it. Dolibarr is a modular PHP application under GPL-3.0 that lets you enable only invoicing, stock, projects, HR or manufacturing, and it runs on MySQL, MariaDB or PostgreSQL on your own servers or on Docker.
Dolibarr tends to fit when your modules are few and well defined, when you want to avoid a per-user license, and when you want the data to stay in your own environment. Its Double Entry Accounting module (module ID 50400) journalizes transactions into a general ledger and exports in formats including CSV, FEC, Sage, Cegid, Quadratus and EBP, which matters if an external accountant already works in one of those tools. Business Central fits better when you need its deeper manufacturing or service functions, native Microsoft 365 workflows, or a partner to take on the implementation. Confirm with your partner whether the Premium plan is required for the functions you need before you compare totals.
The decision turns on three questions. First, what your accounting obligations require: confirm with your accountant whether the Dolibarr double-entry module and its export formats satisfy your ledger and tax reporting, and which tool receives the exports. Second, where your data may reside, since Business Central online stores data in the Microsoft cloud while Dolibarr can run on premises or in a private cloud you control. Third, who will run upgrades: Business Central moves on Microsoft's release waves, while a self-hosted Dolibarr upgrades on a schedule you set, but someone on your side or a partner must own that work, test the modules you use and keep backups current.
Which option fits which business scenario
This table matches common small business situations to the better fit between Business Central and self-hosted Dolibarr, with the reason for each. Read each row as a starting point, then check the flip condition against your own licensing, data location and accounting requirements. Most of the choice depends on whether you need Microsoft 365 integration, a narrow module set or local control over the data.
| Scenario | Better fit | Why | When the choice flips |
|---|---|---|---|
| Firm that runs Microsoft 365 and wants one vendor | Business Central | Identity, support and licensing sit with Microsoft, and Business Central can be deployed online or on premises from the same vendor relationship. | Flips to Dolibarr if per-user Microsoft plans cost more than your user count justifies, or if you want to stop paying for seats that only need occasional access. |
| Firm that needs only invoicing, stock and projects | Dolibarr | You enable only the modules you use, and the application is modular PHP that runs on MySQL, MariaDB or PostgreSQL, so the footprint stays small. | Flips to Business Central if you expect to add broader financials, multi-currency consolidation or Microsoft-hosted workflows within a few years. |
| Manufacturer with light MRP needs | Dolibarr, after a functional check | The Dolibarr module list includes manufacturing (MRP), which suits simple bills of materials and production orders at small volumes. | Flips to Business Central if you need deeper shop-floor planning, routing or costing. Confirm the manufacturing depth of both products against a sample production process. |
| Firm with an external accountant who needs FEC or Sage exports | Dolibarr | The Double Entry Accounting module journalizes transactions into the general ledger and exports in formats including FEC and Sage, which fits accountants working in those tools. | Flips to Business Central if your accountant works inside Microsoft tools and needs live access rather than periodic file exchange. Confirm which export formats your accountant accepts before deciding. |
| Firm with strict data location rules | Dolibarr, self-hosted | You can run Dolibarr on premises, on your own virtual machines or with Docker, so records stay where your policy places them, including air-gapped networks. | Flips to Business Central if Microsoft's cloud data location commitments match your policy and you prefer managed hosting. Confirm the regional storage terms with Microsoft and your data protection lead. |
Does Dolibarr's double-entry module replace Business Central's ledger?
Yes for many small businesses, but only if your ledger needs are modest and your accountant accepts the export formats Dolibarr produces. Dolibarr ships a Double Entry Accounting module (module ID 50400) that groups transactions into journals, journalizes them into the general ledger, and exports in CSV, FEC, Sage, Cegid, Quadratus and EBP formats, according to the Dolibarr wiki. A separate simplified accounting module exists for businesses that do not need double entry, so you can choose the depth before you go live.
Business Central's general ledger carries more structure than many small firms use. Dimensions tag each posting by department, project or cost center, while posting groups and general ledger setup map sales, purchase and inventory transactions to accounts automatically. Dolibarr's module covers journals, the ledger and exports, so you should list which of these controls you actually rely on today. If you use dimensions for reporting, plan how each one becomes an account, a tag or a separate report in Dolibarr before you migrate history.
Before you decide, ask your accountant or tax adviser two questions: which export format your filing and audit requests require (for example, whether an FEC file is expected in your jurisdiction), and whether the ledger depth you use today must be reproduced in the new system or can be supplied as exports. Confirm the format with the receiving party in writing, then run a trial period-end close in a test instance and compare balances against Business Central before you retire it.
Capability by capability: Business Central and Dolibarr
This table compares the modules a small business is most likely to use in Business Central and Dolibarr, and notes where each side is thin or needs add-ons. Read each row against your own process list, then confirm module depth, country tax rules and plan requirements against the current Business Central and Dolibarr versions before you decide. The main takeaway is that Dolibarr covers a broad set of small-business modules out of the box, while Business Central's strength is its Microsoft 365 and AL extension ecosystem.
| Capability | Business Central | Dolibarr |
|---|---|---|
| Invoicing and sales | Sales and receivables posted to the general ledger, with Microsoft 365 document and reporting integration. Confirm e-invoicing and local tax setup for your country. | Invoicing with proposals and orders in the same application. Confirm country-specific tax and e-invoicing requirements for your jurisdiction. |
| Stock and inventory | Items, locations and costing in the core product. Confirm lot, serial and costing method support for your plan and version. | Stock module with warehouses and movements. Confirm costing and lot handling depth against the current version. |
| Projects and timesheets | Project and job management in the core product. Confirm depth of resource planning and time capture against your plan. | Projects module, with timesheets available through the HR modules. Confirm reporting and billing links to invoicing for your workflow. |
| HR | No full HR suite in the core product. Payroll and HR usually come from partner apps or other Microsoft services. Confirm what you need and who supplies it. | Modules for employees, expense reports, leave, timesheets and recruitment, as listed on the Dolibarr site. Confirm payroll coverage for your country. |
| Manufacturing | Manufacturing features require the Premium plan per user. Confirm production orders, bills of materials and shop-floor needs against that plan. | MRP module for production planning. Confirm fit for multi-level bills of materials and shop-floor users with a test scenario. |
| CRM, sales and point of sale | Sales in the core product. CRM sits in Dynamics 365 Sales, a separate product with its own licensing. Confirm point-of-sale fit and integration cost. | CRM with proposals, orders, contracts and help desk, plus a point-of-sale module. Confirm whether each module meets your sales and retail process. |
| Accounting and exports | Double-entry general ledger with Microsoft reporting. Confirm statutory reports for your jurisdiction and the export route to any external accounting tool. | Double Entry Accounting module (ID 50400) with journals, a general ledger and exports to CSV, FEC, Sage, Cegid, Quadratus and EBP. A simplified accounting module exists for businesses without double entry. |
| Extensibility | AL extensions, Power Platform and Microsoft 365 integration. Extensions must be retested at each six-month release wave, so budget for that effort. | Enable only the modules you need, extend with DoliStore add-ons or the low-code Module Builder. Custom code is PHP, and add-on quality varies, so review each one. |
| Databases and hosting | Online on Microsoft's cloud, or on premises on SQL Server. Confirm current on-premises support rules before you choose that route. | Runs on MySQL 5.7.7 or newer, MariaDB 10.3 or newer, or PostgreSQL 9.1.0 or newer, with experimental SQL Server support. Runs on Apache, Nginx, Lighttpd or IIS. |
Where your data sits under each option
The four options differ mainly in who operates the servers, who holds the backups and who must produce compliance evidence. Each card below covers one hosting model and the checks a buyer should make before signing or deploying.
Business Central online
Your database lives in Microsoft's cloud under a Microsoft 365 tenant, so Microsoft operates the hosting and the platform backups. Confirm the tenant region and the data residency commitments in writing before go-live. Identity runs through Microsoft Entra ID, which ties user access to your existing sign-in policies. For evidence, you still need to collect Microsoft's compliance documentation, your own access reviews and your own export records. A BACPAC export is only possible on a paid subscription and up to 10 times per month per environment, so plan any independent copy in advance.
Business Central on premises
Your data sits in SQL Server on servers you own or rent, so your team owns hosting, patching, backups and disaster recovery. Identity usually comes from your Active Directory, and you control network segmentation and encryption at rest. Microsoft documents on-premises as a deployment option, but a BACPAC from the online service does not restore into a working on-premises environment, so the two are separate data paths. Compliance evidence, including backup test records and change logs for each release wave, is entirely your responsibility. Ask your auditor which evidence they accept before you design the controls.
Self-hosted Dolibarr
Dolibarr runs as a PHP application on your own web server with MySQL, MariaDB or PostgreSQL, and it can run on premises, on virtual or dedicated machines, in Docker, or in your own cloud account. Your organization decides the data location, backup schedule and database encryption, and the application can be placed behind your existing single sign-on proxy if your team builds that integration. The application has no built-in tie to a Microsoft tenant, so confirm how user accounts are provisioned and removed. Evidence for access reviews, backup restores and patch records must come from your own logs and runbooks.
DoliCloud as hosted SaaS
DoliCloud hosts Dolibarr for you as SaaS and describes itself as the official Dolibarr preferred partner. Your data sits in the provider's hosting environment, so the contract, data processing terms and hosting location become the main evidence sources. Ask the provider in writing where backups are stored, who can access them, how long they are retained and how you would get a full export if you leave. Identity and user provisioning depend on the service configuration, so confirm them before onboarding. You remain responsible for the controls the contract assigns to you, and DeployOpen does not issue attestations for the provider.
What drives the cost of each option
Start by separating one-time costs from recurring costs for both options, because they fall on different budget lines. For Dolibarr, one-time work covers selecting modules, configuring the chart of accounts, tax rates, numbering and document templates, migrating customers, suppliers, items and open invoices, training staff, and connecting Dolibarr to a bank feed, payment gateway or an external accounting tool. Recurring costs cover hosting, backups, patching, PHP and database upgrades, and support. Dolibarr itself carries no license fee under GPL-3.0, so the recurring line is what you pay to run it, not what you pay to use it.
For the hosted alternative, DoliCloud publishes 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, according to the DoliCloud website. Those are recurring fees that scale with headcount on Basic. Business Central is also recurring and per user, but its plan prices are not in the supplied facts. Take the current per-user Essentials and Premium prices from Microsoft's current price list, and confirm which plan includes the manufacturing and inventory depth you need, since manufacturing is not part of the lower tier. Compare the totals per user per year, not the list price alone.
Self-hosting moves hosting, upkeep and support to you or to a partner. Ask any implementer for a written quote that itemizes: the fixed-scope implementation work and its deliverables, data migration and reconciliation of opening balances, module and add-on purchases from the DoliStore marketplace, hosting and backup infrastructure, a patching and upgrade schedule that covers Dolibarr releases, PHP and the database, support hours and response terms, and who pays for testing after each upgrade. Also ask what happens if the accountant needs an export in a format the partner has not built before. Run the same questions against Business Central partner services and Microsoft licensing so the two quotes can be compared line by line.
How updates reach you under each model
Microsoft applies Business Central online updates through its release waves, and the Modern Lifecycle Policy means your tenant receives each wave without a deferral option you can count on. Your team controls preparation, not the date. Review Microsoft's deployment overview for the current options and confirm which preview and sandbox environments your tenant can use before each wave.
- Two waves a year: Microsoft publishes major updates on a six-month cadence, so plan regression testing for each wave as a recurring task.
- Forced updates: The service applies the wave to your tenant on Microsoft's schedule, so the test window must be ready before that date.
- Extensions and AL apps: Confirm that each per-tenant extension supports the incoming platform version before it reaches production.
- Sandbox testing: Run posting, period close, reports and integrations against the new wave in a sandbox that mirrors production configuration.
- Microsoft 365 connectors: Retest Outlook, Excel and Power Platform connections after each wave, since these links depend on service versions.
After each wave, check journal posting, period close, report output and integration calls against a written test script, and record the results for your auditors.
On premises, your team decides when each update goes live on your own servers, which lets you avoid updates during month-end or audit periods. That freedom has a limit: you must stay on a release Microsoft still supports, and each release wave has a fixed end date. Upgrades cover the application tier, the database and the extensions, so the work is yours from planning through rollback.
- Scheduling control: You choose the upgrade window, which can follow your financial calendar and change freeze periods.
- Supported release floor: Confirm the current end date for the release you run and plan the next upgrade before that date arrives.
- Database upgrade: Test the upgrade against a restored copy of production, since the database step often takes the most time.
- Extension rebuild: Recompile and retest each extension for the release you adopt, including any custom reports and integrations.
- Infrastructure patching: Operating system, SQL Server and service tier updates run on a separate track that your team must coordinate with the application upgrade.
Before each cycle, check the release end date against your plan, confirm the supported upgrade path for your database version and make sure a tested rollback exists.
With self-hosted Dolibarr, your team chooses the version and the date of each move. Dolibarr 24.0.0 was released on August 20, 2026 and 24.0.1 on September 7, 2026, while the 23.0 and 22.0 lines still received maintenance releases in 2026. You can stay on a line that is still maintained, move to a newer line on your own schedule and apply patch releases to the version you run. Check the Dolibarr GitHub releases page before each decision.
- Choose the line: Pick 22.0, 23.0 or 24.0 based on which lines still receive maintenance and on the compatibility of your modules.
- Maintenance releases: Apply patch releases on the line you run and read the release notes for security fixes before scheduling them.
- Module compatibility: Retest DoliStore add-ons and custom Module Builder code for each line change, because these components often lag behind the core.
- Database and PHP: Confirm the MySQL, MariaDB or PostgreSQL and web server versions against the prerequisites page before each upgrade.
- Staging copy: Run each upgrade on a copy of production data, including uploaded documents, before cutover.
Before each move, check the release notes, the module and PHP compatibility, the accounting exports you depend on and the rollback plan from a full backup.
On DoliCloud, the provider schedules and applies Dolibarr updates to the hosted instance, so your control moves from the upgrade decision to the contract and the test window you negotiate. DoliCloud describes itself as the official Dolibarr preferred partner and offers Basic and Premium plans, as listed on its website. The written update policy determines how much time you have to test, so confirm it before you sign.
- Provider-scheduled updates: Ask for the update calendar, the notice period and whether a test or staging instance is included in your plan.
- Module and customization limits: Confirm which DoliStore modules and custom code the hosted plan supports and who retests them after an update.
- Rollback and restore: Ask how a failed update is reversed, who performs the restore and how long a restore takes in practice.
- Data export: Confirm that you can export the database and documents on request, so you keep an exit path if you later self-host.
- Support during updates: Confirm who you contact during an update window and the response commitments in the contract.
Before you commit, check the written update policy, the notice and test window and a restore you have actually tested with the provider.
What a move from Business Central to Dolibarr involves
The sequence turns a Business Central company into a Dolibarr instance that carries the same ledgers, stock, customers and open items, with each step ending in a reconciliation the accountant has signed off. Nothing is switched off until the parallel checks match.
Confirm scope and the modules you need
Your team and DeployOpen list the Business Central functions in use, such as invoicing, stock, projects, HR and manufacturing, and map each one to a Dolibarr module, including the Double Entry Accounting module if your accountant works in double entry. Anything without a module is recorded as a gap with an owner and a decision: keep it outside the new system, build it as a Dolibarr module, or drop it. The output is a signed scope document that names the modules and the open gaps. Confirm which module names, import features and accounting exports exist in the Dolibarr version you plan to run, using the Dolibarr release notes and wiki, before you commit to a design.
Export the Business Central data
For a Business Central online tenant, a database export is a BACPAC file written to an Azure standard storage account. It requires a paid subscription and is limited to 10 exports per month per environment, so plan the export runs around the reconciliation schedule. Microsoft does not support creating a working on-premises Business Central environment from a BACPAC exported from the online service, so the file is a data source for extraction, not a restore point for a running system. Keep the export, the storage account and the access log under your control. The output is a verified copy of the export with a recorded checksum and export date.
Extract master and transaction data through SQL
Load the BACPAC into a SQL Server instance you control, then write extraction queries for each object: customers, vendors, items, the chart of accounts, dimensions, open invoices and orders, stock on hand and the general ledger. Business Central stores tables with company-prefixed names and extension tables that you must map to the base objects, so the queries need a reviewer who knows the schema. Export the results as CSV files with headers, one file per object. The output is a row count for every extracted object, reconciled against the Business Central pages or reports, with any differences explained.
Map the chart of accounts and dimensions
Build the mapping from Business Central's chart of accounts, posting groups and dimension values to the Dolibarr accounting plan, journals and the accounting codes the Double Entry Accounting module uses for sales, purchases and stock. Decide how each Business Central dimension becomes a field, tag or project in Dolibarr, and record the rules for legacy codes that are retired. Your accountant approves the mapping before any load. The output is an approved mapping workbook that lists every source account, its target account, and any dimension that is merged, split or dropped.
Load into a test instance and reconcile
Install Dolibarr on a test environment in your own infrastructure, using the database and web server your team supports, and load the master data first, then open items, then stock and historical ledger entries. Confirm which import method your Dolibarr version supports for each object and how it handles references, so that customers, items and accounts keep their identifiers. Run the reconciliation after each load: account balances, open receivables and payables, stock valuation and document counts. The output is a reconciliation report where each balance either matches Business Central or has a documented, approved difference.
Run parallel checks with the accountant
Run both systems side by side for a set period agreed in advance. Post the same test transactions in each, such as a sales invoice, a purchase receipt, a payment, a stock adjustment and a period close, then compare the journals, the general ledger and any exports to the external accounting tool your accountant uses. Test the exports in the formats your accountant needs, such as CSV or the French FEC format if relevant, and confirm they open correctly in that tool. The output is a sign-off from the accountant and the business owner on the parallel run results, with each exception logged and resolved.
Cut over and retire the Business Central extensions
Freeze Business Central transactions at an agreed cut-off, run the final extraction and load, and reconcile the delta. Move users to Dolibarr, configure roles and access rules, and set up backups and the update routine your team will follow. Review each AL extension: rebuild the required behavior as a Dolibarr module, a workflow or a report, or retire it with a recorded decision. Once the final reconciliation is signed, disable Business Central users and decide with Microsoft's licensing terms how long the online tenant remains for read-only archive access. The output is a production Dolibarr instance, a retirement register for each extension, and an archived record of the cut-over reconciliation.
Questions buyers ask before choosing Dolibarr or Business Central
Is Dolibarr cheaper than Business Central for a small team?
Dolibarr has no license fee because it is GPL-3.0 software, so the cost comes from hosting, implementation, support and your own staff time. Business Central is billed per user under Microsoft's plans, which recur every month for as long as you hold the subscriptions. The gap depends on user count, how much configuration you need, and whether you run the server yourself or pay for DoliCloud. Ask any provider for a written breakdown that separates one-time setup from recurring hosting, support and upgrade work, and compare both options over the same user count and module list.
How long does a Dolibarr implementation take?
The duration depends on how many modules you enable, how much of your existing data needs to be cleaned up, and how many approval flows and document templates you need. A team that uses only invoicing and stock will move faster than one that also needs projects, HR and manufacturing configured together. No timeline is set here because none has been researched for this comparison. Ask for a timeline tied to named deliverables in the written scope, including data loading, testing and user training, and ask which parts depend on your own staff being available.
How much work does Dolibarr need from our own staff?
Your staff will need to decide on the chart of accounts, tax rules, numbering and approval rules, and they must check imported data before go-live. Day-to-day, someone needs to own user access, backups, PHP and database updates, and the module list. Dolibarr's prerequisites page lists MySQL 5.7.7 or newer, MariaDB 10.3 or newer, or PostgreSQL 9.1.0 or newer, so an administrator must be comfortable with those servers. Ask the implementer to name these roles in the scope and to state which tasks transfer to your team after handover.
Can a small team run Dolibarr without an outside partner?
A capable administrator can install Dolibarr, enable modules and maintain a basic setup, and the project's documentation and community resources support that work. The harder parts are the double-entry accounting setup, exports to your external accounting tool, custom modules made with the Module Builder, and secure hosting with tested backups. Those tasks benefit from outside review, especially when finance or audit owners depend on the results. Decide early which of these you will do in-house, and ask for a written handover plan if you bring in a partner.
Should we use DoliCloud or host Dolibarr ourselves?
DoliCloud is a hosted SaaS option from a company that calls itself the official Dolibarr preferred partner, with 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. Self-hosting removes per-user fees but moves backups, patching, uptime and data location onto your team or your implementer. Choose DoliCloud if you want the vendor to run the platform and your data may leave your own environment. Choose self-hosting if data location, network access and maintenance schedule must stay under your control, and ask for hosting costs in the written scope.
Can we replace Business Central in phases with Dolibarr?
Phased replacement is possible when the modules you move first can run alongside Business Central without a single shared ledger. Many teams start with a bounded area, such as invoicing or stock, and keep the general ledger in Business Central until the data and approvals are proven. Business Central can export a database as a BACPAC file only with a paid subscription and up to 10 times per month per environment, so plan extraction windows around that limit. Ask the implementer to define which records are the system of record at each phase and when each cutover happens.
What is a Dolibarr migration project priced on?
A migration is usually priced on the written scope: the modules in use, the number of data sets to extract and clean, the volume of customizations, the environments to build, the testing effort and the training and handover. Hosting and the Dolibarr licence are separate lines, since the software itself carries no fee. Fixed-scope engagements agree scope, deliverables and timelines in writing before work starts. Ask for each deliverable to be listed with its acceptance criteria, and ask what changes cost if the scope grows during the project.
How DeployOpen helps you evaluate, implement or migrate
DeployOpen plans, implements, integrates, hardens, backs up and supports self-hosted open-source platforms inside your own infrastructure. For Business Central vs Dolibarr, we start from the modules your business actually uses and the accounting exports your external tools need, then agree the scope in writing before any work begins.
How we scope
- Inventory the invoicing, stock, projects, HR and manufacturing processes you need in Dolibarr, and those you can drop.
- Confirm which accounting exports, such as CSV or FEC, your external accounting tool expects, and test them early.
- Agree deliverables, timelines and responsibilities in a fixed-scope written document before implementation starts.
How we build
- Install Dolibarr on your own servers, virtual machines, Docker or cloud accounts, on MySQL, MariaDB or PostgreSQL.
- Enable only the agreed modules, configure the double entry accounting module, and set up the chart of accounts and journals.
- Document any custom fields or Module Builder extensions, and test them against your supported Dolibarr version.
How we hand over
- Deliver the configured system, data load results, accounting export tests and reconciliation records to your team.
- Provide written runbooks covering backup, restore, user administration and the Dolibarr upgrade procedure you will follow.
- Walk your administrators and finance staff through daily operation, exports and the steps for updates on your schedule.
How we support
- Offer ongoing support, upgrades and continuous testing as a retainer, sized to the modules you run.
- Plan Dolibarr upgrades across maintenance releases and major lines on a schedule your finance team can approve.
- Confirm with you, before any change, which external accounting and reporting tools depend on each export format.
