Migrate from Lead Commerce to Infor CloudSuite Corporate

Lead Commerce Customer records map to Infor CloudSuite Customer (or Supplier depending on party type). The customer name, contact details, email, phone, and address fields migrate directly. We deduplicate by email during import and preserve the customer-to-order linkage so that historical order context is not lost. If the destination Infor edition uses party-based architecture (Customer and Supplier as separate entities), we split by Lead Commerce's party type flag during the transform phase.

Lead Commerce inventory items carry SKU, description, unit of measure, cost, and stock level per warehouse. These map to Infor CloudSuite Item Master records. We flag any items with zero or negative quantities that may indicate data quality issues at the source. Unit of measure conversions require a mapping table if Lead Commerce uses non-standard UOM codes; Infor requires standard UOMs attached to the item record.

Lead Commerce warehouse records define physical locations where stock is held. These map to Infor CloudSuite Warehouse records, which must be replicated or consolidated depending on whether the target Infor edition supports the same warehouse hierarchy. Multi-location inventory in Lead Commerce requires per-warehouse record mapping so that stock levels land in the correct Infor warehouse context.

Lead Commerce order records with lifecycle stages (pending, processing, shipped, completed) map to Infor CloudSuite Sales Order. We separate fulfilled from open orders during migration scoping. Completed orders land as historical records in Infor; open orders require careful cutover planning because Infor enforces transaction-status sequencing that Lead Commerce does not. Orders created during the migration window require manual entry post-migration or a pause in order creation at cutover.

Lead Commerce PO records represent supplier-facing orders and map to Infor CloudSuite Purchase Order. Open POs and received POs need separate treatment. Received PO lines should map to landed inventory in Infor while open lines represent commitments that may need manual follow-up at the destination. Infor enforces PO approval workflows that may need to be configured post-migration if the source PO statuses do not map to Infor's approval states.

Lead Commerce user accounts and role assignments export as a flat list. We preserve role names and map them to Infor CloudSuite permission groups. The customer's Infor admin provisions matching User accounts before production migration so that OwnerId references on orders and POs resolve correctly. Users without a matching Infor account go to a reconciliation queue.

Lead Commerce custom app data that lives in the platform's database is flagged separately in our scope document. The app logic itself cannot be transferred and must be rebuilt or re-platformed at Infor. We identify any custom app data fields that overlap with standard objects (Customer, Order, Item) and include them in the standard migration where possible, but the application code requires a separate rebuild engagement.

Lead Commerce does not expose saved reports or historical analytics data through its export mechanisms. Customers who rely on period-end reporting in Lead Commerce should pull those reports as PDFs or screenshots before migration cutoff. We include a reporting export step in our pre-migration checklist. Infor CloudSuite custom reports must be rebuilt in Birst or another approved reporting tool; organizations with hundreds of saved reports should budget this rebuild effort separately.

Lead Commerce order line items (product, quantity, unit price, discount) map to Infor CloudSuite Sales Order Line. We resolve the Item reference (from the Item Master import) and the Sales Order header reference at migration time. Tax and shipping amounts from Lead Commerce map to Infor order-level charges where the Infor edition supports them.

Lead Commerce PO line items map to Infor CloudSuite Purchase Order Line. Line status from Lead Commerce (open, partial, received, closed) maps to Infor's PO line receipt status. We flag any lines with partial receipts so that the customer's Infor admin can decide whether to receive remaining quantities against open POs or close them and create new orders.

Lead Commerce stores stock levels per item per warehouse location. Infor CloudSuite maintains item stock at the warehouse level. We split each Lead Commerce inventory record by warehouse and create corresponding item stock records in Infor for each location. Zero-quantity items are imported with zero stock and flagged for the customer's review; negative quantities indicate data quality issues that require cleansing before import.