Customers still using TPCx should begin planning their migration to Epicor EDI. Waiting too long could introduce avoidable risks, especially as support phases out. Based on firsthand experience from the Epicor EDI team, this blog outlines three key lessons for ensuring a smoother, better-informed transition.
With the sunsetting of TPCx underway, many customers are evaluating how and when to make the switch to Epicor EDI.
To help guide that decision, we gathered insights from Jason Miles, Manager, Professional Services at Epicor, who’s worked closely with former TPCx users throughout the migration process.
He shared three important lessons that may help you shape a plan that works for your business.
TPCx will not be supported indefinitely, and a delayed migration could lead to complications, especially as more customers enter the queue. Transitioning late in the timeline raises the likelihood of delays that may affect document automation or trading partner communications.
By starting the process earlier, customers can take the time to plan ahead, test thoroughly, and explore optional features like expanded trading partner connections or managed services.
A proactive migration allows for more control over timing and outcomes, reducing unnecessary pressure on internal teams.
The migration from TPCx is more than a platform switch. It’s also an opportunity to access additional tools and integration options. Customers migrating to Epicor EDI gain access to several key features, such as:
- Document visibility through a web-based portal
- Reporting and alerting tools
- Multiple communication options (e.g., AS2, SFTP, FTP)
- Optional managed services support
- Support for modern data exchange formats beyond X12, including EDIFACT and cXML
Integration is also an important factor. Customers using Epicor ERP platforms like Prophet 21 can leverage SQL access or APIs for tighter, more flexible connections between systems—a capability not found in the legacy TPCx architecture.
Because Epicor has internal access to TPCx maps, ERP data, and system configurations, the migration process is highly informed. This visibility helps reduce ambiguity while limiting the number of decisions customers need to make during the transition.
“Successful migrations are those where it feels almost transparent to the customer,” says Jason Miles. “We handle the heavy lifting behind the scenes, and involve customers only when needed for clarification.”
Following go-live, customers receive two weeks of focused support—known internally as “hypercare”—during which the implementation team continues monitoring the environment. This ensures that any post-migration questions or adjustments are addressed promptly, before transitioning to long-term support or managed services.
The migration process can also be a chance to reassess or expand EDI usage. Some customers choose to onboard new trading partners during the transition, or to activate features that were previously out of scope.
If you’re preparing to migrate, consider what your EDI environment should look like six months or a year from now, and talk with your Epicor team about what’s possible.
The path away from TPCx doesn’t have to be disruptive, and it doesn’t have to be rushed. But it’s important to note that with support timelines moving forward, waiting too long may introduce avoidable friction.
If you're still planning your move, the best first step is an informative conversation.
Start your plan today. Contact your Epicor account representative to begin discussing your migration timeline and options.
