Migrate from EBMS to Microsoft Dynamics 365 Business Central

EBMS Customer records map to Microsoft Dynamics 365 Contact records (for person-level records) and Customer records (for B2B account-level records). We resolve the split based on EBMS's customer type field or the presence of child contact records. Primary address from EBMS maps to the Dynamics 365 address with address purpose set to Invoice and Delivery. Payment terms, credit limits, and customer-specific pricing tiers migrate to the customer finance settings. Any portal-specific fields (price level visibility, payment term enforcement) are flagged for manual configuration in Dynamics 365 because the B2B portal model differs from EBMS Customer Portal.

EBMS Vendor records map directly to Dynamics 365 Vendor records. Contact information, purchasing terms, and payment hold status transfer to the Vendor entity. Custom fields on vendor records require explicit mapping to Dynamics 365 Extended Properties or custom fields on the Vendor entity. Vendor-specific pricing tiers map to Trade Agreements in Dynamics 365 Supply Chain Management if the customer uses centralized vendor pricing.

EBMS inventory items map to Dynamics 365 Released Products with the inventory model (Standard, FIFO, Moving Average, or Periodic) preserved from EBMS unit cost and valuation settings. EBMS units of measure (UOM) map to the Dynamics 365 UOM class structure. Serial number and lot tracking settings transfer to the Tracking dimension group. EBMS product pricing maps to Trade Agreements (Purchase Price and Sales Price) in Dynamics 365 rather than as a fixed product attribute.

EBMS Sales Orders map to Microsoft Dynamics 365 Sales Orders with header fields (customer reference, order date, delivery date, terms) preserved and line items mapped to Sales Order Lines with product, quantity, unit of measure, and price resolved via Trade Agreements. EBMS order status (open, invoiced, partially shipped) maps to the corresponding Dynamics 365 status. If EBMS tracks order holds or credit limits on the order, those map to Microsoft Dynamics 365 Sales Hold or Credit Limit override fields.

EBMS Purchase Orders map to Dynamics 365 Purchase Orders with vendor reference, expected receipt date, and line items. EBMS line item customization (additional charges, notes, delivery instructions) transfer to Purchase Order Lines and line-specific delivery addresses. Custom fields on PO headers or lines require explicit mapping to Dynamics 365 purchase line extension fields or user-defined fields.

EBMS Invoices (open and historical) map to Dynamics 365 Free Text Invoices or posted Sales Invoices depending on whether they have been finalized in EBMS. We scope AR export by date range to avoid mid-period splits: open invoices (not fully paid) and historical invoices (fully paid or closed) are separated. Payment history requires careful date-range scoping to ensure that partial payments do not split across the migration boundary. EBMS invoice numbering sequences are preserved as the Dynamics 365 invoice numbers.

EBMS AP invoices map to Dynamics 365 Vendor Invoice records with vendor, invoice number, invoice date, due date, and amount transferred. Open AP aging data is scoped by date range to separate invoices in process from historical closed invoices. We flag any AP holds or recurring invoice schedules for manual configuration in Dynamics 365 because recurring invoice templates are a separate configuration artifact.

EBMS inventory quantities and warehouse locations map to Dynamics 365 On-hand entries with site and warehouse resolved from EBMS location codes. Inventory dimension groups (site, warehouse, location, batch, serial) transfer from EBMS tracking settings. We capture the snapshot date for the on-hand migration because Dynamics 365 will continue to update inventory through its own warehouse management processes after cutover.

EBMS custom fields created via the Customization Designer are enumerated during data profiling (requiring database access for full discovery). We map each custom field to a corresponding Dynamics 365 extension field on the target entity, preserving data type where possible (text, numeric, date, boolean). Custom field values that cannot be type-mapped (e.g., EBMS-specific picklist values with no Dynamics 365 equivalent) are preserved as text fields and flagged for customer review. This mapping work is done during data profiling, not at migration time.

EBMS Customer Portal accounts store price level assignments and payment term preferences for B2B customers. These map to Dynamics 365 Contact records with the associated Customer Account carrying the price group and payment terms. We preserve the portal-specific login reference in a custom field for reconciliation. The EBMS portal login and authentication model does not migrate; the customer provisions Dynamics 365 authentication (Microsoft Entra ID, SSO, or native credentials) as a separate configuration.

EBMS eCommerce product catalog (Essential/Select/Premium tiers) exports products, availability, pricing, and photos via inventory reports. We export the product data as a subset of the full product migration and map it to Dynamics 365 Released Products with eCommerce-specific attributes (product images, short descriptions, SEO metadata) preserved as extension fields. The EBMS eCommerce site configuration (theme, page layouts, navigation, checkout flow) does not migrate; the customer selects a separate commerce platform (Shopify, Adobe Commerce, or custom connector) as the replacement storefront.

EBMS Reports are a configuration artifact defining data selection, grouping, and formatting. We do not migrate report definitions because they reference EBMS-specific field names, tables, and formatting logic that do not map directly to Dynamics 365. We deliver a written inventory of all EBMS reports with their data sources, filters, and output format as a reference for the customer's Dynamics 365 admin to rebuild as SSRS reports, Power BI datasets, or Dynamics 365 Excel add-in workbooks.