Migrate from mybizz erp to Odoo ERP

MyBizz ERP's Inventory Items export (Dashboard > Menu > Inventory > Items > Export) provides SKU, description, and unit data. We map these to Odoo product.product records, setting type to 'product' for stockable items, 'consu' for consumables, and 'service' for service items. If the customer's MyBizz ERP instance includes bill-of-materials data, we create corresponding mrp.bom records in Odoo with bom.line children mapped from the BOM component lists. Odoo's product variant model requires a template record (product.template) before variants can be created; we handle this hierarchy during import.

MyBizz Customer records map to Odoo res.partner records with customer_rank set to 1. The customer name, email, phone, and address fields transfer directly. MyBizz's custom fields on Customer require a pre-migration field audit: any field not present in the standard MyBizz export format is flagged, and we create corresponding custom res.partner fields (Char, Selection, or Text type) in Odoo before import begins.

MyBizz Vendor records map to Odoo res.partner records with supplier_rank set to 1. Vendor name, contact details, and payment terms migrate directly. We create res.partner records before any Purchase Order import so that the supplier lookup (partner_id) is satisfied at the moment of import. Payment terms from MyBizz (Net-30, Net-60, etc.) map to Odoo's account.payment.term table.

MyBizz ERP's Chart of Accounts exports with account codes and names. We map these to Odoo account.account records, preserving parent-child relationships by importing parent accounts first and resolving the parent_id foreign key before child account rows. Odoo's account.account model requires each record to have user_type_id set to an Odoo account type (asset, liability, equity, revenue, expense); we map MyBizz account classifications to the corresponding Odoo user_type_id values during the transform step.

MyBizz Invoice records (including line items, amounts, dates, and customer references) map to Odoo account.move records. We import account.account (Chart of Accounts) and res.partner (Customers) first so that journal_id, partner_id, and line account_id references are satisfied. Invoice status (paid/unpaid) maps to Odoo's payment_state field; partially paid invoices require a corresponding account.payment record created alongside the account.move. Invoice numbers from MyBizz become the account.move.ref field to preserve audit trails.

MyBizz Quotes migrate to Odoo sale.order records for customer-facing quotes or purchase.order for vendor-requested quotes. Quote line items map to sale.order.line with product_id, product_uom_qty, and price_unit resolved. The MyBizz expiration date migrates to sale.order.validity_date. We flag any MyBizz quote status fields that do not map automatically to Odoo's sale.order.state (draft, sent, sale, done, cancel) and document them in the migration handoff report.

MyBizz Payment records (payment date, amount, payment method) map to Odoo account.payment. We link each account.payment to its corresponding account.move (the paid invoice) via the reconciled_account_payment_ids relationship. Payment method from MyBizz maps to Odoo's journal_id on account.payment, selecting the appropriate bank or cash journal. Payments must import after account.move records are present so that the reconciliation link is valid.

MyBizz Booking records (service date, customer reference, booking status) map to Odoo project.task or calendar.event depending on whether the customer enables Odoo's Project or Field Service modules. We discuss module selection during scoping. Any custom booking status values from MyBizz that have no Odoo equivalent become custom selection fields on project.task, with the original values preserved in a migration audit field.

MyBizz Expense records (vendor, amount, category, date) map to Odoo account.move line entries or hr_expense records depending on whether the Odoo HR module is in scope. If the customer enables Odoo HR, we create hr_expense.sheet records with hr_expense lines and link them to the responsible employee res.partner. If HR is not in scope, expenses import as journal entries against the appropriate expense account from the Chart of Accounts.

MyBizz Lead records (contact information and lead status) map to Odoo crm.lead records. We import crm.lead before sale.order so that lead-to-opportunity conversions in Odoo post-migration can reference the original records. Lead status from MyBizz maps to Odoo's stage_id on crm.lead; custom stage names become new CRM pipeline stages created in the Odoo CRM module before migration begins.