Migrate from PeppyBooks to Acumatica

PeppyBooks clients migrate as Acumatica Customers. PeppyBooks does not store Customer Class, so we assign a default class during migration and surface it in the migration plan for your admin to refine per customer group before the full run. Where PeppyBooks stores customer type or industry codes, we use those to inform class assignments. All default class assignments are flagged in the migration plan and can be adjusted before the full migration runs, particularly for customers with distinct payment terms or credit limits.

PeppyBooks vendors migrate as Acumatica Vendors. Payment terms and Tax ID (if populated in PeppyBooks) map to the corresponding Acumatica Vendor fields; if PeppyBooks stores tax IDs in a custom field, we surface the mapping in the plan. We also preserve vendor classification data, including any vendor categories or type codes from PeppyBooks, to inform vendor class assignments in Acumatica for downstream purchasing workflows.

The PeppyBooks chart of accounts is the migration's largest structural challenge. PeppyBooks stores account names as a flat list; Acumatica requires a Branch + Subaccount structure. We analyze all PeppyBooks accounts by type (Asset, Liability, Equity, Revenue, Expense) and propose a branch-and-subaccount hierarchy during the discovery step before any data loads. The proposed hierarchy preserves account balances in the correct segments and is reviewed with your Acumatica admin before any GL data is loaded.

Open PeppyBooks sales invoices migrate as Acumatica AR Invoices with Customer, Invoice Nbr., Invoice Date, Due Date, and Payment Terms preserved. Line items map to Invoice Details with Inventory ID, Description, Qty., and Unit Price. We also map PeppyBooks tax codes to Acumatica Tax Categories and apply the appropriate Tax Zone from the tax configuration plan. All migrated invoices retain their original PeppyBooks IDs in a custom field for traceability.

Open PeppyBooks purchase invoices migrate as Acumatica AP Invoices. Vendor, Invoice Nbr., Invoice Date, and Due Date carry over; line items map with Inventory ID or Expense Account, Description, Qty., and Unit Cost. PeppyBooks tax codes map to Acumatica Tax Categories, and the vendor's assigned Tax Zone applies the correct tax jurisdiction. Reference numbers and internal notes from PeppyBooks are preserved in Acumatica's invoice record.

PeppyBooks products flagged as inventory items become Acumatica Stock Items. If PeppyBooks does not store a valuation method, we default to Average cost and flag each item for your admin to set the correct Method (Standard, Average, FIFO, Lot-Specific) before the migration finalizes. We also map PeppyBooks item types, lot numbers, and reorder points to the corresponding Acumatica Stock Item fields including ValMethod, LotSerClass, and ReorderPoint.

PeppyBooks products not tracked in inventory become Acumatica Non-Stock Items — used on quotes, sales orders, and purchase orders without stock implications. Non-Stock Items carry over the product description, default unit of measure, and any standard pricing from PeppyBooks. They are created with Item Type = Non-Stock Item and can be flagged as expense or service items depending on their usage in PeppyBooks.

Open PeppyBooks sales orders migrate as Acumatica Sales Orders with Customer, Order Nbr., Date, and Payment Terms. Line items carry over with Product, Description, Qty., Unit Price, and Tax Group mapped. The customer's assigned Tax Zone applies to each order, and any PeppyBooks shipping or fulfillment notes are preserved in Acumatica's order record for warehouse processing.

Open PeppyBooks purchase orders migrate as Acumatica Purchase Orders with Vendor, PO Nbr., Date, Delivery Date, and Status. Line items map with Product, Description, Qty., Unit Cost, and Tax Group. PeppyBooks vendor confirmations and internal notes are preserved, and the vendor's Tax Zone and payment terms apply to the Acumatica PO for consistent accounts payable processing.

PeppyBooks Projects and Milestones have no direct Acumatica equivalent. We export the project structure as a reference document. If your Acumatica license includes the Projects module, we map to Project tasks and billing rules; otherwise, project data migrates as custom fields or tags on related invoices. The exported reference includes project name, milestone names, milestone dates, milestone amounts, and links to associated invoices and purchase orders.

PeppyBooks client contact names and emails migrate as Acumatica Contacts linked to the corresponding Customer record. Primary phone, mobile phone, and job title carry over if populated in PeppyBooks. We preserve the contact's relationship to the PeppyBooks client via the linked Customer record and retain any secondary email addresses stored in PeppyBooks contact records.

PeppyBooks tax codes become Acumatica Tax Zones scoped to the relevant jurisdiction. Each tax code maps to a Tax Zone with one or more Tax Agencies and a Tax Category for each invoice line. We deliver the tax zone and agency configuration plan before the migration runs. The plan includes the PeppyBooks tax code name, the proposed Acumatica Tax Zone name, linked Tax Agency, and default Tax Category for each line type.