Migrate from Zenscale to Dolibarr ERP

Zenscale's hierarchical chart of accounts with cost-center tagging maps to Dolibarr's llx_accounting_account table. We extract account codes, account names, parent account references, and cost-center assignments from Zenscale's Financial Accounting module export and map them to Dolibarr's account structure (account_number, label, pcg_type, pcg_subtype). Indian compliance accounts (GST input/output, TDS, PF, ESI) require explicit mapping to Dolibarr's chart of accounts format and must be verified by the customer's accountant before the accounting module is enabled in production.

Zenscale maintains both customer and supplier ledgers with GST registration numbers (GSTIN), payment terms, and credit limits. We extract third-party records with type (customer/supplier/both), GSTIN, address, phone, email, payment term code, and credit limit and map them to llx_societe. Zenscale's supplier vs customer distinction maps to llx_societe.client and llx_societe.fournisseur boolean flags. GSTIN validation (15-character format) is preserved as a custom field on the third party record since standard Dolibarr third-party records do not enforce Indian GSTIN format natively.

Zenscale item masters include finished goods, raw materials, and semi-finished variants with BOM linkages, unit of measure, and stock thresholds. We extract item code, description, type (product/service), UoM, cost price, and selling price and map them to llx_product (ref, label, type, price, price_ttc). Current stock quantities map to llx_product_stock with warehouse reference (llx_entrepot). Dolibarr's BOM module must be enabled separately to store multi-level bill of materials; without it, item linkages are preserved as notes or custom fields.

Zenscale's open PO records with line-item pricing, delivery schedules, and GST tax components map to Dolibarr's supplier order (llx_commandefournisseur) and supplier order line (llx_commandefournisseurdet). We extract PO number, supplier reference, order date, expected delivery date, line-item product codes, quantities, rates, and tax amounts and map them to Dolibarr's order structure. Open POs migrate with status DRAFT or VALIDATED depending on Zenscale's PO workflow state at migration time.

Zenscale's open SO records with line-item pricing, delivery schedules, and GST tax components map to Dolibarr's customer order (llx_commande) and order line (llx_commandedet). We extract SO number, customer reference, order date, expected delivery date, line-item product codes, quantities, rates, and GST amounts. Open SOs migrate with status DRAFT or VALIDATED; any partially invoiced SOs carry the remaining balance as order lines without invoice links pending customer confirmation.

Zenscale's production orders with routing steps, work-center assignments, BOM component quantities, and consumption rates map to Dolibarr's llx_mrp_production table if the MRP module is enabled. We extract production order number, BOM reference, scheduled start and end dates, work-center assignment, and component consumption quantities. Closed production orders migrate with COMPLETED status; open orders migrate with INPROGRESS status. The production history, including closed orders, is included to preserve BOM version lineage as required for audit trails in manufacturing environments.

Zenscale's multi-level BOMs and routing steps map to Dolibarr's llx_bom_billofmaterials and llx_bom_bomline tables. We extract BOM version, component items, quantities per finished unit, and unit of measure from Zenscale's production module export. Routing steps (work-center sequence, labor hours, machine hours) map to the BOM's notes field or to a separate routing table if the DoliBomRouting community module is installed. BOM revision history migrates as separate BOM versions with version dates preserved.

Zenscale stores employee records with salary components (basic, HRA, allowances, deductions), attendance data, and statutory contributions (PF, ESI, TDS). We extract employee code, name, designation, department, date of joining, gross salary, and active statutory deductions and map them to llx_employee (ref, lastname, firstname, poste, dateEmbauche, salary). PF and ESI numbers map to custom fields on the employee record since standard Dolibarr HR does not enforce Indian statutory ID formats. Historical salary registers migrate as payroll period entries in llx.payroll or a custom salary history table.

Indian GST compliance data—GSTR-1 outward supply summaries, GSTR-3B summary, and input tax credit registers—are stored against transactions in Zenscale. We extract tax summary records and line-item GST amounts with transaction references (invoice number, date, customer GSTIN, taxable value, tax rate, tax amount) and preserve them in a structured export for the customer's accountant to rebuild as GST-compliant reports in Dolibarr's accounting module. GST reconciliation data (GSTR-2A match status) migrates as metadata on the corresponding customer third-party record. We flag any mismatches between Zenscale's GST ledger and transaction totals for accountant review before decommissioning the source system.

Zenscale's quality management module stores inspection results linked to purchase orders and production lots with QC pass/fail status, inspector names, and rejection reasons. We extract inspection reference, linked PO or production order, inspection date, item inspected, quantity inspected, quantity accepted, quantity rejected, and rejection reason. If Dolibarr's Quality Control module is enabled, these map to llx_qcinspection and llx_qcinspectiondet. If the module is not enabled, QC data migrates as custom fields on the linked product or order record.

Zenscale stores contact persons associated with supplier and customer accounts. We extract contact name, role, phone, email, and the parent third-party reference and map them to llx_socpeople linked via fk_soc to the corresponding llx_societe record. Primary contact flags from Zenscale become the default_contact checkbox in Dolibarr.

Zenscale stores attached documents (invoices, GRNs, quality certificates) in a proprietary file store without a documented attachment export API. We extract document filenames, file paths, associated record references, and upload timestamps from Zenscale's database and produce a file inventory spreadsheet. The customer can use this inventory to manually relocate physical files to Dolibarr's /documents/ directory post-migration. Binary file content cannot be extracted without Zenscale's direct database access, which is outside standard migration scope and requires separate vendor coordination.