A logistics leader needed to migrate a large EDI estate without freezing the business. Agents generated and validated mappings directly from requirement specifications, with people approving the edge cases. The migration delivered 110 maps in five weeks.
The situation
Migrating an EDI estate is rarely a technology problem. The maps already work; the trading partners already trade. What makes a migration expensive is that every map has to be rebuilt in new tooling, retested against real documents, and cut over without a single partner noticing. Multiply that by a few hundred maps and the critical path is developer capacity, not architecture.
The usual response is to add people and stretch the timeline. Neither helps much. More developers means more coordination, and a longer timeline means a longer period running two platforms in parallel — which is where migration budgets actually go.
What we did
We changed what the human work was. Instead of developers rebuilding maps by hand, analysts maintained the mapping requirement specification as the system of record, and agents generated the translator from it. The generated maps were then validated automatically against the partner’s real sample files, so failures surfaced as business-readable differences rather than stack traces.
People stayed firmly in the loop, but on the decisions that needed judgement: ambiguous specification clauses, partner-specific quirks, and the edge cases where the right behaviour was a business call rather than a technical one. Everything that was mechanical became mechanical.
The outcome
What made the difference
Two things. First, the specification became the input rather than an email attachment — which meant a change to a partner requirement regenerated the map instead of restarting a development cycle. Second, testing happened immediately and automatically, so the feedback loop was minutes rather than the days a manual test round-trip costs.
Both of those ideas are now productised in DEXA, our EDI operating system, and the governance model behind the human approval steps comes from the SENTRA and TRUST360 frameworks.
We publish the metrics and withhold the names — our clients’ competitive advantage isn’t ours to advertise. Talk to us about what a migration would look like on your estate.
