Migrate from Lead Commerce to Microsoft Dynamics 365 Business Central

Lead Commerce Warehouse records map to Business Central Location. We extract warehouse code, name, and address fields from the Lead Commerce warehouse export and create corresponding Location records in Business Central. Location codes must be alphanumeric and are used as the dedupe key during import. If Lead Commerce uses a flat warehouse structure and Business Central requires zone or bin sub-divisions, we create a default zone per Location and flag this for the customer's admin to configure bin placement logic post-migration. This is the first object imported because Items reference warehouse stock by Location.

Lead Commerce Items map to Business Central Item records. We preserve the original SKU in the Item No. or Global Dimension 1 field, map the item description to Name, unit of measure to the Base Unit of Measure, and unit cost to Unit Cost. Lead Commerce items with multi-location stock create Item Ledger Entries per Location during migration. We flag items with zero or negative quantities that may indicate data quality issues and hold them in a reconciliation queue for the customer to confirm before import.

Lead Commerce inventory records with per-warehouse stock quantities map to Business Central Stockkeeping Units (SKU). Each SKU is a combination of an Item and a Location, allowing the customer to track stock at the location level post-migration. We extract the per-warehouse quantity from Lead Commerce's location-level inventory export and create SKU records with the correct variant and Location references resolved at migration time.

Lead Commerce Customer records map to Business Central Customer. We deduplicate by email address during import and preserve the customer number, name, contact details, address, and payment terms. The customer-to-order linkage is maintained by resolving the customer number on each Sales Order during the order import phase. Customer pricing tiers or special discounts from Lead Commerce are mapped to Business Central Customer Price Groups or Invoice Discount Terms where available.

Closed Lead Commerce Orders (status shipped or completed) map to Business Central Posted Sales Shipment and Posted Sales Invoice records via the Dataverse or Business Central API. Open Orders (status pending or processing) map to Sales Orders. We separate the two groups during scoping: fulfilled orders become G/L entries and posted documents; open orders remain editable documents requiring manual status confirmation at cutover. Order lines map with item number, quantity, unit price, and discount amounts.

Open orders active at the migration cutover date require manual reconciliation. We export open orders as Sales Orders, flag any that have progressed beyond their Lead Commerce status during the migration window, and instruct the customer to confirm or update order status before go-live. Orders created in Lead Commerce during the migration window must be entered manually in Business Central post-cutover.

Lead Commerce Purchase Orders map to Business Central Purchase Orders for open POs and Posted Purchase Receipt and Posted Purchase Invoice for received POs. We separate open POs (commitments still pending receipt) from received POs (where lines have been fulfilled and inventory should already reflect landed cost). Received PO lines map to Item Ledger Entries with vendor invoice references preserved.

Lead Commerce User accounts and role assignments export as a flat list. We match by email against Business Central User records. Any Lead Commerce user without a matching Business Central User is held in a reconciliation queue for the customer's admin to provision before record import. Role names from Lead Commerce map to Business Central Permission Sets or Security Groups where equivalents exist; custom roles are flagged for manual reassignment.

Lead Commerce Custom Apps carry business logic built on the platform's app framework with no standard export mechanism. We document any data stored within custom apps separately and flag that the application code itself cannot be transferred. The customer must rebuild or re-platform custom app functionality in Business Central using AL extensions, AppSource add-ons, or Power Platform components. This is a documented gap in the migration scope.

Lead Commerce does not expose saved reports, historical analytics snapshots, or report definitions through its export mechanisms. We include a pre-migration reporting export step in the checklist instructing the customer to export period-end reports as PDFs or screenshots before the migration cutoff date. Historical dashboards cannot be replicated automatically in Business Central; the customer's admin rebuilds reports using Business Central's built-in report designer or Power BI.

Lead Commerce vendors associated with Purchase Orders map to Business Central Vendor records. We preserve vendor name, contact details, address, and payment terms. Vendor-ledger entries from received POs are mapped to Vendor Ledger Entries in Business Central. Vendors without open PO commitments that the customer does not wish to carry forward are excluded from the migration scope.

Historical sales statistics and dashboard data from Lead Commerce cannot be imported as structured records. We provide the customer with a data export of the sales summary period totals (monthly revenue, order count, top items) as a reference file for manual entry or Power BI dataset backfill. Business Central's built-in Sales Analysis reports and Power BI Sales and Inventory analytics replace the operational reporting capability post-migration.