Migrate from Login ERP to Dolibarr ERP

Login ERP uses a hierarchical account structure with Turkish fiscal classification codes. We map each account to a Dolibarr Bank Account or Accounting Account depending on whether it is a balance sheet or income/expense account. Account type (asset, liability, equity, revenue, expense), currency denomination, and tax classification codes are preserved in Dolibarr's accounting extra fields. Turkish-specific tax rate tables are replaced with Dolibarr's configurable VAT rate setup. Fiscal year closing entries migrate as a separate journal entry batch to avoid inflating opening balances.

Login ERP customer records (company name, Vergi Kimlik No Turkish tax ID, address, contact details, payment terms) map to Dolibarr Third-Party with the Customer flag enabled. We split multi-contact customer records into Dolibarr contact sub-records linked to the parent Third-Party. Any custom extension tables on the customer entity in Login ERP are exported and recreated as Dolibarr extra attributes during migration. Tax ID maps to the siret or VAT number field in Dolibarr.

Login ERP vendor master data mirrors customer structure with Turkish supplier tax IDs and bank account details. These map to Dolibarr Third-Party with the Supplier flag. Vendor categories in Login ERP map to Dolibarr's category system (purchasing category). Bank account details transfer to Dolibarr's Rib field and bank information extra fields.

Login ERP items carry unit of measure conversions, cost layers (FIFO/average), and stock tracking dimensions. These map to Dolibarr Product records with the type (product, service, assembly) determined by the Login ERP item classification. Multi-warehouse stock records in Login ERP map to Dolibarr warehouse locations and stock levels per product per warehouse. Login ERP's multi-level BOMs for manufactured items map to Dolibarr's BOM module if enabled; otherwise BOM structures are documented as a separate import for manual configuration.

Login ERP multi-level BOMs with component structures and routing definitions migrate to Dolibarr BOM records. Parent-child integrity is preserved by sequencing the export so parent BOMs exist before child BOMs are referenced. Dolibarr BOM supports single-level components; multi-level BOMs are flattened or represented as nested BOMs depending on the Dolibarr version installed. We flag any BOMs with expired or inactive components for admin review before activation.

Outstanding Login ERP invoices, credit memos, and payment records carry Turkish Lira amounts with exchange rate histories. We preserve the original posting date, due date, and currency amount, then apply the customer's specified conversion rate to the destination currency. Partial payments on AP/AR records are represented as separate payment records linked to the original invoice in Dolibarr. Voided or reversed invoices in Login ERP are excluded from migration to prevent stale balances.

Journal entries, invoices, and receipts spanning the full fiscal history are chunked by fiscal year to avoid overwhelming Dolibarr's API limits. We scope a cutoff date during discovery, exclude voided or reversed entries, and import closed fiscal periods as historical read-only records. Open fiscal periods migrate as active records that the customer reconciles after go-live. Each chunk produces a reconciliation report comparing total debits to total credits.

Login ERP employee records include compensation, PTO balances, effective-dated job changes, and Turkish SGK and tax regulatory fields. These map to Dolibarr User records with the employee flag. Login ERP payroll history tied to Turkish SGK does not migrate to Dolibarr's HR module, which lacks Turkish SGK-specific fields; we export payroll history as a CSV report for the customer's records and note that Dolibarr's HR module does not include a payroll engine.

Work orders with status completed or cancelled migrate as historical production records in Dolibarr. Work orders with status in-progress or on-hold carry open material allocations and labor postings that cannot safely import into Dolibarr without creating phantom inventory transactions. We scope production orders by status during discovery and migrate only completed and cancelled orders. In-progress work is flagged in the migration report for manual re-entry post-go-live. Login ERP routing and step labor definitions map to Dolibarr production order operations if the production module is enabled.

Login ERP QC inspection data links to purchase orders and production runs via foreign key. The QC schema is customer-extended and not part of the standard module set. We inspect the actual table definition during discovery and, if the customer requires QC data migrated, we create Dolibarr Project records to hold the inspection data or recommend a Dolistore QC module for post-migration installation. We do not commit to QC migration without reviewing the actual schema.

Equipment asset IDs, maintenance schedules, and labor hours link to Login ERP's fixed assets register. Assets not present in the destination cause foreign-key failures. We either create placeholder asset records in Dolibarr before importing maintenance work orders, or flag the records for admin resolution. Dolibarr's maintenance module (if enabled) or a Dolistore maintenance extension handles the full lifecycle post-migration.

Login ERP stores document references and binary attachments in a proprietary file store. We export document metadata (filename, linked entity, date) but not binary content. Full document migration requires a separate engagement involving file system access and Dolibarr's document directory structure. We flag this as a manual step in the migration handoff document and do not include binary document migration in standard scope.