Prophet 21 ERP Upgrade or Cloud Migration: How Distributors Decide

Consideration	Staying on Prophet 21	Migrating to cloud ERP
Timeline	Version upgrades available now. Final on-premises release 2028.1 arrives May 2028.	Most distributors go live in 90 days, depending on branches and data complexity.
What it costs	Upgrade project, testing and downtime, and a hardware refresh when the cycle comes round.	Implementation and data migration. No servers to buy or replace.
Support horizon	Active Support for on-premises installations ends 30 June 2029.	Continuous updates, with no end-of-support date to plan around.
Customisations	Carried forward, and retested with each version upgrade.	Reviewed individually, then rebuilt as configuration where possible.
IT requirement	Servers, patching, backup and disaster recovery remain yours to run.	Hosting, backups, security and updates included.
Best for	Distributors carrying heavy customisation with a stable roadmap through to 2029.	Distributors who would rather move once than move twice.

Prophet 21 dates from Epicor’s published roadmap, confirmed August 2026. On-premises installations only — Epicor-hosted cloud customers are unaffected. If anything here is out of date, tell us and we will correct it.

1. What comes across, and what gets archived

Customers, vendors, item master, pricing and contract records, open orders — and the transaction history behind them. Most Prophet 21 sites are carrying a decade or more of it.

The question is not whether data can be moved. It is which records come across live, which are archived and still reachable for audit, and who decides.

2. What happens to your customisations

Prophet 21 installations are rarely vanilla. Custom screens, reports written years ago by someone who has since left, workflow changes that nobody documented — these are usually the reason a distributor delays moving at all.

A good migration reviews each one and asks whether it still earns its place. Some are rebuilt as configuration. Some are replaced by standard functionality. Some are quietly retired because the process they supported no longer exists.

3. How long it takes

Timeline depends on three things: how many branches you run, how much of your data needs cleaning before it moves, and how many customisations from question two survive the review.

A single-location distributor with clean data and light customisation sits at the short end. A multi-branch operation with heavy customisation sits at the long end, and should plan accordingly.

4. What runs in parallel, and for how long

This is the question behind the question. Nobody is really asking about parallel running — they are asking whether the business stops if the migration goes wrong.

Running both systems for a period lets you validate that orders, pricing and financials reconcile before you commit. It costs something in effort and duplicate entry, and it is usually worth it.

5. What it costs to stay on-premises

Staying is a legitimate choice, and for some distributors it is the right one until 2029. But the costs of staying are easy to underestimate because they never arrive as a single invoice.

Server refresh cycles. Version upgrade projects, with the testing and downtime around them. Patching. Backup and disaster recovery — including whether yours has been tested recently, and who would run it at 2am.