Migrate from ERP Mark 7 to Dolibarr ERP

ERP Mark 7 Customer records with address, contact details, and payment terms map directly to Dolibarr ThirdParty objects with the Stype field set to Customer. We preserve the ERP Mark 7 customer code as ref_customer, primary contact email as email, and payment terms as cond_reglement. If ERP Mark 7 stores multiple contacts per customer, secondary contacts migrate as separate Dolibarr Contact records linked to the parent ThirdParty via the.contact_no_email foreign key. Tax identification numbers from ERP Mark 7 map to Dolibarr's tva_intra field for EU customers or siret for French customers depending on the jurisdiction.

ERP Mark 7 Vendor records with 1099 settings and W-9 status migrate to Dolibarr ThirdParty with Stype set to Supplier. The 1099 flag maps to a custom dolibarr_extra field since native Dolibarr does not include a 1099-equivalent field (US-specific). We preserve W-9 status as a note attached to the ThirdParty. Vendor payment terms map to cond_reglement and delivery delay days map to delivery_delay_days if the ERP Mark 7 instance exposes those fields during schema discovery.

ERP Mark 7 inventory Items with SKU, description, unit cost, and on-hand quantity map to Dolibarr Product with fk_product_type=0 (stockable). The ERP Mark 7 barcode or item number becomes the barcode field, and the primary unit of measure maps to units. We transfer on-hand quantity by creating a Dolibarr stock movement (Stock Mouvement) linked to the destination warehouse (Entrepot) after the Product record is created. Multi-warehouse setups in ERP Mark 7 require a warehouse-mapping phase to assign stock rows to corresponding Dolibarr Entrepot records.

ERP Mark 7 non-inventory items and services map to Dolibarr Product with fk_product_type=1 (service). We preserve the item description, default sales price, and cost price from ERP Mark 7. If ERP Mark 7 exposes custom properties on service items (e.g., billing frequency, subscription tier), we map those to Dolibarr extra fields on the Product object.

ERP Mark 7 chart of accounts entries with account number, name, type, and classification segment map to Dolibarr AccountingAccount records linked to the active plan_comptable. We map standard account numbers directly but flag any non-standard segment configurations (e.g., cost-center segments in the account number itself) that cannot be replicated as native Dolibarr accounting codes. The customer manually re-creates non-standard account segment logic in Dolibarr's account configuration panel or via a third-party cost-center module if one is chosen.

Open receivables in ERP Mark 7 map to Dolibarr Facture records with.facture=0 (draft or open) and.fk_facture_source left empty. Payment status, aging buckets, and payment method all transfer. We chunk by invoice date to maintain chronological order and set the due date from ERP Mark 7's payment_terms field. Any partial payments recorded in ERP Mark 7 generate a corresponding Payment (Paiement) record linked to the Facture before migration continues. The ERP Mark 7 customer reference maps to.ref_customer on the Dolibarr Facture.

Open payables in ERP Mark 7 map to Dolibarr Facture records with.facture=0 and.fk_facture_source set to the ERP Mark 7 vendor invoice number as.ref_supplier. We preserve aging status and payment method. If ERP Mark 7 tracks 1099 eligibility on the vendor, that flag is written to a note on the Dolibarr ThirdParty. Chunks are sequenced by vendor to group related payables and simplify reconciliation after migration.

Transaction history migrates to Dolibarr AccountingEntry (EcritureComptable) records grouped by Piece Comptable (journal entry). We segment pre-close and post-close batches using the fiscal-year boundaries confirmed with the customer during scoping: closed periods migrate as locked entries with.rowid locked and stat=0; the current fiscal year migrates as open entries that the customer can still post to. We preserve the original transaction date, account references, debit/credit amounts, and any ERP Mark 7 memo or narration text as the EcritureComptable label.

ERP Mark 7 Work Orders contain a header (linked Item, priority, machine center, status) and line-level BOM steps and routing steps. We split Work Orders into a Dolibarr Project record (carrying the work order header fields: description, ref, date, status) plus one or more Dolibarr Intervention records (Fichinter) for each production step. The ERP Mark 7 Item linked to the Work Order becomes the.ref and label of the Project. Custom fields on Work Orders (e.g., machine_center, priority_flags) migrate to extra fields on the Project or Intervention depending on their relevance to scheduling vs. labor logging.

Documents stored as attachments to transactions, items, or customers in ERP Mark 7 export in their native binary format. We re-attach them to the corresponding migrated Dolibarr record using Dolibarr's LinkedFiles mechanism. The attachment type (PDF invoice, image, CSV export) determines the file MIME type stored alongside the record reference. Large binary attachments (over 10 MB) are chunked and checksum-validated during re-upload to avoid timeout errors.

ERP Mark 7 User records with name, email, role, and department assignment map to Dolibarr User objects. Role names do not map 1:1 to Dolibarr's permission system, so we match by permission level and flag roles that require manual reassignment in Dolibarr's Rights management panel. Department assignments map to Dolibarr'sllx_user_calendars or a custom department field depending on whether the Dolibarr HR module is enabled at the destination.

Tax codes from ERP Mark 7 (region-specific, product-category-specific, active and deprecated) migrate to Dolibarr Tax model (LocalTax) or VAT rate configurations depending on the jurisdiction. Active ERP Mark 7 tax codes map to corresponding Dolibarr tax rates with the correct fk_c_country reference. Deprecated or jurisdiction-specific codes that have no Dolibarr equivalent are flagged for manual re-creation in Dolibarr's Tax and vat configuration panel. We document the full list in the migration handoff notes.

ERP Mark 7 allows user-defined fields on standard objects that have no external enumeration mechanism. During schema discovery we export a sample record set and diff the exported fields against the standard ERP Mark 7 object definition to identify custom properties. Each discovered custom field is re-created in Dolibarr as an ExtraFields entry on the matching object (ThirdParty, Product, Facture, etc.) before data migration begins. Type mapping is inferred from the ERP Mark 7 field data (string -> varchar, number -> int or float, date -> datetime).

ERP Mark 7 departments with nested hierarchies map to Dolibarr Entrepot records if the department represents a physical location with inventory, or to Dolibarr Project records if the department represents a cost or responsibility center. The mapping choice is confirmed with the customer during scoping since Dolibarr has no native cost-center object. Nested hierarchies are flattened to one level in Dolibarr Entrepot unless a third-party cost-center module is planned for the destination.