Migrate from R4 ENTERPRISE to Infor CloudSuite Corporate

R4 ENTERPRISE Customer records map to Infor CloudSuite Business Partner with Customer role. We extract customer name, address, contact details, credit limits, payment terms, and currency preferences, preserving the original R4 ENTERPRISE customer ID as a reference field. Multi-currency assignments migrate as read-only destination-currency preferences. Customer open order counts and outstanding AR amounts flag during reconciliation so the destination AR aging reflects reality at cutover.

R4 ENTERPRISE Vendor master records map to Infor CloudSuite Business Partner with Vendor role. Address book entries, 1099 flags, W-9 status, and multi-currency settings migrate with vendor IDs mapped to destination vendor numbers. Tax ID fields (EIN/VAT) map to Infor CloudSuite tax registration fields. Open PO reference numbers are preserved as cross-references for accounts payable reconciliation.

R4 ENTERPRISE Item master records migrate to Infor CloudSuite Item Master with unit of measure conversions, cost method settings, and stocking locations. We extract the item's default stocking location, item type (manufactured, purchased, phantom), and planning parameters. Lot and serial controls migrate from R4 ENTERPRISE lot control flags to Infor CloudSuite lot master configuration. Active/inactive item status is preserved; discontinued items are flagged in a separate reconciliation list for the customer to review before inventory snapshot.

R4 ENTERPRISE BOMs are versioned with each revision linked to a specific effective date and item revision. We extract the active BOM revision and flag superseded revisions so Infor CloudSuite receives only the current production version. Routing steps tied to deprecated BOM versions are excluded. Phantom BOMs, co-product and by-product structures, and kitting assemblies migrate with component quantities and operation sequences preserved. We cross-reference each component item against the destination item master to flag any components referencing inactive or discontinued SKUs.

Open work orders carry routings, labor standards, and material allocations referencing active BOM revisions. We migrate open and closed work orders, flagging any routing steps tied to deprecated BOM versions that may not apply in the destination. Work order status (released, in progress, completed, closed) maps to Infor CloudSuite production order status codes. Material issue and labor posting records migrate as historical transactions if the destination supports transaction history import, or as reference records if only current balances are supported.

R4 ENTERPRISE chart of accounts includes account type, cost-center assignments, and intercompany flags. We map the full account hierarchy and preserve segment structures (company, department, division, region) when the destination CloudSuite edition supports matching segment configurations. Account IDs, descriptions, and type assignments migrate 1:1. Intercompany flags map to Infor CloudSuite's intercompany trading partner configuration if multi-entity consolidation is in scope.

Open AP vouchers include vendor, invoice number, due date, and amount in both transaction currency and functional currency. We preserve the original functional-currency amounts and the exchange rate used at invoice entry so Infor CloudSuite can either re-price using current rates or keep historical rates at the customer's election. Closed invoices export as reference history unless the destination supports full AP invoice history import. We flag any AP records referencing vendors not present in the migrated vendor master for resolution before the AP snapshot.

Open AR invoices carry customer, invoice number, due date, and amount in transaction and functional currency. We preserve open invoice aging buckets so Infor CloudSuite maintains accurate cash-flow reporting from day one. Multi-currency AR invoices carry the original exchange rate; we store the rate in a custom field or notes column so revaluation options are clear at cutover. Closed invoices migrate as historical reference unless the customer requests full AR history transfer.

On-hand quantities are extracted per location and per lot/serial number from R4 ENTERPRISE's inventory child tables. We preserve lot numbers, bin locations, and lot expiration dates so the Infor CloudSuite inventory snapshot matches physical reality at cutover. Cost layer histories are extracted as separate child records; if Infor CloudSuite uses average or standard costing, we flatten layered cost records into a single effective cost per item per lot at the migration date. FIFO lot costing migrates directly to Infor CloudSuite's lot cost fields.

R4 ENTERPRISE fixed asset records include acquisition cost, depreciation method, useful life, and location. We migrate the asset register and accumulated depreciation balance as of the migration cutover date. Asset tag numbers map to Infor CloudSuite asset identification fields. Depreciation method (straight-line, declining balance, units of production) migrates to the equivalent Infor CloudSuite depreciation method. Asset book values and accumulated depreciation are reconciled to the general ledger before final migration to ensure balance sheet continuity.

Open sales orders carry customer, line items, quantities, pricing, and promised dates. We extract open orders and flag any that reference discontinued items, inactive price lists, or customer accounts not present in the migrated destination data. Line items with partial fulfillment migrate with remaining quantity and shipped quantity separated. Order hold and credit-hold status maps to Infor CloudSuite order status codes. Price list references migrate to Infor CloudSuite price lists for validation.

Open POs include vendor, line items, quantities, and expected receipt dates. We migrate open PO headers and lines, flagging any PO lines that reference item numbers not present in the destination item master. Partial-receipt PO history migrates as open receipt records. Vendor lead times and PO approval status migrate to Infor CloudSuite PO configuration fields. Scheduled shipment dates are preserved for production planning alignment.