Gentran migration
Move off Gentran without disrupting your trading partners
Many companies still run EDI on Gentran:Server or Gentran for IBM i and z/OS, often on aging hardware with shrinking expertise. ECOM plans and carries out Gentran migrations to IBM Sterling B2B Integrator or ECOM PRISM, converting maps, partners and communications and cutting over partner by partner.
At a glance
- Migration assessment
- Target platform recommendation
- Map conversion and redesign
- Trading partner configuration
- Communications
- ERP and back-end interfaces
The challenge
Gentran still works, until it doesn't
Gentran systems are often decades old and deeply embedded. Maps contain business rules nobody remembers writing, partner setups vary in small but important ways, and interfaces to the ERP use file layouts that only the original developers understood. The people who know the system are retiring, the operating systems and hardware underneath are aging, and every year of delay makes the eventual migration larger and riskier.
- Few people left who understand the Gentran maps and setup
- Aging servers or operating systems underneath the translator
- Many partners, each with slightly different requirements
- Fear of disrupting orders, shipments and invoices during cutover
Scope
What ECOM's Sterling specialists do
-
Migration assessment
Inventory partners, document types, maps, code tables, communications, schedules and ERP interfaces, and identify what is still in use.
-
Target platform recommendation
Recommend IBM Sterling B2B Integrator, ECOM PRISM or another fit, based on your volumes, skills, hosting preferences and roadmap.
-
Map conversion and redesign
Convert or rebuild maps, preserving business rules, and simplify where duplicated or obsolete logic can be retired.
-
Trading partner configuration
Recreate partner profiles, envelopes, identifiers and acknowledgment settings on the new platform.
-
Communications
Move connections such as AS2, SFTP, FTP, Connect:Direct and VAN mailboxes, including certificates and partner coordination.
-
ERP and back-end interfaces
Reconnect the inbound and outbound interfaces to your ERP and other systems, keeping file layouts or modernizing them.
-
Testing and parallel runs
Compare outputs between Gentran and the new platform, test with partners and run in parallel where needed.
-
Cutover planning
Plan cutover in waves by partner or document type, with fallback options and clear communication to partners.
Approach
How an engagement runs
- 01
Discover
Collect the Gentran inventory and identify active partners, maps and interfaces, and those that can be retired.
- 02
Design
Choose the target platform and design partner, map and interface migration, including naming, standards and monitoring.
- 03
Convert and build
Convert or rebuild maps, configure partners and communications, and connect ERP interfaces in a test environment.
- 04
Test
Run side-by-side comparisons, partner tests and end-to-end business tests before each cutover wave.
- 05
Cut over in waves
Move partners in planned groups, monitor closely, then decommission Gentran once all traffic has moved.
Technical considerations
What a Gentran migration has to account for
These dependencies often decide the timeline. ECOM identifies them during the assessment.
-
Map logic and code tables
Gentran maps often embed lookups, code conversions and business rules. These must be understood before conversion, not discovered during testing.
-
ERP file layouts
Keeping the existing application file layouts minimizes ERP changes; modernizing them may simplify the future but adds scope.
-
Partner identifiers and envelopes
Interchange IDs, qualifiers, control numbers and acknowledgment settings must carry over exactly to avoid partner rejections.
-
Communications and certificates
Network connections, VAN mailboxes, AS2 certificates and firewall rules must be in place before each partner moves.
-
Platform differences
Gentran for IBM i or z/OS behaves differently from a server-based platform, so scheduling, file handling and operations change too.
-
Retirement and archives
Decide how long Gentran stays available for reference, and how historical transaction data and audit records are retained.
Why it matters
What you gain
Off an aging platform
Move EDI onto a platform with current support, skills and infrastructure.
Partners keep trading
Wave-based cutover with partner testing keeps orders, shipments and invoices flowing during the move.
Cleaner EDI estate
Retire unused partners, maps and interfaces instead of carrying them forward.
Fit
When teams call us
Hardware or OS end of life
The server or operating system under Gentran must be replaced, forcing a decision about the translator too.
Retiring EDI specialist
The person who maintained Gentran for years is leaving, and the knowledge needs to move with the system.
ERP replacement
A new ERP project is the right moment to move EDI to a modern platform and redesign interfaces once.
Product background
What IBM has published about Gentran
The facts below summarize IBM's published information. Your own Gentran version and support terms should be confirmed with IBM.
IBM sources, checked October 20, 2026:
- End of Support Announcement for versions of IBM Sterling Gentran products (IBM Support) (opens in a new tab)
- IBM Sterling B2B Integrator 6.2.1 documentation (opens in a new tab)
IBM publishes lifecycle and compatibility information that changes over time. Always confirm current details with IBM for your versions and entitlements. IBM and related product names are trademarks of IBM.
- IBM ended support for several older Gentran versions on April 30, 2015, including Gentran:Server for Windows 5.1, Gentran:Server for UNIX 6.0.2, Gentran:Server for iSeries 3.4 and Gentran for zSeries 6.4
- In that announcement, IBM advised customers on those versions to move to a current Gentran release to keep support
- The same announcement positioned IBM Sterling B2B Integrator as IBM's strategic on-premises B2B gateway
- IBM's B2B Integrator 6.2.1 documentation includes guidance on creating and migrating translation maps
Why ECOM
Sterling expertise, plus everything around it
Most Sterling problems are not only platform problems. They involve maps, partners, infrastructure and people. ECOM brings these together:
-
IBM Sterling technical expertise
Specialists who install, upgrade, administer and develop on B2B Integrator, File Gateway and Connect:Direct.
-
EDI mapping and partner integration
Maps, business processes and trading partner onboarding, not only platform administration.
-
Managed infrastructure and operations
Hosting, monitoring and day-to-day operations when you want ECOM to run the environment.
-
PRISM integration and visibility
Add ECOM PRISM for visibility, partner connectivity or a future platform path alongside Sterling.
-
EDI Team as a Service
Sterling and EDI specialists who extend your team on an ongoing basis.
-
Automotive integration
Deep automotive integration experience: schedules, ship notices and plant routing on Sterling or PRISM.
Ways to work with ECOM
A defined project
An upgrade, migration, implementation or fix with an agreed scope, plan and hand-over to your team.
Ongoing administration
ECOM specialists share administration and development work with your team through EDI Team as a Service.
Managed service
ECOM operates the environment within an agreed scope and service levels defined in the service agreement.
Each engagement is scoped individually. Not every engagement includes every service listed on this site.
Frequently asked questions
Should we migrate Gentran to IBM Sterling B2B Integrator or to something else?
It depends on your volumes, partners, skills, hosting preferences and plans. Sterling B2B Integrator suits many enterprises; ECOM PRISM or a managed service suits others. ECOM recommends a target after the assessment.
Can Gentran maps be converted automatically?
Some map logic can be carried over, but every map needs review and testing. ECOM decides per map whether to convert, rebuild or retire it, rather than assuming automatic conversion.
Do our trading partners have to retest?
Partners whose connections, identifiers or certificates change usually need testing. Where nothing visible to the partner changes, ECOM plans lighter verification. Each partner's needs are planned in advance.
How long does a Gentran migration take?
It depends on the number of partners, maps and interfaces and on how much is still in use. The assessment produces a timeline based on your actual inventory.
Can we keep our ERP interface files the same?
Often yes. Keeping existing file layouts limits ERP changes. Some teams use the migration to modernize interfaces, which adds scope but can simplify the future.
Plan a Gentran migration
Tell us which Gentran product you run, how many partners you have and your timeline. We will discuss a practical migration approach.