Migrate from Microsoft Dynamics 365 Business Central to Infor CloudSuite Corporate

Business Central Customer records map to Infor Business Partner with role type Customer. Address, contact, payment terms, and credit limit fields map to MITBAL (M3), BusinessPartner (LN), or Customer master (SyteLine). Business Central vendor-posting-group maps to Infor payment terms and invoice validation rules. We resolve the Business Partner number assignment (auto-generated or sourced from BC number) during migration and maintain a cross-reference table linking BC customer number to Infor BP code.

Business Central Vendor records map to Infor Business Partner with role type Vendor. Pay-to addresses, payment terms, and vendor posting group transfer to the Infor vendor master. Prepayments on purchase orders in BC require mapping to Infor advance payment handling which varies by edition. We flag any vendor record that shares a BP code with an existing customer in Infor (shared BP model) versus a separate BP code per role.

Business Central Items (Inventory, Service, Non-Inventory types) map to Infor Item Master. BC item category code maps to Infor product group or commodity code. Unit of measure, costing method (Standard, FIFO, Average), and inventory posting group transfer to Infor's item attributes. For manufacturing editions (M3, LN), BC Items with bills of materials require BOM mapping to Infor BOMH/BOMD (M3) or BOM/Job traveler (LN). We resolve item number assignment and validate against Infor's item number length and character constraints before import.

Business Central Chart of Accounts with country localization template maps to Infor Chart of Accounts structured by company code. BC account type (Posting, Heading, Total, Begin-Total, End-Total) maps to Infor account classification. Account numbers and names transfer directly. We flag any BC account using a numbering scheme incompatible with Infor's account length constraints and recommend renumbering or alias mapping.

Open Business Central Sales Orders migrate to Infor Sales Order with header fields (customer reference, order date, ship-by date) and line fields (item number, quantity, unit price) preserved. BC document status (Released, Pending Approval) maps to Infor order status. Closed and posted orders migrate as order history or invoice history depending on Infor edition. We resolve Customer number to Infor BP code and Item number to Infor item at migration time using the cross-reference tables built in the master data phase.

Open Business Central Purchase Orders migrate to Infor Purchase Order with vendor reference, order date, expected receipt date, and line quantities preserved. BC Prepayment percentages on PO lines map to Infor prepayment handling if the destination edition supports advance payments. Posted AP invoices migrate to Vendor Ledger entries rather than PO documents. We flag any PO line referencing a vendor item number that requires Infor cross-reference resolution.

Historical G/L Entries are scoped to a migration cutoff date (typically 12-24 months) with opening balances carried forward for older periods. BC G/L Entry detail (account number, debit, credit, posting date, source) maps to Infor GL detail lines within each company code. Pre-cutoff balances are summed per account and inserted as opening balance journal entries rather than line-by-line replay. We validate that Infor's fiscal year configuration is aligned with the opening balance date before inserting.

Open Business Central Item Ledger Entries (quantity on hand, pending receipts, pending shipments) map to Infor inventory transactions. BC Value Entry (cost layers) maps to Infor cost layer records. For manufacturing editions, open production orders map to Infor work orders or job travelers. We preserve cost layers by migrating the BC average or FIFO cost layer data into Infor's inventory valuation records. Closed Item Ledger Entries older than the cutoff are not migrated line-by-line; their quantity impact is carried forward in the opening inventory balance.

Business Central Fixed Asset records (acquisition cost, depreciation book, insurance coverage) map to Infor Fixed Asset master. BC depreciation book and depreciation method map to Infor depreciation schedule. Acquisition date and book value transfer directly. We flag any fixed asset with a pending disposal order or revaluation in BC for manual resolution before migration.

Business Central Employee records map to Infor HR master if the destination Infor edition includes HRM functionality. Demographic data, employment information, and bank account details for payroll integration transfer. BC's basic HR capabilities mean that organizations with complex payroll or HR requirements typically use a dedicated HRMS alongside Infor rather than BC's built-in HR. We map employees to the correct Infor HR table and flag any payroll integration dependencies for the customer's HR/IT team.

Business Central Bank Account records (bank details, statement formats, posting groups) map to Infor Bank Master. Open bank account ledger entries migrate as open bank transactions in Infor. Bank reconciliation data from BC transfers as statement records if the destination edition supports bank reconciliation import.

Business Central Jobs (WBS task breakdowns, resource time entries, job journal postings) map to Infor Project management. BC task lines with hours, costs, and billable amounts transfer to Infor project tasks or job traveler lines depending on edition. We flag any BC Job with a status of Completed to exclude from migration unless the customer specifically requires historical project records in Infor.