What breaks when P21 moves to Epicor Cloud
Anything that reaches into the server or the database. In Epicor's cloud, Epicor runs both, so direct SQL writes, custom database objects, rules that write with SQL, local file paths and on-premises sign-in and printing each need a supported path before cutover.
Download the PDFThe dates
- Final on-premises Prophet 21 feature release
- 2028.1, tentatively May 2028
- Active Support for release 2028.1
- Through June 30, 2029
- Sustaining Support for release 2028.1
- Begins July 1, 2029
- Final on-premises Epicor Kinetic release
- 2028.1
Source: Epicor news release, January 6, 2026. Your own support terms come from your Epicor agreement.
Seven areas to inventory
For the IT lead at a Prophet 21 distributor. Updated October 2026.
| Area | What changes | Inventory now | Date pressure |
|---|---|---|---|
| Customizations | What changesViews, procedures, triggers and custom SQL alerts you added inside the database have nowhere to live. Custom SQL alerts are not recommended for cloud sites. From 24.2 and 25.1, an alert can trigger a business rule instead. | Inventory nowEvery screen change, user-defined field and SQL object, and who uses each one. | Date pressureEach one retired now is one less to rebuild. |
| DynaChange business rules | What changesIn Epicor Cloud, the database you can query directly is a read-only replica. Standard Business Rules, the API, the Stored Procedure Executor and Automation Studio are the approved ways to modify data in the cloud, and SQL-based YDBC rules also run on hosted systems. Rules that write to tables with direct SQL connections or write to local server paths need rework. | Inventory nowReview every registered rule for direct SQL writes (INSERT, UPDATE, DELETE outside approved P21 rule or API paths) or local file and server dependencies, and note each rule's framework. Since 25.2, .NET 8 is recommended for new rules. | Date pressureReworked rules need testing in Play, and direct SQL against the cloud Play database is a paid add-on. |
| Crystal forms | What changesForm files move to the Epicor-hosted file system, reached by SFTP. The Crystal forms package remains a separately licensed product in the cloud. | Inventory nowEvery form in use (invoices, pick tickets, POs, statements), its .rpt file and its data source. | Date pressureForms print daily. Test each in Play before go-live. |
| SQL jobs and direct database access | What changesThe database you can query directly in the cloud is a read-only replica, and SSMS write connectivity is not supported. SQL Agent jobs and external scripts that update data must move to Business Rules, the API, the Stored Procedure Executor, Automation Studio or a scheduled import. | Inventory nowEvery SQL Agent job, linked server, ODBC connection and spreadsheet that touches P21, and whether it writes. | Date pressureJobs that write take the longest to replace, so start with them. |
| Integrations and EDI | What changesFolder-based EDI keeps working, but the folders live on Epicor's SFTP site. Your EDI engine reads and writes there or syncs a local copy. Writes from other systems go through the P21 API. | Inventory nowEach connection, its method (API, file or direct SQL) and the system on the other end: EDI, tax, shipping, document management, ecommerce, payments. | Date pressureTrading partners may each need a test cycle. Schedule them early. |
| Reports | What changesReports that query SQL Server directly must point at the read-only database. Power BI and Power Automate can reach it through Microsoft's data gateway. | Inventory nowEvery report, dashboard and Excel query, with its owner and data source. | Date pressureTest month-end reports against a full close in Play. |
| Users and security | What changesSign-in and printing stop running through your own servers. Revalidate authentication (Active Directory pass-through or Azure AD) and printing (WWMS Edge Agent, label and document printers). | Inventory nowUser accounts and roles, how each user signs in, every printer P21 sends to, and who holds admin rights. | Date pressureRe-test sign-in and printing at every branch before cutover weekend. |
Sources: Epicor news release, January 6, 2026; P21 user group forum threads 246094, 246874, 244996, 245061, 246945, 247751, 233790, 245912, 244693, 226329 and 161883.
Plan the inventory with an engineer
Lumina ERP runs a fixed-fee readiness audit that rates each item as moves as is, needs rework or can retire. Tell us your P21 release, how many rules and custom reports you run and what connects to the database.
Related work
- P21 cloud migration audit
The fixed-fee readiness audit behind this checklist.
- Prophet 21 support
Day-to-day help before and after the move.
- Integration and development
Rebuild connections on supported paths.
- Pricing
How we price audits, projects and support.