ERP migration

Migrate from eFacto ERP to Dolibarr ERP

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

eFacto ERP logo

eFacto ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

83%

10 of 12

objects map 1:1 between eFacto ERP and Dolibarr ERP.

Complexity

CModerate

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from eFacto ERP to Dolibarr is a platform switch from a vendor-locked Indian retail ERP to a community-maintained open-source ERP. The primary extraction challenge is that eFacto publishes no public REST API, so data must come from a read-only SQL export coordinated with the eFacto administrator. The primary schema challenge is that Dolibarr uses a double-entry accounting model with a Chart of Accounts attached to Bank and Cash accounts, while eFacto's retail-oriented ledgers often operate on cash-basis or simplified accrual that does not enforce debit-credit balance at record creation. We design the Dolibarr Chart of Accounts structure before migration, then sequence data loads so that the COA, Third Parties, Products, and Stock precede any invoice or order records. POS receipts from eFacto migrate as individual Bank or Cash transaction entries in Dolibarr rather than as invoices, because Dolibarr's POS module does not auto-link receipts to G/L entries. Custom SSRS reports built in eFacto do not migrate; we export the RDL definitions and document the report parameters for the customer's admin to rebuild in Dolibarr or a reporting tool of choice.

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

eFacto ERP logo

eFacto ERP

What's pushing teams away

  • Pricing is opaque — no public per-user or per-module rates; sales team contact required, creating friction during vendor evaluation.
  • Limited public API documentation makes custom integrations and automated data extraction difficult, forcing reliance on vendor-provided exports.
  • Smaller vendor footprint compared to global ERP platforms raises concerns about long-term product roadmap and support SLAs for enterprise-scale deployments.

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

Each row shows how a eFacto ERP 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.

eFacto ERP

Chart of Accounts

maps to

Dolibarr ERP

Bank Account / Cash Account

lossy
Mapping required

eFacto stores account codes in a flat SQL-based chart (G/L codes, account types, and posting rules). Dolibarr requires a double-entry accounting structure where each account is a Bank or Cash account linked to a journal. We extract eFacto's account master, map each G/L code to a corresponding Dolibarr account type (accounting account type = Banque, Caisse, or Credit), and configure the accounting journal before any transaction import. Inactive accounts in eFacto are mapped to Dolibarr accounts with statut = 0 (inactive) for the customer's admin to review and reactivate as needed.

eFacto ERP

Customer

maps to

Dolibarr ERP

Third Party (client type)

1:1
Fully supported

eFacto Customer records include billing and shipping addresses, payment terms, GSTIN registration, and credit limits. Dolibarr uses a unified Third Party object where the categorie (customer or supplier) is set per record. We deduplicate by phone and email, map eFacto's GSTIN to a custom Dolibarr field (Options for Third Party) for GSTIN compliance, and set the payment term from eFacto's credit_days into Dolibarr's cond_reglement. Customer addresses migrate to Dolibarr's address block (street, zip, town, country).

eFacto ERP

Vendor

maps to

Dolibarr ERP

Third Party (supplier type)

1:1
Fully supported

eFacto Vendor records mirror Customer structure with additional fields for PAN/TIN registration and banking details for payment processing. We map vendors to Dolibarr Third Parties with categorie = Fournisseur, preserving PAN/TIN in a custom field, bank account details in Dolibarr's Ripro and IBAN fields, and purchase payment terms from eFacto's vendor terms. Outstanding purchase order references are carried forward as open PO links against the Third Party record.

eFacto ERP

Item (Product)

maps to

Dolibarr ERP

Product / Service

1:1
Fully supported

eFacto Items carry SKU, description, unit of measure, cost price, selling price, and per-warehouse stock levels. Dolibarr Product records support the same fields plus batch/lot tracking and multi-price tiers. We map eFacto's unit of measure to Dolibarr's unit_of_measure field, eFacto's cost price to Dolibarr's cost_price, and eFacto's selling price to the primary price on the default price level. Variant data (size, color) from eFacto's BOM and variant schema splits into Dolibarr's Product Combination feature.

eFacto ERP

Item (BOM)

maps to

Dolibarr ERP

Bill of Materials (Dolibarr Manufacturing module)

1:1
Fully supported

eFacto BOM (Bill of Materials) structures for manufactured items map to Dolibarr's Manufacturing module BOM entries. Each BOM header and its component lines (item, quantity, unit, position) transfer as Dolibarr llx_product_bom records. The Manufacturing module must be enabled in Dolibarr before this import runs. Customers without the Manufacturing module can archive BOM definitions as Product notes and enable the module later.

eFacto ERP

Open AR (Customer Invoices)

maps to

Dolibarr ERP

Invoice (client)

1:1
Fully supported

We flag open Accounts Receivable invoices and credit notes as of the migration date. Partial payments are carried forward as Dolibarr payment records linked to the invoice, keeping the outstanding balance accurate rather than resetting to zero. Each invoice migrates with full line-item detail, tax amounts, and the eFacto invoice number preserved as a reference. Closed invoices are archived as paid invoices in Dolibarr and not marked open. The migration-as-of date is configurable and agreed with the customer before import.

eFacto ERP

Open AP (Supplier Invoices)

maps to

Dolibarr ERP

Invoice (supplier)

1:1
Fully supported

Open Accounts Payable supplier invoices migrate to Dolibarr supplier invoices in the same way as AR, with partial payments preserved as payment records against the invoice. Credit notes from eFacto vendors migrate as negative-amount supplier invoices or credit notes in Dolibarr depending on how the vendor recorded them. We flag invoices past due date as overdue in Dolibarr by setting their due date and running a reconciliation pass after import.

eFacto ERP

Sales Order

maps to

Dolibarr ERP

Order (customer)

1:1
Fully supported

Open Sales Orders from eFacto migrate with full line-item detail and are linked to the corresponding Third Party (customer) record via the customer_id lookup. Cancelled or fully fulfilled orders are archived and not imported. Dolibarr Order status (Draft, Validated, Shipped, Closed) is mapped from eFacto's order_status field. If eFacto tracks order reference numbers, we preserve them in Dolibarr's ref_customer field.

eFacto ERP

Purchase Order

maps to

Dolibarr ERP

Order (supplier)

1:1
Fully supported

Open Purchase Orders migrate to Dolibarr supplier orders with vendor details, line items, and quantities, linked to the vendor Third Party record. eFacto's PO reference number maps to Dolibarr's ref_supplier field for cross-system audit trails. Fulfilled or cancelled purchase orders are excluded from import and archived in the eFacto export for reference only.

eFacto ERP

POS Transaction

maps to

Dolibarr ERP

Bank or Cash transaction entries

1:many
Fully supported

eFacto POS receipts are stored in a separate transaction log from the accounting ledger and do not auto-link to G/L entries. We aggregate daily POS totals and create individual Bank or Cash transaction entries in Dolibarr per shift or per cashier, depending on the customer's reconciliation requirements. Each transaction entry references the original eFacto receipt number and tender type. If Dolibarr's POS module is enabled, we evaluate whether to use POS invoices instead of direct bank entries on a case-by-case basis during scoping. We flag the POS-to-bank reconciliation decision for the customer's accountant to confirm before migration runs.

eFacto ERP

Inventory Stock

maps to

Dolibarr ERP

Stock (warehouse)

1:1
Mapping required

Current stock quantities are extracted per warehouse from eFacto's inventory ledger. We map each eFacto warehouse to a corresponding Dolibarr entrepot, set the stock-as-of date, and import current quantities as Dolibarr stock entries (reel quantity per product per entrepot). Historical stock valuation entries are not migrated; Dolibarr recreates the stock value based on the current quantity and the migrated cost_price from the Product record. If batch or lot tracking is active in eFacto, batch numbers and expiry dates migrate as Dolibarr batch entries.

eFacto ERP

Employee

maps to

Dolibarr ERP

User (HR module)

1:1
Fully supported

eFacto Employee master records include designation, department, and salary details. We migrate employee records as Dolibarr Users with the HR module enabled, mapping eFacto's designation to the job title, department to a Dolibarr group, and salary structure notes to the user's personal description. Payroll transaction history is not migrated; it stays in eFacto's HR/payroll records for audit and is recreated in Dolibarr's HR module or a dedicated payroll tool. Employee login credentials must be provisioned manually by the Dolibarr admin before cutover.

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.

eFacto ERP logo

eFacto ERP gotchas

High

No documented public REST API for bulk data export

Medium

POS transaction IDs do not auto-link to G/L entries

Low

Custom SSRS reports depend on hard-coded SQL stored procedures

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

  • eFacto has no public API; SQL export requires vendor coordination

    eFacto ERP does not publish API documentation, endpoint references, or a developer portal. All data extraction must be negotiated with the eFacto administrator to obtain a read-only SQL export against the backend database or a structured report-file export. We work with the customer's eFacto administrator to obtain a database read-only user and export the relevant tables (chart of accounts, customer/vendor master, item master, open invoices, orders, POS log, stock ledger). Customers must confirm SQL access permissions before scoping begins. If SQL access is unavailable, we coordinate a vendor-facilitated export, which can extend the discovery phase by one to two weeks.

  • Dolibarr double-entry accounting requires COA setup before invoice import

    Dolibarr enforces double-entry bookkeeping. Invoices and bank transactions in Dolibarr post to a Chart of Accounts with debit and credit rules applied automatically. eFacto's retail-oriented ledger may use cash-basis accounting or simplified accrual without enforced debit-credit balance. We design the Dolibarr Chart of Accounts (Bank accounts, Cash accounts, Sales accounts, Purchase accounts, VAT accounts) before any transaction import runs. If the customer is using eFacto's GST-compliant accounting, we configure the GST accounts in Dolibarr's accounting module to match the Indian tax structure. Skipping this step means invoices import without G/L postings, which breaks GST reporting in Dolibarr.

  • POS receipts do not auto-link to G/L entries in Dolibarr

    eFacto POS receipts live in a separate transaction log from the accounting ledger. When migrating to Dolibarr, POS receipts cannot be imported as invoices with standard G/L postings without manual reconciliation or a custom POS configuration. We create a mapping table linking each eFacto POS receipt number to a corresponding Dolibarr bank or cash transaction entry, and the customer decides during scoping whether to aggregate daily totals per register or post individual receipts. If the customer relies on POS-to-bank reconciliation for cash management, we recommend enabling Dolibarr's Point of Sale module and configuring it with the same cash drawers before migration.

  • Custom SSRS reports built in eFacto cannot be imported into Dolibarr

    eFacto custom reports are built with SSRS Report Builder on stored procedures that reference eFacto's SQL schema. These RDL definitions cannot run in Dolibarr because Dolibarr uses a different database schema and has no SSRS integration. We export the RDL XML and parameter definitions from eFacto and document the report logic (filters, groupings, calculated fields). The customer's admin rebuilds equivalent reports in Dolibarr's native reporting tool or exports data to a spreadsheet. We do not rebuild reports as part of the migration scope.

  • Dolibarr workflows, automations, and custom PHP modules are out of migration scope

    Dolibarr supports workflows, validation chains, and triggers configurable through the UI, plus custom PHP modules available on Dolistore. These are not migrated as code because Dolibarr's workflow engine and eFacto's rule-based configurations use different data models. Any eFacto custom fields or validation rules that drive automated actions must be reconfigured by the customer's admin in Dolibarr after migration. We deliver a written inventory of all identified custom fields and their Dolibarr equivalent field names and types to support the admin rebuild.

Migration approach

Six steps for a successful eFacto ERP to Dolibarr ERP data migration

  1. Discovery and extraction access

    We audit the eFacto database schema and available SQL exports, working with the customer's eFacto administrator to identify tables for Chart of Accounts, Third Parties, Products, BOMs, invoices, orders, POS transaction log, stock ledger, and employees. We assess which modules the customer uses (retail POS, multi-store, manufacturing, HR) and which are inactive. We confirm SQL read-only access permissions and agree on the extraction format (flat CSV or SQL bulk export). We review Dolibarr's installed modules and determine which need to be enabled (Accounting, Products, Stock, Orders, Invoices, HR, POS) before migration data arrives.

  2. Dolibarr accounting and schema design

    We design Dolibarr's Chart of Accounts structure, mapping each eFacto G/L code to a Dolibarr accounting account (accountingaccount type = Banque, Caisse, or other) and configuring the accounting journal (janvier, achats, ventes, banquecaisse). For Indian GST compliance, we configure GST receivable and payable accounts. We configure Dolibarr warehouses (entrepot) to match eFacto's location codes, set up Third Party categories (customer and supplier), configure product price levels, and enable the required Dolibarr modules. All schema design is validated in a Dolibarr test installation before production migration begins.

  3. SQL extraction and data normalisation

    We run the agreed SQL export queries against the eFacto database (or process vendor-provided report files) to extract all source records. We normalise flat-file exports into the structure required by Dolibarr's REST API import or CSV upload format. This includes splitting combined address fields, normalising date formats to YYYY-MM-DD, mapping eFacto currency codes to Dolibarr multicurrency setup, and deduplicating Third Parties by phone and email. We generate a reconciliation report showing source record counts per object before any data is pushed to Dolibarr.

  4. Dolibarr import and POS reconciliation

    We import data into the production Dolibarr instance in dependency order: accounting accounts first, then Third Parties, then Products, BOMs, stock, orders, invoices, and employees. POS transactions are imported as bank or cash transaction entries with the original eFacto receipt reference preserved. We resolve Third Party IDs for order and invoice links, Product IDs for line items, and User IDs for employee records. After each object import, we emit a row-count reconciliation report against the source extraction.

  5. Validation and reconciliation

    We reconcile opened balances in Dolibarr's accounting module against the source eFacto trial balance as of the migration date. Open AR and AP totals are verified per customer and vendor. Stock quantities are spot-checked against eFacto's current inventory report at a sample of 10-15 SKU-warehouse combinations. POS daily totals from eFacto are verified against the total of imported bank entries. We fix any discrepancies before cutover. We deliver a written report summarising record counts, any records excluded (cancelled orders, inactive items), and any open items requiring post-migration resolution.

  6. Cutover and reporting inventory handoff

    We freeze writes in eFacto at the agreed cutover date and run a final delta import for any records modified between the last extraction and cutover. We enable Dolibarr as the system of record and validate live that new records are being created in the correct chart of accounts. We deliver the SSRS custom report inventory with RDL XML and parameter definitions for the customer's admin to rebuild in Dolibarr. We do not rebuild workflows, automations, or custom PHP modules; those are documented in a separate handoff sheet with Dolibarr equivalent configuration guidance. We provide a one-week post-cutover support window for reconciliation issues raised during the first live week.

Platform deep dives

Context on both ends of the pair

eFacto ERP logo

eFacto ERP

Source

Strengths

  • Unified finance, inventory, sales, purchase, HR, and supply chain in one platform.
  • Supports both cloud SaaS and on-premise deployment with a single subscription model.
  • POS module optimized for high-concurrency retail environments with barcode scanning and multi-store management.
  • Role-based dashboards and integrated Power BI / SSRS reporting provide real-time business visibility.
  • Customizable workflows and fields without coding to adapt to changing business processes.

Weaknesses

  • No publicly documented API endpoint reference, bulk export tool, or developer portal — all data extraction requires vendor coordination or direct SQL access.
  • Pricing not published online; sales-led quoting process introduces uncertainty for budget planning.
  • Smaller market presence and review volume compared to global ERP competitors, making independent due diligence harder.
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?

Moderate ERP migration. 4 of 8 objects need a mapping; the rest are 1:1.

C

Overall complexity

Moderate migration

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

  • Object compatibility

    C

    4 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

    eFacto ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your eFacto ERP 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 five weeks for small to mid-sized businesses with under 15,000 Third Parties, 50,000 inventory records, and straightforward accounting needs. Migrations with multi-store POS data requiring per-register bank reconciliation, active BOM structures in the manufacturing module, open invoice carry-forward across a specific migration date, or large historical stock files split across multiple warehouses move to six to ten weeks because of SQL extraction coordination, Dolibarr double-entry accounting setup, and POS reconciliation design.

Adjacent paths

Related migrations to explore

Ready when you are

Move from eFacto ERP.
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