Migrate from eCommerce Pro to Microsoft Dynamics 365 Business Central

eCommerce Pro Products with variants map to a Dynamics 365 Released Product master with Product Variants generated from the variant dimension combination (typically Size, Color, and Style). We compute the Product Dimension combinations from the eCommerce Pro variant rows at migration time, create the Released Product, then attach the variant records. The source product description, metafields, and SEO metadata map to Product Description, Product Attribute, and a custom attribute holding the original URL slug for redirect mapping.

Each eCommerce Pro variant (combination of size, color, material, etc.) becomes a distinct Product Variant in Dynamics 365 via the Product Dimensions feature. The variant SKU maps to the Product Number; variant-level pricing (if held in the variant rather than in a separate price list) maps to Trade Agreement lines scoped to the specific variant.

eCommerce Pro product categories and subcategories map to the Dynamics 365 Category Hierarchy. We preserve the full category path (e.g., Footwear > Running > Trail) and attach it to each Released Product through the Category Assignment entity. The customer's category management workflow in Dynamics 365 Admin is rebuilt using the standard Category hierarchy editor.

eCommerce Pro customer accounts map to a Dynamics 365 Account (company) with a primary Contact record. Billing and shipping addresses from the eCommerce Pro account split into the Account address fields. B2B company hierarchies (parent-child distributor relationships) map to the Dynamics 365 Account Hierarchy feature where the source distinguishes company-level accounts. Guest checkout customers (no account) are created as Contacts without an Account parent.

eCommerce Pro stores multiple addresses per customer (billing, delivery, pickup). Dynamics 365 Finance and Operations allows multiple address roles on an Account but only one address per purpose role. We consolidate: the primary billing address becomes the Account Invoice Address; the primary shipping address becomes the Account Delivery Address; additional addresses are stored as Contact address records attached to the primary Contact.

eCommerce Pro orders map to Microsoft Dynamics 365 Sales Order. The original order date becomes the Order Date; order status maps to a Sales Order Status aligned with the configured Sales Order workflow. Discount amounts from the source line item map to Line Discount; order-level discounts map to the header discount field. Tax lines from the source (where the eCommerce Pro tax engine produced a calculated amount) are held as separate tax lines mapped to the corresponding Tax Group in Dynamics 365.

eCommerce Pro order line items map to Sales Lines with Product ID (lookup to Released Product), Quantity, Unit Price, Line Discount, and Tax Line. Gift card line items (if active) are flagged in a custom field since Dynamics 365 treats gift cards as a separate payment method rather than a product. Refunded lines are migrated as credit note lines attached to the original order.

eCommerce Pro inventory quantities per warehouse map to Dynamics 365 On-hand Inventory entries by Site and Warehouse. The source warehouse name becomes the Dynamics 365 Warehouse ID. Multi-warehouse setups require us to configure the Inventory Dimension group (Site, Warehouse, Location) before import so that On-hand entries carry the correct dimensional breakdown. Inventory Dimension groups are set per Released Product, not globally, and must be configured before on-hand data is loaded.

eCommerce Pro fulfillment records with carrier, tracking number, and shipment date attach to the corresponding Microsoft Dynamics 365 Sales Order as a Shipment entity. The tracking URL is stored in a custom Shipment field. If the destination uses the Dynamics 365 Warehouse Management System (WMS) module, the fulfillment record also generates a WMS Work line (Pick, Pack, Ship) that is attached to the Sales Order.

eCommerce Pro percentage discounts and fixed-amount coupons map to Dynamics 365 Trade Agreement Journal lines with the appropriate Price/Discount type. Buy-X-get-Y rules from the source cannot be represented as standard Trade Agreements and are documented as a configuration handoff for the customer's admin to recreate using the Trade Allowance Management module or a third-party pricing app. Active coupon codes are documented separately.

eCommerce Pro customer-specific price lists and volume tiers map to Dynamics 365 Trade Agreement records. The source customer price list is scoped to a specific Account or Contact group; we create a corresponding Price Group in Dynamics 365 and attach Trade Agreement lines with the same unit price, quantity break, and currency. Currency settings from the source (multi-currency orders) map to the Dynamics 365 Currency configuration for the transaction.

Active eCommerce Pro gift card codes and remaining balances map to Dynamics 365 Loyalty Gift Card records. Expired or fully redeemed gift cards are logged as history entries rather than imported as active balances. The Dynamics 365 Commerce module's Loyalty program must be enabled and configured before gift card data is imported.

eCommerce Pro product and variant images migrate as attachments to the Released Product record via the Document Handling framework. We validate image URLs, optionally re-host assets to Azure Blob Storage or SharePoint (the Dynamics 365 document store), and attach each image with the correct reference type and sequence for display in the Commerce POS and online storefront.

eCommerce Pro custom objects (fields or entities beyond the standard catalog) migrate to Dynamics 365 custom entities created via the Power Platform admin center or via metadata in a developer solution. We pre-create the destination schema including all attributes, data types mapped from the source (string to Text, number to Decimal, date to Date), and any lookup relationships before data import begins.