Migrate from Impact ERP to Dolibarr ERP

Impact ERP's hierarchical COA with Indonesian-chart variants (8-digit account codes grouped by type) maps to Dolibarr's llx_accounting_account table. Account codes, descriptions, and group assignments (account_type: asset, liability, equity, income, expense) transfer directly. We validate account type assignments against Indonesian standard chart templates available in Dolibarr's accounting module. NPWP-linked tax accounts preserve their tax mapping metadata in Dolibarr's Tax module configuration.

Impact ERP customer master records (name, billing address, shipping address, NPWP tax ID, payment terms, credit limit) map to Dolibarr llx_societe with typentCode=2 (customer). NPWP number maps to Dolibarr's Extrafields siret/nif field or a custom tax_id field. Payment terms map to llx_conditions_generales_cgps. We resolve multi-address customer records (billing vs shipping) to Dolibarr's Addresses (llx_societe_address) linked via fk_soc.

Impact ERP vendor masters (NPWP tax ID, bank account details, lead-time fields) map to Dolibarr llx_societe with typentCode=1 (supplier). Bank account details for payment runs map to llx_societe_bank. Lead-time fields migrate as Extrafields since Dolibarr's standard vendor record does not have a native delivery lead-time field. We preserve effective-dated changes on vendor records as separate llx_societe records with a date-validity Extrafield or as notes on the primary record.

Impact ERP item masters (SKU, description, unit of measure, cost, inventory valuation method) map to Dolibarr llx_product. Unit of measure migrates to Dolibarr's Unit of Measure system (llx_c_units). Cost price maps to cost_price; sell price maps to price. Inventory valuation method (FIFO, moving average) maps to Dolibarr's pcm_active field in the stock module. Item type (product vs service) determines Dolibarr's fk_product_type (0=product, 1=service).

Impact ERP BOMs and routings attached to items extract from exported backup as separate tables and re-associate at the destination. Dolibarr's MRP module (mrp) stores BOMs in llx_mrp_production and components in llx_mrp_production. Routing steps (workstations, cycle times) map to Dolibarr's llx_mrp_mo and workstation assignments. If the destination Dolibarr instance does not have the MRP module enabled, we flag this as a prerequisite before BOM import and deliver a module-enablement checklist.

Impact ERP open payables and receivables (invoice number, due date, amount, currency, status) map to Dolibarr llx_facture (invoices) with status=open (unpaid). Invoice type determines fk_facture (customer=facture, supplier=facture_fourn). We migrate open items as unresolved balances and flag fully-paid records for optional historical carry-forward depending on the customer's audit requirements. Currency handling (IDR vs multi-currency) requires Dolibarr multi-currency module activation if amounts span multiple currencies.

Past customer invoices and supplier bills from Impact ERP's transaction tables migrate to Dolibarr llx_facture with status=paid (closed). Line items map to llx_facturedet with product references resolved via SKU match. We extract in date-range chunks to respect Dolibarr's import performance limits and map journal-entry links to Dolibarr's llx_accounting_record. Fiscal year boundaries must align with Dolibarr's accounting period configuration before invoice import begins.

Impact ERP purchase orders migrate to Dolibarr llx_commande_fournisseur with status mapped from Impact ERP state (draft, validated, received, closed). Line items map to llx_commande_fournisseurdet. Received quantities vs ordered quantities require reconciliation against any linked GRN (goods receipt) records in Impact ERP before migration to avoid duplicate stock entries in Dolibarr.

Impact ERP sales orders migrate to Dolibarr llx_commande with status mapped (draft, validated, shipped, invoiced, closed). Line items map to llx_commandedet. If the original sales order in Impact ERP generated a linked delivery note (llx_expedition), we reconstruct that relationship in Dolibarr before importing orders to preserve shipment traceability.

Impact ERP GL journal entries generated from transactions migrate to Dolibarr llx_accounting_account and llx_bank. Header-level entries map to llx_accounting_mvt; line-item entries map to llx_accounting_det with debit_amount and credit_amount. Memo fields and department references migrate to Extrafields on both tables. We validate that Impact ERP's double-entry balance (debits = credits) holds before inserting into Dolibarr; unbalanced entries are flagged for customer review.

Impact ERP user accounts (login, role assignments, department assignments) map to Dolibarr llx_user. Role-to-role mapping requires the customer to define Dolibarr module-level permissions that map to each Impact ERP role. Passwords are not migratable (Impact ERP stores hashes in an unrecoverable format). We provision new Dolibarr accounts with a temporary password and deliver an account-activation guide. Admin vs standard user distinctions map to Dolibarr's SuperAdmin and rights configuration.

Impact ERP custom fields and user-defined objects added during implementation have no standardized schema. We identify custom field definitions via exported metadata and map them to Dolibarr Extrafields on the equivalent standard object (llx_societe, llx_product, llx_facture, etc.). For custom objects with independent schema, we use Dolibarr's Module Builder to pre-create equivalent tables before data import. All custom field mappings are documented field-by-field in the migration specification for customer sign-off.