ERP migration
Field-level mapping, validation, and rollback between Xledger and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
Xledger
Source
Dolibarr ERP
Destination
Compatibility
12 of 13
objects map 1:1 between Xledger and Dolibarr ERP.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Moving from Xledger to Dolibarr is a structural migration that flattens Xledger's multi-entity hierarchy into Dolibarr's third-party-centric model. Xledger organizes data across Entities, each with its own Subledger, Chart of Accounts, and AP/AR; Dolibarr uses a flat third-party table for Customers and Suppliers with category assignments. We collapse the Entity-level structure, map Subledgers to Dolibarr category assignments, and preserve intercompany journal posting notations so the customer's finance team can reconstruct elimination entries in Dolibarr's accounting module. Open AP/AR migrate as invoice records with aging preserved. Projects, budgets, and fixed assets transfer with full dimension mapping. Time entries and expense records transfer without workflow status, which is non-transferable. Xledger's automated workflow engine, approval chains, and intercompany elimination automation do not migrate; we document each active configuration for manual rebuild in Dolibarr.
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.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Xledger 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.
Xledger
Entity
Dolibarr ERP
Category (ThirdParty Category)
1:manyXledger Entities are top-level organisational containers with their own Subledger, Chart of Accounts, and bank connections. Dolibarr has no native Entity concept; instead we map each Xledger Entity to a Dolibarr third-party Category (categorie type Societe). Cross-Entity shared Customers and Suppliers are assigned to multiple Categories or held as unclassified Third Parties. Multi-entity reporting that relied on live Xledger consolidation requires a separate reconciliation step in Dolibarr's accounting module post-migration.
Xledger
Subledger (AP, AR, Banking, Project)
Dolibarr ERP
Category (ThirdParty Category)
1:1Xledger Subledgers carry a type classification (AP, AR, Banking, Project) linked to an owning Entity. We map Subledger type and Entity assignment to Dolibarr third-party Categories, preserving the Subledger-to-Entity relationship as a custom field on each Third Party so that reporting by Subledger type is reconstructable in Dolibarr.
Xledger
Customer and Supplier
Dolibarr ERP
Third Party (societe)
1:1Xledger Customer and Supplier records map to Dolibarr Third Parties. The Xledger Subledger reference becomes a custom field on the Third Party record. Multi-entity Customers and Suppliers shared across Xledger Entities are deduplicated by company registration number or tax ID; if no unique key exists, we flag duplicates for the customer's admin to resolve. Payment terms and tax codes map to Dolibarr conditions_reglement and Mode of Regulation / payment terms fields.
Xledger
Chart of Accounts
Dolibarr ERP
Accounting Account (compte)
1:1Xledger's configurable Chart of Accounts varies by industry and Entity type. We map each account code and name to Dolibarr's accounting chart of accounts, preserving account type (charge, product, tiers, immobilsation). Non-profit and fund accounts from Xledger map to Dolibarr's accounting scheme with custom account type assignments. Account dimension tags used for project or cost-centre reporting become accounting extra-fields or category assignments.
Xledger
General Ledger Journal Entries
Dolibarr ERP
Account Booking (ecritures comptables)
1:1Historical GL journal entries migrate to Dolibarr accounting entries with account code, debit/credit amount, and posting date preserved. Multi-line journal distributions with intercompany Entity references are flagged during migration with an intercompany notation field so the customer's finance team can manually create elimination entries in Dolibarr's accounting module. We do not recreate Xledger's automated intercompany elimination engine.
Xledger
Open AP (Accounts Payable)
Dolibarr ERP
Supplier Invoice (facture_fournisseur)
1:1Open AP in Xledger is tracked via Subledger invoice records linked to Suppliers. We extract every outstanding supplier invoice, map it to Dolibarr supplier invoice records, and preserve line items, payment terms, and aging data. Closed AP invoices migrate as historical GL journal entries against the General Ledger rather than as open invoice records.
Xledger
Open AR (Accounts Receivable)
Dolibarr ERP
Customer Invoice (facture)
1:1Open AR in Xledger is tracked via Subledger invoice records linked to Customers. We extract every outstanding customer invoice, map it to Dolibarr customer invoice records, and preserve line items, payment terms, and aging data. Closed AR invoices migrate as historical GL journal entries rather than as open invoice records.
Xledger
Bank Account
Dolibarr ERP
Bank Account (comptes_bancaires)
1:1Xledger bank account records include routing details, account type, currency, and Entity assignment. We map these to Dolibarr bank account records. Bank feed configurations (JPMorgan, Wells Fargo, Bank of America in Xledger) are captured as configuration notes for the customer to reconfigure within Dolibarr's bank feed module or via a third-party aggregator.
Xledger
Fixed Asset
Dolibarr ERP
Asset (immobilisation)
1:1Fixed Asset records in Xledger include acquisition date, cost, depreciation method, useful life, and Asset Register entries. We map asset definitions and current depreciation schedules to Dolibarr's Asset module. Depreciation schedules transfer as active depreciation records; future period depreciation is recalculated in Dolibarr's Asset module post-migration.
Xledger
Budget Item
Dolibarr ERP
Budget Line (budget_lines)
1:1Xledger budgets are created at the Entity level and linked to specific accounts and dimensions. Budget versions and forecast iterations are preserved as Dolibarr budget lines with account code and year assignments. Dolibarr's budget module does not natively support multi-dimensional budget versions; we flatten multi-dimensional budgets into separate budget lines with a dimension reference as a custom field.
Xledger
Project and Project Accounting
Dolibarr ERP
Project (projet)
1:1Project records in Xledger track billing, revenue recognition, and cost allocation against a project's financial lifecycle. We map project definitions, customer assignments, and associated Subledger references to Dolibarr project records. Custom project fields transfer to Dolibarr extra-fields on the project object.
Xledger
Time Entry and Expense
Dolibarr ERP
Expense Report (expensereport) and Project Time (projet_task_time)
1:1Time entries and expense records in Xledger are linked to Employees and Projects. We migrate entry records, amounts, and project assignments to Dolibarr expense report and project time-tracking records. Xledger OCR-captured receipt data and approval workflow status do not transfer; we document the approval chain for the customer's admin to rebuild in Dolibarr's expense workflow module.
Xledger
Document and Attachment
Dolibarr ERP
GED Document (ecm)
1:1Documents and attachments in Xledger are stored against journal entries, vendors, customers, and assets. We migrate document metadata and link references to Dolibarr's Electronic Document Management (GED) module. Large-volume document archives may require chunked transfer and Dolibarr's attachment upload limits considered during scoping.
| Xledger | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Entity | Category (ThirdParty Category)1:many | Fully supported | |
| Subledger (AP, AR, Banking, Project) | Category (ThirdParty Category)1:1 | Fully supported | |
| Customer and Supplier | Third Party (societe)1:1 | Fully supported | |
| Chart of Accounts | Accounting Account (compte)1:1 | Mapping required | |
| General Ledger Journal Entries | Account Booking (ecritures comptables)1:1 | Mapping required | |
| Open AP (Accounts Payable) | Supplier Invoice (facture_fournisseur)1:1 | Fully supported | |
| Open AR (Accounts Receivable) | Customer Invoice (facture)1:1 | Fully supported | |
| Bank Account | Bank Account (comptes_bancaires)1:1 | Fully supported | |
| Fixed Asset | Asset (immobilisation)1:1 | Fully supported | |
| Budget Item | Budget Line (budget_lines)1:1 | Fully supported | |
| Project and Project Accounting | Project (projet)1:1 | Fully supported | |
| Time Entry and Expense | Expense Report (expensereport) and Project Time (projet_task_time)1:1 | Fully supported | |
| Document and Attachment | GED Document (ecm)1: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.
Xledger gotchas
Multi-entity intercompany journal entries require careful cross-mapping
Historical AP/AR records map to invoice-level objects, not account balances
Workflow and approval configurations are custom and non-transferable
ERP implementations extend well beyond the initial migration window
Built-in integrations are Xledger-side only and require separate destination-side configuration
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 Entity scoping
We audit the source Xledger environment across all Entities, Subledgers, Chart of Accounts structure, active Customers and Suppliers, open AP/AR invoice volumes, historical GL journal entry depth, budget versions, fixed asset registers, and project count. We review active Xledger workflows, approval chains, intercompany posting rules, bank feed configurations, and integration endpoints. We document the Subledger-to-Entity mapping matrix and identify any cross-Entity shared third parties. The discovery output is a written migration scope with object counts, Entity complexity assessment, and Dolibarr module activation plan.
Dolibarr schema design and module activation
We activate the required Dolibarr modules (Third Party, Invoice, Supplier Invoice, Accounting, Bank, Project, Expense Report, Asset, Budget, GED) and configure the accounting chart of accounts aligned to the migrated Xledger account structure. We create third-party Categories to represent Xledger Entities and Subledger types, pre-create all custom fields for Entity codes, Subledger references, and intercompany notations, and configure payment term defaults. Schema is validated in a staging Dolibarr instance before production deployment.
Staging migration and reconciliation
We run a full migration into a staging Dolibarr environment using production-like data volumes. The customer's finance lead reconciles record counts (Third Parties in, Accounts in, Invoices in, Journal entries in), spot-checks 25-50 records against the Xledger source for field accuracy and currency precision, and validates that intercompany journal entries carry the correct notation. Any mapping corrections are documented and applied to the production migration script before cutover.
Entity and Subledger category reconciliation
We map every Xledger Entity and Subledger to a Dolibarr third-party Category. Cross-Entity shared Customers and Suppliers go through a dedupe pass using tax ID or company registration number as the unique key; records without a unique key are flagged for the customer's admin to resolve. Subledger type assignments are preserved as custom fields on each Third Party so that reports filtered by Subledger type remain available in Dolibarr.
Production migration in dependency order
We run production migration in record-dependency order: bank accounts and chart of accounts first; then third parties with Subledger category assignments and intercompany custom fields; then open supplier invoices and customer invoices with line items, payment terms, and aging preserved; then historical GL journal entries with intercompany notation; then fixed assets with active depreciation schedules; then budget lines; then project records with custom fields; then document metadata to GED. Each phase emits a row-count reconciliation report before the next phase begins. Custom field value imports run after base object IDs are confirmed.
Cutover, validation, and workflow handoff
We freeze writes to Xledger during cutover, run a final delta migration of any records modified during the migration window, then switch the system of record to Dolibarr. We deliver a written inventory of every active Xledger workflow and approval chain with its trigger, conditions, actions, and recommended Dolibarr equivalent. We document the intercompany elimination posting procedure for the finance team to follow. We support a one-week hypercare window where we resolve reconciliation issues. We do not rebuild Xledger workflows, approval chains, or bank feed integrations in Dolibarr; that work is handled by the customer's admin team or a Dolibarr implementation partner.
Platform deep dives
Xledger
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Xledger and Dolibarr ERP.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
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
Xledger: Not publicly documented.
Data volume sensitivity
Xledger doesn't expose a bulk API — REST + parallelization used for high-volume runs.
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 Xledger to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your Xledger 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 Xledger
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.