ERP migration

Migrate from Microsoft Dynamics 365 Business Central to Dolibarr ERP

Field-level mapping, validation, and rollback between Microsoft Dynamics 365 Business Central and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.

Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

85%

11 of 13

objects map 1:1 between Microsoft Dynamics 365 Business Central and Dolibarr ERP.

Complexity

BStandard

Timeline

3-6 weeks

Rollback included Accuracy guarantee Field-level validation

Try the reverse

Dolibarr ERP
Microsoft Dynamics 365 Business Central

Overview

What this migration involves

Moving from Microsoft Dynamics 365 Business Central to Dolibarr is a significant architectural step down in exchange for dramatically lower total cost of ownership. Business Central organizes data around de-normalized data entities with dimensional accounting, multi-company tenancy, and a REST API with undocumented rate limits; Dolibarr uses a simpler flat-record model with a modular plugin architecture and no per-user licensing. We extract data from Business Central via its API v2.0, map the chart of accounts and dimensional-accounting structure to Dolibarr's simplified accounting module, and migrate open Sales Orders, Purchase Orders, and Invoices while carrying forward GL account balances as opening balances for the migration cutoff date. Posted historical transactions, approval workflows, and AL extensions do not migrate as records or code; we deliver a written inventory of these for your team to reconstruct. The migration is feasible for organizations with straightforward financial structures and up to several thousand active customer, vendor, and item records; organizations with complex multi-entity consolidations or manufacturing routing requirements should evaluate Dolibarr's capabilities against those specific processes before committing to the switch.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central

What's pushing teams away

  • Named-user licensing is expensive for organizations with many occasional users — teams report that even staff who only upload invoices or run reports each need a full paid license.
  • The learning curve is steep for users unfamiliar with Microsoft's ERP paradigm; G2 reviews cite 51 mentions of learning difficulties as a top frustration.
  • Customization requires partner support and technical expertise — G2 reviews note 20 mentions of difficult customization processes and 28 mentions of missing features for simple needs.
  • The interface is described as visually busy and overwhelming, especially for teams coming from simpler accounting tools.
  • October 2024 pricing increases (first since 2019) with another adjustment in October 2025 have alarmed existing customers and prospects already concerned about total cost of ownership.

Choosing

Dolibarr ERP logo

Dolibarr ERP

What's pulling them in

  • Free open-source core with no per-user license fee makes it the lowest-cost entry point for small teams needing ERP and CRM in one package.
  • Self-hosted deployment gives full data ownership and eliminates vendor lock-in, especially attractive to businesses with compliance requirements.
  • Modular architecture means teams enable only the features they use, keeping the interface uncluttered and reducing learning curve.
  • Fast installation with no technical knowledge required — one reviewer set up multiple businesses in minutes using their own hosting.
  • Active community forum and marketplace of third-party add-ons provide support and extension options without mandatory subscription costs.

Object mapping

How Microsoft Dynamics 365 Business Central objects map to Dolibarr ERP

Each row shows how a Microsoft Dynamics 365 Business Central object lands in Dolibarr ERP, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Microsoft Dynamics 365 Business Central

Customer

maps to

Dolibarr ERP

Third Party (type = Client)

1:1
Fully supported

Business Central Customer master records map to Dolibarr Third Party records with the Client category flag. Address, contact, payment terms, and credit-limit fields map to their Dolibarr equivalents (address, phone, email, payment term code). The Business Central Customer Posting Group maps to a Dolibarr price list or customer category. Customer contacts migrate as separate Dolibarr Contact records linked via the Societe ID. We deduplicate by customer number as the primary key.

Microsoft Dynamics 365 Business Central

Vendor

maps to

Dolibarr ERP

Third Party (type = Fournisseur)

1:1
Fully supported

Business Central Vendor records map to Dolibarr Third Party with the Supplier type. Pay-to addresses, payment terms, and vendor posting groups map to the corresponding Dolibarr fields. Vendor ledger entries (open purchase invoices) migrate as Dolibarr Supplier Invoices with the vendor's account balance carried forward as an opening balance on the supplier record.

Microsoft Dynamics 365 Business Central

Item (Inventory Item)

maps to

Dolibarr ERP

Product (type = Stock)

1:1
Fully supported

Business Central Items with Item Type = Inventory map to Dolibarr Products with the Stock checkbox enabled. Unit of Measure, item category, and base unit cost migrate to the corresponding Dolibarr product fields. The product's default warehouse in Dolibarr is set from Business Central's location code. Non-inventory items (services) map to Dolibarr Products with the Stock checkbox disabled.

Microsoft Dynamics 365 Business Central

General Ledger Account

maps to

Dolibarr ERP

Accounting Account

lossy
Fully supported

Business Central's Chart of Accounts with its account numbering scheme maps to Dolibarr's Accounting Account plan. This is a configuration pass, not a direct record migration, because Dolibarr's accounting module uses a simpler flat account structure without native dimension tagging. If Business Central uses Dimensions (Department, Project, Division) for posting segregation, we create sub-account categories or use Dolibarr's user-defined auxiliary accounts to preserve reporting segregation, and we document the dimension-to-account mapping for the customer's finance team.

Microsoft Dynamics 365 Business Central

Sales Order

maps to

Dolibarr ERP

Customer Proposal / Order

1:1
Fully supported

Open Business Central Sales Orders migrate as Dolibarr Customer Proposals with status set to draft or validated depending on the order's shipment status. Order lines (Item lines and comment lines) migrate with quantities, unit prices, and tax codes preserved. Document dates and promised delivery dates carry forward. Already-invoiced lines are skipped because the invoice records cover the financial record.

Microsoft Dynamics 365 Business Central

Sales Invoice (Posted)

maps to

Dolibarr ERP

Customer Invoice

1:1
Fully supported

Posted Business Central Sales Invoices map to Dolibarr Customer Invoice records. We migrate open (unpaid) invoices as validated invoices requiring payment recording; paid invoices are migrated as paid invoices for historical record. The invoice total, tax amounts, and customer reference all map to Dolibarr fields. Full historical posted invoice replay is scoped selectively based on the migration cutoff date agreed during discovery.

Microsoft Dynamics 365 Business Central

Purchase Order

maps to

Dolibarr ERP

Supplier Proposal / Order

1:1
Fully supported

Open Business Central Purchase Orders migrate as Dolibarr Supplier Proposals with the appropriate status. Expected receipt dates and quantities migrate to line records. Prepayment amounts on purchase orders map to Dolibarr prepayment invoice records if the destination configuration supports advance payment tracking.

Microsoft Dynamics 365 Business Central

Purchase Invoice (Posted)

maps to

Dolibarr ERP

Supplier Invoice

1:1
Fully supported

Posted Business Central Vendor Ledger Entries for purchase invoices map to Dolibarr Supplier Invoice records. Open AP invoices (unpaid) migrate with the outstanding balance preserved; paid invoices migrate as closed records for historical reporting. Pre-cutoff paid invoices are typically skipped or migrated as summary entries unless specifically required by the customer's audit requirements.

Microsoft Dynamics 365 Business Central

Item Ledger Entry (Open Quantity)

maps to

Dolibarr ERP

Stock Movement

lossy
Fully supported

Open Business Central Item Ledger Entries (quantity on hand, pending receipts, pending shipments) migrate as Dolibarr Stock Real Worth entries or as initial stock warehouse values depending on the inventory complexity. Cost layers (Value Entries) are not fully replayed; instead, we carry forward the current average cost as the product's default purchase price in Dolibarr to maintain consistent product costing without replicating the full inventory valuation history.

Microsoft Dynamics 365 Business Central

Bank Account

maps to

Dolibarr ERP

Bank Account

1:1
Fully supported

Business Central Bank Account records map to Dolibarr Bank Account records with bank name, account number, and currency preserved. Open bank account ledger entries migrate as initial balance entries in Dolibarr's bank reconciliation module. Bank posting groups map to Dolibarr's bank account category.

Microsoft Dynamics 365 Business Central

Job

maps to

Dolibarr ERP

Project

1:1
Fully supported

Business Central Jobs (project management) map to Dolibarr Project records. Task breakdowns migrate as Dolibarr Project Tasks with WBS hierarchy preserved in the task structure. Resource time entries migrate as Dolibarr Project Task Time entries linked to the corresponding Project and Task. Billable budgets and job journal postings map to Dolibarr Project budget lines. We flag any Job that uses billable resources not natively supported in Dolibarr's time-tracking module.

Microsoft Dynamics 365 Business Central

Fixed Asset

maps to

Dolibarr ERP

Asset

1:1
Fully supported

Business Central Fixed Asset records (acquisition cost, depreciation books, insurance coverage) map to Dolibarr Asset records. Depreciation schedules and current book value migrate as opening depreciation entries in Dolibarr's fixed asset module. Accumulated depreciation to date of migration carries forward as a fixed asset ledger entry.

Microsoft Dynamics 365 Business Central

Approval Workflow

maps to

Dolibarr ERP

Approval Workflow

1:1
Fully supported

Business Central approval workflow definitions are environment-specific, tied to named user accounts, delegate settings, and response limits configured within the Business Central tenant. These are not portable between systems. We do not migrate them. We deliver a written inventory of every active approval workflow in Business Central (trigger, approver chain, conditions, actions) with a Dolibarr workflow reconstruction recommendation. Dolibarr's workflow module is simpler and document-centric (approvals on proposals, orders, invoices); the customer's admin rebuilds the approval logic based on the inventory.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central gotchas

High

Named-user licensing has no concurrent-use relief

High

API rate limits throttle large-volume migrations

Medium

Historical posted transactions require selective migration scoping

Medium

NAV-to-Business Central cloud migration requires partner coordination

Low

Custom fields and AL extensions require separate migration handling

Dolibarr ERP logo

Dolibarr ERP gotchas

High

Foreign key constraint errors on cross-distribution database restore

High

SQL injection vulnerabilities in version 9.0.1

Medium

Custom fields stored as JSON in extraoptions require field-by-field deserialization

Medium

Decimal precision and rounding configuration affects price fields

Low

No native iOS/Android app forces reliance on browser

Pair-specific challenges

  • Dimensional accounting has no direct Dolibarr equivalent

    Business Central's dimensional accounting (G/L Account plus up to three Dimensions such as Department, Project, and Division) allows posting-level segmentation without separate account codes. Dolibarr's accounting module uses a flat account structure where reporting segmentation relies on account code prefixes or auxiliary sub-accounts. Organizations that depend on dimensional reports (profit-and-loss by department, by project) will need to either restructure their chart of accounts to encode dimension data in the account code, use Dolibarr's user-defined auxiliary account feature, or export dimension-tagged data to a reporting layer outside Dolibarr. We document the specific dimension-to-account mapping strategy during scoping and flag any dimensional reports that will require structural changes in Dolibarr.

  • Posted transaction history must be scoped to a defined cutoff

    Business Central's posted transaction tables (G/L Entry, Item Ledger Entry, Value Entry) grow indefinitely and can contain millions of rows for organizations with multi-year histories. Migrating full historical postings into Dolibarr is impractical and would extend the cutover window substantially. We work with the customer to define a migration cutoff — typically the last 12 to 24 months of posted history plus all open documents — and carry forward account balances as opening balances for pre-cutoff periods. Historical invoice and order documents are migrated as open or closed records rather than replayed as individual ledger entries. This keeps the go-live window manageable while preserving the data the customer actually needs for audit continuity.

  • Multi-company tenancy requires separate Dolibarr instances

    Business Central supports multiple companies within a single tenant, allowing consolidated reporting and intercompany transactions within one environment. Dolibarr runs one company per installation. Organizations with two or more Business Central companies must either run separate Dolibarr installations (one per company) or consolidate into a single Dolibarr instance with company data separated by accounting account ranges or project tagging. Intercompany transaction tracking in Business Central does not have a native Dolibarr equivalent. We identify all Business Central companies during discovery and agree on a consolidation or separation strategy before migration begins.

  • Custom AL extensions and Dataverse fields require separate migration handling

    Business Central allows custom fields via AL extensions stored in separate extension tables. Custom fields added to standard entities (Customer, Vendor, Item) are not part of the standard data entity API and may not appear in standard API exports. We identify all custom fields during the discovery phase, assess whether they are accessible via the API or require a custom export via RapidStart configuration packages or the Import Export PowerTool, and migrate them in a second pass after the base entity migration is validated. Fields with no destination equivalent are flagged for the customer to configure in Dolibarr before the second pass runs.

  • Manufacturing and warehouse management are not supported in Dolibarr

    Business Central's Production Orders, routings, work centers, and warehouse management features (available on Premium tier) have no equivalent in Dolibarr's standard modules. Organizations using these features for make-to-order or assemble-to-order manufacturing must evaluate whether Dolibarr's BOM (bill of materials) module for simple product assemblies meets their needs before committing to the migration. We flag any Production Order or warehouse shipment records in the source data as out-of-scope for standard migration and document them in the written automation inventory with a recommendation to use Dolibarr's product assembly feature or a third-party manufacturing add-on if the customer's requirements justify the additional implementation cost.

Migration approach

Six steps for a successful Microsoft Dynamics 365 Business Central to Dolibarr ERP data migration

  1. Discovery and migration cutoff definition

    We audit the source Business Central environment across company count, active user count, custom fields and AL extensions, dimensional-accounting configuration, open document volume (Sales Orders, Purchase Orders, Invoices), and inventory complexity. We extract the chart of accounts with its account categories and dimension assignments, and we profile the G/L Entry and Item Ledger Entry tables to estimate row counts at various cutoff windows. The discovery output is a written migration scope document specifying the cutoff date, dimensional-accounting mapping strategy, object list with row counts, and Dolibarr module recommendations based on the customer's actual Business Central usage.

  2. Dolibarr module and chart-of-accounts configuration

    We install Dolibarr (or work with the customer's existing Dolibarr instance) and enable the modules required by the migration scope: Third Party (CRM), Product (Stock or Service), Commercial (Proposals and Orders), Invoice (Customer and Supplier), Accounting, Bank, Project, and Stock. We configure the chart of accounts in Dolibarr to align with the Business Central account structure, including any auxiliary accounts needed to preserve dimensional-accounting segregation. If the customer runs multiple Business Central companies, we configure either separate Dolibarr installations or a single installation with company-tagged account ranges based on the consolidation strategy agreed in discovery.

  3. Sandbox migration and reconciliation

    We run a full migration into a Dolibarr staging environment using production-like data volume. The customer's finance team reconciles record counts (Customers in, Vendors in, Products in, open Orders in, open Invoices in, Project records in), spot-checks 25-50 records against the Business Central source, and reviews the chart-of-accounts mapping and dimensional-accounting encoding. Any field mapping corrections, missing fields that need configuration in Dolibarr, or dimensional-accounting adjustments happen here before production migration begins.

  4. Data extraction and transformation from Business Central

    We extract data from Business Central using its REST API v2.0 with OAuth 2.0 authentication. For custom fields and deep table access, we use RapidStart configuration packages or the Import Export PowerTool (an AppSource extension) to produce structured CSV exports. We transform records in a staging layer: the Lead-Contact-style split logic does not apply here (Dolibarr has no such concept), but we do apply the dimensional-accounting encoding (converting BC Dimensions to Dolibarr account prefixes or auxiliary tags), deduplicate by Business Central number as the primary key, and resolve any Business Central number series to Dolibarr's entity ID format.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Third Parties (Customers and Vendors) first, then Products, then open Sales and Purchase documents, then open Invoice records, then bank accounts and fixed assets, then Project records. GL account balances are carried forward as opening balance entries after all master data is in place. Activity history beyond the cutoff date is not replayed as detailed ledger entries. Each phase emits a row-count reconciliation report before the next phase begins. We use Dolibarr's built-in import tools for structured CSV loads with batch processing and error logging.

  6. Cutover, validation, and automation inventory handoff

    We freeze Business Central writes during cutover, run a final delta migration of any records modified during the migration window, then set Dolibarr as the system of record. We deliver the written inventory of Business Central approval workflows, production orders, warehouse shipment records, and custom AL extensions that were excluded from the migration, with Dolibarr reconstruction recommendations for each. We support a one-week hypercare window where we resolve any reconciliation issues the customer's team surfaces. We do not rebuild Business Central workflows, production orders, or AL extensions in Dolibarr; those are separate configuration engagements or internal admin tasks.

Platform deep dives

Context on both ends of the pair

Microsoft Dynamics 365 Business Central logo

Microsoft Dynamics 365 Business Central

Source

Strengths

  • Tight integration with Microsoft 365 (Outlook, Teams, SharePoint) for users already in the Microsoft ecosystem.
  • Includes Copilot AI, predictive analytics, and embedded Power BI dashboards at no additional cost in both license tiers.
  • Supports multiple companies within a single tenant for holding-company or multi-entity organizational structures.
  • Open REST API v2.0 with OAuth 2.0 authentication and data entity abstraction layer for developer-friendly integrations.
  • Strong partner ecosystem specializing in NAV-to-Business Central migrations provides implementation confidence for legacy upgrades.

Weaknesses

  • Named-user licensing model means every active user account requires a paid license — no concurrent access model to reduce costs for occasional users.
  • SaaS-only deployment means no on-premises option; organizations requiring full data residency control may not have viable alternatives within Microsoft's stack.
  • Manufacturing module (Production Orders, routing, work centers) is only available on Premium tier, pushing cost-sensitive manufacturers to higher-priced plans.
  • Customization and extension development requires AL language knowledge and developer licenses, limiting what power users can do without a partner engagement.
  • Global pricing increases effective October 2024 and again October 2025 after five years of stable pricing, creating budget uncertainty for existing customers.
Dolibarr ERP logo

Dolibarr ERP

Destination

Strengths

  • Free core software with AGPL license and no per-user mandatory fee for self-hosted deployments.
  • Modular architecture lets teams activate only needed features, keeping the interface focused and the database lean.
  • Self-hosted option provides full data sovereignty and avoids recurring SaaS subscription costs.
  • Built-in CSV/Excel import and export wizard with saved profiles simplifies recurring data operations.
  • Low-code Module Builder allows functional extensions without writing PHP code.

Weaknesses

  • No native documented REST API for programmatic bulk operations — all migrations depend on the import/export wizard or direct database access.
  • Reporting and analytics are weak without paid add-ons, and built-in charts are limited compared to modern SaaS platforms.
  • UI design is described as dated by multiple reviewers, with infrequent visual updates to the default theme.
  • Community-only support for self-hosted deployments means no SLA or guaranteed response time for issues.
  • Security vulnerabilities (CVE-2024-5314, CVE-2024-5315) in version 9.0.1 with no immediate patch reported.

Complexity grading

How hard is this migration?

Standard ERP migration. All 8 core objects map 1:1 between Microsoft Dynamics 365 Business Central and Dolibarr ERP.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Microsoft Dynamics 365 Business Central and Dolibarr ERP.

  • Object compatibility

    A

    All 8 core objects map 1:1 between Microsoft Dynamics 365 Business Central and Dolibarr ERP.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Microsoft Dynamics 365 Business Central: Maximum 5 concurrent requests per user with a request queue size of 95; HTTP 429 returned when exceeded.

  • Data volume sensitivity

    A

    Microsoft Dynamics 365 Business Central exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Microsoft Dynamics 365 Business Central to Dolibarr ERP migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Microsoft Dynamics 365 Business Central to Dolibarr ERP data migrations

Answers to the questions buyers ask most during Microsoft Dynamics 365 Business Central to Dolibarr ERP migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Microsoft Dynamics 365 Business Central to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between three and six weeks for organizations with straightforward financial structures, under 5,000 active customer and vendor records, and a defined 12-to-24-month posted-history cutoff. Migrations with dimensional-accounting reconstruction, multiple Business Central companies, large open document stacks, or complex item-cost-layer requirements move to eight to fourteen weeks. The timeline depends heavily on data quality: organizations that invest in pre-migration data cleansing (removing duplicate vendors, resolving inconsistent item costing methods, standardizing dimension usage) move faster than those expecting the migration process to clean the data during transform.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Microsoft Dynamics 365 Business Central.
Land in Dolibarr ERP, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day