Migrate from Bizowie ERP to Dolibarr ERP

Bizowie Customers map to Dolibarr Third Parties with the Client checkbox enabled. We extract via saved report CSV including billing address, shipping addresses, payment terms, and credit limits. The 78% duplicate rate in Bizowie implementations requires fuzzy-match deduplication on name and address before import; we flag potential duplicates and present them for business-user resolution. Email, phone, and address fields map directly to Dolibarr's third-party address and contact blocks.

Bizowie Vendors map to Dolibarr Third Parties with the Supplier checkbox enabled. Payment terms, remit-to addresses, and PO defaults migrate to Dolibarr's supplier tab. Duplicate vendor records follow the same fuzzy-match deduplication workflow as customers. We preserve vendor contacts as Dolibarr contacts linked to the third-party record.

Bizowie Items map to Dolibarr Products with type (Product or Service) determined by Bizowie item type. The multi-UOM structure (sell by case, buy by pallet, track by each) requires transformation: Dolibarr uses a single stock unit per product. We extract the primary selling UOM and map Bizowie selling-unit, buying-unit, and tracking-unit to Dolibarr's unit-of-measure field and unit conversion table. Lot numbers and serial numbers migrate as Dolibarr lot/serial records linked to the product.

Bizowie bin-level warehouse locations with zone and aisle hierarchy map to Dolibarr Warehouses. We preserve location assignments from Bizowie as Dolibarr warehouse addresses and custom location fields. Multi-location inventory in Bizowie creates multiple Dolibarr warehouses; bin-level detail beyond warehouse address requires a custom Dolibarr field or the stocklocation community module if the customer requires it.

Bizowie on-hand quantities by location and lot/serial snapshot to Dolibarr Stock at migration cutover date. We map Bizowie location IDs to Dolibarr warehouse IDs, and lot/serial traceability records link to Dolibarr lot/serial batches. Catch weight data from Bizowie (where applicable) migrates to Dolibarr's weight fields if the weight module is enabled; otherwise it is archived as a CSV supplement.

Active Bizowie Sales Orders map to Dolibarr Customer Orders with header fields (order number, date, customer reference, internal notes) and line items (product, quantity, pricing, warehouse assignment). Order status in Bizowie maps to Dolibarr status (Draft, Validated, Shipped, Closed). We preserve customer references and internal notes from the order header as Dolibarr line notes.

Outstanding Bizowie Purchase Orders map to Dolibarr Supplier Orders. Line items include expected receipts and line-level pricing. We preserve warehouse receiving assignments linking PO records to Bizowie receiving data for partial versus complete receipt tracking. Status mapping follows the same Draft/Validated/Received/Closed progression.

Outstanding Bizowie receivables extract from saved reports with original invoice dates, amounts, and aging buckets. These map to Dolibarr Customer Invoices in Open (unpaid) status. We preserve the original invoice number as reference and the aging classification as a custom field. Closed AR transactions require a separate historical extract scoped to the retention period.

Outstanding Bizowie payables map to Dolibarr Supplier Invoices in Open status. Original invoice dates, amounts, and vendor references migrate directly. We preserve aging bucket classification as a custom field for accounts payable review.

Bizowie GAAP-compliant chart of accounts with parent-child hierarchy maps to Dolibarr's accounting module accounts. We extract the full account structure including account type, number, and parent relationship. Dolibarr's accounting configuration requires explicit account type assignment (Customer, Supplier, Bank, Cash, Expense, Revenue) per account, which we map from Bizowie account classification. This phase requires the Dolibarr accounting module to be enabled during migration.

Historical invoices, POs, and receipts from Bizowie migrate to Dolibarr if within the agreed retention scope (typically two to four years). We recommend scoping older closed transactions to archive rather than import because Dolibarr performance degrades with large transaction tables. We export historical records as a structured archive CSV with the same schema as active records, stored alongside the migrated system for lookup rather than imported into Dolibarr's active tables.

Bizowie custom knowledge bases and wiki databases have no direct Dolibarr equivalent. We export the content as structured CSV (title, body, author, dates, attachments) and assess whether Dolibarr's project module, third-party wiki integration, or a custom Dolibarr module can host the data. Organization-specific custom database schemas vary widely and require individual assessment during scoping. Attachments extract as separate files with reference links preserved in the CSV.

Bizowie's native eCommerce sync with Shopify, Magento, BigCommerce, WooCommerce, and 3DCart has no equivalent in Dolibarr's core software. We do not migrate eCommerce connection configurations. We deliver a written inventory of the active sync feeds (which platforms, which data flows) for the customer to rebuild using Dolibarr's third-party eCommerce modules or third-party integration tools. Order and product data from the eCommerce platforms can be exported and re-imported to Dolibarr as one-time data loads if needed.

Bizowie user accounts and role assignments extract from the system. Dolibarr user management assigns permissions by module (read/write on specific modules) rather than Bizowie's functional role model. We extract the user list and role assignments and present a mapping to Dolibarr module-level permissions for the customer's admin to assign post-migration. Owner assignments on records migrate as Dolibarr user references where a matching user exists; orphaned assignments (Bizowie user with no Dolibarr equivalent) are flagged for admin resolution.