Migrate your Shipedge data

Orders is Shipedge's central object, spanning omnichannel sources (Shopify, Amazon, Walmart, etc.), fulfillment status, shipping method, and tracking. We export full order records including line items, addresses, and metadata via REST API v4 (OMS). All standard fields map 1:1 to most destination systems.

Products carry SKU-level details, variant attributes (size, color), supplier links, and barcodes. Shipedge organizes these in a dedicated Product Catalog module. We extract Products via the WMS API and preserve variant parent-child relationships in the target import.

Inventory is warehouse-site-specific in Shipedge's WMS, with location-aware quantities, lot numbers, and bin assignments. We export per-warehouse inventory snapshots and map them to destination inventory objects or warehouse records.

Suppliers in Shipedge store contact details, lead times, and are linked to Purchase Orders. Custom fields on Supplier records vary by account configuration, so we map standard fields (name, email, SKU associations) and flag any custom properties for explicit value mapping before load.

Customer records in Shipedge include billing and shipping addresses, order history associations, and contact info. Name, email, and address fields are standard; custom fields or customer tags require field-level mapping to destination equivalents.

Shipedge tracks shipment records linked to orders, including carrier, service level, tracking number, weight, and dimensions. We preserve full shipment history and map carrier and service-level values to the destination system's shipping object schema.

Return Authorizations, return reasons, and disposition codes are tracked in Shipedge's reverse logistics module. We export return records and flag disposition mappings (e.g., restock vs. dispose) since destination systems use different enumeration values for return statuses.

Integration configurations (channel connections, order pull rules, inventory sync settings) are account-specific. We export integration records to document which channels are active, but the connection credentials and rule sets require manual reconfiguration in the destination platform.

Order Rules define automated routing logic (e.g., warehouse selection, carrier assignment, split-order conditions). These are Shipedge-specific workflow configurations that need to be manually recreated or re-implemented in the destination OMS since rule engines vary significantly between platforms.

Batch Fulfillment View is a v11+ feature grouping orders into batches for warehouse picking efficiency. Batch records include batch number, order count, SKU count, units, and ship method. We export these as linked metadata on the associated orders.

Kit (bundle) configurations define which SKUs compose a kit and whether kitting happens on-the-fly or as pre-built assemblies. We export kit structure and component links but note that kit representation differs across platforms and may require redefinition at the destination.

User accounts store login credentials, roles, and warehouse assignments. We export user name, email, and role but cannot transfer authentication credentials; users must be provisioned fresh in the destination system with roles mapped manually.

Shipedge's WMS supports multiple warehouse sites, each with its own inventory pool, picking workflows, and shipping accounts. We export warehouse records including address, operating hours, and carrier configuration so the destination can replicate site-level setup.