Migrate from Ridder iQ to Infor CloudSuite Corporate

Ridder iQ Customer records map to Infor CloudSuite Business Partner with Party Type = Customer. Customer ID, name, billing address, shipping address, payment terms, and credit limit migrate. Infor stores business addresses separately from the Business Partner header, so we split the multi-address records into the appropriate Infor address roles (Sold-to, Ship-to, Bill-to). Any CRM-linked contact records on the Customer in Ridder iQ attach as Person records linked to the Business Partner.

Ridder iQ Supplier records map to Infor CloudSuite Business Partner with Party Type = Supplier. Supplier ID, name, contact info, payment terms, lead times, and bank details migrate. The Infor Business Partner may carry both Customer and Supplier party types on the same record if the entity is both; we flag these dual-role records for customer review during scoping.

Ridder iQ Contact records (linked to Customer or Supplier) map to Infor CloudSuite Person. We preserve email address, phone, role, and the Person-to-Business Partner association. Outlook integration links in Ridder iQ do not migrate; we document the contact list requiring re-association in Infor OS after go-live.

Ridder iQ Item records (raw materials, components, finished goods) map to Infor CloudSuite Item Master. Unit of measure, cost, and supplier-link data migrate to Item Warehouse and Purchasing views. We flag any items using multiple UOMs that require UoM conversion rules to be defined in Infor before the item can be transacted.

Ridder iQ multi-level BOMs with routing steps map to Infor CloudSuite BOM with revision control. Each BOM variant in Ridder iQ (same finished item with different component paths) becomes a separate BOM revision in Infor. We flag items with more than one active BOM variant for customer review: the customer determines which variants represent active production paths versus engineering drafts. Phantom assemblies migrate as BOM lines with Phantom checkbox set.

Ridder iQ BOM routing steps (work center, operation sequence, standard time, setup time) map to Infor CloudSuite Routing with revision control. Routing is stored as a separate object from BOM in Infor, so we reconstruct the BOM-routing linkage by creating matching BOM revision and Routing revision records and linking them on the Work Order. Work center codes from Ridder iQ map to Infor Manufacturing Work Center IDs; we reconcile the work center master during staging.

Ridder iQ Production Orders map to Infor CloudSuite Work Order. We preserve the BOM reference (resolving to the correct BOM revision), routing reference (resolving to the correct routing revision), scheduled start and end dates, quantity, and component allocations. Work center assignments on the production order map to Infor Operation Resource records. Open production orders migrate with their current status; closed production orders migrate as historical records for cost and audit purposes.

Ridder iQ Sales Orders map to Infor CloudSuite Sales Order. Order header data (customer reference, order date, payment terms, shipping terms) and line data (item, quantity, unit price, scheduled dates) migrate. Pre- and post-calculation margin data at the order line level in Ridder iQ requires a discussion during scoping: Infor CloudSuite Industrial does not expose margin fields at the order line by default, so we map margin data to a custom numeric field or discuss whether margin is recomputed post-migration using standard cost and price data.

Ridder iQ Purchase Orders map to Infor CloudSuite Purchase Order. We map PO headers and lines, preserving supplier references (via Business Partner mapping), due dates, and quantities. Open POs with remaining receipt quantities migrate as open; closed POs migrate as historical. Lines referencing BOM-level demand calculations are mapped to standard PO lines with the item reference resolved to the Infor Item Master.

Ridder iQ Projects (engineering-to-order workflows covering R&D, engineering, purchasing, and production phases) map to Infor CloudSuite Project. Budget, milestone, phase, and cost-tracking data migrate as project phases and WBS elements. Phase-specific cost breakdowns map to Infor Project Cost Categories. We flag any Projects with active Production Order linkages so that the Work Order mapping is reconciled against the Project cost ledger after migration.

Ridder iQ Invoices map to Infor CloudSuite Invoice records linked to the corresponding Sales Order or Project. Invoice headers, line items, amounts, and payment status migrate as read-only records for closed invoices. Open invoices requiring further processing migrate with their current status. Payment reconciliation records migrate to Infor's Accounts Receivable or Accounts Payable ledger entries.

Ridder iQ Document attachments (linked to Orders, Projects, Items) migrate as file references to Infor Document Management (IDM). Document metadata (name, description, creation date, attached-to object) migrates; version history and previous revision content do not migrate as they are not reliably extractable from the source file store. We export the file store as a zip archive and deliver it alongside the IDM metadata mapping so the customer's admin can attach files post-migration.