16 Sep Prophet 21 Cloud Migration FAQs: Your Questions Answered
Contact us to schedule a Prophet 21 cloud-readiness assessment.
Epicor’s cloud announcement has created an understandable list of questions for Prophet 21 customers.
Does on-premises Prophet 21 stop working in 2028? Will existing customizations survive the move? What happens to reports, integrations, database access, and the desktop interface?
The short answer is that a Prophet 21 cloud migration is not a forced shutdown or a simple software upgrade. It is a transition that affects the system, its connected applications, and the people and processes surrounding it.
Below, we answer the questions we hear most often from P21 users—and explain how Scaled Solutions helps distributors prepare for the move.
For a closer look at the announced dates, read our overview of what the Prophet 21 2028 timeline means for distributors.
1. Is Prophet 21 on-premises shutting down in 2028?
No. Your Prophet 21 system will not automatically stop working in 2028.
Epicor has announced that Prophet 21 version 2028.1, tentatively scheduled for May 2028, will be the final on-premises release to receive new features. Active Support is scheduled to continue through June 30, 2029. Sustaining Support begins July 1, 2029.
The system may continue operating after those dates, but future innovation will be delivered through Epicor Cloud, and on-premises support will become more limited.
How Scaled helps: We assess your current environment and help leadership understand the operational, technical, and support implications of staying on-premises, completing a phased transition, or moving fully to Epicor Cloud.
2. Do we have to migrate before May 2028?
Epicor has not described May 2028 as a forced shutdown date. However, waiting until 2028 to begin planning could create unnecessary pressure.
A typical migration can take several months. Environments with extensive customizations, integrations, multiple companies, complex reporting, or significant data issues may require more time.
Beginning with an assessment does not commit your company to an immediate migration. It gives you a realistic view of your scope, risks, resource needs, and timeline.
How Scaled helps: Our on-premises migration assessment inventories your customizations, integrations, data complexity, reporting, infrastructure, and user requirements before a migration date is selected.
3. Are we considered on-premises if another company hosts our system?
Possibly. If your Prophet 21 environment is not hosted within Epicor Cloud, do not assume that it falls outside the announced timeline.
This may include environments running:
- On servers in your facility
- In a private or colocated data center
- On infrastructure your company manages through Azure or AWS
- Through an unaffiliated third-party hosting provider
Your licensing arrangement alone may not determine how the environment is classified.
How Scaled helps: We review your current hosting model, infrastructure, version, licensing, and technical dependencies so you understand which parts of the transition apply to your organization.
4. Will we lose our Prophet 21 customizations?
Not necessarily—but every customization should be reviewed before migration.
DynaChange rules, forms, custom screens, business rules, scripts, and source-code modifications do not all transition in the same way. Some may remain compatible, some may require rebuilding, and others may no longer be necessary because standard functionality has changed.
Automatically recreating every customization can also carry outdated processes into the cloud.
How Scaled helps: Our in-house development team conducts a pre-migration compatibility audit of each custom solution. We identify what can move, what must be redesigned, and what should be retired before rebuilding begins.
For a broader list of technical preparation steps, see our existing guide to upgrading Prophet 21 to Epicor Cloud Hosted.
5. What happens to our integrations and direct database access?
Cloud environments can change how data is accessed and how connected applications communicate with Prophet 21.
Integrations that use supported APIs may carry forward more easily. Connections relying on direct SQL access, database writes, scheduled jobs, or older import methods require closer evaluation.
Do not wait until testing to discover which applications depend on your current database structure.
How Scaled helps: We map every integration, data connection, and third-party application before migration. Our team then determines what can be reconnected, what needs to be rebuilt, and how each connection will be validated.
6. What happens to Crystal Reports and SSRS?
Your existing reporting environment will need to be inventoried.
That does not mean every report should automatically be rebuilt. Some reports may be business-critical, while others may duplicate newer functionality or no longer be used. The migration is an opportunity to determine what information each department actually needs and how it should be delivered in the cloud.
How Scaled helps: We document Crystal Reports, SSRS reports, forms, dashboards, and their users. We then help scope and execute the transition to supported cloud reporting options while validating that essential information remains available.
7. Will users have to move to the Prophet 21 Web UI?
The move to Epicor Cloud should include a clear plan for the Web UI. For teams accustomed to the legacy desktop interface, this is both a technical and organizational change.
Screens, navigation, workflows, and user expectations may differ. Employees need time to validate their responsibilities in the new environment and practice realistic scenarios before go-live.
How Scaled helps: We configure and validate Web UI screens, review user roles and permissions, and provide role-based training using your company’s actual workflows. Learn more about our Prophet 21 training services.
8. How can we be confident everything will work after migration?
Testing should cover complete business processes—not just individual screens.
An order can affect sales, purchasing, pricing, inventory, warehouse operations, accounting, reporting, and customer communication. Testing only order entry may leave downstream issues undiscovered.
Your team should validate:
- Common daily transactions
- High-volume workflows
- Business rules and custom solutions
- Reports and forms
- Third-party integrations
- User roles and permissions
- Exceptions and uncommon scenarios
- Converted data and financial balances
How Scaled helps: We create and manage structured testing plans, support user acceptance testing, document issues, and validate corrections before cutover. Read more about Prophet 21 user acceptance testing.
9. What happens after go-live?
Go-live is the beginning of stabilization—not the end of the project.
Users will have questions. Real transactions may expose exceptions that did not appear during testing. Performance, integrations, workflows, and adoption must be monitored closely.
Without structured support, employees may create new workarounds when early issues arise.
How Scaled helps: The same team that supports your assessment, migration, configuration, and training stays involved through go-live and stabilization. We help prioritize issues, support users, monitor performance, and continue improving the environment after launch.
Learn more about our approach to Prophet 21 post-go-live support and optimization.
Your First Step Is Understanding What You Have
The most important question is not simply, “When should we migrate?”
It is: “What must be understood, improved, rebuilt, and validated before we do?”
Scaled Solutions manages the full Prophet 21 cloud migration process, including:
- On-premises migration assessments
- Custom solution compatibility reviews and rebuilds
- Data migration and validation
- Cloud environment configuration
- Legacy UI to Web UI transition
- Reporting and integration changes
- User training and change management
- Go-live support and stabilization
- Multi-company and carve-out separation
As an Epicor Platinum Partner and Authorized Prophet 21 Reseller, Scaled Solutions combines Prophet 21 application expertise, in-house development, process improvement, and change management within one team.
Not sure how ready your Prophet 21 environment is?
Contact us to schedule a Prophet 21 cloud-readiness assessment.