Migrate from PeppyBooks to Dolibarr ERP

PeppyBooks maintains a hierarchical COA with account codes, types (Asset, Liability, Equity, Revenue, Expense), and tax-mapping attributes. We export the full COA as a structured list and create matching accounts in Dolibarr's llx_accounting_account table. Account code lengths, naming conventions, and parent-child hierarchies vary by PeppyBooks customer, so we either merge source accounts into existing Dolibarr default accounts or create new ones. The source account name is preserved as the account label to assist accountants during reconciliation. This migration runs first so that account codes are available for all downstream transaction mapping.

PeppyBooks Clients with contact details, billing address, payment terms, and opening balance map to Dolibarr llx_societe records with the Tiers type flag set to Customer. PeppyBooks opening balance migrates as an opening balance entry in Dolibarr's accounting journal. Client-specific custom fields migrate to llx_societe_extrafields. PeppyBooks allows multiple contacts per Client; Dolibarr stores contacts separately in llx_socpeople and links via fk_soc, so we create one primary contact and flag additional contacts for manual linking post-migration.

PeppyBooks Vendors mirror the Client structure with address, payment terms, and opening balance. They map to Dolibarr llx_societe with Tiers type = Supplier. Outstanding AP balances migrate as opening balance entries in the accounting journal linked to the appropriate vendor account. PeppyBooks Vendors and Clients are separate entity types; in Dolibarr they share the llx_societe table with a type distinction, so we split the PeppyBooks export by type flag during the transform step before loading.

PeppyBooks invoices linked to Clients, line items, tax codes, and COA revenue accounts map to Dolibarr llx_facture (type = Invoice). We export invoice status (Draft, Sent, Paid, Overdue), due dates, payment records, and multi-currency amounts with their original exchange-rate context. PeppyBooks tax codes (US sales tax rates, SST codes) map to Dolibarr tax rules configured per tax authority before invoice import. Invoice PDFs migrate as Dolibarr document attachments linked to llx_facture.

PeppyBooks expense records capture date, vendor, amount, COA debit account, and tax treatment. They map to Dolibarr llx_facture with type = Invoice_Fournisseur (Supplier Invoice). Each expense line item is linked to the PeppyBooks vendor now mapped as a Dolibarr supplier. Tax code mapping from PeppyBooks to Dolibarr tax rules is applied before expense import to ensure correct VAT or sales tax posting.

PeppyBooks manual journal entries support multi-line debits and credits with optional references to invoices or expenses. We export the full journal entry including all line items and map them to Dolibarr llx_bank (for bank account movements) or llx_accountrprow (accounting ledger rows) depending on whether the journal entry represents a bank transaction or a pure ledger posting. PeppyBooks journal entry naming conventions are preserved as labels to aid reconciliation.

PeppyBooks Product master records include name, SKU (hs_sku equivalent), unit price, cost, tax category, and stock-on-hand (Premium and above). They map to Dolibarr llx_product with type = Product (for inventory) or Service. PeppyBooks tax category maps to a Dolibarr product tax group. Stock-on-hand migrates with the product record; warehouse assignments (Premium tier) map to Dolibarr warehouse stock entries in llx_product_stock per warehouse location.

PeppyBooks multi-store warehousing is available on Premium and above. Warehouse location records map to Dolibarr llx_entrepot. Stock levels per product per warehouse migrate to llx_product_stock entries linked to the corresponding warehouse. If PeppyBooks tracks batch numbers, these map to Dolibarr's lot tracking module if activated; otherwise batch data is preserved as a product custom field.

PeppyBooks Purchase Orders (headers and line items) at Premium tier map to Dolibarr llx_commande_fournisseur. PO workflow states (Open, Closed, Partial) map to Dolibarr status values (Draft, Validated, Approved, Ordered, Received). Line items link to the mapped Supplier third party and Product records. PeppyBooks PO-to-invoice conversion logic does not map directly to Dolibarr's purchasing workflow; we flag any partially-received POs for manual resolution by the purchasing team.

PeppyBooks Sales Orders with headers, line items, and fulfillment status map to Dolibarr llx_commande. Order-to-invoice conversion logic varies; PeppyBooks allows direct invoice creation from orders, which maps to Dolibarr's order-to-invoice action. Order status (Draft, Sent, Fulfilled, Cancelled) maps to Dolibarr status values. PeppyBooks custom order fields migrate to llx_commandedet_extrafields.

PeppyBooks CRM Leads with source, status, owner, and custom fields map to Dolibarr's llx_societe with Tiers type = Prospect. PeppyBooks lifecycle statuses (New, Contacted, Qualified, Lost) map to Dolibarr ProspectStatus values. PeppyBooks allows multiple contacts per Lead; Dolibarr stores contacts separately, so we create a primary contact and flag additional contacts. PeppyBooks Lead scores and custom fields migrate to llx_societe_extrafields.

PeppyBooks Deals carry value, stage, expected close date, and associated contact/company. Dolibarr does not have a native CRM Opportunity object in all versions; we map Deals to llx_projet records with the Opportunity flag (Projet type = Opportunity) if the Project module is activated with the Opportunity feature, or to Dolibarr Commercial Proposals (llx_propal) for sales pipeline tracking. PeppyBooks pipeline stage names are fully customizable and map to Dolibarr project status or proposal status values configured during schema setup.

PeppyBooks Activity records capture calls, emails, notes, and tasks linked to contacts or deals. They map to Dolibarr llx_actioncomm (for calendar events and calls), llx_note (for text notes), and llx_task (for task records). Activity type taxonomy differs; we classify PeppyBooks call records as Dolibarr Interventions (llx_fichinter), emails as Notes with an email flag, and tasks as llx_task. Historical timestamps are preserved as ActivityDate on the Dolibarr record. PeppyBooks CRM attachment links migrate as Dolibarr document attachments.

PeppyBooks Projects, Milestones, and Tasks are available on the Professional plan tier. They map to Dolibarr llx_projet with the Project type (not Opportunity). Milestones map to Dolibarr Task parent records, and PeppyBooks Tasks map to Dolibarr child Task records. PeppyBooks Resource Allocation and Time Spent tracking fields migrate to Dolibarr llx_projet_task_time if the TimeSpent module is activated; otherwise they are preserved in project custom fields for manual time entry.