Cloud is the right answer for most EDI buyers most of the time. We say that plainly, and we sell cloud EDI. But "most of the time" is not "always," and the businesses in the exception tend to find that nobody will discuss it with them, because a cloud-only vendor has no product to sell if the answer is no.
Effective Data has run both models for 35 years. What follows is the actual decision, without a preferred conclusion.
Four reasons on-premise is still the right call
Regulatory or contractual data residency
Decisive when it appliesSome customer contracts and some regulators specify where data physically sits and who can access it. If that language is in your agreements, cloud is a procurement conversation before it is a technical one.
An ERP that is not going anywhere
Common, and usually underweightedA mainframe, an AS/400 or a heavily customized on-premise ERP with a decade of business logic in it. Moving EDI to the cloud in front of a system that is staying put adds a network hop and a failure mode without removing any work.
An internal team that wants control
Depends on your teamIf you have people who know EDI and want direct access to the maps, logs and queues, cloud platforms can feel like a black box. That is a real cost, not a preference.
Latency or volume at the edge
Rarer than claimedHigh-volume, time-sensitive flows sitting close to a warehouse system. Less common than people assume, worth measuring rather than believing.
What "hybrid" actually means
Hybrid is used as a single word for four quite different architectures. Naming which one you mean is most of the work.
AS2, SFTP and VAN connectivity handled off-site; mapping and ERP integration stay in your data center. The most common shape, and usually the cheapest to run.
New trading partners are onboarded to a cloud environment while established, heavily customized flows stay where they work. Avoids a big-bang migration nobody asked for.
The in-house environment runs the traffic; a cloud instance takes over if it goes down. Buys resilience without changing the day-to-day.
Almost everything moves; the one document set with a data-residency requirement stays behind. Keeps a compliance edge case from dictating the whole architecture.
When we will tell you to go cloud instead
We run on-premise environments, so this list costs us work. It is here because it is true.
The cost comparison nobody publishes
Cloud replaces capital cost with operating cost. That is the whole trade, and whether it favors you depends mostly on document volume, because cloud pricing usually scales with documents and hardware does not.
- On-premise carries: hardware, software licenses, patching and upgrades, monitoring, disaster recovery, and the staff hours to run all of it.
- Cloud carries: a subscription that grows with volume and partner count, plus whatever the overage rate is above your allowance.
- Both carry: mapping, partner onboarding and exception handling. Those costs do not change with hosting, and they are usually the largest line.
That last point is the one most often missed. The hosting decision moves a minority of the total cost of running EDI. If someone is selling cloud primarily on price, ask what happens to the mapping and onboarding work. It has not gone anywhere. Our breakdown of what EDI actually costs covers the charging models in full.
Working with what you already have
A large share of our work is environments we did not sell and did not build: IBM Sterling, Cleo, OpenText, and in-house translators older than some of the people maintaining them. We will manage what you have, document what nobody documented, and tell you honestly if replacing it would cost less than keeping it running. See managed EDI services for how that is scoped, or cloud EDI for the other side of this decision.
Frequently asked
+ Is on-premise EDI obsolete?
No, but it is out of fashion, which is not the same thing. Plenty of manufacturers, healthcare organizations and companies with regulated data still run EDI in their own data centers and have no good reason to move. What has changed is that most vendors no longer offer it, so the option quietly disappears from the shortlist before it has been assessed.
+ What does hybrid EDI actually mean?
Usually one of four shapes: cloud communications with on-premise translation; cloud for new partners and on-premise for legacy flows; on-premise primary with cloud failover; or cloud primary with one regulated flow kept in-house. "Hybrid" on its own is a marketing word. The useful question is which of those four you are describing.
+ Is on-premise EDI cheaper than cloud?
Rarely, once you count honestly. On-premise trades a monthly subscription for hardware, licenses, patching, monitoring and the staff time to do all of it. It can work out cheaper at high volume, because most cloud pricing scales with documents and hardware does not. The break-even is a real calculation, not a slogan, and it depends far more on volume than on partner count.
+ Can we move to cloud later if we start on-premise?
Yes, and it is easier than the reverse. The work is in the maps and the partner relationships, not the hosting. What makes a later migration painful is business logic embedded in a translator in ways nobody documented, which is an argument for documentation discipline rather than an argument for either model.
+ Do you support environments you did not sell us?
Yes, and a large share of our work is exactly that. We manage IBM Sterling, Cleo, OpenText and in-house environments that were built long before we were involved. Being asked to migrate as a precondition of getting help is usually a sign that the provider only supports their own stack.
Tell us what you are running and we will tell you whether to move it
Your ERP, roughly how many documents a month, and any data-residency language in your contracts. That is enough for a straight answer, including 'stay where you are', which is the answer more often than the market suggests.
Or call 847.969.9300Answered by a named EDI specialist on the same business day. If we are not the right answer we will say so on the first call.