Migrate your PeppyBooks data

PeppyBooks maintains a hierarchical COA with account codes, types, and tax-mapping attributes. We export the full COA as a structured list and create matching accounts in the destination, flagging any tax-related accounts that require special destination-side configuration.

Client records in PeppyBooks include contact details, billing address, payment terms, and opening balance. We map them 1:1 to Customers in most destination systems and preserve the opening balance as a receivable or equity entry.

Vendor master data mirrors client structure with address, payment terms, and opening balance. We migrate Vendors to the destination's supplier or vendor entity and carry forward any outstanding AP balances as payables.

PeppyBooks generates invoices linked to Clients, Line items, tax codes, and COA revenue accounts. We export all invoice fields including status (draft/sent/paid), due dates, and payment records, and recreate them in the destination with line-item fidelity preserved.

Expense records capture date, vendor, amount, COA debit account, and tax treatment. We migrate expenses as individual line items, mapping PeppyBooks tax codes to the destination's equivalent tax setup.

Journal entries in PeppyBooks support multi-line debits and credits with optional references to invoices or expenses. We export the full journal entry including all line items, but journal-entry naming conventions and reversal mechanics vary between platforms and require field-level mapping per customer.

Product master records include name, SKU, unit price, cost, tax category, and stock-on-hand at Premium and above. We migrate products 1:1 along with current inventory quantities, treating stock levels as an opening balance in the destination.

Warehouse assignments are only available on Premium and Ultimate tiers. Where a customer uses multiple stores, we map warehouse locations to the destination's corresponding inventory location or branch entity, flagging any warehouses that have no equivalent in the target.

Purchase Orders are available at Premium tier and above. We export PO headers and line items, but PO workflow states (open/closed/partial) do not always map directly to destination ERP PO objects and may need manual review post-migration.

Sales Orders in PeppyBooks support conversion to invoices. We export order headers, line items, and fulfillment status, noting that order-to-invoice conversion logic varies across destination platforms and may require re-conversion.

PeppyBooks CRM holds Leads with source, status, owner, and custom fields. Many destination CRMs use a different lifecycle model (Contacts vs Leads vs Prospects) so we merge or split accordingly and preserve the original Lead status as a custom property in the target.

Deals in PeppyBooks CRM carry value, stage, expected close date, and associated contact/company. Pipeline stage names are fully customizable, so we export the active stage map and apply a naming convention in the destination or carry original stage names as a label set.

Activity records capture calls, emails, notes, and tasks linked to contacts or deals. We export activities as notes or tasks in the destination, noting that activity-type taxonomies differ between PeppyBooks and most target CRMs.

Projects, Milestones, and Tasks are available on the Professional plan tier. We export the project hierarchy and task assignments, but project-specific fields like Resource Allocation and Time Spent Tracking require field mapping against the destination's project object schema.