Migrate from Extensiv Order Manager to Microsoft Dynamics 365 Business Central

Extensiv Orders map to Microsoft Dynamics 365 Sales Order or blanket Sales Quote depending on the order's fulfillment status at migration time. We preserve order number, order date, line items (product, quantity, unit price), shipping fees, warehouse assignment, and order status (pending, processing, shipped, cancelled). Custom Order Info fields migrate to Dynamics 365 custom fields on Sales Line if the admin has activated the custom fields setting in Extensiv Admin > Settings before extraction runs.

Extensiv Customer records split into Dynamics 365 Customer (the account-level record with billing address and payment terms) and Contact (the individual-level record with email, phone, and shipping address). The customer name becomes the Customer Name field; the customer email becomes the primary Contact email. If the customer has multiple contacts, each migrates as a separate Contact record linked to the parent Customer/Account.

Extensiv Products map to Dynamics 365 Items (Business Central) or Products (Sales). SKU maps to Item No. or Product Number; product name maps to Display Name; cost and price fields map to Unit Cost and Unit Price. The product type in Extensiv (standalone, bundle, kit) determines whether the destination record is a standard Item, a BOM-based Item, or an Item with variant codes.

Extensiv bundle and kit products with individual SKU-tracked components translate to Dynamics 365 BOM structures. The parent bundle SKU becomes the BOM header; each component SKU becomes a BOM line with quantity per assembly. Bundle pricing overrides from Extensiv are stored as custom fields on the BOM Item in Dynamics 365. We flag bundle compositions that include discontinued or archived source SKUs and reconcile those before migration so the BOM builds without missing components.

Extensiv inventory levels are warehouse-specific. We map each warehouse in Extensiv to a corresponding Location in Dynamics 365 Business Central, then populate Item Ledger Entries with the warehouse-level stock quantity for each SKU. Customers must designate a canonical warehouse for inventory if multiple Extensiv warehouses map to a single Dynamics 365 location. Open stock transfers (in-transit inventory) map to Transfer Orders with in-transit location specified.

Extensiv Shipment records preserve carrier, tracking number, shipment date, and shipping cost. In Dynamics 365 Business Central, shipment records are created as posted sales shipment lines linked to the original sales order. Tracking URL and carrier information map to custom fields on the shipment record. We validate that the carrier name in Extensiv matches a valid carrier setup in Dynamics 365 before import.

Extensiv Warehouses map to Dynamics 365 Business Central Locations with Location Code and Address preserved. In-house warehouses and 3PL locations each become separate Location records. Warehouse-level filter settings in Extensiv Integration Management that affect order routing do not migrate; we document these for the customer's Dynamics 365 admin to re-implement using Power Automate workflows.

Extensiv Purchase Orders map to Dynamics 365 Business Central Purchase Orders with vendor, PO number, line items, quantities, and status preserved. Inbound receipt records associated with Extensiv POs map to Posted Purchase Receipts in Dynamics 365. We flag any Extensiv PO with a status of partially received so the customer can plan the remaining receipt workflow post-migration.

Extensiv Stock Transfers between warehouses map to Dynamics 365 Business Central Transfer Orders with source location, destination location, and line-item quantities. Cross-warehouse transfers that are in-transit at migration time are flagged as open Transfer Orders; completed transfers are stored as historical records. The customer specifies whether to migrate all historical transfers or only open and recent transfers.

Extensiv Custom Order Info fields on orders require the Enable custom fields setting in Admin > Settings to be active before export. Without this, custom fields are not exposed in the API even if the customer has created them. We confirm this setting is active during discovery and create equivalent custom fields on the Microsoft Dynamics 365 Sales Order or Sales Line table before migration. Any custom field objects that would be unmapped due to the setting being off are flagged in the discovery report.

Pre-configured custom fields under Customers in Extensiv require the same admin opt-in. We verify the Enable custom fields setting during discovery, then create matching custom fields on the Dynamics 365 Customer and Contact tables. Ad-hoc order-level custom fields created at order time map to custom fields on Sales Line. All custom field metadata (field type, label, API name) is captured in the migration specification.

Extensiv Sales Channels (Shopify, Amazon, Walmart, etc.) are stored as integration source metadata on orders. We preserve the channel name as a label or custom field on the Sales Order in Dynamics 365. Channel connection credentials do not migrate; the customer re-establishes these integrations in Dynamics 365 AppSource or via partner connectors post-migration.

Extensiv FIFO cost basis, SKU profitability, and inventory aging reports export as data. We map the exported values to Dynamics 365 Business Central Item Ledger Entries and Value Entries, which store the financial value of inventory movements. Inventory Valuation reports in Dynamics 365 reproduce the Extensiv FIFO view from these migrated entries. We do not migrate the reporting configuration or saved report definitions.