Migrate from Breeze ERP to Microsoft Dynamics 365 Business Central

Breeze ERP's Chart of Accounts exports as a flat account list via HTML table conversion or negotiated CSV download. We map each account code and name to Microsoft Dynamics 365 Finance MainAccount with the account type (Asset, Liability, Equity, Revenue, Expense) preserved. Breeze ERP's account segments (if any exist in the export) map to Financial Dimensions in Dynamics 365; we create a dimension for each segment and build a dimension hierarchy before GL data migrates. GL balances migrate as opening journal entries posted to the appropriate account and period.

Breeze ERP customer records map to Dynamics 365 Finance CustTable. We extract customer name, billing address, shipping address, payment terms, and credit limit from available exports, map them to the corresponding CustTable fields, and create the customer in the appropriate legal entity. Customer balance outstanding at cutover migrates as an open AR invoice via the CustInvoiceJour and CustInvoiceTrans tables, with the invoice date preserved for aging reporting.

Breeze ERP vendor master records map to Dynamics 365 Finance VendTable. We extract vendor name, address, payment terms, and W-9 or tax registration data from available exports and map them to the corresponding VendTable fields. Open AP balances at cutover migrate as vendor invoices via the VendInvoiceJour and VendInvoiceTrans tables, preserving original invoice date and due date for AP aging.

Breeze ERP inventory items map to Dynamics 365 ReleasedProduct with the item's standard cost, item model group, and storage dimension group pre-configured. We extract item number, description, unit of measure, and stock valuation method from the available export and map to the corresponding Dynamics 365 fields. Inventory dimensions (site, warehouse, and any variant dimensions like color or size) are created as dimension combinations before items are released to the legal entity.

Non-inventory items from Breeze ERP (service items, miscellaneous charges) map to ReleasedProduct with the ProductType set to Service and the inventory model group set to a non-stock group. These items do not receive inventory transactions but are available on purchase and sales documents.

Breeze ERP BOM records map to Dynamics 365 Supply Chain Management BOMVersion and BOMLine. BOM components from Breeze ERP export require explicit scoping because the platform does not publish a schema for BOM relationships. We request a sample BOM export during discovery, infer the component structure from UI labels, and map each component item to a BOMLine with the quantity-per and bom-unit preserved. Active BOMs receive a BOMVersion with the current effective date.

Breeze ERP work orders map to Dynamics 365 Supply Chain Management ProdTable. Open production orders (status In Process or Scheduled) migrate with their production route, scheduled start and end dates, and BOM reference preserved. Finished and cancelled production orders are scoped for historical reference only if the customer requires the audit trail; otherwise they are excluded from migration to avoid cluttering the production order history.

Breeze ERP project records map to Dynamics 365 Project Operations or Finance ProjTable depending on the destination module. We extract project name, description, project type (Time and Materials, Fixed Price, Internal), project stage, and any assigned resources. Project hour forecasts and actuals migrate as ProjJournalTrans entries with the activity and category preserved. We flag resource assignment mapping for manual reconciliation because Breeze ERP resource definitions may not align with Dynamics 365 worker or contact records.

Historical vendor invoices from Breeze ERP export migrate to VendInvoiceJour and VendInvoiceTrans. We preserve vendor account, invoice number, invoice date, due date, invoice amount, and tax amount. Invoice lines map to VendInvoiceTrans with item number, quantity, unit price, and line amount. Only posted invoices migrate; open invoices requiring GL correction are flagged for the customer's finance team to handle manually post-migration.

Historical customer invoices from Breeze ERP export migrate to CustInvoiceJour and CustInvoiceTrans. We preserve customer account, invoice number, invoice date, due date, invoice amount, and sales tax amount. Invoice lines map to CustInvoiceTrans with item number, quantity, unit price, and line amount. Paid invoices migrate with status Closed; unpaid invoices migrate as open AR items for the customer's collections team to manage.

Open AP and AR balances at cutover migrate as CustTrans and VendTrans records in Dynamics 365. We extract the outstanding amount, original invoice date, due date, and aging bucket from Breeze ERP's AP/AR aging report export and map to the corresponding transaction records. This preserves the customer's current payables and receivables positions without re-entering data manually, and allows Dynamics 365's payment journal to be used for subsequent cash applications.

Historical inventory transactions (receipts, issues, adjustments) from Breeze ERP export migrate to Dynamics 365 InventTrans. We extract item number, transaction date, quantity, transaction type, cost amount, and warehouse from the inventory history export and map to InventTrans. The InventSettlement and InventOnHand tables are updated accordingly to maintain inventory value consistency. Only transactions within the agreed historical window (typically 12-24 months) migrate; older transactions are archived.