Prophet 21 Is Moving to Epicor's Cloud: What Changes for EDI

In January 2026, Epicor published the schedule for its last on-premises releases. For Prophet 21, the final on-premises feature release is 2028.1, tentatively scheduled for May 2028, and future versions move to Epicor Cloud (Epicor's announcement, summarized by Constellation Research).

For most P21 distributors, that means a move to Epicor-hosted P21 within the next few years. EDI is one of the integrations that has to move with it. Several of our P21 customers already run on Epicor-hosted P21, and more have moves planned. This guide sums up what we've learned so far: what changes for EDI, what stays the same and what to ask for early.

The Epicor Timeline in Brief

• 2028.1, tentatively May 2028: the final on-premises feature release of Prophet 21.
• Through June 30, 2029: Active Support for on-premises release 2028.1.
• From July 1, 2029: Sustaining Support begins.
• After 2028.1: new versions ship in Epicor Cloud. Epicor's migration program is called Ascend with Epicor.

On-premises P21 doesn't stop working in 2028. But new features will reach only the cloud version, and active support ends in mid-2029. If you plan to move, plan the EDI part at the same time as the ERP part, not after it.

What Changes for EDI When P21 Leaves Your Server Room

On-premises, EDI software usually sits on the same network as P21. It reads the SQL Server database directly to build outbound documents and to check inbound ones. It hands orders, receipts and invoices to P21 as import files in a folder that P21's scheduled import picks up.

In Epicor's cloud, four things are different:

1. Database access is limited. You no longer run the SQL Server. In the hosted moves we have handled, Epicor provided read-only database logins on request. Anything that used to write straight to the database, even a small status field, needs another route.
2. Connections are encrypted. Epicor now requires encrypted connections to hosted P21 databases, so connection settings that worked on your local network have to be updated.
3. Imports go over SFTP or an API. Import files go to an SFTP import folder that Epicor provides for the hosted environment instead of a local share. P21's Transaction API is the alternative.
4. The EDI software still needs a home. Moving P21 doesn't move your EDI server. It still needs a machine to run on, with a network route to the hosted database and the SFTP folder.

How EDI Connects to Epicor-Hosted P21

Reading P21 Data

Outbound documents such as 855 acknowledgments, 856 ship notices and 810 invoices are built from P21 data. Inbound documents are checked against it too: ship-to lookups, duplicate-order checks and item matches. On hosted P21, those reads go through the read-only login over an encrypted connection. Expect them to cross a longer network path than before.

Import Files Over SFTP

The import route P21 teams already know still works. Inbound orders, receipts and vouchers become P21 import files, and P21's scheduled import processes them. The difference is the destination: the files go to the hosted SFTP import folder. Comparatio sends them one SFTP session at a time.

The P21 Transaction API

P21 can also accept transactions through its Transaction API. In release 14.18 (October 2026), Comparatio added the API as an optional import path for all P21 imports. That includes orders and order changes, quotes, customers, contacts and ship-tos, purchase orders and receipts, ASNs, transfers and adjustments, AP and AR, and 832 catalogs.

The API is switched on per document type, in three steps: file, shadow, API. In shadow mode, the file import keeps doing the real work while the API path runs beside it, and the results are compared document by document. A document type moves to the API only after those comparisons are reviewed. If a post ends with an unknown outcome, such as a timeout, it is held for review rather than sent again, so a network hiccup doesn't create a duplicate order. The API path supports Epicor-hosted P21 through Epicor's identity sign-in, and it was tested against a customer's P21 Play environment in October 2026.

The API path is new. You don't need it to run EDI on hosted P21: SFTP import files remain the standard route.

A Planning Checklist and Timeline

As Soon as You Have a Move Date

• List every EDI touchpoint with P21: which documents read P21, which ones import, and any fields EDI updates directly.
• Decide where the EDI software will run after the move: a virtual machine you control, or a server your EDI provider hosts.
• Check whether any of your EDI still runs through TPCx. TPCx reaches end of life in December 2026, long before Epicor's on-premises dates, so finish that TPCx migration first.
• Give your EDI provider the date, and get the reconfiguration scheduled and quoted.

When Epicor Sets Up the Hosted Environment

• Request read-only database logins for Live and Play.
• Request the SFTP import folder and its login.
• Confirm the encrypted connection settings, and how the EDI server will reach the hosted database and SFTP folder, including any IP allow-listing.

During Play Testing

• Point EDI at hosted Play and run real documents for your largest partners: inbound orders, outbound acknowledgments, ship notices and invoices.
• Run lookups with realistic volume and watch the timings.
• Look for anything EDI used to do that the hosted login now refuses.
• If you plan to use the API path, run those document types in shadow mode and review the comparisons.

Cutover

• Switch in the morning, never on a Friday, with an engineer watching the first hours.
• Confirm that the first import files are picked up and the first outbound documents are sent and acknowledged.
• Agree in advance what happens if the first day goes wrong.

The First 30 Days

• Watch for import files that stop being picked up, for query timeouts and for permission errors.
• Re-check EDI after every Play refresh and P21 upgrade. Both are common reasons for an EDI support ticket.

Common Pitfalls

Assuming it will "connect the same way." It is the same P21, but the connection, the import path and the permissions all change. Plan a reconfiguration, not a reconnect.

No Play database login. Epicor's hosting may not include Play database access unless you ask for it. Without it, your first real EDI test happens in Live.

Writes that used to work. On-premises, EDI software may update small fields in P21 directly, such as a flag recording that an acknowledgment went out. A read-only hosted login refuses those updates. On one hosted move this year, we had to change how such a status is tracked. Find these in testing, not after cutover.

Timeouts across the wire. A lookup that was instant on a local network can time out against a hosted database. On one move, a ship-to lookup had to be rebuilt as two smaller queries. Test with real volume.

Direct partners when the EDI server moves. Partners on a VAN won't notice a change. If you trade directly over AS2 or SFTP and your EDI server gets a new address, those partners may need new connection details and a test round.

Stacking projects. A TPCx migration, a P21 cloud move and a partner onboarding in the same month leave no room to work out which change caused a problem.

How Comparatio Helps

Comparatio runs managed EDI for Prophet 21 distributors: our team builds and maintains the maps and partner connections and watches the system day to day. For a move to Epicor's cloud, that means:

• Your maps and trading partner setups stay. It is the same P21 data. What we reconfigure is how the converter reaches P21: logins, the encrypted connection, the import path and schedules. It's a one-time reconfiguration, quoted before the move.
• Testing in your hosted Play environment before anything touches Live.
• A shadow comparison before switching. When a document type moves to the P21 Transaction API, it runs beside the file import first, and the two are compared document by document.
• Hosting if you want it. Keep the EDI software on a virtual machine you control, or let Comparatio host it on AWS with monitoring.
• Monitoring after the move. Among other checks, Comparatio flags P21 import files that have waited more than 12 hours, so a stopped import doesn't go unnoticed.

Some distributors use Epicor's timeline to look at other ERPs. If that's you, the same approach applies. Comparatio also has connectors for NetSuite and Infor CloudSuite Distribution, and a new ERP path runs beside the current one, compared document by document, before cutover.

For how Comparatio connects to P21 today, see our Prophet 21 EDI integration page. If you have a move date, or you're still deciding, request a call and we'll go through your partners and document types with you.

Frequently Asked Questions