Epicor Prophet 21
Prophet 21 consulting, implementation & migration
Cloud and on-prem. We implement P21, land the data, build the rules and reports, and keep it running, with the discipline of engineers who administered it before they consulted on it.
The full P21 surface
Implementation & module rollout
Company and entity setup, core settings, module rollout, power-user training, and a cutover that happens in dependency order, rehearsed in Play before it touches Live.
Data migration
QuickBooks, point-of-sale systems, Sage, and legacy ERPs, extracted, cleansed, and landed with a written reconciliation. Done when the trial balance ties, not when the load finishes.
Pricing Service & import discipline
Layouts, match keys, scheduled imports, and the load-order rules that keep a catalog clean. The import module is powerful and unforgiving, we treat it with respect.
DynaChange business rules
Validation, automation, and event-driven rules built on the extensibility suite, tested against the workflows they guard, not just the happy path.
Reports: Crystal & SSRS
Form reports (invoices, pick tickets, POs, statements), operational reporting, and the repair of reports whose totals stopped being trusted.
API integration
REST, OData, and the transaction API, the full write surface. E-commerce, freight, catalog feeds, and automation, built idempotent and logged.
Health check & audit
A read-only pass over configuration, imports, pricing, and reports that tells you what is drifting before it costs you, findings in writing.
We map the software, not just use it
297 windows, mapped
We hold the transaction-API definition of every P21 window, the fields, the keys, the valid values. When we push data, it's schema-validated before it ever reaches your tenant.
22 years of community knowledge
The P21 user community's questions and answers, indexed and searchable. When something breaks, odds are we've already read every thread about it.
The document flows, cold
Quote to order to pick ticket to shipment to invoice to cash, and PO to receipt to voucher, as working knowledge: which windows write which tables, and what breaks when the chain is loaded out of order.
Straight answers
Can you migrate us from QuickBooks to Prophet 21?
Yes, it's one of the most common paths we work. QuickBooks exports feed P21's data templates; GL opening balances come from the trial balance as a journal-entry load; open AR and AP come from the aging detail. Everything lands in a rehearsal environment until the balances tie, and only then does production see data.
We're already live, but pricing and imports keep breaking. Do you only do implementations?
No, rescue and stabilization is its own practice area. We diagnose the mechanism first, put it in writing, and fix it with a regression guard so it stays fixed.
Cloud or on-prem?
Both. The surfaces differ, hosted tenants are API-first while on-prem adds direct SQL access, and our tooling speaks both. The method doesn't change.
Do you replace our current partner, or work alongside them?
Either. We take full engagements, and we also subcontract specialist work, migrations, integrations, report estates, under another firm's project structure.
How do engagements get priced?
From an assessment, in writing. We don't quote blind: the assessment produces a fixed-scope plan with the cost and the verification method attached. Scope changes are change orders, agreed before the work.
Running P21, or about to be?
Tell us where you are, an engineer replies within one business day.
Talk to an Engineer