Migrate from mybizz erp to Dolibarr ERP

MyBizz ERP inventory items (SKU, description, unit cost, stock quantity, category) map to Dolibarr Product records with the product type set to Ware or Service as determined by the item type in MyBizz ERP. We pull the primary inventory export via Dashboard > Menu > Inventory > Items > Export, transform column headers to match Dolibarr's import profile (ref, label, description, price_ttc, stock_theoretical), and resolve the product type field. If MyBizz ERP uses custom stock fields, we create matching custom fields in Dolibarr before import. Multi-warehouse configurations in MyBizz ERP map to Dolibarr warehouse locations stored in the product_warehouse table.

MyBizz ERP Customer records (contact name, company, email, phone, address, payment terms) map to Dolibarr Third-Party records with the Tiers type set to Customer. The import profile is ThirdParty.csv using Dolibarr's Import Module under Tools > Import. We map MyBizz ERP's customer_code or name to Dolibarr's code field, email to email, phone to phone, and payment terms to cond_reglement. Customer-company relationships in MyBizz ERP where a contact belongs to a company map to Dolibarr's contact-to-third-party hierarchy, with contacts imported as separate Contact records linked by fk_soc.

MyBizz ERP Vendor records (vendor name, contact details, payment terms) map to Dolibarr Third-Party records with Tiers set to Supplier. We apply the same import workflow as Customer records using Dolibarr's ThirdParty import profile, switching the Tiers type flag. Payment terms from MyBizz ERP map to cond_reglement and mode_reglement on the supplier record. If MyBizz ERP stores vendor-specific purchase pricing, we create custom fields or map to the supplier price field if available in the Dolibarr edition.

MyBizz ERP Chart of Accounts (account codes, names, parent-child hierarchy) map to Dolibarr's accounting module (Accountancy > Chart of Accounts). We preserve hierarchical parent-child relationships using the account parent structure during import. Note that Dolibarr's base accounting module does not include native cost-centre functionality; if the MyBizz ERP migration includes cost-centre assignments, we document them for the customer's admin to evaluate the DoliStore Cost Accounting module as a post-migration add-on. Account type (asset, liability, equity, income, expense) maps to the account_type field in Dolibarr's pcg_version structure.

MyBizz ERP Invoice records (line items, amounts, dates, customer reference, status) map to Dolibarr Facture records. Customer invoices (sales) use Facture type Facture (customer) and supplier invoices use Facture type FactureFournisseur (supplier). We resolve the fk_soc (third-party) reference by looking up the third-party code before inserting invoices, and fk_product by matching product references. Invoice status (paid, unpaid, cancelled) maps to Dolibarr's pfk_statut and statut fields. Invoice line taxes and totals are recalculated or preserved depending on whether the source export includes tax-inclusive or tax-exclusive amounts, with explicit mapping documentation provided to the customer before import.

MyBizz ERP Quotes (standalone documents with line items, expiration dates, status) map to Dolibarr Propal records. The fk_soc (third-party) and fk_product references are resolved before insert, and validity date maps to fin_validite. Quote status fields in MyBizz ERP (draft, sent, accepted, lost) map to Dolibarr Propal statut values (Draft, Open, Signed, Not Signed). We flag any MyBizz ERP quote PDFs as archived content for manual reference since Dolibarr's native document import does not migrate binary attachments; the customer retains original quote files in their archive.

MyBizz ERP Payment transactions (linked to invoices and customers) map to Dolibarr Payment records (paiement) and optionally to bank statement line records (payment_bank). We resolve the fk_facture reference by looking up the invoice number from the migrated invoices, the fk_soc by third-party code match, and amount and payment date directly. If MyBizz ERP records the payment method (cash, cheque, bank transfer, UPI), we map it to Dolibarr's paiementType field. Payments without a resolvable invoice reference are held in a reconciliation queue for manual review before insert.

MyBizz ERP Expense records (vendor, amount, category, date, description) map to Dolibarr's expense module (Dépenses) if enabled in the target Dolibarr installation. We map vendor to fk_depense_type, amount to amount, expense date to date, and category to the expense type. Note that Dolibarr's expense module is a module that must be explicitly enabled; if it is not active in the destination instance, we flag this during scoping and either configure it pre-migration or document it as a post-migration setup step.

MyBizz ERP Booking records (service date, customer reference, booking status) do not have a direct Dolibarr equivalent in the base installation. We map bookings to Dolibarr Project records (with type Projet) using the booking date as the project start date and the booking status mapped to a custom status picklist. If the customer requires appointment or resource scheduling features, we document the DoliStore Project Scheduling or Booking module as a post-migration add-on recommendation. This is a configuration decision made during scoping with the customer's input.

MyBizz ERP Lead records (contact information, lead status) map to Dolibarr Third-Party records if the customer prefers to manage unqualified prospects as Third-Parties with type Prospect, or to Dolibarr's native Lead module if the Leads module is enabled in the destination instance. We determine the appropriate target during scoping based on the customer's sales process. The lead status from MyBizz ERP maps to a custom status field or the built-in status field depending on the chosen model. Any lead score or source attribution data from MyBizz ERP is preserved as custom fields.

MyBizz ERP supports custom fields on several objects, but the platform's UI export utility may not expose all custom field values in the standard export format. We perform a pre-migration field audit with the customer to identify every custom field in use, determine whether each appears in the standard export, and create explicit mapping rules for non-standard fields. Dolibarr custom fields are defined per module before import and are included in the CSV column headers. Fields that cannot be exported from MyBizz ERP are documented in the migration handoff report with recommended manual re-entry or a custom export script estimate.

MyBizz ERP Owner records (user name, email) map to Dolibarr User records by email match. We extract distinct owner references from all migrating records (Contacts, Companies, Invoices, Payments) and match by email against the Dolibarr destination User table. Any MyBizz ERP owner without a matching Dolibarr User goes to a reconciliation queue; the customer's Dolibarr admin provisions missing users before record migration resumes. Dolibarr user permissions (read/write/admin per module) are set based on the user's role in MyBizz ERP, with the admin's input during scoping.