Support for TPCx ends in December, and many organizations are planning their next steps. Based on internal migration activity and lessons learned, the Epicor EDI team has compiled the most common customer questions, along with actionable answers. Whether you're already planning ahead or just starting to evaluate the move, these insights are designed to help.
As the support window for TPCx closes, organizations that delay migration may encounter avoidable challenges. These can include reduced access to migration support resources or potential disruption to automated EDI if transition timelines are compressed. To maintain continuity, we recommend beginning your migration planning well before the final cutoff.
Migrating to Epicor EDI introduces a range of improvements:
- Real-time document visibility via a web-based portal
- Built-in alerts and reporting functionality
- Support for modern transmission protocols (AS2, SFTP, FTP)
- Optional managed services for ongoing support
- Broader format support beyond X12, including EDIFACT and cXML
- Integration via SQL or API with Epicor ERP systems
These capabilities allow organizations to scale and integrate more effectively across systems and trading partners.
For most customers, the transition is more straightforward than expected. Epicor has internal access to TPCx maps, ERP configurations, and trading partner data, which significantly streamlines planning and execution. The result is a well-informed migration process with fewer unknowns.
The majority of migrations proceed without significant issues. For on-premises environments, some customers have fac ed security or access constraints, but these are typically resolved through collaboration between Epicor and the customer’s IT team. Cloud or hybrid environments tend to experience fewer access-related delays.
A successful migration is one that is transparent to end users. Customers receive a clear timeline, coordinated communication, and minimal disruption to their current workflows. Prior to go-live, Epicor provides training and testing. After go-live, a dedicated support period (known internally as "hypercare") ensures a smooth handoff to long-term support or managed services.
Post-migration, Epicor provides two weeks of elevated support. During this time, the same team that handled implementation continues to monitor the environment and resolve any issues proactively. Customers using managed services are transitioned into the managed support model once the system stabilizes.
Most technical preparation is handled by the Epicor team. However, it’s helpful for customers to identify any custom workflows or additional trading partners that may not be part of the initial TPCx configuration. Some organizations use this opportunity to expand EDI usage or add functionality.
Migrating from TPCx to Epicor EDI doesn’t have to be disruptive. With a proactive plan, access to internal configuration data, and post-go-live support, customers can expect a controlled, well-supported transition.
Contact your Epicor account representative to discuss migration timelines and available options.
