Plenty of enterprise brands run a capable, established OMS like Manhattan or Sterling. These systems were built to do serious work and they still run real operations every day. The problem is rarely that they do nothing well. It is that they are rigid, slow to change, expensive to maintain, and unable to keep up with the channels, real-time demands, and agentic patterns the business now needs. Replacing them outright is the project nobody wants. Running a modern layer alongside them is the move that works.
The Architecture
In this pattern, the legacy OMS stays in place and Pipe17 goes in as the orchestration layer on top of it. Pipe17 connects to the commerce platforms, marketplaces, 3PLs, and carriers on one side and to the legacy OMS and ERP on the other, using managed connectors rather than custom bridges. New order flow, new channels, and the capabilities the legacy system handles poorly route through Pipe17. Everything that already works and has not yet moved continues to run on the legacy OMS. The two operate together, with Pipe17 orchestrating and the legacy system handling its remaining responsibilities, until the balance has tipped far enough that the legacy OMS can be retired.
What Moves First
The capabilities that tend to move to Pipe17 early are the ones a legacy OMS struggles with most. Real-time, event-based inventory replaces the batch syncs that cause overselling. Delivery promising gets calculated against the live fulfillment network rather than a static table. New sales channels and marketplaces connect through Pipe17’s managed connectors instead of waiting on a legacy change request that takes a quarter. Business users get to change routing rules and workflows through a screen rather than filing a ticket for a systems integrator. Each of these is net-positive on day one and does not disturb what the legacy system is still doing.
Why Not Just Replace the Legacy OMS Outright
Because the outright replacement concentrates all the risk and cost into one event, and because most brands cannot pause operations or break a multi-year contract to do it. Running Pipe17 alongside the legacy system removes the bet-the-company moment. Value arrives in the first phase, the legacy system keeps the business running while the modern layer proves itself, and the migration becomes a gradual handoff. Every integration Pipe17 builds in the first phase carries forward, so none of the early work is thrown away when the legacy system finally retires.
Frequently Asked Questions
No. Pipe17 goes in alongside the legacy OMS and takes on specific capabilities first, while the legacy system keeps running what has not moved. Over time more shifts to Pipe17, until retiring the legacy system becomes a low-risk final step rather than a big-bang cutover.
Through managed connectors maintained by Pipe17 rather than custom integrations your team builds and maintains. A canonical data model normalizes orders, inventory, and fulfillment across systems, so each new capability plugs into a consistent foundation.
The ones the legacy system handles worst: real-time inventory, delivery promising, new channel and marketplace connections, and business-user control over routing rules. These deliver value quickly without disturbing existing operations.
Yes. Pipe17 runs alongside the system you are committed to and delivers value while the contract runs its course, so you start modernizing now instead of waiting for it to expire.
No. Because connectivity is managed and the data model is shared, the integrations built in the first phase keep working through full migration. The work compounds across phases rather than being rebuilt.
