Migrate from BizAutomation Cloud ERP to Dolibarr ERP

BizAutomation Organizations map to Dolibarr Third Parties with the Client checkbox enabled. We extract organization name, type, billing and shipping address, phone, email, and any custom Organization properties from the database export. The Third Party's code (customer number) is generated from BizAutomation's org_id. Address records in BizAutomation's multi-address structure map to Dolibarr's address table with the address_type field indicating billing versus shipping.

BizAutomation Contacts link to Organizations and carry name, email, phone, role, and lifecycle stage. We map these directly to Dolibarr Contacts with the socid (Third Party) reference resolved at import time. Custom Contact properties and user-defined fields require field-level mapping against the database export columns; we present a mapping spreadsheet during scoping for the customer's review before any import begins.

BizAutomation Vendor records map to Dolibarr Third Parties with the Supplier checkbox enabled. Vendor name, contact info, payment terms, and address export from the vendors table and map to the equivalent Dolibarr fields. Payment term references (Net 30, Net 60) from BizAutomation map to Dolibarr's Payment Terms configuration which must be set up in Dolibarr's Bank-Accounts module before vendor import.

BizAutomation's GL Chart of Accounts maps to Dolibarr's accounting plan structure. We export the full account list including account number, name, type (asset, liability, equity, income, expense), and parent hierarchy. The Chart of Accounts must be imported before any purchase orders, sales orders, or invoices because Dolibarr's accounting module validates account codes on transaction entry. We create any missing account types in Dolibarr's accounting setup before loading the account records.

BizAutomation Inventory Items (SKU, description, cost, price, warehouse location, quantity-on-hand) map to Dolibarr Products. The product_type field determines whether the item is a stockable product (stock managed), a service, or a consumable. We preserve unit cost as the pmp (weighted average purchase price) and unit price as the price_ttc or price_ht depending on whether the customer uses inclusive or exclusive tax pricing. Matrix items and custom item properties require reconstruction: we export the parent item template first, then generate child product combinations in Dolibarr with the correct attribute assignments from the matrix child records.

BizAutomation Sales Orders map to Dolibarr Orders (Commande client) with status mapping: open orders become Draft or Validated; fulfilled orders become Shipped; invoiced orders become Billed. We export order header fields (order number, date, customer reference, shipping address) and line items (product, quantity, unit price, discount) from the order tables. Dolibarr requires a validated Third Party and an activated Product before an Order line can reference them, so the Third Party and Product imports must complete first.

BizAutomation Purchase Orders map to Dolibarr Supplier Orders (Commande fournisseur) with status mapping preserving the PO lifecycle. Vendor references resolve to the corresponding Dolibarr Third Party (Supplier type) via vendor name or ID lookup. Line items map to Products with the cost field populated from BizAutomation's purchase price. Historical PO records carry financial obligations that must land with matching supplier accounts in Dolibarr's accounting module.

BizAutomation Shipment records map to Dolibarr Shipments (Expéditions). We export shipment date, carrier, tracking number, and the linked sales order reference. In Dolibarr, each shipment must be linked to an order, which means the Order import must precede Shipment import. If the destination Dolibarr instance does not have the Expedition module activated, we flag this as a prerequisite configuration before migration.

BizAutomation Projects (spanning the PSA module with tasks, time entries, and contract billing) map to Dolibarr Projects. We export project status, start and end dates, owner, and task hierarchy. Custom project fields and milestone definitions require field-level mapping review. Time entries in BizAutomation map to Dolibarr Project Time tracking if the project's ref and third-party reference are preserved during the parent project import.

Billable time contracts in BizAutomation tracking sold hours against project tasks map to Dolibarr Contracts. We export contract type, value, remaining hours, and linked project references. Contract line items with rate schedules require mapping to Dolibarr's service Products if the contract references service billing. Dolibarr Contracts must link to a valid Third Party; we resolve this lookup before contract import.

BizAutomation Opportunities tracking pipeline deals against Organizations map to Dolibarr Commercial Proposals (Propales) or, if the customer uses a project-based pipeline, to Projects with a stage field. Stage and probability from BizAutomation map to proposal status (Draft, Open, Signed, Lost). Custom pipeline stages in BizAutomation may not map 1:1 to Dolibarr's proposal states; we document the value mapping during scoping.

BizAutomation Activities (calls, emails, tasks, notes) linked to Organizations and Contacts map to Dolibarr Interventions (linked to Projects) and Agenda events. Activity type, date, owner, and linked record export from the activity tables. Dolibarr's Agenda module must be activated for event import; notes migrate as Intervention records linked to the relevant Project or Third Party. Custom activity types require field-level mapping review against the database export.

Orders originating from Shopify, BigCommerce, WooCommerce, Magento, or EDI marketplaces via BizAutomation's multi-channel integration carry the same structure as standard Sales Orders and map to Dolibarr Customer Orders. We extract the channel identifier from a custom field or order prefix and document the channel mapping for the customer's admin to reconfigure the e-commerce integration in Dolibarr or a third-party connector post-migration.