ERP migration
Field-level mapping, validation, and rollback between e-Emphasys ERP and Dolibarr ERP. We move data and schema; workflows are rebuilt natively in Dolibarr ERP.
e-Emphasys ERP
Source
Dolibarr ERP
Destination
Compatibility
9 of 14
objects map 1:1 between e-Emphasys ERP and Dolibarr ERP.
Complexity
BStandard
Timeline
4-6 weeks
Overview
Migrating from e-Emphasys ERP to Dolibarr is a structural migration, not a record copy, because e-Emphasys has no publicly documented API. All data extraction relies on direct SQL Server or Oracle database access, or CSV exports from the built-in reporting module. We negotiate read-only database credentials during discovery, reverse-engineer the source table schemas, and transform the data into Dolibarr-compatible CSV files organized by object type. e-Emphasys carries a dealer-specific data model built for heavy equipment, serialized parts, OEM warranty claims, and branch-level inventory that does not map directly to Dolibarr's general-business third-party import schema. We resolve equipment serialization, rental contract rate structures, technician labor records tied to work orders, and multi-location branch assignments as part of the migration transform. Dolibarr does not natively support dealer-specific OEM warranty claim workflows or multi-tier rental billing, so we flag these records for manual verification post-import. Workflows, automations, and custom reports do not migrate as code; we deliver a written inventory of every active workflow and report requiring rebuild in Dolibarr's module framework.
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 e-Emphasys 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.
e-Emphasys ERP
Customer/Account
Dolibarr ERP
ThirdParty (llx_societe)
1:1e-Emphasys customer records with full contact details, billing addresses, and branch assignments map to Dolibarr ThirdParty (stored in llx_societe). The is_customer flag maps to client=1 and is_prospect=1 for pre-conversion records. Billing and shipping addresses map to llx_societe_address with fk_soc resolved. Branch-level assignments in e-Emphasys (branch_id) map to Dolibarr's tags or a custom fk_entrepot field if the customer has configured warehouse-level assignments.
e-Emphasys ERP
Whole Goods (Equipment Inventory)
Dolibarr ERP
Product (llx_product) with custom fields
1:1e-Emphasys serialized equipment records (OEM codes, VIN-equivalent identifiers, branch assignment, status) map to Dolibarr Product records with type=1 (stockable) and a custom serial_number field. The equipment status (new, used, rental, consignment) maps to a Dolibarr custom field or product status workflow. We preserve OEM warranty codes as product properties and link serialized units to the customer ThirdParty via a custom fk_equipment_customer field for audit.
e-Emphasys ERP
Parts Inventory (Serialized)
Dolibarr ERP
Product (llx_product) + Stock Movement (llx_product_batch)
1:1e-Emphasys serialized parts with bin locations, vendor links, cost/price tiers, and OEM cost tiers map to Dolibarr Product with type=1. Serialized tracking (lot/serial numbers) maps to Dolibarr's batch/stock management module if enabled; otherwise we store serial numbers in a custom field. Bin location maps to fk_entrepot and we generate llx_product_stock entries per warehouse. We preserve stock levels and reorder points from e-Emphasys into Dolibarr's pmp (weighted average price) and seuil_stock_alerte fields.
e-Emphasys ERP
Parts Inventory (Non-Serialized)
Dolibarr ERP
Product (llx_product)
1:1Non-serialized parts export from e-Emphasys with vendor links, cost tiers, and pricing tiers. These map to Dolibarr Product records with type=1 (stockable), barcode from e-Emphasys part_number, and price tiers mapped to Dolibarr's price list architecture (llx_product_price per customer price list or tier). Reorder points migrate to seuil_stock_alerte.
e-Emphasys ERP
Work Orders
Dolibarr ERP
Intervention (llx_fichinter) or Project (llx_projet) with Task (llx_projet_task)
lossye-Emphasys service work orders tied to equipment, technicians, and line items map to Dolibarr Interventions (if the Interventions module is enabled) or to Projects with Tasks. The equipment serial number becomes a link to the Product record via a custom field. Technician labor records map to Tasks with time spent in minutes and assigned to the User record matched by email. Parts used on the work order map to llx_fichinterdet line items. Warranty claim associations migrate as notes or custom fields if no native warranty module is active.
e-Emphasys ERP
Rental Contracts
Dolibarr ERP
Contrat (llx_contrat) with custom rate structure
lossye-Emphasys rental contracts with daily/weekly/monthly billing tiers, equipment swaps, and early return conditions map to Dolibarr Contracts (llx_contrat). We extract rate schedules into an intermediate schema and flag any multi-tier billing configurations that exceed Dolibarr's flat-rate contract model. Equipment assignments map to the contract's linked Product records. Early return conditions and swap terms are documented in the contract note field for manual verification before go-live.
e-Emphasys ERP
Sales Orders / Quotes
Dolibarr ERP
CommandeClient (llx_commande) or Proposal (llx_propal)
1:1e-Emphasys whole goods sales orders and quotes linked to customer and equipment records map to Dolibarr Proposals (llx_propal) for pre-approval records and Commandes (llx_commande) for confirmed orders. Pricing tiers and OEM incentives migrate to llx_propaldet or llx_commandedet with the linked Product record resolved. Order status from e-Emphasys (quote, pending, confirmed, shipped, invoiced) maps to Dolibarr's statut andbilled fields.
e-Emphasys ERP
General Ledger / Journal Entries
Dolibarr ERP
Accounting (llx_accounting_bookkeeping) or accounting module records
1:1e-Emphasys GL accounts, journal entries, and account balances export from the financial module preserving chart of accounts structure and period associations. Dolibarr's accounting module (when enabled) uses llx_accounting_account for the chart of accounts and llx_accounting_bookkeeping for transactions. We map e-Emphasys account codes to Dolibarr account numbers and preserve debit/credit amounts with the original transaction dates. Period and fiscal year associations are retained in the bookkeeping records.
e-Emphasys ERP
Accounts Payable
Dolibarr ERP
Supplier Invoice (llx_facture_fourn) and Purchase Order (llx_commande_fournisseur)
1:1e-Emphasys vendor invoices and payment records export with full vendor linkage and PO-to-invoice associations where they exist. These map to Dolibarr Supplier Invoices (llx_facture_fourn) and Purchase Orders (llx_commande_fournisseur). Vendor ThirdParty records are created or matched by vendor code and email during import. Payment records map to llx_paiement_fourn and link to the invoice via fk_paiement.
e-Emphasys ERP
Accounts Receivable
Dolibarr ERP
Customer Invoice (llx_facture) and Payment (llx_paiement)
1:1e-Emphasys customer invoices, payments, and AR aging data export with customer linkage and open balance status. These map to Dolibarr Customer Invoices (llx_facture) with client=1 and payments map to llx_paiement linked to the invoice via fk_paiement. Open invoice balances and payment history are preserved with the ThirdParty link. Aging data is not natively stored in Dolibarr but can be generated post-import from invoice due dates.
e-Emphasys ERP
Technicians / Employees
Dolibarr ERP
User (llx_user) with project/task assignments
1:1e-Emphasys employee records with labor rates, certifications, and branch assignments map to Dolibarr User records. We match technicians by email and map branch assignments to Dolibarr tags or warehouse (fk_entrepot) assignments. Labor rate categories migrate to a custom field rate_per_hour__c on the User record. Certifications and OEM training records are stored in the user's note field or a custom certifications__c field for manual verification.
e-Emphasys ERP
Warranty Records
Dolibarr ERP
Custom fields or Note on Product / ThirdParty
lossye-Emphasys warranty records tied to serialized equipment and OEM claims preserve claim history and coverage periods. Dolibarr has no native OEM warranty tracking module, so we map coverage start/end dates to custom fields on the Product record (warranty_start__c, warranty_end__c, warranty_oem_code__c) and claim history to a Note attached to the Product. We document the original OEM code mapping for customer reference.
e-Emphasys ERP
Custom Fields (e-Emphasys user-defined fields)
Dolibarr ERP
Extra fields (llx_element_contact or llx_extrafields)
lossye-Emphasys user-defined fields across modules are identified during discovery and mapped to Dolibarr extra field tables (llx_propal_extrafields, llx_commande_extrafields, llx_societe_extrafields, etc.) if the CustomFields module is installed. For values that do not map directly, we generate a reconciliation report listing the e-Emphasys field name, Dolibarr target table and column, and a sample of the migrated values for admin verification.
e-Emphasys ERP
Branch / Location
Dolibarr ERP
Warehouse (llx_entrepot) or Tag (llx_categorie)
lossye-Emphasys multi-location inventory and branch assignments map to Dolibarr Warehouses (llx_entrepot) if the stock module is enabled. Each e-Emphasys branch_id becomes a Dolibarr warehouse with its address stored in the warehouse record. If branch assignments are used only for organizational purposes (not inventory tracking), we use Dolibarr tags (llx_categorie) with a dedicated 'Branch' category instead.
| e-Emphasys ERP | Dolibarr ERP | Compatibility | |
|---|---|---|---|
| Customer/Account | ThirdParty (llx_societe)1:1 | Fully supported | |
| Whole Goods (Equipment Inventory) | Product (llx_product) with custom fields1:1 | Fully supported | |
| Parts Inventory (Serialized) | Product (llx_product) + Stock Movement (llx_product_batch)1:1 | Fully supported | |
| Parts Inventory (Non-Serialized) | Product (llx_product)1:1 | Fully supported | |
| Work Orders | Intervention (llx_fichinter) or Project (llx_projet) with Task (llx_projet_task)lossy | Fully supported | |
| Rental Contracts | Contrat (llx_contrat) with custom rate structurelossy | Mapping required | |
| Sales Orders / Quotes | CommandeClient (llx_commande) or Proposal (llx_propal)1:1 | Fully supported | |
| General Ledger / Journal Entries | Accounting (llx_accounting_bookkeeping) or accounting module records1:1 | Fully supported | |
| Accounts Payable | Supplier Invoice (llx_facture_fourn) and Purchase Order (llx_commande_fournisseur)1:1 | Fully supported | |
| Accounts Receivable | Customer Invoice (llx_facture) and Payment (llx_paiement)1:1 | Fully supported | |
| Technicians / Employees | User (llx_user) with project/task assignments1:1 | Fully supported | |
| Warranty Records | Custom fields or Note on Product / ThirdPartylossy | Fully supported | |
| Custom Fields (e-Emphasys user-defined fields) | Extra fields (llx_element_contact or llx_extrafields)lossy | Fully supported | |
| Branch / Location | Warehouse (llx_entrepot) or Tag (llx_categorie)lossy | 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.
e-Emphasys ERP gotchas
No publicly documented API for programmatic export
Acquisition history complicates licensing and support continuity
Rental contract terms require manual reconciliation
Serialized parts tracking complexity
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 database access assessment
We audit the e-Emphasys ERP environment: hosting model (cloud or on-premise), database platform (SQL Server or Oracle), version, and custom field usage across modules. We confirm read-only database credentials or reporting module access. We inventory all objects to migrate: customer records, equipment inventory, parts (serialized and non-serialized), work orders, rental contracts, financial records, technicians, and custom fields. We also identify any e-Emphasys-specific modules (OEM warranty, branch management) that carry data requiring custom field mapping in Dolibarr. The discovery output is a written migration scope, source table schema map, and database access confirmation.
Dolibarr instance provisioning and module activation
We provision a Dolibarr instance on the customer's target environment (self-hosted server or DoliCloud). We activate only the modules required for the migration scope: Third Parties (CRM), Products (inventory), Stock, Commercial Proposals, Customer Orders, Supplier Invoices, Interventions (service), Contracts, Projects (if work orders use project tracking), and the Accounting module (if financial data migrates). We install the CustomFields module from Dolistore if e-Emphasys custom fields require dedicated columns. We verify the PHP version, MySQL/PostgreSQL engine version, and database character set to avoid the migration upgrade key-length issue documented in Dolibarr GitHub issue #16315.
Schema design and e-Emphasys to Dolibarr mapping document
We design the destination Dolibarr schema: product categories (aligned with e-Emphasys parts categories), warehouse records (one per e-Emphasys branch), user accounts (one per e-Emphasys technician), price list structure, and custom extra fields for OEM codes, serial numbers, warranty dates, and rental rate tiers. We produce a written mapping document that specifies for each e-Emphasys table: the source column, the Dolibarr destination table and column, the transform rule (direct map, concatenation, lookup), and any constraint flags. This document is reviewed and signed off by the customer's admin before any data moves.
Direct SQL extraction and intermediate schema transform
We run direct SQL queries against the e-Emphasys database to extract each object in dependency order, or fall back to CSV exports from the reporting module if database access is restricted. We apply transform logic to each object: e-Emphasys branch_id becomes a Dolibarr warehouse ID, e-Emphasys customer billing addresses split into Dolibarr address records, serialized equipment serial numbers populate custom fields, and rental contract rate schedules flatten into contract note fields. We generate reconciliation counts (total records per object, records with missing foreign keys, records with custom fields) before building the final CSV files.
Staging import and reconciliation
We import the full dataset into a staging Dolibarr instance (Full Copy Sandbox or local clone) using Dolibarr's native CSV import tool per object in strict dependency order. We reconcile record counts against the source extraction output: ThirdParties in, Products in, Stock in, Contracts in, Interventions in, Invoices in, Users in. We spot-check 25-50 records per object against the e-Emphasys source for field-level accuracy. Any mapping corrections are made to the transform scripts and re-run on staging. The customer reviews the staging instance and signs off before production import begins.
Production migration and go-live
We run production migration in dependency order into the live Dolibarr instance. Each phase (ThirdParties, Products, Stock, Contracts, Interventions, Financial records, Users) emits a row-count reconciliation report before the next phase begins. We freeze e-Emphasys writes during the final cutover window and run a delta migration for any records modified during the migration window. We enable Dolibarr as the system of record. We deliver the workflow and report inventory document to the customer's admin for rebuild in Dolibarr's module framework. We support a one-week hypercare window for reconciliation issues and do not perform post-migration admin support or workflow rebuild as standard scope.
Platform deep dives
e-Emphasys ERP
Source
Strengths
Weaknesses
Dolibarr ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. All 8 core objects map 1:1 between e-Emphasys ERP and Dolibarr ERP.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across e-Emphasys ERP and Dolibarr ERP.
Object compatibility
All 8 core objects map 1:1 between e-Emphasys ERP and Dolibarr ERP.
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
e-Emphasys ERP: Not publicly documented.
Data volume sensitivity
e-Emphasys 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 e-Emphasys ERP to Dolibarr ERP migration scoping. Not seeing yours? Book a call.
Walk through your e-Emphasys 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 e-Emphasys 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.