Migrate from MONITOR ERP to Infor CloudSuite Corporate

MONITOR ERP Customer records (address, contact, currency, payment terms) map to Infor Cloudsuite Contact or Party records depending on the target module (Industrial uses Contact; Distribution uses Customer). Currency and payment terms require configuration in Infor OS before migration to avoid validation errors. We use Customer Number from MONITOR as the dedupe key during import.

MONITOR ERP Supplier records mirror the Customer structure and map directly to Infor Cloudsuite Vendor or Supplier records. Linked Purchase Orders and Accounts Payable positions migrate after the Supplier record is validated. We resolve any duplicate Supplier records using the MONITOR Supplier Number as the dedupe key.

MONITOR ERP Items include BOM (Bill of Materials) links, routing data, unit of measure, cost, and inventory levels. We map Items to Infor Cloudsuite Product or Item records, preserving BOM relationships as separate BOM records in the destination. Unit of measure conversions (MONITOR's UoM to Infor's UoM class structure) require a pre-staging mapping table.

MONITOR ERP BOMs embedded in Items decompose into separate Infor Cloudsuite BOM records with line items referencing component Items. The BOM revision and effective date from MONITOR map to Infor's BOM revision control. Multiple BOM versions in MONITOR (for different routing configurations) map to multiple BOM revisions in Infor.

MONITOR ERP Production Orders carry embedded routing, work-centre assignments, and traceability links to lots. These do not map 1:1 to Infor Cloudsuite; we decompose them into a Job header and separate Operation records linked to work centres. Routing steps from MONITOR become Infor Operations with sequence numbers, work centre references, and estimated times. Lot and serial traceability links migrate as Job物料 (Job Material) records with lot number preserved.

MONITOR ERP Customer Orders (sales orders with status, lines, delivery dates, and pricing) map to Infor Cloudsuite Sales Order. Order status from MONITOR (Open, Invoiced, Cancelled) maps to Infor's Order Status with open orders flagged for special handling to avoid duplication during cutover. Pricing and discount logic migrates as order-level adjustments and line-level discounts.

MONITOR ERP Purchase Orders map to Infor Cloudsuite Purchase Orders with status, lines, and expected delivery preserved. Open purchase orders require special handling to ensure that received quantities and pending receipts align with Infor's receiving workflow after cutover. We flag any Purchase Orders with status inconsistencies for manual review before migration.

MONITOR ERP open and historical invoices export via configured file paths. Invoice headers and lines are structured differently between MONITOR and Infor Cloudsuite; we perform field-level mapping and preserve the full line structure including tax codes and discount amounts. Historical invoices migrate with a flag indicating they are closed/paid so that they do not trigger open-invoice workflows in Infor.

MONITOR ERP Journal Entries export in batches via file export with no date-range filtering. We export to a working directory, perform in-house date filtering and chunking (typically by fiscal period), then load into Infor Cloudsuite General Ledger. Account codes require reconciliation against the Infor Chart of Accounts before journal import. Debit/credit amounts and posting dates preserve; any journal entries referencing unmapped account codes go to a suspense account for post-migration reconciliation.

MONITOR ERP Inventory positions (quantity by Item, Warehouse, Lot/Serial) export as stock reports. We map these to Infor Cloudsuite Inventory records with Warehouse and Location mapped from MONITOR's warehouse structure. Lot/serial number fields require dedicated handling if Infor's target module uses lot/serial control; we flag these fields in the scoping report and configure lot/serial number mapping during the pre-migration audit.

MONITOR ERP Account codes, descriptions, and account types export via file. We map these to Infor Cloudsuite Chart of Accounts, noting that MONITOR ERP uses account-numbering conventions that may conflict with Infor's default chart structure. Account code conflicts (same code, different description) require a decision rule during scoping: whether to create new Infor accounts, merge into existing ones, or append a suffix. We deliver a written account mapping table before import begins.

MONITOR ERP Bank accounts and cash accounts export via file paths. We map these to Infor Cloudsuite Bank or Cash Accounts and reconcile opening balances against the latest trial balance. Bank reconciliation data does not migrate; we recommend running bank reconciliation manually in Infor for the first period post-go-live.