Migrate from BizeeBuy to Dolibarr ERP

BizeeBuy Suppliers map to Dolibarr Third Parties with the Third Party type set to Supplier. We extract supplier name, contact details, sourcing category, and performance metadata. Dolibarr's Suppliers module must be enabled before import; otherwise records land as Contacts without the supplier role flag. The supplier's unique ID from BizeeBuy is preserved as an external reference field for reconciliation.

BizeeBuy Items (SKU, unit of measure, cost, category) map to Dolibarr Products. We map sku to ref, label to label, and unit_cost to cost_price. BizeeBuy variant and bundle structures are flagged for flattening during import since Dolibarr handles product variants through a separate module (Product Variant) that may require activation and configuration.

BizeeBuy Warehouses map to Dolibarr Warehouses. We export warehouse name, address, and assigned roles (receiving, storage, shipping). Dolibarr's Stock module must be enabled; otherwise warehouse records exist but stock assignment fails silently. If BizeeBuy uses multi-warehouse configurations, each warehouse becomes a separate Dolibarr warehouse record.

BizeeBuy Purchase Orders map to Dolibarr Supplier Proposals (draft orders to suppliers) or directly to Purchase Orders depending on the customer's approval stage in BizeeBuy. PO headers, line items, approval statuses, and cost-center assignments migrate. The approval workflow routing from BizeeBuy does not carry over; we document the workflow structure for the customer to rebuild in Dolibarr's workflow engine.

BizeeBuy GRNs serve as the three-way match anchor between POs, receipts, and invoices. We export GRN headers with linked PO references and invoice associations, preserving the matching state as a custom field in Dolibarr. GRNs are not a standalone Dolibarr object; they are reconstructed as inventory receptions against the relevant Purchase Order using Dolibarr's Stock Reception feature.

BizeeBuy real-time stock quantities and FIFO-based pricing per item per warehouse map to Dolibarr stock product-warehouse quantities. We export the latest stock snapshot. If BizeeBuy provides movement logs, we calculate opening stock and apply movements to reconstruct historical stock positions in Dolibarr's stock movement table. Dolibarr's Stock module must be active and the correct warehouse defined before import.

BizeeBuy Production Batches link raw-material consumption to finished-goods output. We export batch headers, associated BoM references, and production-linked inventory adjustments. Dolibarr's MRP (Manufacturing) module must be enabled. Batch records map to Dolibarr Manufacturing Orders with status reflecting the production stage. Raw material consumption is recorded as stock movements linked to the production order.

BizeeBuy BoMs define multi-level component structures with quantities and scrap rates. We export the BoM hierarchy and flatten nested structures for Dolibarr, which supports multi-level BoMs but may require configuration of the Production module. Component quantities map to bomqty in Dolibarr's bom and bomline tables. We flag any BizeeBuy nested sub-assemblies that require separate BoM creation as parent records before the top-level BoM is imported.

BizeeBuy AP records (supplier invoices, payment status, two-way or three-way match results) map to Dolibarr Supplier Invoices. We export invoice headers, line items, and match outcomes against POs and GRNs preserved as metadata. Dolibarr's Accounting module must be enabled for double-entry bookkeeping; if only the Invoice module is active, records post to the customers-suppliers ledger without full accounting entries.

BizeeBuy cost centers and budget allocations drive procurement approval routing. We export the cost-center hierarchy and active budget balances. Dolibarr does not have a native cost-center module in the core; we map cost centers to Dolibarr Projects with budget tracking enabled, or to accounting categories if the customer activates the Accounting module. Approval routing is documented for rebuild in Dolibarr's workflow system.

BizeeBuy supports custom fields on core entities but does not expose a dedicated custom-field schema endpoint. We infer custom field presence from record payloads and map them as Dolibarr Extra Fields on the corresponding objects. Dolibarr's Extra Fields feature is available on most standard objects without a module activation requirement, but the field type mapping (text, date, numeric, select) must be inferred from the BizeeBuy payload data types.

BizeeBuy does not expose a public user management API. We cannot export user records or role assignments. This is documented as a limitation of the source platform and must be manually recreated in Dolibarr by the customer's administrator after migration. We provide a user-role matrix template during the discovery phase to facilitate manual provisioning.