Migrate from PeppyBooks to Epicor Prophet 21

PeppyBooks maintains a hierarchical CoA with account codes, types, and tax-mapping attributes. Epicor ERP uses a segmented GL Account structure with Company, Division, Department, and Account segments. We export the full PeppyBooks CoA as a structured list, then create a segment-mapping configuration in Epicor that resolves each PeppyBooks account code to the appropriate Epicor account segment combination. If Epicor has a default CoA, we either merge source accounts into existing Epicor accounts or create new ones, preserving the PeppyBooks account name as a description label for accountant reconciliation.

PeppyBooks Client records include contact details, billing address, payment terms, and opening balance. We map them 1:1 to Epicor Customer records, preserving the opening balance as an AR aging entry. PeppyBooks multi-currency support (Growth tier) maps to Epicor's currency configuration with exchange rate context carried forward. Customer payment terms migrate as Epicor Payment Terms linked to the Customer record.

PeppyBooks Vendor master data mirrors Client structure with address, payment terms, and opening balance. We migrate Vendors to Epicor Vendor records, carrying forward any outstanding AP balances as AP aging entries. 1099 vendor classification from PeppyBooks maps to Epicor Vendor's tax configuration. Multi-currency vendor amounts migrate with their original exchange-rate context.

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, then create Epicor AR Invoice records. PeppyBooks tax codes map to Epicor Tax Business Unit configuration. Historical paid invoices migrate as posted records with full line-item detail; open invoices migrate as open AR items for follow-up.

PeppyBooks Expense records capture date, vendor, amount, CoA debit account, and tax treatment. We migrate expenses as Epicor AP Invoice or Expense Entry records, mapping PeppyBooks tax codes to Epicor's equivalent tax authority setup. PeppyBooks Malaysia SST postings tied to inventory movements receive dedicated tax-code mapping to ensure both financial records and stock valuation carry forward correctly.

PeppyBooks journal entries support multi-line debits and credits with optional references to invoices or expenses. We export full journal entries including all line items and create Epicor GL Journal Entry records. PeppyBooks journal-entry naming conventions and reference fields map to Epicor Journal Entry description and explanation fields. Entry dates and posting periods migrate to ensure period assignment is preserved.

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 to Epicor Part master records, treating stock levels as on-hand quantity in Epicor's primary Site. PeppyBooks product categories map to Epicor Product Group codes. Unit of measure from PeppyBooks maps to Epicor Part's UOM configuration.

PeppyBooks SKU codes migrate to Epicor Part Number with alternate part number (Xref) records created where multiple SKU formats exist. Epicor's alternate part number cross-reference table handles scenarios where PeppyBooks customers used supplier-specific or customer-specific SKU formats. We preserve the original PeppyBooks SKU as an Xref to support incoming POs or SOs referencing the old code.

PeppyBooks Warehouse assignments are only available on Premium and Ultimate tiers. Where a customer uses multiple stores, we map warehouse locations to Epicor Site and Warehouse entities. Epicor's multi-site architecture supports transfer orders and inter-site inventory visibility that PeppyBooks does not provide, so we configure Site relationships during migration to enable these workflows post-migration.

PeppyBooks Purchase Orders are available at Premium tier and above. We export PO headers and line items, mapping PeppyBooks PO statuses to Epicor PO states (open, pending, closed). PeppyBooks PO approval workflows do not migrate; we document the approval chain as a configuration item for Epicor's PO workflow setup. Line items resolve Part and Vendor references at migration time.

PeppyBooks Sales Orders support conversion to invoices. We export order headers, line items, and fulfillment status, then create Epicor Sales Order records. Order-to-invoice conversion logic from PeppyBooks is noted and mapped to Epicor's order billing and fulfillment rules. Open orders migrate as active Epicor SOs; closed and fulfilled orders migrate as historical records.

PeppyBooks batch tracking is available at Ultimate tier. Where a customer uses batch tracking, we migrate lot numbers to Epicor's Lot/Serial number tracking linked to Part records. Epicor's lot traceability supports full FIFO and FEFO costing methods; we flag any PeppyBooks lot expiration dates for Epicor's lot-specific cycle counting setup. If PeppyBooks batch data is absent, we initialize lot tracking as not lot-controlled for migrated stock.

PeppyBooks CRM holds Leads with source, status, owner, and custom fields. Epicor ERP's CRM module uses a different lifecycle model. We map PeppyBooks Leads to Epicor Lead or Prospect records, preserving source attribution and lead scoring values. PeppyBooks pipeline stage names export and are mapped to Epicor's lead status configuration during CRM module setup.

PeppyBooks Deals carry value, stage, expected close date, and associated contact or company. Epicor's manufacturing-oriented CRM model uses Quotes and Orders as the primary sales document rather than Deals. We map PippyBooks Deal values to Epicor Quote records with the expected revenue amount and close date. Pipeline stage names are fully customizable in PeppyBooks; we export the active stage map and apply a naming convention to Epicor's Quote or Lead status values.

PeppyBooks Activity records capture calls, emails, notes, and tasks linked to contacts or deals. We export activities and create Epicor Activity records linked to the corresponding Customer, Vendor, Part, or Order. PeppyBooks activity-type taxonomies differ from Epicor's; we map call records to Epicor Activity with activity type Phone Call, emails to Email, and notes to Note. Historical activity timestamps and owner assignments migrate to preserve the audit trail.