ERP migration
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
Source
Dolibarr ERP
Destination
Compatibility
9 of 12
objects map 1:1 between ECOUNT ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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)
Dolibarr ERP
Products
1:1ECOUNT 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
Dolibarr ERP
Third Parties (type=Customer)
1:1ECOUNT 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
Dolibarr ERP
Third Parties (type=Supplier)
1:1ECOUNT 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
Dolibarr ERP
Customer Orders, Invoices, or Commercial Proposals
1:manyECOUNT 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
Dolibarr ERP
Supplier Orders and Invoices
1:manyECOUNT 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)
Dolibarr ERP
Bills of Materials (Production module)
1:1ECOUNT 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
Dolibarr ERP
Accounting (Accounting module)
1:1ECOUNT'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
Dolibarr ERP
HRM Module (Employees)
1:1ECOUNT 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
Dolibarr ERP
Banking / Money Operations
1:1ECOUNT 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
Dolibarr ERP
ExtraFields on corresponding objects
lossyECOUNT 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
Dolibarr ERP
Linked Documents via DolibarrAttachments
1:1File 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
Dolibarr ERP
Invoices and Shipping Labels
1:1ECOUNT 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.
| ECOUNT ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Items (Inventory) | Products1:1 | Fully supported | |
| Customers | Third Parties (type=Customer)1:1 | Fully supported | |
| Vendors | Third Parties (type=Supplier)1:1 | Fully supported | |
| Sales Slips | Customer Orders, Invoices, or Commercial Proposals1:many | Fully supported | |
| Purchase Slips | Supplier Orders and Invoices1:many | Fully supported | |
| Bills of Materials (BOM) | Bills of Materials (Production module)1:1 | Mapping required | |
| Chart of Accounts | Accounting (Accounting module)1:1 | Mapping required | |
| Employees / HR Records | HRM Module (Employees)1:1 | Mapping required | |
| Vouchers | Banking / Money Operations1:1 | Fully supported | |
| Custom Input Screens | ExtraFields on corresponding objectslossy | Mapping required | |
| Documents and Attachments | Linked Documents via DolibarrAttachments1:1 | Mapping required | |
| Invoices and Packing Lists | Invoices and Shipping Labels1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Excel is the only documented bulk migration path
Custom input screen fields are not in a published schema
Invoice confirmation email creates recipient confusion
Open API requires active subscription to access docs
Report exports convert print layouts to Excel
Dolibarr ERP gotchas
Foreign key constraint errors on cross-distribution database restore
SQL injection vulnerabilities in version 9.0.1
Custom fields stored as JSON in extraoptions require field-by-field deserialization
Decimal precision and rounding configuration affects price fields
No native iOS/Android app forces reliance on browser
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
ECOUNT ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across ECOUNT ERP and Dolibarr ERP.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
ECOUNT ERP: Not publicly documented.
Data volume sensitivity
ECOUNT ERP doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during ECOUNT ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave ECOUNT ERP
Other ways to arrive at Dolibarr ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.