ERP migration

Migrate from Edara to Dolibarr ERP

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

Edara logo

Edara

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

83%

10 of 12

objects map 1:1 between Edara and Dolibarr ERP.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Edara ERP to Dolibarr ERP is a cloud-to-self-hosted transition that removes per-user licensing entirely and eliminates the API access ceiling that blocks programmatic exports for Basic and Pro Edara customers. The migration requires careful extraction planning because Edara's Basic and Pro tiers have no API access, relying instead on CSV export through Edara support or financial reports, and Edara's Pro plan caps monthly sales transactions at 30,000 which can silently truncate large historical exports. On the Dolibarr side, CSV import enforces strict date-format validation that rejects datetime values in favor of pure date strings, requiring a transform step that most self-hosted migration guides overlook. We handle the extraction sequencing, date normalization, currency alignment across open AR/AP documents, multi-warehouse inventory mapping, and fixed asset depreciation schedule reconstruction as part of the standard migration scope. Workflows, automations, POS integrations with external payment processors, and third-party integrations do not migrate; we deliver a written inventory of these for the customer's admin to rebuild in Dolibarr's module ecosystem.

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

Edara logo

Edara

What's pushing teams away

  • Transaction volume caps on the Pro plan (30,000 sales orders/month) force high-volume businesses to upgrade to Ultimate or face overage issues, creating billing surprises.
  • API access is locked behind the Ultimate plan at 100k calls/tenant/month, making it inaccessible for Pro-tier customers who need programmatic data extraction for migration or reporting.
  • Support tiers split email (24x7) and phone (24x5) — businesses needing phone support outside business hours report gaps during weekends and holidays.
  • The base register fee plus per-register charges can make multi-location POS deployments significantly more expensive than initially projected from per-user pricing alone.

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

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

Edara

Chart of Accounts

maps to

Dolibarr ERP

Account (Comptabilité module)

1:1
Fully supported

Edara's Chart of Accounts maps directly to Dolibarr's accounting account table (llx_accounting_account). We export all account codes, names, types (asset, liability, equity, income, expense), and active/inactive status. Dolibarr's accounting module must be activated before import, and the account codes must conform to the configuredaccounting_length system setting. Historical account balances from Edara's trial balance export map to Dolibarr's opening balance entry mechanism. If Edara's chart uses a non-numeric code scheme, we normalize to numeric-compatible codes per Dolibarr's accounting module requirements.

Edara

Customer

maps to

Dolibarr ERP

Third Party (type = Customer)

1:1
Fully supported

Edara Customer records with billing/shipping addresses, contact info, payment terms, and customer currency assignments map to Dolibarr Third Party records (llx_societe) with the Customer flag enabled. Edara's customer code and tax ID map to Dolibarr's code and siret/tva fields. Multiple contacts per customer in Edara map to Dolibarr contact records (llx_socpeople) linked via the fk_soc foreign key. If Edara stores customer-specific price lists, we flag these for manual Dolibarr price list configuration since Dolibarr manages pricing through separate price list modules rather than per-customer defaults.

Edara

Vendor

maps to

Dolibarr ERP

Third Party (type = Supplier)

1:1
Fully supported

Edara Vendor records map to Dolibarr Third Party with the Supplier flag. Vendor addresses, tax IDs, default payment terms, and bank details transfer to the llx_societe record. We check for duplicate vendor names during the import phase and flag any conflicts for the customer's admin to resolve before committing. Edara's vendor-specific purchase price assignments map to Dolibarr's supplier price lists under the Products module.

Edara

Item

maps to

Dolibarr ERP

Product (or Service)

1:1
Fully supported

Edara Item master records including SKU, description, cost, price, unit-of-measure, and warehouse assignments map to Dolibarr Product records. We determine product type (stockable, service, assembly) from Edara's item type classification. Inventory valuation method per item (FIFO, average cost) maps to Dolibarr's stock valuation configuration at the warehouse level. Unit-of-measure conversions from Edara transfer to Dolibarr's uil table. Negative stock entries detected in Edara are flagged for the customer's inventory manager to investigate before inventory levels are committed to Dolibarr.

Edara

Open AR

maps to

Dolibarr ERP

Customer Invoice (draft or open status)

1:1
Fully supported

Edara open receivables with outstanding amounts, due dates, and multi-currency assignments require careful reconciliation during migration. We export Edara's AR aging report and create draft invoices in Dolibarr with the original document number preserved in the ref_client or import_key field. Currency assignments from Edara map to Dolibarr's MultiCurrency module with original and converted amounts stored. If Edara's open AR includes partially paid invoices, we create Dolibarr invoices at the remaining balance and note the original total in a custom field. Any discrepancy between the AR aging report and the general ledger is flagged for the customer's accountant to reconcile before we finalize the import.

Edara

Open AP

maps to

Dolibarr ERP

Supplier Invoice (draft or open status)

1:1
Fully supported

Edara open payables map to Dolibarr supplier invoices (llx_facture_fourn) with vendor assignments and original document numbers preserved. Outstanding amounts and due dates transfer to Dolibarr's invoice fields, and multi-currency AP documents use Dolibarr's MultiCurrency module to store both the original currency amount and the converted amount in the base currency. Prepaid supplier invoices in Edara map to Dolibarr's prepayment mechanism under the supplier invoice module. Any AP aging discrepancies relative to the trial balance are flagged for manual reconciliation.

Edara

Sales Order

maps to

Dolibarr ERP

Customer Order

1:1
Fully supported

Edara Sales Orders (open and closed) migrate to Dolibarr Customer Orders (llx_commande). Line items, quantities, unit prices, and discount percentages transfer directly. Sales order status (Draft, Confirmed, Shipped, Completed, Cancelled) maps to Dolibarr statuts with the closest equivalent. If Edara stores sales order approvals, we preserve the approval status in a custom field since Dolibarr's standard workflow does not include approval gates on customer orders without the Workflow module. Edara Pro plan customers with over 30,000 historical orders require batched extraction aligned to monthly billing cycles; we coordinate this during discovery.

Edara

Purchase Order

maps to

Dolibarr ERP

Supplier Order

1:1
Fully supported

Edara Purchase Orders map to Dolibarr Supplier Orders (llx_commande_fournisseur). Vendor assignments, line items, quantities, and prices transfer as-is. PO approval status from Edara maps to a custom field in Dolibarr since standard supplier orders do not enforce approval workflows. Linked receipt records from Edara (goods received against a PO) map to Dolibarr's supplier order receipt mechanism. If Edara stores multi-currency purchase orders, we activate Dolibarr's MultiCurrency module before this import phase.

Edara

Warehouse / Inventory

maps to

Dolibarr ERP

Warehouse (llx_entrepot) + Stock

1:1
Fully supported

Edara warehouse records, stock levels, and bin locations map to Dolibarr warehouses and stock entries. Each Edara warehouse becomes a Dolibarr warehouse (llx_entrepot) with the description and address preserved. Current stock quantities per item per warehouse transfer to Dolibarr's stock movement table (llx_product_stock). Multi-warehouse setups in Edara map to multiple Dolibarr warehouses; if Edara uses bin locations, we note them in the warehouse description field and flag for the customer's warehouse manager to configure Dolibarr's location tracking module if needed. Negative stock entries in Edara are flagged for reconciliation before stock levels are committed.

Edara

Fixed Asset

maps to

Dolibarr ERP

Asset (llx_asset)

1:1
Fully supported

Edara Fixed Asset records including acquisition cost, accumulated depreciation, depreciation method (straight-line, declining balance), and residual value map to Dolibarr's Asset module (requires activation). Only fully accessible on Edara Ultimate plan; Basic and Pro customers have limited visibility into fixed asset records. We export the depreciation schedule from Edara's financial reports and reconcile against the general ledger trial balance. Any discrepancy between the asset register and the general ledger is flagged for the customer's accountant to resolve before committing the asset ledger. Dolibarr's Asset module supports depreciation computation, but the customer must configure the accounting chart of accounts to accept asset-related journal entries.

Edara

POS Register

maps to

Dolibarr ERP

POS Configuration (point of sale module)

lossy
Fully supported

Edara POS register definitions including base register fee, additional register assignments, and salesperson attributions do not have a direct Dolibarr equivalent in terms of billing association, but the POS functionality itself migrates. We export register configurations and salesperson assignments from Edara and recreate them in Dolibarr's Point of Sale module. Each Edara register becomes a Dolibarr cash control or point of sale terminal configuration. Salesperson attribution migrates as Dolibarr User records with the appropriate POS permissions. Note that Edara's per-register billing model does not apply in Dolibarr; POS usage has no incremental per-terminal charge on the self-hosted model.

Edara

Multiple Currencies

maps to

Dolibarr ERP

MultiCurrency module

lossy
Fully supported

Edara multi-currency transactions with exchange rate history map to Dolibarr's MultiCurrency module if the customer requires currency preservation. We export exchange rate history alongside transactional data (open AR/AP, orders) and configure Dolibarr's currency rates to match. Open AR/AP documents originally created in a foreign currency retain both the original amount and the converted base currency amount. If Edara's multi-currency support is used on Pro or Ultimate, we activate Dolibarr's MultiCurrency module before the corresponding import phases. Currency alignment between Edara and Dolibarr requires a scoping decision: the customer chooses whether to migrate with original currency amounts preserved or converted to a single base currency.

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.

Edara logo

Edara gotchas

High

API access is Ultimate-plan exclusive with a 100k call ceiling

High

Pro plan monthly transaction cap can interrupt large historical exports

Medium

Fixed asset depreciation schedules require Ultimate-plan access to export fully

Medium

Multi-register POS setup adds per-register costs not visible in per-user pricing

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

  • Edara Basic and Pro have no API access

    Edara's API at 100k calls/tenant/month is exclusively available on the Ultimate plan. Basic and Pro customers have no programmatic export path through any documented API endpoint. We handle this by coordinating CSV exports through Edara's support-facing data export mechanism, which requires the customer's Edara credentials and may involve manual steps with Edara support. The absence of API access also means we cannot run automated delta exports between the initial extraction and cutover; any records modified during the migration window must be re-exported manually. We detect the customer's Edara plan tier during discovery and budget additional scoping time for CSV export coordination on non-Ultimate plans.

  • Edara Pro plan 30,000 transaction monthly cap truncates large exports silently

    The Edara Pro plan hard-caps sales transactions at 30,000 per month. If the customer's historical data exceeds this count, the export truncates silently without a warning message in most export interfaces. We detect the transaction volume during discovery by querying Edara's transaction counts before scheduling extraction. For customers exceeding the cap, we stage the migration in monthly batches aligned with the billing cycle, or we recommend upgrading to Ultimate for the duration of the migration export window. Without this detection step, a Pro-plan customer could complete migration with tens of thousands of closed sales orders missing from the historical record.

  • Dolibarr CSV import rejects datetime values with a strict regex

    Dolibarr's native CSV import enforces a strict date-format regex: ^[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]$ (YYYY-MM-DD only). Any date field containing a datetime value like 2015-01-01 12:30:00 will reject the entire row with an Incorrect value for field error. This is a known Dolibarr bug (GitHub issue #24700) that persists across versions. We handle this by running a pre-import transform that strips time components from all date fields in the Edara export before loading into Dolibarr. If the customer needs time-component preservation for any field, we store it as a separate custom field in Dolibarr rather than in the standard date column.

  • Edara fixed asset records require Ultimate plan and reconciliation

    Fixed asset management in Edara is an Ultimate-tier feature. Asset records including acquisition cost, accumulated depreciation, depreciation method, and useful life are not fully visible on Basic or Pro plans. We export what is accessible via standard financial reports (depreciation schedule, asset register) and reconcile against the trial balance. Any discrepancy between the asset register and the general ledger is flagged for the customer's accountant to resolve before committing to Dolibarr's Asset module. If the customer is on Basic or Pro and needs full fixed asset history, they must either request the data from Edara support or upgrade to Ultimate for the export duration. Dolibarr's Asset module must be activated and configured with the correct accounting chart-of-accounts mapping before assets are imported.

  • Dolibarr native import struggles with cross-version database dumps

    Direct database dump imports between different Dolibarr versions frequently fail due to schema differences in the llx_ tables and foreign key constraint incompatibilities. The most common errors are errno 150 (foreign key constraint incorrectly formed) and errno 1071 (index key length exceeds 767 bytes on certain MariaDB/MySQL configurations). The Dolibarr community workaround is to use the Dolibarr repair.php script (/install/repair.php) after import, but the safest approach is a version-matched migration where source and destination Dolibarr installations use the same major version. Since we are migrating from Edara (not Dolibarr) to Dolibarr, we avoid database dump imports entirely and use Dolibarr's native CSV import wizard and REST API, which are version-agnostic and avoid the constraint error class entirely.

Migration approach

Six steps for a successful Edara to Dolibarr ERP data migration

  1. Discovery and Edara plan assessment

    We audit the source Edara instance across plan tier (Basic/Pro/Ultimate), active modules, transaction volumes, and custom fields. We run a transaction count query to detect whether the Pro plan 30,000/month cap applies. We identify whether the customer has API access (Ultimate only) or requires CSV export coordination. We document the full chart of accounts structure, open AR/AP aging amounts, warehouse and item counts, fixed asset presence, POS register count, and multi-currency usage. The discovery output is a written migration scope with a Edara export plan and a Dolibarr module activation checklist.

  2. Edara data extraction

    For Ultimate-plan customers, we extract data using Edara's API with batched requests and careful quota monitoring against the 100k calls/month ceiling. For Basic and Pro customers, we coordinate CSV exports through Edara's support-facing export mechanism. We extract in dependency order: chart of accounts first, then customer and vendor masters, then items, then open AR/AP aging reports, then historical orders (staged in monthly batches if Pro-plan cap applies), then warehouse inventory, then fixed assets, then POS configurations. Each extract is checksummed against Edara's internal reports for completeness before we proceed to transform.

  3. Dolibarr target preparation

    We set up the target Dolibarr instance on the customer's chosen hosting environment (self-hosted VPS, DoliCloud, or a cloud clusters managed instance). We activate only the modules present in the Edara source: Accounting, Third Parties, Products, Commercial (orders and proposals), Stock, Assets, and Point of Sale. We configure Dolibarr's accounting code length to match the Edara chart of accounts structure. We set the base currency and, if applicable, configure the MultiCurrency module with exchange rates from the Edara export. We configure warehouse locations matching the Edara warehouse structure.

  4. Data transformation and date normalization

    We transform Edara's export files into Dolibarr CSV import format, handling field renaming, type conversion, and value mapping at this stage. Critically, we strip time components from all datetime fields to satisfy Dolibarr's strict date regex before any import attempt. We split multi-contact customer records into parent Third Party and linked Contact records. We map Edara's account codes to Dolibarr's accounting account codes with any necessary normalization. We prepare lookup tables for foreign key resolution (customer IDs in orders, vendor IDs in purchase orders, product IDs in line items) so that Dolibarr's referential integrity is satisfied at import time.

  5. Staged import and reconciliation

    We import data into Dolibarr in strict dependency order: accounts first (accounting module), then third parties (customers and vendors), then products, then stock levels, then purchase orders, then sales orders, then open AR/AP invoices, then fixed assets, then POS configurations. After each phase we emit a row-count reconciliation report comparing the Edara source count against the Dolibarr destination count and investigate any discrepancy before proceeding. For Edara Pro customers with large historical order sets, the import is staged across multiple sessions aligned with the extraction batches.

  6. Cutover and post-migration handoff

    We freeze Edara write access during the cutover window and run a final delta export for any records modified during the migration. We commit the final import batch and run a full reconciliation pass. We activate Dolibarr's native accounting module configuration, verify the chart of accounts linkage, and confirm that the trial balance in Dolibarr matches the final Edara trial balance within any agreed tolerance. We deliver a written inventory of Edara workflows, automations, POS integrations with external payment processors, and third-party integrations (Slack, Google Calendar, Google Sheets) that do not migrate. We support a one-week hypercare window for reconciliation issues. We do not rebuild Edara automations or POS 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

Edara logo

Edara

Source

Strengths

  • Single cloud platform covering accounting, warehouse, sales, purchases, and POS with a unified data model.
  • Microsoft Azure-hosted with a published recommendation from Microsoft Azure's official channel.
  • Bilingual Arabic/English UI built-in without third-party localization plugins.
  • Tiered pricing starting at $5/user/month with a base fee structure that is transparent and predictable.
  • Manufacturing MTO (Make-to-Order) and fixed asset lifecycle management available on Ultimate.

Weaknesses

  • API access gated to Ultimate plan only at 100k calls/tenant/month, blocking programmatic exports for Pro and Basic customers.
  • Pro plan transaction cap of 30,000 sales orders/month is a hard limit that can block high-volume retailers.
  • No documented public API reference or developer portal for Basic and Pro tiers — integration requires purchasing Ultimate.
  • Fixed asset management and BI reports (market basket, cohort analysis) require the highest paid tier, increasing cost for businesses that only need one of those features.
  • No public migration tooling, partner network, or documented data export procedures — customers must work directly with Edara support for data extraction.
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 Edara and Dolibarr ERP.

B

Overall complexity

Standard migration

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

  • Object compatibility

    A

    All 8 core objects map 1:1 between Edara 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

    Edara: 100,000 API calls per tenant per month on Ultimate plan; no documented per-minute or per-request limits found in public documentation.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Edara to Dolibarr ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Standard migrations covering chart of accounts, customers, vendors, items, orders, and open AR/AP land between three and five weeks and complete in four to six weeks. Migrations with fixed asset depreciation schedules, multi-warehouse inventory mapping, POS register assignments, or large historical transaction sets requiring batched Pro-plan extraction move to eight to twelve weeks. The Pro-plan transaction cap detection and batched extraction on non-Ultimate Edara plans adds one to three weeks to the extraction phase compared to a direct API extraction on Ultimate.

Adjacent paths

Related migrations to explore

Ready when you are

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