Prophet 21 Cloud Migration & 2028 Readiness

Your Prophet 21 system runs your business — and a decade of custom SQL, business rules, and Crystal Reports runs inside it. Epicor is moving all future innovation to the cloud, which means that work has to come along. We make sure it does, on your timeline, without breaking what already works.
Start a Migration Readiness Assessment →
P21 Consultanting

What the 2028 timeline actually means

  • There’s a lot of noise about this date. Here are the facts, straight:

    • The final on-premises feature release of Prophet 21 is version 2028.1, tentatively scheduled for May 2028.
    • Active Support for that release runs through June 30, 2029 — security updates, critical patches, and compliance updates included.
    • Sustaining Support begins July 1, 2029. Your system keeps running, but new features stop and support becomes progressively more limited.

    Translation: this is not a shutdown. It’s a planning window. The distributors who come out ahead are the ones who use that window — not the ones scrambling at the edge of it. And if you’re self-hosted in Azure or AWS, note that Epicor still counts you as “on-premises.” This applies to you.

Why the migration is harder than the sales deck suggests

Migrating your base P21 data is the easy part. The risk lives in everything you’ve customized over the years:

  • Custom SQL views and stored procedures
  • Business rules and DynaChange screen modifications
  • Crystal Reports and SSRS reports tied to your schema
  • Third-party, eCommerce, and EDI integrations
  • Bolt-on databases and shadow systems your team built to fill gaps

That’s the part that quietly breaks in a migration — and it’s the part the standard process isn’t built to carry. Cataloging it, re-platforming it, and validating it is the actual project.

How we do it

  1. Migration Readiness Assessment. We inventory every customization, integration, report, and business rule and produce a risk map: what moves cleanly, what has to be rebuilt, and what you can finally retire. You own this document either way.
  2. API-based data conversion. We use the Prophet 21 REST APIs for clean, scriptable, repeatable conversions instead of fragile manual loads — so the move is testable.
  3. Rebuild and validate. We re-implement your rules, reports, and integrations in the target environment and validate against production before anyone relies on them.
  4. Cutover with a rollback plan. A staged cutover with a way back if something surprises us.

Start with a Readiness Assessment

You don’t have to commit to a full migration to get clarity. Our fixed-scope Migration Readiness Assessment gives you a complete customization inventory, a risk map, and a realistic timeline — the document you need to plan the move and brief your CFO or board. The output is yours to keep.

Book a call to scope your assessment →

FAQ

Does my Prophet 21 system stop working in 2028?

No. The final on-premises feature release is around May 2028, with Active Support through June 30, 2029, then Sustaining Support after. Your system keeps running — it just stops getting new features.

I’m self-hosted in Azure. Does this apply to me?

Yes. Self-hosted public-cloud and private-datacenter installs are still treated as on-premises for support purposes.

Do we have to migrate right away?

No — it’s a planning window, not a deadline. But customization-heavy systems need lead time, which is why the smart move is to assess now and schedule the work on your terms.

What’s the hardest part of a P21 cloud migration?

Your customizations — business rules, reports, and integrations — not the base data. That’s where projects run over, and it’s where we focus.