Changing ERPs? Your EDI moves with you
Your trading-partner connections and maps stay with Comparatio; only the ERP connection changes. Before the switch, we compare the new ERP’s documents with the ones your current ERP sends, then cut over on a planned date with a planned rollback.
- Partners and maps stay
- Documents compared before the switch
- Planned cutover and rollback
What stays, what changes
An ERP move changes one connection, not your trading partners
Comparatio sits between your trading partners and your ERP. When the ERP changes, the partner side stays where it is and we rebuild the ERP side.
| Part of your EDI | When you change ERPs |
|---|---|
| Trading-partner connections | Stay. AS2, SFTP and VAN connections keep running, and partners keep sending to your EDI IDs. Only if the EDI server itself moves do partners connected directly over AS2 or SFTP get new connection details. |
| Maps | Stay with Comparatio. A few that use data only the old ERP had are adjusted, and every partner is tested against the new ERP before the switch. |
| The ERP connection | Changes: from P21 import files to a RESTlet in NetSuite, from SX.e’s web services to Infor’s ION API gateway, or to an SFTP import folder or the P21 Transaction API in Epicor’s cloud. |
| Item, customer and vendor matching | Checked again: partner item numbers and IDs are matched to the new ERP’s records in its sandbox or test tenant. |
| Monitoring and support | Continue: the same engineers watch every document, now on the new ERP connection. |
The moves we run
From the ERP you have to the one you’re moving to
These are the moves distributors ask us about most. Each links to how Comparatio connects the ERP you are moving to.
Prophet 21 to NetSuite
Customer orders become Sales Orders; supplier acknowledgments, ASNs and invoices land on the Purchase Order, as Inbound Shipments and as Vendor Bills. Partners are tested in your NetSuite sandbox while P21 keeps trading.
SX.e to CloudSuite Distribution
The connection moves from SX.e’s web services and exports to Infor’s ION API gateway and SX.API. Every flow is proven in your CSD test tenant before it is switched on in live.
Prophet 21 on your servers to Epicor’s cloud
The same P21 data over a new route: read-only database logins, an SFTP import folder or the P21 Transaction API, and a one-time reconfiguration. Several Comparatio customers already run EDI against Epicor-hosted P21.
Business Central, Acumatica or another ERP
Talk to us. Comparatio has no ready-made connector for Business Central or Acumatica today, so we scope the ERP connection with you before you commit.
Moving to an ERP not listed here? See every ERP Comparatio connects. Your suppliers move with you too: procure-to-pay EDI runs on Prophet 21, NetSuite and CloudSuite Distribution.
Before the switch
The new ERP’s documents, compared side by side with the old
Part of our migration service. Before cutover, the acknowledgments, ship notices and invoices built from your new ERP run beside the ones your current ERP sends, and each pair is compared document by document. Your partners see none of it until the switch.
Built in parallel, never sent
Documents from the new ERP are written to a review folder only. Nothing from the comparison run is sent to a partner or counted as sent.
Compared field by field
Control numbers and timestamps are left out, so the comparison shows only real differences, such as a price, a quantity or a description.
A daily difference report
Our engineers work through it, fix maps and setup, and bring you the business questions, such as a price the new ERP calculates differently.
Inbound tested in the sandbox
Customer orders and supplier documents run through the new ERP’s sandbox or test tenant, so you see each one land on the right record.
We have run these comparisons for NetSuite, Infor and Agility connections since October 2026.
Timeline
How long an ERP move takes for EDI
- 1
Connect the new ERP: days to weeks
We install the connector in the new ERP’s sandbox or test tenant, and your admin grants access from our checklist. How fast depends mostly on how quickly that access is in place.
- 2
Move the program: a few months
Each trading partner is tested against the new ERP while the old one keeps trading, with the side-by-side comparison running. Most of the time goes into partner testing and settling differences.
- 3
Cut over, with a way back
On a date set with your ERP project, partners switch together or in groups. Backups are taken and document counters carried over, and a planned rollback returns EDI to the old ERP if the first day goes wrong.
New trading partners added after the move typically go live in 4–8 weeks, paced by the partner.
Who does what
Managed EDI through an ERP move
Our engineers carry the EDI side of the project. Your team owns the new ERP and its records.
| Task | Comparatio | Your team |
|---|---|---|
| Trading-partner connections | Keeps them running through the move | Nothing, unless the EDI server moves |
| Maps | Keeps them, and adjusts the few that used data only the old ERP had | Forwards partner notices if they reach you first |
| New ERP connection | Installs and configures the connector and runs the setup check | Grants access: a NetSuite role and token, an ION API service account, or Epicor logins |
| Records | Matches partner item numbers and IDs to the new ERP | Loads and keeps item, customer and vendor records current in the new ERP |
| Side-by-side comparison | Runs it, reports differences daily and fixes maps and setup | Decides the business differences, such as how the new ERP prices an order |
| Cutover | Plans the cutover and rollback with you and watches the first hours | Sets the date with your ERP project |
FAQ
Changing ERPs, asked and answered
Will our EDI work if we change ERP systems?
Yes, if your EDI provider moves it with you. With Comparatio, your trading-partner connections and maps stay where they are; only the connection to the ERP changes. A few maps that use data only the old ERP had are adjusted, and every partner is tested against the new ERP before the switch.
How long does it take to move EDI to a new ERP?
Connecting the new ERP takes days to weeks, depending mostly on how quickly access is granted. Moving an existing EDI program takes a few months: every partner is tested against the new ERP, with the new ERP’s documents compared side by side with the old one’s, before a planned cutover with a rollback plan.
Can we keep trading on the old ERP while the new one is tested?
Yes. The old ERP keeps trading until cutover. The new one runs in its sandbox or test tenant, and documents built from it are compared with what the old ERP sends, without anything going to your partners.
What happens if the ERP cutover goes wrong?
The rollback is planned before the date. Backups are taken and document counters carried over, and if the first day goes wrong, EDI goes back to the old ERP while the problem is fixed.
Do our trading partners have to do anything when we change ERPs?
Usually very little. Partners on a VAN keep sending to the same EDI ID, and partners connected directly over AS2 or SFTP only get new connection details if the EDI server itself moves. The side-by-side comparison is there to show that the documents they receive stay the same.
We’re moving from Prophet 21 to NetSuite. What happens to our EDI?
Your trading-partner connections and maps stay with Comparatio. We install the RESTlet in your NetSuite sandbox, test every partner against NetSuite while P21 keeps trading, compare the documents NetSuite builds with the ones P21 sends, and switch on a planned date with a rollback plan.
Read the NetSuite supplier EDI guideWe’re moving from SX.e to CloudSuite Distribution. What changes for EDI?
The ERP connection. On SX.e, EDI orders and supplier invoices import through SX.e’s web services, and outbound documents come from SX.e’s exports. On CSD, documents post through Infor’s ION API gateway and SX.API, and outbound documents are read through CSD’s read-only service interface. Partner connections and maps stay, and every flow is proven in your CSD test tenant first.
Read the SX.e to CSD guideIs moving Prophet 21 to Epicor’s cloud an ERP change for EDI?
Not a new ERP, but a new route to it. Maps and trading-partner setups stay. How EDI reaches P21 changes: read-only database logins, an SFTP import folder or the P21 Transaction API, and a one-time reconfiguration tested in your hosted Play environment.
Read the P21 cloud guideDo you support Microsoft Dynamics 365 Business Central or Acumatica?
Talk to us. Comparatio has no ready-made connector for Business Central or Acumatica today. If you are moving to one of them, we scope the ERP connection with you as a project before you commit.
Should we change EDI providers and ERPs at the same time?
Better one at a time. An EDI provider change, an ERP move and new partner onboarding in the same month leave no room to tell which change caused a problem. Plan them as steps, and we’ll help you put them in order.
When should we involve our EDI provider in an ERP project?
As soon as you have a date. Plan the EDI part with the ERP project, not after it: sandbox access to the new ERP, your partner list and the cutover date all shape the EDI plan.
Does moving EDI to a new ERP cost extra?
An ERP move is a project, so we scope it and agree the cost before it starts, once we have seen your partner list and the new ERP. Maps, connections and monitoring continue as before.
Planning an ERP move? Bring the EDI in early
Tell us your new ERP and your date, and we’ll walk through your trading partners and what changes for each.