Migrate from PeppyBooks to Odoo ERP

PeppyBooks maintains a hierarchical CoA with account codes, types, and tax-mapping attributes. We export the full PeppyBooks CoA first to establish destination account codes, then create matching Odoo Account records using the account.type model (receivable, payable, expense, revenue, other). If the destination has a default country CoA already installed, we merge PeppyBooks accounts into existing Odoo accounts or create new ones and preserve the PeppyBooks account name as the account long_name field for accountant reconciliation. Account code lengths and hierarchies from PeppyBooks are preserved during mapping.

PeppyBooks Client records include contact details, billing address, payment terms, and opening balance. We map them 1:1 to Odoo Res.partner records with partner_type set to customer and the opening balance carried as a receivable account.move line (opening balance journal entry). We preserve PeppyBooks payment terms as Odoo property_payment_term_id on the partner.

PeppyBooks Vendor master data mirrors Client structure with address, payment terms, and opening AP balance. We map Vendors to Odoo Res.partner records with partner_type set to vendor and the outstanding payable balance carried as a payable account.move line via opening balance journal entry. PeppyBooks vendor-level GST/SST registration numbers map to Odoo property_supplier_tax_id on the partner.

PeppyBooks Invoices are linked to Clients, line items, tax codes, and revenue CoA accounts. We export all invoice fields including status (draft/sent/paid), due dates, amounts, and payment records, then create Odoo account.move records with move_type = out_invoice (for AR invoices) or out_refund (for credit notes). PeppyBooks tax codes are mapped to Odoo account.tax records during the tax-code reconciliation step before invoice migration begins.

PeppyBooks Expense records capture date, vendor, amount, CoA debit account, and tax treatment. We migrate expenses as individual Odoo account.move records with move_type = in_invoice (for vendor bills) or in_refund (for vendor credit notes), mapping PeppyBooks tax codes to the Odoo account.tax equivalents and the debit account to the matching Odoo expense or asset account from the CoA mapping.

PeppyBooks Journal entries support multi-line debits and credits with optional invoice or expense references. We export full journal entries including all line items, then create Odoo account.move records with move_type = entry. Journal-entry naming conventions and reference fields carry forward from PeppyBooks to Odoo statement_ids for audit trail continuity.

PeppyBooks Product master records include name, SKU, unit price, cost, tax category, and stock-on-hand at Premium and above. We migrate products 1:1 as Odoo product.product records, mapping PeppyBooks tax category to Odoo supplier_taxes_id and customer_taxes_id. Current stock-on-hand values are set as Odoo Stock Quant quantities against the mapped warehouse after warehouse records are created.

Warehouse assignments in PeppyBooks are only available on Premium and Ultimate tiers. Where a customer uses multiple stores, we map PeppyBooks warehouse locations to Odoo stock.warehouse records and configure warehouse codes and names to match the source. If PeppyBooks warehouses carry distinct inventory valuation methods, we set the corresponding Odoo costing method on each product. If PeppyBooks is on a lower tier with no warehouse data, no warehouse mapping is performed.

PeppyBooks Purchase Orders are available at Premium tier and above. We export PO headers and line items, then create Odoo purchase.order records. PO workflow states (open/closed/partial) do not always map directly to Odoo PO states because PeppyBooks and Odoo use different state machine logic; we migrate PO header and line data and flag state mapping discrepancies for the customer admin to validate post-import. Purchase order-to-bill conversion logic must be verified against Odoo's active purchase workflow.

PeppyBooks Sales Orders support conversion to invoices. We export order headers, line items, and fulfillment status, then create Odoo sale.order records. PeppyBooks order-to-invoice conversion logic varies from Odoo's make_invoice workflow, so we migrate order data as records and flag the invoice creation step for the customer's admin to run manually or automate via Odoo sale.advance.payment.inv wizard after migration.

PeppyBooks CRM holds Leads and Deals as separate entities with customizable Pipeline Stages. Odoo uses a single crm.lead object where the type field distinguishes between lead and opportunity. We map PeppyBooks Deals to Odoo crm.lead records with type = opportunity and the PeppyBooks pipeline stage name preserved as stage_id in the destination CRM team. PeppyBooks Leads map to Odoo crm.lead with type = lead. We export the active pipeline stage map from PeppyBooks and configure matching Odoo stage records with correct sequence and team assignment before Deal import.

PeppyBooks Activity records capture calls, emails, notes, and tasks linked to contacts or deals. Odoo uses the mail.message model for the activity timeline in CRM and the note.note model for static notes. We map PeppyBooks activity types to Odoo mail.message records with subtype matching (note, call, email) and attach them to the migrated crm.lead records using the res_id and model fields. Activity dates and owner information carry forward to preserve the timeline sequence.