Migrate from Shipedge to Microsoft Dynamics 365 Business Central

Shipedge Orders map to Dynamics 365 Business Central Sales Orders for open orders and Posted Sales Invoices for fulfilled orders. The Shipedge order number becomes the External Document Number on the Dynamics 365 document. Order status (pending, processing, shipped, cancelled) maps to the corresponding Sales Document Status values. Line items migrate as Sales Order Lines with Item No., quantity, unit price, and discount percent. Shipping address from Shipedge becomes the Sell-to Address on the header; billing address becomes the Bill-to Address.

Shipedge Products (SKUs with variants) map to Dynamics 365 Business Central Item records. The Shipedge SKU becomes the Item No.; the product name becomes the Description. Shipedge variant attributes (size, color) map to Business Central Product Variants if the customer's Business Central edition supports them, or to Item dimensions (Size, Color) if configured as shared dimensions. Barcode data migrates to the Item's bar code field. Supplier SKU from Shipedge's supplier links migrates to the Item's Vendor No. and Vendor Item No. fields.

Shipedge's warehouse-site-specific inventory quantities map to Dynamics 365 Business Central Item Ledger Entries under each Location. We create a Location record in Business Central for each Shipedge Warehouse, preserving the address and operating hours. Quantities per bin and lot number in Shipedge map to Business Central Bin Content records and Item Tracking Lines respectively. If Shipedge lot numbers were never entered (common in fast-moving SKU environments), only the quantity figures transfer.

Shipedge Customer records (billing and shipping addresses, contact info, order history associations) map directly to Dynamics 365 Business Central Customer records. The customer's email becomes the Contact field, the billing address maps to the Bill-to Address, and the shipping address maps to the Ship-to Address. Shipedge customer-specific pricing rules that are stored as custom fields are flagged for mapping to Customer Price Groups or Line Discount groups in Business Central.

Shipedge Suppliers (contact details, lead times, linked to Purchase Orders) map to Dynamics 365 Business Central Vendor records. The supplier name, email, phone, and address migrate to the Vendor Card. Lead time data from Shipedge supplier records becomes the Base Calendar and lead time fields on the Vendor. Custom fields on Supplier records vary by account configuration; we map standard fields and flag custom fields for manual Business Central extension field creation before migration.

Shipedge shipment records (carrier, service level, tracking number, weight, dimensions) map to Dynamics 365 Business Central Posted Sales Shipment records linked to the corresponding Sales Order. The carrier name maps to the Shipping Agent field; tracking number becomes the Tracking Number on the shipment line. We preserve the full shipment history and map service level values to the appropriate Shipping Agent Service in Business Central.

Shipedge Return Authorizations with return reasons and disposition codes map to Dynamics 365 Business Central Sales Return Orders for open returns and Posted Sales Credit Memos for processed returns. The Shipedge return reason maps to the Reason Code field on the Business Central return document. Disposition codes (restock vs. dispose) map to the appropriate Return Reason Code in Business Central. We flag any disposition mappings that require configuration of Business Central's Return Reason setup.

Shipedge's multiple warehouse sites map to Business Central Location records, each with its own inventory pool, picking workflows, and shipping accounts. The Location Code becomes the primary inventory dimension for all Item Ledger Entries. We export warehouse address and carrier account associations from Shipedge and document them for configuration in Business Central's Shipping Agents and Locations setup.

Shipedge kit (bundle) configurations define which SKUs compose a kit and whether kitting is on-the-fly or pre-built assembly. We export kit structure and component links. On-the-fly kits map to Business Central Sales Kit items (if using the Sales Kit extension) or to a Bill of Materials if the kit is assembled. Pre-built assemblies map to Production BOM records. The customer chooses the kit representation strategy during scoping based on Business Central edition and manufacturing requirements.

Shipedge Batch Fulfillment View records (v11+ feature grouping orders into batches for warehouse picking efficiency) map to Business Central Warehouse Shipment lines and pick documents. Batch number, order count, SKU count, and units migrate as Warehouse Shipment header metadata. Ship method from the batch becomes the Shipping Agent and Agent Service on the shipment. We note that Business Central's directed picking and put-away rules may require reconfiguration of the warehouse's location directives.

Shipedge user accounts (login credentials, roles, warehouse assignments) map to Dynamics 365 Business Central User records. We export user name, email, and role. Authentication credentials cannot transfer; users must be provisioned fresh in Business Central through Microsoft 365 admin center. Role assignments from Shipedge map to Business Central Permission Sets (Essential, Standard, or custom) based on the user's warehouse and OMS responsibilities.

Shipedge Order Rules automate routing decisions (warehouse selection, carrier assignment, split-order logic) based on account-specific configurations. These are Shipedge-specific workflow configurations with no documented export mechanism. We flag all active Order Rules during discovery, document each rule's trigger conditions and actions, and deliver a written inventory with recommended Business Central Location Directives (for warehouse and bin selection) and Power Automate flow equivalents for the customer's admin to rebuild post-migration.