Migrate from Shipedge to Infor CloudSuite Corporate

Shipedge Orders map to Infor Sales Order (or Distribution Order depending on CloudSuite edition). The Shipedge order number becomes the external order reference in Infor; order status (pending, shipped, cancelled) maps to Infor's order status codes. Shipedge's line items map to Infor order detail lines with SKU resolved to the Infor Item Master. We resolve Warehouse location from Shipedge's routing rules and set the Infor ship-from warehouse accordingly. Open orders migrate as open; closed orders migrate with full fulfillment history preserved.

Shipedge Products (SKUs with variant attributes) map to Infor Item Master records. The Shipedge SKU becomes Infor Item Number; variant attributes (size, color, material) map to Infor's item specifications or UDFs. Supplier links from Shipedge Product records attach to Infor Supplier items. Barcodes migrate to Infor Item Bar Code records. Kit configurations from Shipedge migrate as Infor BOMs with assembly steps if the destination CloudSuite edition includes manufacturing.

Shipedge inventory is warehouse-site-specific with location-aware quantities, lot numbers, and bin assignments. We export per-warehouse inventory snapshots and map them to Infor's inventory ledger per warehouse site. Bin and lot data migrates to Infor Inventory Location and Lot/Serial records respectively. Note: if lot numbers were never entered in Shipedge (common in fast-moving SKU environments), they will not appear in the export. Infor's multi-warehouse configuration requires each Shipedge warehouse to be pre-created as an Infor Site.

Shipedge Customer records (billing/shipping addresses, contact info, order history) map to Infor Customer Master. The customer email becomes the Infor contact key; addresses map to Infor ship-to and bill-to locations. Customer-specific pricing or discount tiers from Shipedge map to Infor price lists attached to the Customer Master. Custom fields or customer tags on Shipedge records require custom field mapping in Infor's UDF structure.

Shipedge Suppliers (contact details, lead times, linked to Purchase Orders) map to Infor Supplier Master. Shipedge supplier SKU references migrate as supplier item cross-references in Infor. Custom fields on Shipedge Supplier records vary by account configuration; we map standard fields (name, email, phone, address) and flag any custom fields for Infor UDF mapping during discovery.

Shipedge shipment records (carrier, service level, tracking number, weight, dimensions) map to Infor shipment records linked to the corresponding Sales Order. Carrier codes and service-level values transform to Infor carrier and method codes. Tracking URLs migrate as shipment notes. Historical shipment records preserve the original shipping cost from Shipedge for audit trail purposes.

Return Authorizations, return reasons, and disposition codes from Shipedge's reverse logistics module map to Infor RMA records. Disposition mappings (restock vs. dispose vs. return to supplier) translate to Infor disposition codes. Open RMAs migrate as active; closed RMAs preserve disposition history. We flag disposition code differences between Shipedge and Infor during scoping so the customer can confirm the mapping before migration.

Shipedge warehouse sites (each with own inventory pool, picking workflows, and shipping accounts) map directly to Infor Sites. We export warehouse address, operating hours, carrier accounts, and picking workflow flags from Shipedge and configure the equivalent Infor Site records before inventory migration begins. Multi-warehouse Shipedge customers require each site to be pre-created in Infor as a prerequisite for inventory load.

Shipedge Order Rules define automated routing logic (warehouse selection, carrier assignment, split-order conditions) based on account-specific configurations. These rules are stored in Shipedge's proprietary format with no documented export mechanism. We flag all active Order Rules during discovery with their trigger conditions and actions, and the customer manually re-implements them in Infor (typically 1-3 days of manual work depending on rule complexity). This object is flagged as NOT migrating automatically.

Shipedge channel integrations (Shopify, Amazon, Walmart, Magento) store OAuth tokens and API credentials bound to Shipedge's app registrations. We cannot export these secrets for security reasons. We export the full list of active integrations with their configuration parameters (order pull rules, inventory sync settings, channel-specific mappings) so the customer's admin can re-authorize each connection in Infor ION or the equivalent channel connector. This is a manual reconnection step, not an automated data migration.

Shipedge User accounts (name, email, role, warehouse assignments) map to Infor User or Employee records. We export user name, email, and role from Shipedge but cannot transfer authentication credentials; users must be provisioned fresh in Infor with new passwords. Role mappings from Shipedge (warehouse picker, admin, manager) map to Infor role assignments. Inactive Shipedge users migrate as inactive Infor users unless the customer specifies otherwise.

Shipedge Batch Fulfillment View (v11+ feature) groups orders into batches for warehouse picking. Batch records include batch number, order count, SKU count, units, and ship method. We export batch metadata and link it to the corresponding migrated orders in Infor. Batch-level picking workflows in Infor need to be reconfigured per Infor's warehouse execution module since batch representation differs from Shipedge's v11 batch view.