Migrate from Login ERP to Acumatica

Login ERP customer records map directly to Acumatica Customers (BAccount with Customer type). Primary contact details, billing address, and shipping address fields translate 1:1. Customer class in Acumatica determines tax zone and payment terms. The mapping also preserves the customer’s credit limit, payment term reference, and any custom attributes stored in Login ERP’s customer module.

Login ERP vendor records map to Acumatica Vendors (BAccount with Vendor type). Remit-to address and vendor class fields align with Acumatica's AP invoice assignment rules and 1099 configuration. Vendor payment terms, currency settings, and any custom fields specific to Turkish procurement regulations are carried over as Acumatica UDFs, ensuring compliance without manual re-entry.

Login ERP inventory items map to Acumatica Stock Items with ItemClass controlling posting settings. Valuation method (Standard, Average, FIFO) is preserved. Login ERP's lot/serial tracking rules map to Acumatica's lot/serial classes. Item warehouse assignments and default stocking locations are translated into Acumatica’s Warehouse and Location fields, preserving bin-level traceability.

Login ERP service items and miscellaneous charges map to Acumatica Non-Stock Items. Used on sales and purchase orders for labor, handling, or materials tracked by vendor rather than inventory. Each non-stock item’s default vendor, unit of measure, and any custom fields (e.g., Turkish compliance codes) are transferred to Acumatica UDFs to maintain operational continuity.

Open sales orders migrate with line items, quantities remaining, and scheduled ship dates preserved. Acumatica uses SOOrder DAC; order type determines workflow behavior. Line-level discounts stored as percentages map to ManualDiscount field. Customer references, internal notes, and any Login ERP custom order fields are transferred as UDFs on the SOOrder DAC, ensuring all contextual information is available in Acumatica.

Open purchase orders migrate with vendor, line items, and receipt expectations. Acumatica PO receives against POLine records; open quantity maps to OrderNbr. Prepayments migrate as CashSales entries if applicable. Vendor payment terms, split accounting requirements, and any custom fields (e.g., Turkish tax exemption codes) are mapped to UDFs on the POOrder DAC, preserving the full procurement context.

Login ERP chart of accounts maps to Acumatica Accounts. Account code structure is preserved. Active/inactive status, account type (Asset, Liability, Expense, Income), and posting settings transfer directly. Currency settings, tax settings, and any department or cost-center designations stored in Login ERP’s account records become UDFs on the Account DAC, allowing granular reporting without altering the base account structure.

Login ERP's cost-center and department fields combine into Acumatica Subaccount objects via Subaccount Mask configuration. Each unique Login ERP department value becomes a Subaccount with the configured mask pattern. If Login ERP uses hierarchical department codes (e.g., 01‑02‑03), the Subaccount Mask can be set to reflect up to three segments, preserving the full organizational hierarchy in Acumatica’s subaccount structure.

Login ERP warehouse and location records map to Acumatica Warehouse entities. Each warehouse gets a Branch assignment in Acumatica's organizational hierarchy. Default location codes map to WarehouseLocation. Warehouse-specific parameters such as lead times, replenishment settings, and any custom fields (e.g., Turkish compliance flags) are transferred to UDFs on the Warehouse DAC, ensuring all operational details are retained.

Login ERP production/manufacturing orders translate to Acumatica Manufacturing Production Orders. BOM revision numbers map to AMBillOfMaterials. Planned and released production order status translates to equivalent Acumatica status codes. Material requirements, operation steps, and any work center assignments from Login ERP are migrated to AMProdMatl and AMOperation lines, preserving the full production routing within Acumatica Manufacturing.

Open and historical AR invoices migrate with customer reference, invoice number, date, due date, and line amounts. Tax calculation is source-system based; Acumatica tax is recalculated on posting or suppressed via Hold flag. Payment holds, credit memos, and any custom invoice fields (e.g., Turkish e-invoice codes) are transferred as UDFs on the ARInvoice DAC, maintaining compliance and auditability.

Open AP invoices map to Acumatica AP Invoice with vendor reference and terms. Prepaid invoices and credit memos migrate as separate AP Document records with appropriate document types. Vendor-specific tax exemption codes, withholding tax details, and any custom AP fields (e.g., Turkish KD V or withholding rates) are mapped to UDFs on the APInvoice DAC, preserving the full payables context.

Login ERP module-specific custom fields (Turkish compliance fields, local regulatory attributes) require pre-created Acumatica UDFs using the Usr prefix. Each module's custom table must be analyzed individually to determine which fields have no standard Acumatica equivalent. During migration, we create the UDFs on the appropriate DACs and populate them with the source values, ensuring data continuity and avoiding manual re-entry across all modules.