ERP migration

Migrate from Xledger to Dolibarr ERP

Field-level mapping, validation, and rollback between Xledger and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.

Xledger logo

Xledger

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

92%

12 of 13

objects map 1:1 between Xledger and Dolibarr ERP.

Complexity

BStandard

Timeline

4-6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Xledger logo

Xledger

What's pushing teams away

  • ERP implementations frequently extend beyond the initial 6-12 month estimate for mid-market organisations, with large multi-entity rollouts reaching 18-21 months, making the migration window longer and more disruptive than expected.
  • Smaller finance teams report a steep learning curve when configuring multi-entity structures, custom workflows, and the Chart of Accounts for the first time, leading to extended reliance on Xledger's in-house consultants.
  • Some organisations evaluate switching to Sage Intacct, NetSuite, or Acumatica after implementation, citing specific feature gaps or total cost of ownership comparison after the initial subscription period ends.
  • Power users note that the flexibility of configurable dashboards and reports requires dedicated configuration time, and knowledge does not transfer easily when team members leave.

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 Xledger objects map to Dolibarr ERP

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

maps to

Dolibarr ERP

Category (ThirdParty Category)

1:many
Fully supported

Xledger 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)

maps to

Dolibarr ERP

Category (ThirdParty Category)

1:1
Fully supported

Xledger 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

maps to

Dolibarr ERP

Third Party (societe)

1:1
Fully supported

Xledger 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

maps to

Dolibarr ERP

Accounting Account (compte)

1:1
Mapping required

Xledger'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

maps to

Dolibarr ERP

Account Booking (ecritures comptables)

1:1
Mapping required

Historical 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)

maps to

Dolibarr ERP

Supplier Invoice (facture_fournisseur)

1:1
Fully supported

Open 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)

maps to

Dolibarr ERP

Customer Invoice (facture)

1:1
Fully supported

Open 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

maps to

Dolibarr ERP

Bank Account (comptes_bancaires)

1:1
Fully supported

Xledger 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

maps to

Dolibarr ERP

Asset (immobilisation)

1:1
Fully supported

Fixed 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

maps to

Dolibarr ERP

Budget Line (budget_lines)

1:1
Fully supported

Xledger 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

maps to

Dolibarr ERP

Project (projet)

1:1
Fully supported

Project 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

maps to

Dolibarr ERP

Expense Report (expensereport) and Project Time (projet_task_time)

1:1
Fully supported

Time 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

maps to

Dolibarr ERP

GED Document (ecm)

1:1
Fully supported

Documents 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.

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.

Xledger logo

Xledger gotchas

High

Multi-entity intercompany journal entries require careful cross-mapping

High

Historical AP/AR records map to invoice-level objects, not account balances

Medium

Workflow and approval configurations are custom and non-transferable

Medium

ERP implementations extend well beyond the initial migration window

Low

Built-in integrations are Xledger-side only and require separate destination-side configuration

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

  • Data inconsistencies emerge when field formats diverge

    Xledger stores multi-currency amounts, Entity codes, and Subledger references in formats that do not map directly to Dolibarr's flat third-party and invoice schemas. Data profiling during discovery frequently reveals inconsistent country codes, tax ID formats, and currency precision across Entities. We run a data-quality cleanse pass before any import, normalising currency precision, validating tax IDs against country-specific formats, and standardising Entity and Subledger codes against Dolibarr's allowed character set for custom fields.

  • Data mapping is the most delicate technical step

    Xledger field names and data structures differ from Dolibarr's schema across all object types. Customer names and addresses map cleanly, but multi-entity codes, tax registration numbers, Subledger references, and Subledger-to-Entity linkages require custom field creation and transformation logic. Dolicraft's migration guide notes that some data requires transformations rather than direct mapping, and we build those transforms during the schema design phase before any production data moves.

  • Cross-module relationships require element_element queries

    Dolibarr stores cross-module relationships in the llx_element_element table, linking objects such as Interventions linked to Invoices, or Projects linked to Tasks. Migration queries must account for these relationships rather than importing modules in isolation. We write separate queries to migrate element_element cross-references after base object IDs are assigned, so that related records remain connected in Dolibarr after migration.

  • Custom field migration requires separate queries

    Xledger custom object values and extended properties require separate migration queries beyond the standard object import. Dolibarr custom fields are stored in llx_customfields and associated via object type and row ID. We pre-create all required custom fields during Dolibarr schema design, then run custom field value imports after base object IDs are confirmed, using the same batch and reconciliation process as standard object migration.

  • Server migration and conf.php configuration cause common failures

    Moving Dolibarr between servers requires correct configuration in conf.php, including the database host, port, name, credentials, character set, collation, document root, data root, and the unique instance ID. If any parameter is incorrect, Dolibarr returns a configuration error and prompts a fresh installation. We validate the conf.php configuration against the database before any migration query runs and flag any character set or collation mismatches that could cause import failures on text-heavy fields.

Migration approach

Six steps for a successful Xledger to Dolibarr ERP data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Xledger logo

Xledger

Source

Strengths

  • Native multi-entity consolidation with live roll-up across parent and subsidiary hierarchies in a single subscription.
  • Advanced OCR for AP invoice capture and expense receipts built into the platform at no additional licensing fee.
  • Multi-currency and multi-language support for international operations without edition gating.
  • True multi-tenant cloud architecture with automatic updates and no per-user replication of integrations.
  • Project accounting, time tracking, and fund accounting modules designed for contract-based and grant-funded organisations.

Weaknesses

  • No publicly available pricing tiers or rate limit documentation on the public website, requiring direct sales engagement for scoping.
  • Limited public review presence with only 2 verified reviews on G2 and 1 on Gartner Peer Insights, making independent feature validation difficult.
  • Implementation timelines frequently extend to 12-18 months for organisations with complex multi-entity or multi-currency configurations.
  • Web Services API uses a legacy SOAP-based interface alongside the newer GraphQL API, requiring two different authentication schemes depending on the integration path.
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. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Xledger and Dolibarr ERP.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • 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

    Xledger: Not publicly documented.

  • Data volume sensitivity

    B

    Xledger doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Xledger 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 Xledger to Dolibarr ERP data migrations

Answers to the questions buyers ask most during Xledger to Dolibarr ERP migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between four and six weeks for organisations with fewer than 10,000 third parties, a single Entity or simple Entity hierarchy, and under 12 months of historical GL journal entries. Complex multi-Entity migrations with 50+ Entities, multi-currency Subledgers, extensive intercompany journal histories, and project accounting with custom dimensions move to eight to twelve weeks because of the Entity-to-category reconciliation, Subledger mapping design, and intercompany posting notation work required before any data moves.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Xledger.
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