Migrate from inoERP to Microsoft Dynamics 365 Business Central

inoERP GL accounts map directly to the Ledger and Chart of Accounts structure in Dynamics 365 Finance and Operations. The account code, description, type (Asset, Liability, Equity, Revenue, Expense), and currency assignments transfer. We extract the current period trial balance from inoERP and map it to the opening balance in the destination ledger. If the destination is Business Central, the chart of accounts maps to the Chart of Accounts page with Main Account type and dimension categories preserved. Account dimension structures in D365 F&O (Financial Dimensions) require a mapping design decision: inoERP's cost-centre-on-account approach may map to D365's Financial Dimension set framework, and we configure the dimension set during schema design.

inoERP journal entries carry header data (journal batch name, date, description, source module) and line data (account, debit, credit, dimensions, reference). We extract all posted journal entries and map them to D365 F&O General journal lines or Business Central General Journal lines. Entries with non-posting status are flagged for customer review. Intercompany journal entries in inoERP require a dimension-based intercompany mapping design in D365 if multi-entity consolidation is in scope.

inoERP AR subledger contains customer records, open and closed invoices, credit memos, and payment history. Customer party records map to D365 F&O CustTable with address, contact, and payment terms. inoERP invoice headers and lines map to CustInvoiceJour and CustInvoiceTrans respectively. Open invoice status is preserved so that D365 displays correct aging. inoERP's party-based model requires mapping to D365's customer-account structure. Customer-specific price lists and discount groups transfer if configured in inoERP.

inoERP AP subledger includes vendor records, open and closed bills, debit memos, and payment history. Vendor records map to D365 F&O VendTable with the same address and payment terms mapping as the AR side. inoERP vendor invoices map to VendInvoiceJour and VendInvoiceTrans. We extract all posted AP transactions and preserve the invoice approval workflow status where inoERP stores it. Vendor-specific terms and charges require a line-by-line review because inoERP stores some terms as header-level while D365 supports both header and line-level terms.

inoERP item masters store UOM, cost layers (FIFO, Average, Standard), item category hierarchies, and on-hand balances by inventory location. We extract item definitions, on-hand quantities, cost layers, and location assignments. Items map to D365 F&O Released Products with the appropriate product type (Item or Service). Inventory dimension groups in D365 (Site, Warehouse, Location, Batch, Serial) require a mapping decision: inoERP multi-location setups map to D365 Warehouse dimension, and lot and serial number tracking settings transfer if enabled. Cost layer data in inoERP's inventory valuation table maps to D365's InventDim and InventValue tables for open item cost preservation.

inoERP sales orders include header fields (order number, customer reference, dates, terms, warehouse) and line items (item, quantity, price, discount, warehouse). We extract open and closed sales orders by status. Open orders map to D365 F&O SalesTable and SalesLine records for continuation post-migration. Closed orders migrate as historical records with a status flag so they do not trigger fulfilment actions in D365. Header charges, freight, and miscellaneous items in inoERP map to SalesOrderHeaderCharge and SalesOrderLineCharge tables in D365 F&O.

inoERP purchase orders contain vendor references, item lines, quantities, prices, delivery dates, and warehouse assignments. Open purchase orders map to D365 F&O PurchTable and PurchLine records. Closed purchase orders migrate as historical records. inoERP's approval workflow status transfers to D365's purchase order workflow state. Multi-line purchase orders with mixed delivery dates are preserved at line level, and any landed cost components in inoERP map to D365's cargo type and costing version structures.

inoERP work orders contain routing steps, material issues, resource transactions, and completion records. WIP ledger aggregates costs per work order. We extract the full work order history including start and end dates, material consumption, operation resource time, and completion quantities. Active and scheduled production orders map to D365 F&O ProdTable and ProdBOM. The inoERP WIP cost roll-forward maps to the InventValue table in D365 with a WIP dimension so that the customer's finance team can reconcile work-in-progress balances post-migration. Historical completed work orders migrate as closed production orders.

inoERP BOMs and routings define product structures and manufacturing steps with multi-level BOM support and super BOM capability. We export the full BOM hierarchy and routing sequence including phantom BOMs and co-products. Phantom BOMs and configurable BOMs in inoERP map to D365 F&O BOM versions with the appropriate BOM type (Phantom or Static). Routing operations, work centre assignments, and process times transfer to D365 route versions with the same operation sequence. BOM explosion in D365 during production order creation will recalculate based on D365's lot sizing rules, which may differ from inoERP's dynamic pull calculations, and we document this divergence during scoping.

inoERP HR module contains employee profiles, job definitions, position assignments, compensation records, and leave balances. We extract employee records and position assignments. Compensation history (salary, bonuses, deductions) migrates to D365 HR Core Worker compensation structures. inoERP leave balances map to D365 HR Core leave plans, though leave plan template configuration is required post-migration because leave types and accrual rules differ between platforms. inoERP role-based access control maps to D365 Security roles, though the role permission model differs and we document the mapping rather than apply it automatically.

inoERP asset registers include acquisition details, depreciation schedules, and asset categories. We export the full asset record including acquisition cost, book value, accumulated depreciation, and the depreciation method. Asset records map to D365 F&O Fixed Assets with the same acquisition date, acquisition cost, and depreciation convention. Depreciation methods (straight-line, declining balance, units of production) transfer with the same parameters, and the customer's fixed asset register opening balance posts to the general ledger through D365 Fixed Asset posting profiles.

inoERP users and role-based access control records export as user accounts with role assignments. We map inoERP roles to D365 F&O Security roles and duty/privilege sets. Because the permission models differ significantly between platforms, we provide a role-mapping matrix rather than a direct permission transfer. The customer's D365 admin reviews and assigns security roles post-migration based on the mapping matrix we deliver.

inoERP payroll generates electronic bank files for direct deposit via its customisable JavaScript REST API. We export payroll registers, leave balances, and compensation history. Bank file formats are inoERP-instance-specific and require a custom transformation to match the customer's payroll processor format. D365 HR Core payroll integration is typically handled through a payroll add-on (such as ADP, Blue-badge, or another certified payroll provider), and we document the payroll data export format so the customer's payroll partner can configure the integration.