Migrate from Rootstock Cloud ERP to Infor CloudSuite Corporate

Rootstock maintains the full chart of accounts on Salesforce with segment definitions, account types, and intercompany settings. Infor CloudSuite uses a Company-Ledger-GL Account structure where each Company defines the fiscal calendar, currency, and segment schema. We map Rootstock GL accounts to Infor GL Account codes, preserving account type (Asset, Liability, Equity, Revenue, Expense) and any multi-company intercompany flags as Infor Intercompany Account definitions. Multi-currency settings from Rootstock map to Infor Currency tables with appropriate exchange rate handling.

Item master records are the foundational object in both systems. We map Rootstock Item fields (description, stocking policy, costing method, unit of measure, stocking location,ABC code) to Infor Item Master fields including Item Code, Description, Item Group, Unit of Measure, and Costing Method (Standard, Average). Rootstock's lot/serial tracking flag maps to Infor's serial and lot controls on the Item. Any custom Salesforce fields on the Item record are mapped to Infor User Defined Fields or ION User Area tags using XSLT transformations in the Graphical Mapper.

Rootstock stores vendors as Account objects with the Vendor checkbox enabled, plus associated purchase terms, W-9/1099 settings, and EDI identifiers. Infor CloudSuite uses a separate Supplier Master with supplier sites for multi-address vendor management. We map the Rootstock vendor Account to an Infor Supplier with the primary site created from the Account address. EDI identifiers and payment terms migrate to Infor Supplier EDI and Payment Terms respectively. Multiple vendor sites in Rootstock map to multiple Infor Supplier Site records.

Rootstock shares the Salesforce Account object for customer records, with credit limits, payment terms, and tax codes stored on the Account or related custom fields. Infor CloudSuite uses a Customer Master with Customer Sites for multi-address management. We map Rootstock Account records to Infor Customer records, preserving credit limits, payment terms, and tax codes on the Customer or Customer Site. If Rootstock stores tax registration numbers in custom Salesforce fields, those map to Infor Customer Tax Registration records.

Lot and serial traceability in Rootstock links Items to source documents and inventory transactions with full trace and track capabilities. Infor CloudSuite manages lot numbers at receipt and serial numbers at manufacturing or receipt. We migrate lot master records and serial number assignments with their original receipt dates, expiration dates, and associated transaction history. The traceability chain—linking lots and serials to the source Purchase Receipt or Work Order completion—is preserved by migrating the inventory transaction records alongside the lot/serial masters so that the full genealogy remains intact in Infor.

Rootstock Sales Orders include header fields (customer, ship-to, terms, order date) and line items tied to the Item master with pricing, quantity, and scheduling. We map Rootstock Sales Order headers to Infor Sales Order with Order Type, Customer Reference, and terms. Line items map to Infor Sales Order Lines with Item Code, ordered quantity, unit price, and scheduled dates. Open and historical orders migrate with their fulfillment status preserved so that partially shipped orders retain their shipped and back-ordered quantities in Infor. Customer and ship-to addresses resolve to Infor Customer Site references.

Purchase Orders in Rootstock manage direct and indirect materials procurement with header, line items, receipt linkages, and approval status. We map PO headers to Infor Purchase Order with Supplier reference, Currency, and Terms. PO lines map to Infor PO Lines with Item Code, ordered quantity, and unit cost. Vendor records must be migrated first so that the Supplier reference is satisfied at import time. Partial receipt flags and received quantities map to Infor receipt records linked to the PO, preserving the partially received state for in-flight purchase orders.

Purchase Receipts in Rootstock link to POs and update inventory with received quantities, dates, and supplier references. We migrate receipt records with their PO line linkage and received quantities into Infor Purchase Receipts. Receipt dates and partial receipt flags reconcile against the destination PO to ensure that the received quantity does not exceed the PO line quantity. Receipts that reference lot or serial numbers link to the migrated lot/serial masters to maintain the receipt-to-lot traceability chain.

Rootstock BOMs define multi-level component structures with quantities, operations, effective dates, and version control including alternate BOMs for manufacturing constraints. Infor CloudSuite Industrial BOMs use a production version model with Item BOMs, routing sequences, and ECO management through engineering change orders rather than native version tables. We collapse multi-version Rootstock BOMs into a single active revision using an effective-date selection rule (most recent non-future effective date), and we write obsolete BOM version references and their effective date ranges into a custom BOM Version History field on the Infor Item BOM for audit. Alternate BOMs from Rootstock map to separate Infor BOM records with a user-defined alternate code.

Work Orders in Rootstock represent manufacturing operations tied to a Sales Order or standalone job, with routing steps, labor estimates, and material allocations. Infor CloudSuite uses Production Orders as the primary manufacturing execution record with Work Order Master, routing operations, and material reservations. We map Rootstock Work Order headers to Infor Production Order with the Work Order number, linked Sales Order (via Infor Sales Order reference), Planned Start and Due dates, and BOM reference resolved to the migrated BOM revision. Material allocations map to Infor material requisition lines, and routing steps map to Infor Operation records with work center references.

Locations in Rootstock represent warehouses, plants, and stock points with address data, location types, and ABC analysis codes. Infor CloudSuite uses a Warehouse-Location-Bin hierarchy where Warehouses contain Locations (bins or stock points). We map Rootstock location records to Infor Warehouse records, and if Rootstock uses parent-warehouse relationships for multi-level hierarchies, we map those to Infor Warehouse structures. Current on-hand quantities migrate as Infor Inventory balances linked to the mapped Warehouse and Location, with ABC codes preserved as user-defined fields on the warehouse.

ECOs in Rootstock manage BOM and engineering change approvals with affected BOM revisions, approval workflow status, and effective dates. We migrate ECO headers and affected BOM revision links into Infor Engineering Change Order records. Approval workflow history and electronic signature records from Rootstock cannot be fully preserved because Infor's ECO approval model differs. We document the approval chain (approver, date, status) in a custom ECO Approval History field on the Infor ECO record so that the customer has an audit trail even if the native approval workflow requires rebuild.