Migrate from BizeeBuy to Microsoft Dynamics 365 Business Central

BizeeBuy Supplier records map to Dynamics 365 Vendor. The supplier name, contact details, sourcing category, and performance metadata transfer as fields on the Vendor entity. Vendor addresses map to the Logistics postal address structure. We resolve any duplicate vendor names created under different spellings during the data profiling phase before import.

BizeeBuy PO headers, line items, cost-center assignments, and approval statuses map to Dynamics 365 Purchase Order. The PO approval status from BizeeBuy (pending, approved, rejected) maps to a Workflow state we configure in Power Automate post-migration since BizeeBuy approval workflows do not transfer as code. Line items link to Items by SKU resolution.

GRNs are the three-way match anchor in BizeeBuy's payable workflow. We export GRN headers with their linked PO references and invoice associations, then map to Product Receipt lines in Dynamics 365. The three-way match state (matched, variance, pending) is preserved in a custom field on the receipt for payable reconstruction.

BizeeBuy Items carry SKU, unit of measure, cost, and category assignments. We export the full item master and map to Dynamics 365 Released Products with the same item number and unit. Variant or bundle structures in BizeeBuy require flattening; we decompose bundles into component lines and flag the parent bundle for manual reassembly if required.

BizeeBuy warehouse definitions with addresses and assigned roles (receiving, storage, shipping) map directly to Dynamics 365 Warehouse. Site and Location hierarchies are created based on the warehouse role. BizeeBuy's single-warehouse configuration (Starter tier) maps to a single Dynamics 365 site; multi-warehouse setups map to multiple sites with inter-company transfer orders if applicable.

Stock quantities per item per warehouse transfer as on-hand inventory transactions. BizeeBuy's FIFO-based pricing preserves as the costing version in Dynamics 365 inventory setup. We export the latest stock snapshot and any available movement logs; movement logs without a dedicated API endpoint require ledger posting reconstruction from invoice history.

Batch records link raw-material consumption to finished-goods output. We export batch headers, associated BoM references, and inventory adjustments. In Dynamics 365 Finance and Supply Chain, these map to Production Orders with the production BOM version and route. Business Central production orders use a simpler structure without route operations; we flag the difference during scoping and advise on the appropriate destination module.

BizeeBuy multi-level BoM hierarchies with component quantities and scrap rates flatten into single-level BOM lines in Dynamics 365. We decompose sub-assemblies into their component items and map each to a separate BOM line. Dynamics 365 BOM versions are date-effective; we set the BOM version effective date to the original BoM creation date from BizeeBuy.

AP records including supplier invoices, payment status, and two-way or three-way match results map to Vendor Invoice headers and lines. Match outcomes against POs and GRNs are preserved in custom fields since Dynamics 365 match states are computed at invoice-posting time rather than stored as attributes. Open invoice balances are recorded as pending vendor ledger entries for the AP team to resolve in the new system.

BizeeBuy cost-center hierarchy and active budget balances map to Dynamics 365 Departments and Financial Dimensions. Approval routing in BizeeBuy tied to cost-center budgets requires rebuild in Power Automate or Dynamics workflow as a post-migration task. We export the budget balance snapshot and flag it as a manual opening balance in the Dynamics 365 budget module.

BizeeBuy custom fields on core entities are inferred from record payloads since the API does not expose a dedicated custom-field schema endpoint. We infer field presence, map the field name to a Dynamics 365 custom field (user-defined field in Finance and Operations or custom field in Business Central), and assign the appropriate data type. The customer validates custom field completeness against a pre-migration field list during sandbox sign-off.

BizeeBuy does not expose a public user management API, so user records and role assignments cannot be exported. We provision users in Dynamics 365 Azure Active Directory, assign the appropriate security roles based on the customer's documented role structure, and deliver a role matrix mapping BizeeBuy role names to Dynamics 365 security roles. This is a manual step coordinated with the customer's IT admin during cutover.