← Back to blog
Logistics

ERP migration: should you wait before launching a TMS?

Not necessarily. A first scope can start with file imports of orders or deliveries, before interfaces are automated. The main constraint is often the availability of business and IT teams: decide which use cases go live first and which interfaces can wait.

This article sets out our recommendations for transport, supply chain and IT leaders who have to fit both projects into the same calendar.

Why does an ERP migration push back a TMS project?

Two concerns, often tangled together. The first is technical: if the TMS is connected to the old ERP, the integration will need rebuilding after cutover. The second is about people: the migration absorbs business teams and IT, leaving no capacity for a second project.

Separate the two before deciding. The technical concern depends on the first scope you choose and how data is exchanged. The capacity concern depends on your actual schedule, and no software makes it go away.

Can a TMS start without an ERP interface?

Yes, if the first scope allows it. File imports can carry the order lines and deliveries needed to create transport orders. An API or EDI (electronic data interchange) interface, one-way or two-way, does not have to come first.

On its integrations page, OneChain states that a structured file may suit an initial flow before an API is considered. Fields, format, frequency and checks still have to be defined in the project. Whichever vendor you talk to, ask them to walk through this kind of start using a sample of your own file.

There is a trade-off: someone has to produce the file and handle what gets rejected. Decide who extracts it from the ERP, who reviews incomplete lines and who decides whether to fix or exclude them. If supplier orders are central to the first use case, the purchase order tracking page shows what that scope covers.

How do you reduce dependence on a specific ERP version?

If your architecture includes an intermediary system between the ERP and third-party tools, often called middleware, consider connecting the TMS to it rather than directly to the ERP. A version change or a new ERP then affects that layer first.

This reduces the dependency; it does not remove it. Formats, references or field mappings can change with the new ERP, and some adaptation may still be needed. The integrations page states that an intermediary system can handle field mappings and that the channel is chosen around the flow.

Two questions to put to IT before you decide. Will the current middleware stay in place after the migration? When will the new ERP’s order and delivery formats be frozen?

Which data stays in the ERP?

The ERP usually remains the reference for master data. The TMS uses the information transport needs. Some elements, such as transport plans, can stay in the ERP for a while before moving into the TMS.

This split lets you start on a narrow scope without moving the reference. It also means deciding which source is authoritative for each field: the FAQ on the integrations page addresses this master data question. The TMS will also expose data issues, which are fixed in the ERP; the guide ERP data quality: what to fix to start a TMS explains how to organize those fixes.

How do you protect teams during the migration?

Plan around their real availability, not the theoretical schedule. An ERP migration often draws on the same people as a TMS project, on both the business and IT sides.

We recommend not tying the whole TMS schedule to the ERP schedule, while still taking team workload seriously. In practice:

  • pick a first use case that needs little IT effort, such as an order import for one site;
  • defer interfaces that depend on formats still in flux in the new ERP;
  • book time in key users’ calendars rather than relying on their spare hours;
  • set a joint decision point for both projects, timed for when the new ERP’s formats are frozen.

What schedule should you plan?

Sequence by use case, not by interface. Take a fictional example: a company is replacing its ERP. It launches the TMS on shipments from one site, fed by an order file, then automates the exchange once the new ERP and its middleware are stable.

StepPrerequisitesWhat can wait
First scope on file importsOrder or delivery file in the agreed format, an owner for extraction and checksAPI or EDI with the ERP
Transport use cases on that scopeKey users available, reliable data for that use caseOther sites, other transport modes
Automated interfaceNew ERP formats frozen, middleware identified, IT time bookedData returned to the ERP that launch does not require
Later phasesFirst scope stable, next needs prioritizedNon-priority improvements

The table gives no standard duration: each step depends on your migration and your teams. The deployment and support page describes a method built on the same logic: launch essentials are separated from improvements planned later, and flows can use files, an API or EDI/SFTP depending on the system and scope.

This is one of several decisions to make before a TMS project; they are brought together in TMS project: eight questions to settle before you start. For how a TMS sits alongside the ERP and the WMS (warehouse management system), see the general TMS guide.

To review your own schedule, tell us about your migration and your first transport flow. Describe your systems and the scope you have in mind; keep files and confidential documents out of the form.