ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
11 of 13
objects map 1:1 between Microsoft Dynamics 365 Business Central and Dolibarr ERP.
Complexity
BStandard
Timeline
3-6 weeks
Try the reverse
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
Microsoft Dynamics 365 Business Central platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Business Central.
Destination platform
Dolibarr ERP platform overview
Scorecard, SWOT, gotchas, and pricing for Dolibarr ERP.
Data migration guide
The complete Dolibarr migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Source platform guide
Dynamics 365 Business Central migration guide
Understand the data you're exporting from Microsoft Dynamics 365 Business Central before mapping it.
Destination checklist
Dolibarr migration checklist
Pre- and post-cutover tasks for moving onto Dolibarr ERP.
Source checklist
Dynamics 365 Business Central migration checklist
Exit checklist for unwinding your Microsoft Dynamics 365 Business Central setup cleanly.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Dolibarr ERP
Third Party (type = Client)
1:1Business 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
Dolibarr ERP
Third Party (type = Fournisseur)
1:1Business 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)
Dolibarr ERP
Product (type = Stock)
1:1Business 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
Dolibarr ERP
Accounting Account
lossyBusiness 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
Dolibarr ERP
Customer Proposal / Order
1:1Open 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)
Dolibarr ERP
Customer Invoice
1:1Posted 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
Dolibarr ERP
Supplier Proposal / Order
1:1Open 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)
Dolibarr ERP
Supplier Invoice
1:1Posted 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)
Dolibarr ERP
Stock Movement
lossyOpen 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
Dolibarr ERP
Bank Account
1:1Business 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
Dolibarr ERP
Project
1:1Business 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
Dolibarr ERP
Asset
1:1Business 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
Dolibarr ERP
Approval Workflow
1:1Business 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.
| Microsoft Dynamics 365 Business Central | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer | Third Party (type = Client)1:1 | Fully supported | |
| Vendor | Third Party (type = Fournisseur)1:1 | Fully supported | |
| Item (Inventory Item) | Product (type = Stock)1:1 | Fully supported | |
| General Ledger Account | Accounting Accountlossy | Fully supported | |
| Sales Order | Customer Proposal / Order1:1 | Fully supported | |
| Sales Invoice (Posted) | Customer Invoice1:1 | Fully supported | |
| Purchase Order | Supplier Proposal / Order1:1 | Fully supported | |
| Purchase Invoice (Posted) | Supplier Invoice1:1 | Fully supported | |
| Item Ledger Entry (Open Quantity) | Stock Movementlossy | Fully supported | |
| Bank Account | Bank Account1:1 | Fully supported | |
| Job | Project1:1 | Fully supported | |
| Fixed Asset | Asset1:1 | Fully supported | |
| Approval Workflow | Approval Workflow1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Named-user licensing has no concurrent-use relief
API rate limits throttle large-volume migrations
Historical posted transactions require selective migration scoping
NAV-to-Business Central cloud migration requires partner coordination
Custom fields and AL extensions require separate migration handling
Dolibarr ERP gotchas
Foreign key constraint errors on cross-distribution database restore
SQL injection vulnerabilities in version 9.0.1
Custom fields stored as JSON in extraoptions require field-by-field deserialization
Decimal precision and rounding configuration affects price fields
No native iOS/Android app forces reliance on browser
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Microsoft Dynamics 365 Business Central
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between Microsoft Dynamics 365 Business Central and Dolibarr ERP.
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
All 8 core objects map 1:1 between Microsoft Dynamics 365 Business Central and Dolibarr ERP.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
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
Microsoft Dynamics 365 Business Central exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Microsoft Dynamics 365 Business Central to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Microsoft Dynamics 365 Business Central
Other ways to arrive at Dolibarr ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.