Migrate from R4 ENTERPRISE to Microsoft Dynamics 365 Business Central

R4 ENTERPRISE Customer records map to Microsoft Dynamics 365 Finance and Supply Chain Management Customer records, carrying address book entries, payment terms, credit limits, and currency assignments. Multi-currency customer preferences migrate as read-only currency settings in D365. The R4 customer ID becomes a reference field; D365 assigns its own customer account number during import. We deduplicate on customer name plus address and flag potential duplicates for customer review before final insert.

R4 ENTERPRISE Vendor master records carry address book entries, 1099 tax reporting flags, W-9 status, and multi-currency settings that map directly to D365 Vendor records. Tax ID fields (EIN/VAT) migrate to the corresponding D365 tax registration fields. Vendor payment terms map to D365 terms of payment groups. Multi-currency assignments preserve as read-only settings in D365.

R4 ENTERPRISE Item master records include unit-of-measure conversions, cost layers, lot and serial controls, and stocking locations. Lot numbers from R4 migrate to D365 inventory batch numbers; serial numbers map to inventory serial numbers. Layered cost records require flattening before load because D365 uses a single costing method per item group (FIFO, average, standard, or moving average) configured at the time of D365 setup. We extract all cost layers, compute the effective cost as of the migration date, and load the single value at cutover. Items marked discontinued in R4 are flagged and not released in D365 unless the customer elects to carry them as inactive.

R4 ENTERPRISE Chart of Accounts records carry account type, cost-center assignments, and intercompany flags that map to D365 main accounts with financial dimension framework. Account segment structures migrate with their full hierarchy preserved. Where R4 uses a flat account number scheme and D365 uses a financial dimension framework with multiple segments, we map the R4 account structure to the D365 chart of accounts hierarchy during setup and confirm the segment mapping with the customer's accountant before import.

R4 ENTERPRISE BOMs carry versioned revisions linked to items with effective-from dates. Each revision may include alternate component allocations and routing steps. Dynamics 365 Finance and Supply Chain Management stores BOM versions with an active status per date range. We extract the currently effective BOM revision based on the R4 effective-from date, flag superseded revisions for customer review, and map the primary BOM to the D365 production BOM with component lines and operations. Routing operations map to D365 production route operations; untyped operations without defined times migrate as informational. Alternate BOMs require a separate BOM version record in D365.

R4 ENTERPRISE open and recently closed work orders carry routings, labor standards, material allocations, and BOM revision references that map to D365 Production Orders. We extract work order status, promised dates, material lines, and operation sequences. Any routing steps referencing a deprecated BOM version are flagged so the customer can re-attach to the current BOM before releasing in D365. Closed work orders migrate as production order history records. Items referenced in work orders but not present in the D365 item master are held in a reconciliation queue pending item setup completion.

R4 ENTERPRISE open sales orders carry customer reference, line items with quantities, pricing, and promised dates that map to D365 Sales Order records. We extract open order headers and lines, flagging any lines that reference discontinued items or inactive price lists. R4 order numbering sequences do not map directly to D365 sales order number sequences; we preserve the R4 order number as a reference field and assign D365 order numbers at import. Lines referencing items not yet released in D365 are held in a reconciliation queue.

R4 ENTERPRISE open purchase orders carry vendor, line items, quantities, and expected receipt dates that map to D365 Purchase Order records. Open PO lines referencing item numbers not present in the D365 item master are flagged for the customer's procurement team to resolve before receipt processing. R4 PO numbering is preserved as a reference field; D365 assigns its own PO number at import. Expected receipt dates and line delivery dates migrate to D365 confirmation dates for planning visibility.

R4 ENTERPRISE open AP vouchers carry vendor, invoice number, due date, functional currency amount, and transaction currency that map to D365 Vendor Invoice records. Multi-currency AP requires exchange rate revaluation at cutover because D365 uses its own exchange rate tables. We preserve the original functional-currency amount and the exchange rate from R4 so the customer's accountant can re-price or keep historical rates per their policy. Closed AP vouchers migrate as reference history unless D365 is configured to carry historical voucher records.

R4 ENTERPRISE open AR invoices carry customer, invoice number, due date, functional currency amount, and transaction currency that map to D365 Customer Invoice or Free Text Invoice records depending on whether the invoice originated from a sales order or is a standalone debit memo. Aging buckets migrate so the D365 collections workspace shows accurate aging from day one. Multi-currency AR requires exchange rate revaluation at cutover using the same approach as AP.

R4 ENTERPRISE on-hand quantities extracted per location and per lot or serial number map to D365 on-hand inventory across warehouse locations. Lot numbers become D365 inventory batch numbers; serial numbers become inventory serial numbers. Bin and location references from R4 map to D365 warehouse location IDs. On-hand balances load as an opening inventory adjustment transaction on the migration date with cost computed from the flattened cost layer.

R4 ENTERPRISE fixed asset records carry acquisition cost, depreciation method, useful life, accumulated depreciation balance, and location that map to D365 Fixed Asset records. We migrate the asset register with current net book value as of the migration cutover date. Depreciation conventions must match D365 fixed asset depreciation groups; we extract the current accumulated depreciation and remaining depreciable base, then set up D365 to continue depreciation from the cutover date rather than recalculating from acquisition.

R4 ENTERPRISE user-defined fields on master records are extracted by field name and value and mapped to D365 custom fields using a customer-approved mapping table built during scoping. D365 custom fields require the customer's administrator to create the field definition in the entity form before data import. We provide the field mapping table and sample transformed values during the staging phase so the customer can provision fields in the D365 sandbox before production migration.

R4 ENTERPRISE user accounts include login name, role assignment, and menu preferences. We export user records and map roles to D365 security roles using a role-equivalence matrix the customer approves during discovery. R4 role names do not map directly to D365 role names; we provide the recommended D365 role assignment for each active user. User provisioning in D365 requires Entra ID assignment, which the customer's M365 administrator handles separately from data migration.