Migrate from Breeze ERP to Dolibarr ERP

Breeze Companies and Customer records map to Dolibarr Third Party objects with the Client checkbox enabled. We extract available fields from Breeze HTML or CSV exports (company name, address, phone, email, tax ID) and map them to socpeople and societe table columns in Dolibarr. Dedup is performed on company name and email during import. Any Breeze custom fields attached to company records are captured as Dolibarr extrafields (custom fields) if the Dolibarr instance has the ExtraFields module enabled.

Breeze Vendor master records map to Dolibarr Third Party with the Supplier checkbox enabled. Vendor name, address, contact name, phone, and payment terms migrate as societe rows with fournisseur=1. We flag any Breeze vendor records that have open purchase orders and carry those as Purchase Order objects in Dolibarr, preserving PO number, line items, quantities, and amounts as open documents requiring fulfillment or closure in the destination.

Breeze Item records that are non-inventory (services, finished goods without stock tracking) map to Dolibarr Product records with type=1 (Service) or type=0 (Product). SKU, description, unit of measure, and selling price migrate directly. If Breeze tracks cost price we map it to the cost_price field in Dolibarr to support margin calculations.

Breeze inventory SKUs map to Dolibarr Product records with type=0 and the stock module enabled. Current stock quantities per warehouse migrate to Dolibarr stock_entrepot records. Warehouse assignments from Breeze are created as Dolibarr Entrepots before stock import so that product_stock.warehouse references are satisfied. Stock value at cost migrates as a product_batch or product_stock entry.

Breeze BOM records (engineering-to-order and make-to-order) require explicit scoping because Dolibarr's MRP module is less granular than Breeze's manufacturing-first orientation. We extract BOM header and line data from available exports and deliver a written BOM mapping document that describes the source BOM structure, the nearest Dolibarr equivalent (native MRP module or a DoliStore addon), and what assembly or production features cannot be expressed in the destination. BOM migration is configuration-scope, not automatic migration.

Breeze Chart of Accounts entries map to Dolibarr accounting Account records with account_type, account_parent, and pcg_type populated. Account code, name, and type (asset, liability, equity, income, expense) migrate directly. We extract the full account list from Breeze exports and map to the French PCG (Plan Comptable Général) or the customer's chart structure if they use a custom plan. GL balances at cutover date are carried as opening journal entries in Dolibarr's ecriturebank and ecriturecomptable tables.

Open accounts receivable in Breeze migrate as Dolibarr Customer Invoice records in draft or validated status matching the original invoice date, number, and amount. Each invoice's line items map to facturedet rows. We preserve the original invoice number and date for audit trail. Payment status at cutover is set to unpaid (paye=0) with the original due date carried in the dlv date field.

Open accounts payable in Breeze migrate as Dolibarr Supplier Invoice records with the linked Third Party (Supplier) resolved by vendor name match. Line items migrate to facturedet_fourn rows. We preserve original vendor invoice number and date, and set payment status to unpaid at cutover so that the accounts payable aging report reflects the true open balance in Dolibarr.

Breeze Project records map to Dolibarr Project objects. Project name, description, start and end dates, status, and assigned user (owner) migrate directly. We resolve Breeze project assignments by email match against Dolibarr User records. Project time entries and task assignments migrate as Dolibarr Task rows linked to the parent Project. Any project-specific custom fields are preserved as Dolibarr extrafields.

Breeze work order and production schedule records require explicit scoping because Dolibarr's production module handles manufacturing orders differently from Breeze's manufacturing-first model. We extract work order headers and line data and deliver a written scoping note describing the mapping to Dolibarr's mrp_production object (if the MRP module is enabled) or to Project tasks as a workaround. This is configuration-scope; work orders are not auto-migrated without explicit customer sign-off on the destination structure.

Breeze HR module employee records map to Dolibarr Employee objects if the HR module is enabled in the destination. Employee name, designation, department, and employment status migrate as Hammer rows. Salary, attendance, and leave records are flagged as configuration-scope because Breeze's HR depth may exceed what the standard Dolibarr HR module covers; we document what is migratable and what requires manual re-entry or an HR addon.

Breeze document attachments (uploaded files, generated PDFs) are extracted from the source export where available and imported into Dolibarr's ECM module under the matching record reference. We map each document to the corresponding dolibarr.document object with entity_id and ref referencing the parent Third Party, Product, Project, or Invoice. If Breeze exports documents in a flat directory structure, we resolve the document type from file extension and naming convention during import.