Migrate from Login ERP to Infor CloudSuite Corporate

Login ERP uses a hierarchical account structure with Turkish fiscal classification codes embedded in the account number. We map each Login ERP account to an Infor CloudSuite GL Account with the account type, currency denomination, and tax code preserved. Multi-company account structures in Login ERP (used when the company runs multiple legal entities) map to separate Infor CloudSuite Company codes. We flag any inactive or zero-balance accounts for exclusion unless the customer specifies otherwise during scoping.

Login ERP customer records include company name, Turkish tax ID (Vergi Kimlik No), address, contact details, and payment terms. We map these to Infor CloudSuite Business Partner records with the Customer role enabled. The Turkish tax ID maps to the Business Partner tax identification field. Any custom extension tables the customer has added to Login ERP are audited during discovery and mapped to Infor CloudSuite extended fields or User Defined Fields (UDFs).

Login ERP vendor master data mirrors the customer structure with Turkish supplier tax IDs and bank account details for payment processing. We map vendor categories and fiscal identification codes to Infor CloudSuite Business Partner records with the Supplier role enabled. Bank account details transfer to the Business Partner banking tab for SEPA/EFT payment configuration in Infor.

Login ERP items carry complex attributes: unit of measure conversions, cost layers (FIFO or average), bill of materials for manufactured items, and stock tracking dimensions across multiple warehouses. We map Login ERP items to Infor CloudSuite Item Master records, preserving the costing method, UOM conversions, and warehouse assignments. Login ERP's multi-warehouse stock records map to Infor's warehouse-specific inventory quantities.

Login ERP multi-level BOMs with parent-item and component-item relationships map to Infor CloudSuite BOM structures. We preserve the parent-child hierarchy integrity, including phantom bills for sub-assemblies, and copy routing or labor step definitions. BOM validation in Infor CloudSuite checks for component items that do not exist in the Item Master; we pre-create placeholder items or flag missing components before BOM import to avoid validation failures.

Outstanding invoices, credit memos, and payment records carry Turkish Lira amounts with exchange rate histories. We preserve the original posting date, due date, and currency. Before importing into Infor CloudSuite, we apply currency conversion if the destination company code uses a different base currency, and we scale the monetary values to match Infor's decimal precision configuration. Fiscal year closing entries are treated as a separate dataset to avoid inflating opening balances in Infor.

Journal entries, invoices, and receipts spanning the full fiscal history require date-windowed chunking to avoid overwhelming Infor CloudSuite's import limits. We scope a cutoff date with the customer during discovery and exclude voided or reversed entries. Open AP/AR invoices are migrated as a separate object from historical closed transactions. Historical data exceeding two fiscal years may be archived separately depending on the customer's reporting needs and Infor storage planning.

Login ERP employee records include compensation, PTO balances, and effective-dated job changes tied to Turkish SGK and tax regulations. We map employee records to Infor CloudSuite HR Employee, preserving the tax ID, bank account for payroll, and job assignment. Custom payroll fields require manual review because Turkish SGK-specific fields may not have direct Infor equivalents without configuration. We flag any non-standard HR fields for customer review before import.

Completed and cancelled production orders migrate as historical records in Infor CloudSuite. We scope in-progress and on-hold work orders during discovery and exclude them from migration because their open material allocations and labor postings cannot safely import without creating phantom inventory transactions. The customer re-enters in-progress work orders post-go-live. Completed production orders preserve the BOM reference, quantities produced, and labor hours.

QC inspection data links to purchase orders and production runs in Login ERP. The schema is customer-extended and not part of the standard module set. We inspect the actual table definition during discovery before committing to a migration path. If the QC tables have foreign-key dependencies on items and production orders that are not present in the destination, we either create placeholder records or flag QC data for manual migration.

Equipment asset IDs, maintenance schedules, and labor hours link to the fixed assets register in Login ERP. We map these to Infor CloudSuite Maintenance Work Orders. Assets not present in Infor's asset register cause foreign-key failures during import; we either create placeholder assets or flag the discrepancy for the customer's admin to resolve before migration proceeds.