Migrate from Extensiv Order Manager to Infor CloudSuite Corporate

Extensiv Orders map to Infor CloudSuite Sales Order records. We preserve order number, order date, customer reference, order status, channel assignment, line items with SKU and quantity, handling fees, and shipping cost. Channel assignments from Extensiv (Shopify, Amazon, Walmart, etc.) are preserved in a custom field or Business Partner role in Infor. We audit the Integration Management Skipped Orders log before scoping to confirm no orders are excluded by filter mismatches in Order Status, Payment Status, or date range.

Extensiv Customer records map to Infor CloudSuite Business Partner entries. We preserve contact fields, billing address, shipping address, and any pre-configured custom fields associated with the customer record. Business Partner role (Customer, Vendor, or both) is assigned during import based on whether the Extensiv customer also has associated Purchase Orders or is only an order source.

Extensiv Products map to Infor CloudSuite Item master records. We preserve SKU (mapped to Item Code), product name, description, standard cost, standard price, and unit of measure. The Extensiv hs_sku equivalent maps to the Item Code or an alias in Infor. Products are imported before inventory so that Item references are satisfied when stock positions load.

Extensiv stores per-warehouse inventory levels. We aggregate or split these into Infor CloudSuite Location-level stock positions. Customers must designate canonical warehouse(s) during discovery. If the customer runs multiple active fulfillment locations in Extensiv, we create corresponding Location records in Infor and map each warehouse's stock separately. Lot and serial number assignments from Extensiv Warehouse Manager carry into Infor if the destination uses lot control; otherwise they are flagged as requiring manual reconciliation.

Extensiv Shipment records map to Infor CloudSuite Shipment records, preserving carrier, tracking number, shipment date, and shipping cost. We validate that carrier codes in Extensiv have corresponding carrier codes in Infor; unmapped carriers are logged for admin configuration before shipment import.

Extensiv Warehouses map to Infor CloudSuite Location records. We preserve warehouse name, warehouse ID, and currency. Infor Location records carry additional configuration (site, company code, address structure) that we complete during schema mapping. Warehouse-level filter settings in Extensiv Integration Management do not migrate; they are documented as a configuration task for the customer post-migration.

Extensiv Purchase Orders map to Infor CloudSuite Purchase Order records with vendor, PO date, PO status, and line items. Vendor records must exist in Infor before PO import, so we run vendor validation during discovery and flag any Extensiv vendors without matching Infor Business Partner records. The customer's admin creates missing vendor records before PO migration begins. Inbound receipt records from Extensiv map to Infor PO receipt or goods receipt records.

Extensiv Stock Transfers between warehouses map to Infor CloudSuite Transfer Order records. We preserve source warehouse, destination warehouse, line item quantities, and transfer status. In-flight transfers (status other than Complete) are flagged as requiring customer review because they represent open movement of inventory that may not cleanly map to Infor's transfer order state machine.

Extensiv Bundle and Kit products with parent-child SKU relationships map to Infor CloudSuite kit structures. We preserve bundle composition (component SKUs, quantities), pricing overrides at the bundle level, and component-level inventory assignments. Infor CloudSuite supports kit configurations that define the allowed components and exploded view; we use the Extensiv bundle breakdown as the source of truth for component relationships.

Extensiv custom fields on orders and customers require the 'Enable custom fields' admin setting to be active before extraction. We confirm this during discovery. Custom field values are mapped to Infor CloudSuite extended attributes or custom fields on the corresponding entity. Ad-hoc order-level custom fields migrate as order attributes; pre-configured customer-level custom fields migrate as Business Partner extended fields.

Extensiv Sales Channels (Shopify, Amazon, Walmart, etc.) are stored as integration sources assigned per order. We map channel assignments to an Infor Business Partner role type or to a custom attribute field on the Sales Order, depending on whether the customer uses Infor's channel management configuration. Channel connection credentials do not migrate; we document the channel list for the customer to re-establish integrations post-migration.