ERP migration

Migrate from ECOUNT ERP to Dolibarr ERP

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

ECOUNT ERP logo

ECOUNT ERP

Source

Dolibarr ERP

Destination

Dolibarr ERP logo

Compatibility

75%

9 of 12

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

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

ECOUNT ERP and Dolibarr are both ERP platforms, but they differ in architecture, migration path, and pricing model. ECOUNT organizes its data model around Items, Customers, Vendors, Sales/Purchase Slips, Vouchers, BOMs, and Employees, with all modules bundled at $55/month flat. Dolibarr is open-source and modular: the core is free, and businesses add the specific modules they need—Third Parties, Products, Invoicing, Banking, Accounting, HR, Projects—rather than licensing everything upfront. There is no publicly documented REST API for ECOUNT; all migration extraction relies on the Excel upload/download layer, which requires us to reverse-engineer each customer's upload template structure before mapping. Dolibarr accepts CSV imports through its native mass-import module, and we write transformation scripts to convert the ECOUNT Excel exports into Dolibarr-compatible CSV format. We preserve BOM structure, multi-level item dependencies, and historical transactional records, but we do not migrate ECOUNT screen-level custom workflows, approval chains, or formula-driven calculations as code. We deliver a written inventory of these for your admin to configure 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

ECOUNT ERP logo

ECOUNT ERP

What's pushing teams away

  • Invoice email delivery requires the recipient to click a 'Confirm Received Document' link before accessing the attached PDF, causing frequent confusion and requiring manual re-sends.
  • Reporting customization is limited—standard report templates offer few options, and shipped date, customer PO number, and invoice number cannot always appear together on customer A/R statements.
  • Sending invoices individually one at a time rather than batching multiple invoices in a single transmission creates friction for high-volume billing workflows.
  • Customer support quality is inconsistent; some users report slow bug resolution and documentation that does not fully explain complex menu configurations.

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

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

ECOUNT ERP

Items (Inventory)

maps to

Dolibarr ERP

Products

1:1
Fully supported

ECOUNT Items with descriptions, codes, units, cost, price, and stock levels map to Dolibarr Products. We export the Item master via ECOUNT's Excel download, preserving the item type (finished goods, raw material, sub-assembly), stock tracking flags, and reorder points. Multi-BOM items carry BOM links that we resolve during the BOM migration phase. Dolibarr's product type (Product vs Service) is set from the ECOUNT item classification. Custom columns in the customer's upload template are mapped as Dolibarr ExtraFields on the Product object.

ECOUNT ERP

Customers

maps to

Dolibarr ERP

Third Parties (type=Customer)

1:1
Fully supported

ECOUNT Customer master records map to Dolibarr Third Parties with the Category set to Customer. We extract contact details, payment terms, credit limits, outstanding balances, and any custom screen fields. The customer code in ECOUNT becomes the ref (reference) field in Dolibarr. Outstanding balance fields are migrated as read-only reference data since Dolibarr computes balances from open invoices rather than storing a static field.

ECOUNT ERP

Vendors

maps to

Dolibarr ERP

Third Parties (type=Supplier)

1:1
Fully supported

ECOUNT Vendor records follow the same structure as Customers and map to Dolibarr Third Parties with Category set to Supplier. Vendor-specific fields such as lead time and preferred shipping terms migrate to Dolibarr ExtraFields on the Third Party object. The download-and-upload batch process mirrors the Customer migration workflow.

ECOUNT ERP

Sales Slips

maps to

Dolibarr ERP

Customer Orders, Invoices, or Commercial Proposals

1:many
Fully supported

ECOUNT Sales Slips are transactional documents with header and line-item detail. We split them by document status: Draft slips map to Dolibarr Propal (Commercial Proposal); Confirmed slips map to Dolibarr Commandes (Customer Orders); Posted slips with payment status map to Dolibarr Factures (Invoices). Line items resolve to Dolibarr order lines with the Product reference matched from the Item migration. Tax codes map from ECOUNT tax settings to Dolibarr VAT rate configurations. Historical slip dates are preserved as invoice or order dates.

ECOUNT ERP

Purchase Slips

maps to

Dolibarr ERP

Supplier Orders and Invoices

1:many
Fully supported

ECOUNT Purchase Slips map to Dolibarr Fournisseur Commandes (Supplier Orders) and Factures Fournisseur (Supplier Invoices) following the same draft/confirmed/posted split logic as Sales Slips. Incidental cost allocations (freight, duties, insurance) attached to purchase slips are migrated as separate line items with the expense category mapped to a Dolibarr product or expense account. We flag any ECOUNT purchase slip with currency differences for manual review.

ECOUNT ERP

Bills of Materials (BOM)

maps to

Dolibarr ERP

Bills of Materials (Production module)

1:1
Mapping required

ECOUNT BOMs support multiple BOMs per product and include process-level inventory adjustments. We export the BOM structure including sub-material links, quantities, unit-of-measure, and scrap factors. Multi-level BOMs (sub-assemblies with their own BOMs) are resolved recursively before import. Dolibarr's BOM module must be activated; if it is not, we document the BOM structure in a written inventory for your admin to configure. BOM routing (process steps) does not map directly and is included as a configuration note.

ECOUNT ERP

Chart of Accounts

maps to

Dolibarr ERP

Accounting (Accounting module)

1:1
Mapping required

ECOUNT's accounting structure uses accounts, departments, and cost centers with customizable account codes. We map the full chart of accounts including account type (asset, liability, equity, revenue, expense) and department-level restrictions. Dolibarr's Accounting module must be activated to receive these records; if it is not, we deliver the account structure as a written plan for your admin to configure before opening the accounting period. ECOUNT department and cost center hierarchies map to Dolibarr'sanalytical accounting dimensions if the module is enabled.

ECOUNT ERP

Employees / HR Records

maps to

Dolibarr ERP

HRM Module (Employees)

1:1
Mapping required

ECOUNT stores employee data including attendance, compensation, and payroll history. We extract employee records and effective-dated compensation rows as separate imports, preserving historical pay rates and attendance summaries. Dolibarr's HRM module is separate from the core ERP; we map employee records and basic compensation history but do not migrate ECOUNT payroll calculation rules, tax withholdings, or payslip configurations because these are regulated by jurisdiction and require a local payroll implementation specialist. Attendance records migrate as notes or as HRM event entries depending on Dolibarr HRM module version.

ECOUNT ERP

Vouchers

maps to

Dolibarr ERP

Banking / Money Operations

1:1
Fully supported

ECOUNT Vouchers represent financial transactions including cash receipts, journal entries, and bank-related movements. We map them to Dolibarr Bank Account records and associated Bank Transaction lines. ECOUNT voucher types (payment, receipt, adjustment) map to Dolibarr payment types. Bank statement data from ECOUNT's bank statement service migrates as Dolibarr bank statement imports linked to the corresponding bank account.

ECOUNT ERP

Custom Input Screens

maps to

Dolibarr ERP

ExtraFields on corresponding objects

lossy
Mapping required

ECOUNT allows per-company field additions, renames, and formula-driven fields on any input screen. These exist in the screen configuration rather than a standard schema. We request the customer's upload templates during discovery to identify all active columns. Each custom ECOUNT field maps to a Dolibarr ExtraField on the corresponding object (e.g., a custom field on the Item screen becomes an ExtraField on Product). Formula-driven fields are migrated as static values since Dolibarr does not replicate ECOUNT's calculation engine; a configuration note describes the original formula for your admin to re-implement if needed.

ECOUNT ERP

Documents and Attachments

maps to

Dolibarr ERP

Linked Documents via DolibarrAttachments

1:1
Mapping required

File attachments linked to ECOUNT slips and records are extracted by file reference. We download attachments, rename them using a migration naming convention that includes the ECOUNT record ID, and provide them as a file package with a manifest mapping each file to the destination Dolibarr record type and ID. Re-association in Dolibarr is done by your admin post-migration using the manifest as a guide, or via Dolibarr's document management module linking by reference number.

ECOUNT ERP

Invoices and Packing Lists

maps to

Dolibarr ERP

Invoices and Shipping Labels

1:1
Fully supported

ECOUNT export invoices include L/C issuing bank details and shipper information beyond the standard sales slip. We extract the complete invoice history and map invoice headers to Dolibarr Factures. L/C bank details migrate to Dolibarr ExtraFields on the Third Party or the invoice, and shipper information migrates to ExtraFields on the shipping record. Packing lists are documented separately as a written note since Dolibarr handles shipping via its Expedition (shipping) module which may require activation and configuration.

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.

ECOUNT ERP logo

ECOUNT ERP gotchas

High

Excel is the only documented bulk migration path

Medium

Custom input screen fields are not in a published schema

Medium

Invoice confirmation email creates recipient confusion

Low

Open API requires active subscription to access docs

Low

Report exports convert print layouts to Excel

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

  • Excel upload templates vary per ECOUNT customer

    Ecount does not publish a fixed schema for its Excel upload templates. Each customer can add, rename, or remove columns on any input screen, and the upload template reflects the customized screen rather than a canonical field list. During discovery, we request the customer's current upload templates or a screen export to identify every active column. If we receive only the standard template without the customer's modifications, we flag the discrepancy and request the actual template before migration begins. Skipping this step results in missing custom fields on every migrated object.

  • Ecount has no publicly documented REST API

    Ecount advertises an Open API but does not publish endpoint documentation publicly. Full API access and documentation require logging into an active Ecount account. For migrations relying on API-based extraction, we coordinate with the customer during discovery to obtain API credentials and documentation. Without API access, we use the Excel export/download feature as the extraction path, which means report-based exports may include print-layout formatting that requires flattening before mapping. Rate limits and endpoint availability are not publicly documented for Ecount, so extraction relies entirely on the documented Excel batch interface.

  • Dolibarr module activation is required before data import

    Dolibarr ships with a core module and requires specific modules to be activated before corresponding data can be imported. For example, the Third Party module must be active before importing Customers and Vendors; the Product module must be active before importing Items; the BOM module must be active before importing Bills of Materials; the Accounting module must be active before importing the chart of accounts. We provide a module activation checklist as part of our migration scope, and the customer's Dolibarr admin must enable the relevant modules before each import phase begins. If modules are not activated, import validation fails silently or produces errors that require re-import.

  • Report exports from Ecount carry print layout formatting

    Ecount's convert-report-to-Excel feature exports the formatted print layout rather than raw database rows. Merged cells, column widths, and print template headers are included in the export. We clean these exports by detecting merged-cell regions, extracting data rows from the print layout structure, normalizing column positions, and stripping formatting before mapping to Dolibarr's import schema. This adds a data-cleaning step to the migration pipeline that is not required when migrating from systems with a raw-data export mode.

  • Dolibarr accounting module requires jurisdiction-specific setup

    Dolibarr's Accounting module must be configured with a compatible chart of accounts for the customer's jurisdiction before the account migration phase. ECOUNT's chart of accounts uses customizable account codes that may not align with a standard chart such as PCMN (Belgium), PCG (France), or HMRC (UK). We import the ECOUNT account structure and map it to the customer's chosen chart; if no chart is selected, we deliver the imported account structure as a written plan for the admin to configure. Importing into an unconfigured or incorrectly configured accounting module produces validation errors that block the import.

Migration approach

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

  1. Discovery and Ecount template extraction

    We audit the Ecount installation by requesting the customer's active Excel upload templates for Items, Customers, Vendors, Sales Slips, Purchase Slips, BOMs, and the Chart of Accounts. We also request a sample download of each object to understand current field values, any custom screen fields, and the volume of historical records. This allows us to identify all customized columns that are not part of Ecount's standard template and to build a complete field map before any data moves.

  2. Dolibarr module and schema configuration

    We provide a written Dolibarr module activation checklist specifying which modules must be enabled for each migration phase (Third Party, Product, BOM, Invoicing, Accounting, HRM, Banking). We also provide a schema design for ExtraFields on each Dolibarr object, derived from the Ecount custom fields identified in discovery. The customer's Dolibarr admin activates the required modules and creates the ExtraFields before migration phases begin. We validate that modules are active before each import batch.

  3. Data extraction and cleaning

    We download Ecount data via the Excel export and batch download interfaces for each object. We clean the Ecount print-layout-formatted exports by flattening merged cells, extracting data rows, and normalizing column positions. Custom screen fields are identified by comparing the customer's template against Ecount's standard template. The cleaned export data is staged in a migration database with source record IDs preserved for reconciliation. BOM extraction includes recursive resolution of multi-level sub-assemblies.

  4. Transformation and Dolibarr CSV preparation

    We write transformation scripts to convert cleaned Ecount Excel exports into Dolibarr-compatible CSV format for each import phase. Transformation includes: splitting Ecount Customers and Vendors into Dolibarr Third Parties with category assignments; splitting Sales Slips into Dolibarr Proposals, Orders, and Invoices based on status; resolving Product references from the Item migration phase; mapping Ecount account codes to Dolibarr accounting codes; and populating Dolibarr ExtraFields from Ecount custom screen fields. Each phase emits a row-count reconciliation report before import.

  5. Phased import into Dolibarr

    We run imports in dependency order: Third Parties first (Customers and Vendors resolve before any order or invoice); Products next (Items must exist before order lines can reference them); BOMs after Products (sub-assembly references resolved); Invoices and Orders after Third Parties and Products; Accounting chart of accounts after the account schema is configured; Vouchers and Bank transactions after Banking module activation; Employees and HR data last if the HRM module is enabled. Each phase is validated with a reconciliation report comparing source record count to destination record count.

  6. Attachment handling and migration handoff

    We download Ecount file attachments, rename them with a migration manifest including the source record reference, and deliver them as a file package. Re-association in Dolibarr's document management module is documented step-by-step for your admin. We deliver a written inventory of Ecount workflows, approval chains, and formula-driven custom fields that do not migrate as code, with configuration notes for rebuilding each in Dolibarr. We provide a one-week post-migration support window for reconciliation issues. Post-go-live admin support, training, and workflow rebuild are outside standard migration scope.

Platform deep dives

Context on both ends of the pair

ECOUNT ERP logo

ECOUNT ERP

Source

Strengths

  • Flat $55/month with unlimited users and storage across all ERP modules.
  • Built-in Excel upload and download for bulk data entry and extraction without API access.
  • Customizable input screens, invoice templates, and reports to fit specific business processes.
  • ISO 27001 certified with daily multi-server backups and encrypted data transmission.
  • Integrated production management with BOM, MRP, and process-level inventory adjustment.

Weaknesses

  • Public API documentation is gated behind login—programmatic integration requires an active ECOUNT account to access.
  • Invoice delivery requires recipient confirmation before attachment access, creating confusion and extra administrative work.
  • Reporting templates offer limited customization, forcing users to export to Excel for complex statement formats.
  • No bulk invoice send; invoices must be transmitted one at a time from the UI.
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 ECOUNT ERP 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

    ECOUNT ERP: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Migrations under 5,000 Items, 500 Customers and Vendors, and no multi-level BOMs complete in three to five weeks. Migrations with over 20,000 Items, multiple BOM levels, large historical transactional records (Sales Slips, Purchase Slips, Vouchers), and heavily customized Ecount input screens requiring template reverse-engineering take eight to fourteen weeks. Timeline scales with data volume, custom field complexity, and how quickly the Dolibarr admin activates the required modules and configures ExtraFields.

Adjacent paths

Related migrations to explore

Ready when you are

Move from ECOUNT 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