Migrate from Login ERP to Microsoft Dynamics 365 Business Central

Login ERP customer records (company name, Vergi Kimlik No tax ID, address, contact details, payment terms) map to Dynamics 365 Customer either as a Customer account (for B2B) or as a Contact linked to an Account. We preserve the Turkish tax ID in the Party Tax Registration ID (TaxRegistrationNumber) field on the DirPartyTable equivalent. Custom extension tables added by the customer are inspected during discovery and mapped individually if they contain standard fields; extension tables without standard equivalents are flagged for manual post-migration review.

Login ERP vendor master data mirrors the customer structure with Turkish supplier tax IDs and bank account details. Turkish bank account IBAN fields map to the vendor's bank account entity in Dynamics 365. Vendor categories migrate as a vendor group (VendGroup) in Finance and as a vendor category in Business Central. Vendor hold or blocked status from Login ERP maps to the blocked flag on the vendor record.

Login ERP Items carry unit of measure conversions, cost layers (FIFO/average), and stock tracking dimensions across multi-warehouse locations. We map the primary stockkeeping unit to the Released Product's product number, preserve cost layer method as the costing version in Dynamics 365, and normalize multi-warehouse warehouse codes to the destination's inventory site/warehouse structure. Login ERP's lot and serial number tracking dimensions map to tracking dimension groups in the destination product.

Login ERP's hierarchical account structure with Turkish fiscal classification codes maps to Dynamics 365 main accounts with the account type preserved (Revenue, Expense, Asset, Liability). We apply a fiscal classification code mapping table during export to resolve Turkish MUH (Muhasebe Uygulama Hizmetleri) codes to Dynamics 365 account types and posting definitions. Financial dimensions (Cost Center, Department, Project) are derived from Login ERP's cost object fields if the customer uses them. Configuration happens in a golden-config environment before any data load.

Outstanding Login ERP 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 transaction currency field. Exchange rates at the time of original posting are stored as a historical rate field on the transaction. Outstanding AP maps to vendor transaction lines; outstanding AR maps to customer transaction lines. We exclude voided or reversed entries from migration scope based on the void flag in Login ERP.

Journal entries, invoices, and receipts spanning the full fiscal history require date-windowed chunking to avoid overwhelming Dynamics 365 data entity limits. We scope by fiscal year with a defined cutoff date, exclude voided or reversed entries, and load by period. Fiscal year closing entries (Login ERP's Yilsonu Devir entries) are treated as a separate dataset and mapped to Dynamics 365 opening transaction entries for the new fiscal year to avoid inflating balances. We chunk by 50,000-line batches per fiscal period.

Login ERP production orders with completed or cancelled status migrate as historical production records. We flag in-progress and on-hold work orders during scoping; these carry open material allocations and labor postings that cannot be safely imported without creating phantom inventory transactions in Dynamics 365. In-progress work is excluded from the automated migration and flagged for manual re-entry post-go-live. Completed production orders preserve the bill of materials used, labor hours consumed, and output quantities as production history records.

Login ERP multi-level BOM component structures with parent-child relationships map to Dynamics 365 BOM versions with exploded component lines. We preserve the bill of materials header (BOM ID, effective date, site), line-level components (item number, quantity per, phantom flag for sub-assemblies), and routing or step labor definitions as operation resources. Phantom BOMs that represent sub-assemblies migrate as phantom items in the destination. The top-level BOM must be active and approved before production order import references it.

Login ERP employee records include compensation, PTO balances, and effective-dated job changes tied to Turkish SGK and tax regulations. We map employee number, name, hire date, termination date, job title, and department. Compensation and PTO balances migrate as HR variables or accrual entries in the destination HR module. Custom payroll fields tied to Turkish SGK-specific deductions require mapping to the destination's payroll configuration; these are scoped during discovery and often require a payroll implementation partner to finalize.

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. Standard QC results (pass/fail, measurement values) map to Quality Order test results if the destination has the Quality Management module enabled; otherwise they migrate as notes or custom fields on the related Purchase Order or Production Order.

Login ERP equipment asset IDs, maintenance schedules, and labor hours link to the fixed assets register. Assets not present in the destination cause foreign-key failures during work order import; we either create placeholder asset records before work order import or exclude work orders referencing unmigrated assets and flag them for manual reconciliation. Maintenance labor hours, spare parts consumed, and failure codes map to the corresponding work order line types in Dynamics 365 Fixed Asset Management.

Login ERP stores document references and binary attachments in a proprietary file store. We export document metadata (filename, linked entity, date, document type) but not binary content, as the file store format is not directly compatible with Dynamics 365's document handling (SharePoint Online, Azure Blob Storage, or network file share). We deliver a file manifest mapping Login ERP document IDs to the linked entity's primary key in Dynamics 365 so that the customer's admin can manually re-attach files post-go-live or configure a document migration tool.