ERP migration

Migrate from EQUAL to Dolibarr ERP

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

EQUAL logo

EQUAL

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

83%

10 of 12

objects map 1:1 between EQUAL and Dolibarr ERP.

Complexity

CModerate

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from EQUAL to Dolibarr is a migration from a cloud-native spend management platform to a self-hosted open-source ERP. EQUAL tracks bank accounts, virtual cards, and multi-currency transactions with live SQL query access. Dolibarr provides a modular ERP and CRM stack with llx_bank for bank accounts, llx_bank_account for bank account records, llx_facture for invoices, and llx_societe for third parties. We map EQUAL's Accounts to Dolibarr llx_bank, Transactions to llx_bank_line, Cards to llx_bank_account entries with card metadata stored in a custom field set, and multi-currency amounts with their original exchange rates preserved. Dolibarr's community-supported 3.7/5 support rating means post-migration admin tasks require self-service or paid support contracts. We do not migrate SQL query configurations, custom reporting dashboards, or API access tokens; these require rebuild in Dolibarr's module framework.

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

EQUAL logo

EQUAL

What's pushing teams away

  • No free trial is offered, which makes self-serve evaluation impossible — buyers must commit to a paid engagement before testing core functionality.
  • Limited independent review footprint on Capterra and other public sites makes it difficult to validate the vendor's claims against real customer experience.
  • $3,000 one-time fee is a Basic-plan entry point; higher tiers and customizations are not publicly priced, complicating budgeting.
  • No public API documentation or developer portal was located in research, leaving integration and migration paths reliant on vendor-mediated support.
  • Regional vendor presence (Abu Dhabi / India focus) limits support coverage and ecosystem depth versus global ERPs like NetSuite, SAP Business One, or Odoo.

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

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

EQUAL

Account

maps to

Dolibarr ERP

llx_bank

1:1
Fully supported

EQUAL bank account records map to Dolibarr llx_bank entries representing the bank itself. The account name from EQUAL becomes the label (label) field, and the currency code maps to Dolibarr's currency module configuration. Bank account numbers from EQUAL store in a custom field cf_bank_account_number on llx_bank. Multi-currency accounts use Dolibarr's multi-entity or multi-currency configuration which must be enabled in Dolibarr Setup before migration.

EQUAL

Transaction

maps to

Dolibarr ERP

llx_bank_line

1:1
Fully supported

EQUAL transaction records map to Dolibarr llx_bank_line (bank line entries). The debit or credit amount maps to debot and credit fields respectively. The original currency amount from EQUAL's multi-currency transactions stores in a custom field cf_original_amount with the exchange rate in cf_exchange_rate, preserving the original ledger value for audit. The transaction date becomes the dateo (operation date) and datev (value date) fields.

EQUAL

Card

maps to

Dolibarr ERP

llx_bank_account + Custom Fields

1:1
Fully supported

EQUAL virtual card and expense card records map to llx_bank_account entries with card metadata (card type, BIN range, spending limits, status) stored in custom fields on the bank account. The parent llx_bank reference links the card to the issuing bank account. Card assignment (which user or cost center the card is assigned to) maps to the fk_user (user assignment) or a custom fk_expense_category field depending on the customer's cost-center structure.

EQUAL

Currency Balance

maps to

Dolibarr ERP

llx_bank_currency

lossy
Fully supported

EQUAL multi-currency ledger balances map to Dolibarr llx_bank_currency records linked to the parent llx_bank account. We preserve the original currency code, balance amount in that currency, and the exchange rate to the base currency as of the migration snapshot date. Dolibarr's currency module must be activated and configured with exchange rate feeds before this object migrates.

EQUAL

Expense Category

maps to

Dolibarr ERP

llx_categorie

1:1
Fully supported

EQUAL expense category tags map to Dolibarr llx_categorie entries with type=3 (products/categories). We preserve the category hierarchy if EQUAL supports parent-child tags, mapping it to Dolibarr's fk_parent nested structure. Tags that do not have a direct equivalent in Dolibarr's category system store as custom fields cf_expense_tag on the llx_bank_line record for granular expense reporting.

EQUAL

Merchant Metadata

maps to

Dolibarr ERP

Custom Fields on llx_bank_line

lossy
Fully supported

EQUAL merchant metadata (MCC code, merchant name, merchant category) attaches to llx_bank_line records via a custom field group. Dolibarr's native transaction view does not include merchant metadata fields by default, so we create cf_mcc_code, cf_merchant_name, and cf_merchant_category custom fields on the bank line table. This preserves the full merchant context for expense categorization and policy compliance.

EQUAL

Third Party (counterparties)

maps to

Dolibarr ERP

llx_societe

1:1
Fully supported

EQUAL transaction counterparties (vendors, suppliers, income sources) map to Dolibarr llx_societe (third-party) records. The company name maps to the nom field, and the counterparty's country and VAT number map to country and tva_intra if present. Customer versus supplier classification uses llx_societe.client (1=customer, 2=supplier, 3=both) which we populate from EQUAL's party type.

EQUAL

Contact

maps to

Dolibarr ERP

llx_socpeople

1:1
Fully supported

EQUAL contact records associated with accounts map to Dolibarr llx_socpeople linked via fk_soc to the corresponding llx_societe record. Email, phone, and address fields migrate directly. The contact's role (billing, technical, primary) maps to the fk_socpeople_role or a custom field cf_contact_role if role-based contact segmentation exists in the source.

EQUAL

Invoice

maps to

Dolibarr ERP

llx_facture

1:1
Fully supported

EQUAL invoice records (if exported from a connected accounting layer) map to Dolibarr llx_facture. The invoice number becomes ref, the total maps to total_ttc, and tax amounts map to total_tva. Status (paid, unpaid, cancelled) maps to Dolibarr's fk_statut field. Multi-currency invoice amounts store in a custom field cf_original_amount with the applicable exchange rate.

EQUAL

Product

maps to

Dolibarr ERP

llx_product

1:1
Fully supported

EQUAL products or SKUs referenced in expense transactions map to Dolibarr llx_product if the destination uses inventory or project management modules. The product reference becomes ref, description maps to description, and price maps to price. If the customer does not activate the product module, these records are flagged as optional scope during discovery.

EQUAL

User

maps to

Dolibarr ERP

llx_user

1:1
Fully supported

EQUAL user records who own cards or are assigned to transactions map to Dolibarr llx_user. We resolve by email match. Active versus inactive status maps from EQUAL's user status. Admin flag maps to admin=1 in Dolibarr. Users without an email match go to a reconciliation queue for manual provisioning before card assignment records migrate.

EQUAL

Timestamp History

maps to

Dolibarr ERP

date_creation, tms on target tables

1:1
Fully supported

EQUAL's historical transaction timestamps migrate to Dolibarr's datec (creation date) and tms (modification timestamp) fields on llx_bank_line. We preserve the original ledger timestamp rather than overwriting with migration run time, maintaining audit continuity. For transactions with no timestamp in EQUAL, we use a default migration-date value and flag the record in the reconciliation report.

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.

EQUAL logo

EQUAL gotchas

High

No documented public API for self-service extraction

Medium

Regional tax and compliance baked into modules

Medium

One-time licensing model complicates cutover budgeting

Low

Limited independent review data complicates customer-side validation

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

  • Dolibarr multi-currency requires pre-activation and manual rate feeds

    Dolibarr ships with single-currency mode enabled by default. Multi-currency support requires activating the Currency module in Dolibarr Setup and entering exchange rates manually, via a third-party module, or through a custom API integration. EQUAL stores multi-currency transactions with live exchange-rate context. If Dolibarr's currency module is not configured before migration, multi-currency amounts migrate as raw numbers without rate traceability, breaking currency reconciliation for auditors. We activate the module and configure a baseline rate feed during the schema design phase, and we store original currency amounts in custom fields regardless to preserve audit data.

  • Dolibarr support is community-only unless you purchase a support contract

    Dolibarr scores 3.7/5 for support on Software Advice across 105 verified reviews. One Reddit user who ran Dolibarr for approximately a year reported solving zero technical issues independently. Migrating to Dolibarr means accepting that post-migration issues require community forum posts, paid MarketPlace support contracts, or internal technical resources. EQUAL as a SaaS platform offers vendor-backed support. We document the support contract options available from Dolibarr MarketPlace during migration scoping so the customer can decide whether to purchase coverage before go-live.

  • Card metadata is not a native Dolibarr object and requires custom fields

    EQUAL tracks virtual card and expense card records with rich metadata (card type, BIN, spending limit, assignment, status). Dolibarr has no native card management object; cards must be modeled as llx_bank_account entries with custom fields for card-specific attributes. Custom field creation requires access to Dolibarr's CustomFields module or direct database schema work. We define the custom field schema during discovery, deploy it before migration, and document the fields so the customer's admin can maintain them post-migration. If the CustomFields module is not installed, we use a custom PHP import script that writes directly to the llx_bank_account table.

  • Self-hosted deployment requires PHP version and module compatibility

    Dolibarr requires a specific PHP version (7.4 to 8.2 depending on Dolibarr version) and MySQL/MariaDB with specific character set configuration (utf8mb4). GitHub Issue #16315 documents a database key length error (DB_ERROR_1071: max key length 767 bytes) that occurs when upgrading Dolibarr across certain MariaDB versions. We verify the target server's PHP version and database configuration during discovery. If the hosting environment uses an incompatible PHP version or MariaDB release, we document the required changes and the customer's sysadmin or hosting provider applies them before migration begins.

Migration approach

Six steps for a successful EQUAL to Dolibarr ERP data migration

  1. Discovery and hosting readiness

    We audit the EQUAL portal for account count, transaction volume, multi-currency currency codes used, card records, expense category tags, and merchant metadata fields. We simultaneously assess the target Dolibarr hosting environment: PHP version, MariaDB/MySQL version, Dolibarr version planned, and whether the CustomFields module is installed. We deliver a written scope document that lists every EQUAL object, its record count, and the target Dolibarr table and custom field plan. If multi-currency is in scope, we confirm that Dolibarr's currency module is activated and exchange rate feeds are configured.

  2. Schema design and custom field deployment

    We design the Dolibarr target schema: llx_bank entries from EQUAL accounts, llx_bank_line structure for transactions, llx_societe for counterparties, llx_bank_account for cards with custom fields (cf_card_type, cf_bin_range, cf_spending_limit, cf_merchant_name, cf_mcc_code, cf_original_amount, cf_exchange_rate). Custom fields deploy via Dolibarr's CustomFields module or via a PHP migration script that writes directly to the database. We validate the schema in a staging Dolibarr instance before production migration to catch any foreign key constraint violations.

  3. Currency and third-party normalization

    We normalize currency codes from EQUAL against Dolibarr's currency table (llx_c_currencies) and create any missing currency records. We deduplicate counterparty names from EQUAL's transaction feed, merge identical counterparties, and create llx_societe records in bulk. Any counterparty that requires manual review (name ambiguity, missing VAT number) goes to a reconciliation queue for the customer's admin to resolve before the final import.

  4. Staging migration and reconciliation

    We run a full migration into a staging Dolibarr instance using production-like data volume. The customer's finance lead reconciles transaction totals per currency, card count per assignee, and expense category distribution. We compare the EQUAL ledger balance at migration date against the Dolibarr llx_bank_line sum and flag any discrepancy above 0.01 units. The customer signs off on the staging reconciliation before production migration is scheduled.

  5. Production migration in dependency order

    We run production migration in record-dependency order: currencies first, then llx_bank (accounts), llx_societe (counterparties), llx_bank_line (transactions), llx_bank_account (cards), llx_socpeople (contacts), and finally llx_facture (invoices) if applicable. Each phase emits a row-count report. We preserve original transaction timestamps in datec and tms fields. Multi-currency amounts store in custom fields alongside the converted base-currency amounts.

  6. Cutover, validation, and admin handoff

    We freeze EQUAL write access during cutover, run a final delta migration of any transactions created after the snapshot, and deliver a reconciliation summary comparing EQUAL's final ledger total against Dolibarr's llx_bank_line sum. We provide a written document listing the CustomFields created, the custom report SQL templates (if applicable), and the recommended next steps for activating Dolibarr's report module. We offer a one-week hypercare window for reconciliation issues. We do not rebuild EQUAL's SQL query configurations, custom reporting dashboards, or API access tokens in Dolibarr; these require rebuild in Dolibarr's PHP-based module framework and sit outside the migration scope.

Platform deep dives

Context on both ends of the pair

EQUAL logo

EQUAL

Source

Strengths

  • Single integrated suite spanning finance, property, inventory, HR, BI, and project modules.
  • Web, Android, and iOS deployment for multi-device access.
  • One-time licensing model for buyers preferring capex over subscription.
  • 24/7 multi-channel support plus training resources.
  • Targets freelancers through enterprises with a single platform.

Weaknesses

  • No public API or developer portal documented in research.
  • No free trial; paid engagement required to evaluate.
  • Limited independent review footprint.
  • Public pricing covers only the Basic tier ($3,000 one-time) with higher tiers undisclosed.
  • Regional vendor presence concentrated in MEA and India versus global ERP competitors.
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. 8 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 EQUAL and Dolibarr ERP.

  • Object compatibility

    D

    8 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

    EQUAL: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your EQUAL 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 accounts under 10,000 transactions and 500 bank accounts with no multi-currency complexity. Migrations with large transaction histories (over 100,000 rows), multiple currency pairs requiring exchange-rate preservation, or custom card-assignment schemas move to eight to twelve weeks because of staging reconciliation time and custom field schema validation.

Adjacent paths

Related migrations to explore

Ready when you are

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