Migrate from PeppyBooks to Infor CloudSuite Corporate

PeppyBooks maintains a hierarchical COA with account codes, types, and tax-mapping attributes. Infor CloudSuite Industrial also uses a hierarchical COA with account codes and types. PeppyBooks allows fully custom account code lengths and naming conventions, so we export the complete COA as a structured list before any transaction migration, manually map each source account code to a destination account code, and preserve the original PeppyBooks account name as a label or description in Infor. If the destination Infor deployment has a default COA template, we merge source accounts into existing Infor accounts where a clear match exists and create new Infor accounts where no match is possible.

PeppyBooks Clients contain contact details, billing address, payment terms, and opening balance. We map them 1:1 to Infor Customer records. The PeppyBooks opening balance is migrated as an opening-receivables journal entry in Infor rather than as a field on the Customer record itself, because Infor handles opening balances through the accounting module. Multi-currency clients carry their original exchange-rate context to Infor's currency fields on the Customer record.

PeppyBooks Vendors mirror the Client structure with address, payment terms, and opening balance. We map them 1:1 to Infor Supplier records, carrying forward outstanding AP balances as opening-payables journal entries in Infor. PeppyBooks Malaysia SST vendor tax registrations are mapped to the corresponding Infor tax authority codes during import, with an SST reconciliation report run post-import to catch mismatches.

PeppyBooks Invoices link Clients, line items, tax codes, and COA revenue accounts. We export all invoice fields including status (draft, sent, paid), due dates, and payment records. Open invoices migrate as open AR records in Infor with the original PeppyBooks invoice number preserved as a reference field. Paid invoices migrate as historical records with the payment date and amount. PeppyBooks tax codes map to Infor tax codes, and the mapping is validated before import to prevent tax-amount discrepancies propagating into the financial records.

PeppyBooks Expense records capture date, vendor, amount, COA debit account, and tax treatment. We migrate each expense as an individual line item, mapping PeppyBooks tax codes to Infor's equivalent tax setup. Outstanding vendor bills (unpaid expenses) migrate as open AP records in Infor, preserving the PeppyBooks expense number as a reference.

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. Journal-entry naming conventions in PeppyBooks are customer-defined, so we preserve the original PeppyBooks journal name as a memo field in Infor and map each line's COA account code using the COA mapping established in the first migration step.

PeppyBooks Product records include name, SKU, unit price, cost, tax category, and stock-on-hand (Premium and above). We migrate products 1:1 to Infor Item Master records, mapping the PeppyBooks SKU to the Infor Item Number and preserving the current stock-on-hand quantity. Products without inventory tracking (Growth tier) migrate with zero stock and are flagged for the customer to populate manually if they activate inventory management in Infor.

Warehouse assignments in PeppyBooks are only available on Premium and above. Where a customer uses multiple stores, we map each PeppyBooks warehouse to a corresponding Infor warehouse or branch location. Infor CloudSuite Industrial uses a plant and warehouse location model; we match PeppyBooks warehouse codes to Infor site codes and flag any PeppyBooks warehouses that have no corresponding Infor site for manual configuration before inventory import.

Purchase Orders in PeppyBooks are available on Premium tier and above. We export PO headers and line items with supplier, date, and fulfillment status. Open and partially received POs migrate as open Purchase Orders in Infor. PeppyBooks PO line status (pending, received, closed) maps to Infor PO line receipt status, but PeppyBooks partial-receipt quantities are reconciled against PeppyBooks inventory records to catch discrepancies before import.

Sales Orders in PeppyBooks support conversion to invoices. We export order headers, line items, and fulfillment status. Open Sales Orders migrate to Infor as open Sales Orders, preserving the customer reference and line-item mapping to the Infor Item Master. Infor Sales Order conversion to Invoice follows Infor's own workflow, which is different from PeppyBooks' one-click conversion, so we document the equivalent steps for the customer's admin.

PeppyBooks CRM Leads contain source, status, owner, and custom fields. Infor CloudSuite Industrial has no native CRM module; CRM is a separate add-on evaluated independently. We export the full PeppyBooks Lead list including all fields and custom properties, and deliver it as a structured CSV with a written recommendation for Infor CRM add-on or a third-party CRM (Salesforce, HubSpot) as the rebuild destination. This is not a live CRM migration; it is a data inventory for manual rebuild.

PeppyBooks Deals carry value, stage, expected close date, and associated contact or company. Infor CloudSuite Industrial does not include a pipeline management module, so Deals have no direct Infor equivalent. We export the active pipeline stage names and values from PeppyBooks and document the full deal list with stage assignments and deal values in a CSV for the customer to use when rebuilding pipeline tracking in the selected CRM platform.