Migrate your Login ERP data

Login ERP uses a hierarchical account structure with Turkish fiscal classification codes. We map each account to the destination's equivalent, preserving account type, currency denomination, and tax code associations. Turkish-specific accrual and expense deferral accounts require manual field mapping during schema alignment.

Customer records include company name, tax ID (Vergi Kimlik No), address, contact details, and payment terms. Standard fields migrate cleanly; we flag any custom extension tables the customer has added for regional compliance.

Vendor master data mirrors customer structure with Turkish supplier tax IDs and bank account details. We map vendor categories and fiscal identification codes to the destination equivalent.

Items carry complex attributes: unit of measure conversions, cost layers (FIFO/average), bill of materials for manufactured items, and stock tracking dimensions. Login ERP's multi-warehouse stock records require disaggregation before importing into single-warehouse destinations.

Outstanding invoices, credit memos, and payment records carry Turkish Lira amounts with exchange rate histories. We preserve the original posting date and due date, and map the currency to the destination's equivalent. Partial payments recorded against invoices must be reconstructed from the payment ledger.

Journal entries, invoices, and receipts span the full fiscal history. Migration scoping must define a cutoff date and exclude voided or reversed entries to avoid importing stale records. We chunk by fiscal year and handle year-end closing entries separately.

Employee records include compensation, PTO balances, and effective-dated job changes. Login ERP's HR module stores payroll history tied to Turkish SGK and tax regulations. Custom payroll fields require explicit mapping to the destination's compensation schema.

Bill of materials with multi-level component structures and routing/step labor definitions migrate with parent-child integrity preserved. We flag work orders that are in-progress or hold status, as these cannot be cleanly imported into a fresh production environment.

QC inspection data links to purchase orders and production runs. The schema is customer-extended and not part of the standard module set, so we inspect the actual table definition before committing to migration scope.

Equipment asset IDs, maintenance schedules, and labor hours link to the fixed assets register. Assets not present in the destination cause foreign-key failures; we either create placeholder assets or flag for exclusion.

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 manual retrieval from the file system.