Migrate from Login ERP to Epicor Prophet 21

Login ERP uses a hierarchical account structure with Turkish fiscal classification codes. We map each account to an Epicor GL Account with segment values derived from the source classification hierarchy. Account type (asset, liability, equity, revenue, expense), currency denomination, and tax code map to Epicor fields COAID, Type, CurrencyCode, and TaxRegionID. Turkish-specific fiscal closing entries (dönem kapanış) are treated as a separate journal batch to avoid inflating opening balances in Epicor. We scope which modules the customer actively uses so we do not attempt to migrate dormant or zero-balance ledgers.

Login ERP customer records include company name, Turkish tax ID (Vergi Kimlik No), address, contact details, and payment terms. Vergi Kimlik No maps to Epicor's TaxID field on the Customer record. We flag any custom extension tables the customer has added to the Login ERP customer schema and create equivalent UD fields in Epicor. Customer credit limits map to Customer.CreditHolds and Payment Terms map to the Epicor Terms table.

Vendor master data mirrors the customer structure with Turkish supplier tax IDs and bank account details. Vergi Kimlik No maps to Supplier.TaxID, and Turkish bank account fields (IBAN, banka kodu) map to Epicor SupplierBankAcct records. Vendor categories and fiscal identification codes map to Epicor SupplierGroup and TaxRegionID equivalents. We inspect the Login ERP vendor schema during discovery because some customers store extended supplier qualification data in custom tables.

Login ERP items carry complex attributes: unit of measure conversions, cost layers (FIFO or average), stock tracking dimensions, and stock/reorder parameters. Each item maps to Epicor Part with Part.UnitCost, PartSales.Prices, and PartWhse records carrying warehouse-specific stock levels. Login ERP's multi-warehouse stock records map to Epicor PartWhse with the warehouse code preserved. We flag items that have been deactivated in Login ERP (stok pasif) to exclude them from migration unless the customer specifies otherwise.

Login ERP multi-level BOMs with component structures and routing or step labor definitions migrate with parent-child integrity preserved. We extract the top-level BOM and all sub-assemblies, then create Epicor PartMtl records with the correct material quantity, scrap percent, and BOM sequence. Where Login ERP stores routing steps (işlem adımları), we map these to Epicor PartMtl.RscSeq and JobOper records. We validate the BOM explosion in Epicor's Bill of Materials editor before production migration.

Outstanding Login ERP vendor invoices, credit memos, and payment records carry Turkish Lira amounts with exchange rate histories. We preserve the original posting date and due date, map currency to the Epicor destination currency (typically USD or EUR for international operations), and apply exchange rate conversion. Fiscal year closing entries are excluded to avoid inflating opening balances. We chunk AP records by fiscal period to avoid overwhelming Epicor's AP API during import. Vendor references resolve via the Supplier mapping established in the vendor master migration phase.

Outstanding Login ERP customer invoices and credit memos migrate to Epicor AR Invoice with customer references resolved through the Customer mapping. Turkish Lira amounts convert using the exchange rate on the original posting date, and the converted amount lands in the Epicor functional currency field. Original invoice numbers map to InvoiceNum for audit trail continuity. Payment records migrate as AR Payment records linked to the corresponding invoices.

Login ERP journal entries spanning the full fiscal history migrate to Epicor GL Journal Entry records. Migration scoping defines a cutoff date and excludes voided or reversed entries. We chunk by fiscal period to avoid Epicor API limits on large batch inserts. Each journal entry preserves the original account code (mapped to the new Epicor COA), debit/credit amount, and posting date. The migration scope excludes future-dated entries and fiscal close batches that would conflict with Epicor's accounting period controls.

Login ERP production orders (üretim emri) map to Epicor Job records with BOM and routing references resolved. Completed and cancelled production orders migrate as historical records with JobHead.JobComplete set accordingly. We flag work orders that are in-progress or on-hold status because they carry open material allocations and labor postings that cannot be safely imported into Epicor without creating phantom inventory transactions. In-progress work is documented in a separate handoff list for manual re-entry post-go-live.

Login ERP employee records include compensation, PTO balances, and effective-dated job changes tied to Turkish SGK (social security) and tax regulations. We map Employee records to Epicor's HR module with SGK number preserved in a custom field, and Turkish tax withholding codes mapped to Epicor's tax configuration. PTO balances migrate as accrual records where the Epicor destination includes the HR module. Custom payroll fields require schema inspection during discovery because extended payroll tables vary by customer configuration.

Login ERP 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 during discovery before committing to migration scope. QC results migrate to Epicor's Quality Management module if the destination includes it; otherwise, we deliver a written export of QC data as a reference file for the customer's quality team.

Equipment asset IDs, maintenance schedules, and labor hours link to Login ERP's fixed assets register. Assets not present in the Epicor destination cause foreign-key failures during import; we either create placeholder assets or hold the maintenance record until the asset is provisioned by the customer's admin. We extract the maintenance work order history (emir kaydı) with job steps, labor hours, and parts consumed, mapping them to Epicor Maintenance Work Order records with the linked asset.

Login ERP stores document references and binary attachments in a proprietary file store. We export document metadata (filename, linked entity, date, description) but not binary content. The metadata export is delivered as a reference CSV so the customer's admin can re-associate documents manually in Epicor Kinetic Document Management. Full binary document migration requires the Login ERP file store export to be performed by the customer's IT team before our engagement begins.