Migrate from MRPeasy to Infor CloudSuite Corporate

MRPeasy Items map to Infor Part Master records. The MRPeasy item number becomes the Infor part number; description, cost, and unit of measure map to Infor Part Master fields. On MRPeasy Professional and above, custom fields on Items require pre-creation of matching Infor user-defined fields in the Part Master schema before import. We flag any Items referencing inactive vendors for manual reconciliation before the Part Master load.

MRPeasy BOMs (multi-level, co-product, and disassembly BOMs on Professional+) map to Infor BOM structures. We resolve the parent item reference and all component line items in dependency order so that child-level BOMs exist before parent-level BOMs reference them. Co-product BOMs map to Infor by-product or co-product BOM types. The MRPeasy BOM quantity-per and operation waste/scrap percentages transfer to the Infor BOM line quantity and scrap fields.

MRPeasy Routings define the production operation sequence, workstation assignments, and labor times. Infor separates Work Center definition from Routing assignment. MRPeasy Workstations must be created as Infor Work Centers before the Routing can reference them. MRPeasy's operation overlap and parallel execution flags map to Infor Routing backflush and concurrent operation settings. If the MRPeasy customer used piece-payment operations, those map to Infor labor rate configurations.

MRPeasy Manufacturing Orders link BOM and Routing to actual production. Open or active Manufacturing Orders in MRPeasy trigger Dynamic Rescheduling on import — Infor recalculates start/end dates based on Work Center capacity and current Routing after any relevant data change. We flag open MOs during scoping, advise customers to close or freeze orders before export where possible, and document the post-import reschedule delta as a reconciliation item.

MRPeasy Vendors map to Infor Supply Chain Parties (of type Supplier). We follow MRPeasy's documented dependency order by loading Vendors before Items because Items reference vendor purchase terms. Purchase Terms per vendor-item pair transfer as Infor supplier price agreements. Multi-currency vendor terms from MRPeasy map to Infor currency codes on the supplier record.

MRPeasy Customers map to Infor Distribution Chain records. MRPeasy's customer code becomes the Infor customer ID; name, contact, address, and tax ID map to the corresponding Infor fields. Price List assignments from MRPeasy become Infor price/discount agreements linked to the customer record. If the MRPeasy customer used B2B Customer Portal (Professional+), that maps to Infor's customer-facing portal configuration separately.

Current stock quantities and costs per storage location in MRPeasy map to Infor inventory records at the warehouse level. MRPeasy's 3,000-line CSV import cap means large multi-site inventory files must be chunked before staging — a 10,000-item warehouse requires at least four import passes. We segment large datasets before the Infor load and track partial completion to avoid duplicating already-migrated records. Infor's multi-warehouse structure supports the customer's multiple storage locations as separate warehouse codes.

MRPeasy Stock Lots with batch traceability, expiry dates, and received status map to Infor Lot/Batch Master records. Lot number, quantity, expiry date, and storage location assignment transfer directly. MRPeasy's received-status-on-creation flag maps to Infor's lot status field. If the MRPeasy customer used Serial Number tracking on Professional+, those map to Infor serial number records linked to the Lot.

MRPeasy Price Lists define customer-specific or product-specific pricing. We map price list lines to Infor price agreements with effective date ranges, currency codes, and break quantities. MRPeasy's tiered pricing (available on Professional+) maps to Infor quantity-based price break structures. Currency preservation is critical for multi-currency customers migrating from MRPeasy's multi-currency configuration.

MRPeasy Transfer Orders moving stock between sites and storage locations map to Infor Inventory Transfer Orders. The lifecycle (New, Ready, Shipped, Received, Canceled) transfers with status. MRPeasy requires manual status change to 'Received' after goods arrive — this does not auto-complete. We document any in-transit Transfer Orders as a cutover checklist item requiring manual receipt completion before going live in Infor.

MRPeasy Custom Fields (Professional+ tier) must be replicated as User-Defined Fields in the Infor schema before any dependent data imports. We extract custom field definitions from MRPeasy Settings, map field types to equivalent Infor UDF data types, and create the destination UDFs in the Infor staging environment before record migration begins. Custom fields on BOMs, Items, and Manufacturing Orders require special sequencing because their import depends on the UDF schema existing first.

MRPeasy User records (name, email, role, active/inactive status) map to Infor User records with role-based security assignments. We extract active users from MRPeasy Settings -> User management and map role assignments to Infor security groups. Inactive users are archived in Infor rather than imported as active. Any MRPeasy custom permissions or approval system configurations do not migrate and are flagged for manual rebuild in Infor's role configuration.