Migrate from PeppyBooks to Microsoft Dynamics 365 Business Central

PeppyBooks maintains a hierarchical CoA with account codes, types, and tax-mapping attributes. Because PeppyBooks allows fully custom account code lengths, naming conventions, and parent-child hierarchies, we export the full CoA as a structured CSV before any transaction migration. Each source account is mapped manually to a destination G/L Account, preserving the PeppyBooks account name as the Account Name field with the original code stored in a custom field for reconciliation. If the destination has a default CoA template, we either merge source accounts into existing destination accounts or create new ones per the customer's accountant's preference.

PeppyBooks Client records include contact details, billing address, payment terms, and opening balance. We map them 1:1 to Dynamics 365 Customer. The opening balance from PeppyBooks carries forward as an opening balance transaction or as a starting value on the Customer ledger entry in Business Central. Payment terms map to Dynamics Payment Term codes. PeppyBooks assigns each Client a number; we preserve this as the external reference number in Dynamics.

Vendor master data mirrors Client structure with address, payment terms, and opening balance. We migrate Vendors to Dynamics Vendor, carrying forward any outstanding AP balance as an opening balance entry. PeppyBooks vendor-specific fields (tax registration, W-9 status) map to the corresponding Dynamics Vendor tax registration fields.

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, payment records, and currency. Invoices are imported as posted or open based on their PeppyBooks status, with the PeppyBooks invoice number preserved as an external document number. Partial payments are handled as payment journals applied to the invoice.

PeppyBooks Expense records capture date, vendor, amount, CoA debit account, and tax treatment. We migrate expenses as individual journal lines, mapping PeppyBooks tax codes to the destination's equivalent tax group and tax product posting group. Prepaid expenses with uncredited amounts require a separate balance-sheet posting, which we handle by creating a prepaid expense account mapping during scoping.

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 varies by customer. We import them as General Journal batches in Dynamics with each PeppyBooks journal preserved as a separate batch with a reference to the original PeppyBooks entry number. Reversing entries are created for any PeppyBooks entries with future effective dates.

Product master records in PeppyBooks include name, SKU, unit price, cost, tax category, and stock-on-hand at Premium and above. We migrate products 1:1 to Dynamics Item with the SKU stored in the item number or as a custom identifier. Inventory quantities are imported as opening inventory journal entries against the destination warehouse location. Product type (stock, service, non-stock) is determined from the PeppyBooks product category.

Warehouse assignments are only available on PeppyBooks Premium and Ultimate tiers. Where a customer uses multiple stores, we map warehouse locations to Dynamics Location or Warehouse codes. PeppyBooks batch tracking maps to Dynamics Item Tracking (lot/serial) if the Ultimate tier is in scope. Business Central allows up to 99 locations by default; Finance and Operations supports unlimited warehouse configurations.

Purchase Orders are available at PeppyBooks Premium tier and above. We export PO headers and line items, mapping the PeppyBooks PO status to Dynamics Purchase Order status. Open POs migrate as open orders; closed POs are archived with their fulfillment history. PeppyBooks does not support PO approval workflows natively, so any PO workflow states are preserved as custom status fields rather than mapped to Dynamics approval workflows.

Sales Orders in PeppyBooks support conversion to invoices. We export order headers, line items, and fulfillment status. Order-to-invoice conversion history is preserved by importing fulfilled lines as shipped and invoiced, and open orders as open Sales Orders. Dynamics Sales Order numbering is mapped from the PeppyBooks order number series.

PeppyBooks CRM holds Leads with source, status, owner, and custom fields. Dynamics 365 CRM apps use a Lead object for unqualified prospects. We migrate PeppyBooks Leads as CRM Leads, mapping the PeppyBooks lead status to the Dynamics Lead Status picklist. PeppyBooks custom fields are mapped to Dynamics custom fields on the Lead entity. PeppyBooks lifecycle or lead score fields migrate as custom integer fields.

Deals in PeppyBooks CRM carry value, stage, expected close date, and associated contact or company. Pipeline stage names are fully customizable in PeppyBooks, so we export the active stage map and apply a naming convention that aligns with the destination Dynamics Sales Process. Each PeppyBooks pipeline becomes a Dynamics Opportunity Record Type with its own Sales Process whitelisting the relevant stage values. Deal value and expected close date migrate directly to Opportunity Amount and Close Date.

Activity records capture calls, emails, notes, and tasks linked to contacts or deals. PeppyBooks activity-type taxonomy differs from Dynamics CRM. We export activities and map calls to Task with TaskSubtype=Call, emails to EmailMessage, and notes to Note. Activity dates are preserved as ActivityDate or Start DateTime on the corresponding Dynamics record. PeppyBooks attachment URLs are noted for manual re-upload since Dynamics stores attachments as Note records or SharePoint files.

Projects, Milestones, and Tasks are available on PeppyBooks Professional plan. We export the project hierarchy and task assignments. Project-specific fields like Resource Allocation and Time Spent Tracking do not have direct Dynamics equivalents in all tiers; Business Central requires the Project Essentials or Premium extension for full project accounting. We flag which PeppyBooks project fields are migratable versus which require a Dynamics project module configuration decision during scoping.