DSV begins migrating from CargoWise to DB Schenker’s Tango system

A tech specialist quoted by The Loadstar described the strategy as incremental rather than disruptive. “What Jens [Lund, DSV chief executive] is doing is looking for an exit strategy. It’s not rip-and-replace. It’s a baby-step approach,” the specialist said. “Today, they are maybe 70%–80% CargoWise and the rest Tango, and moving it slowly to avoid disruption.

But it is happening. The technology today, with APIs, means they don’t need everything parallelised. The systems can talk to each other.” The move comes as CargoWise’s revised pricing model has triggered a broader reassessment across the forwarding sector.

CargoWise has served as the default operating system for large and mid-sized freight forwarders for more than a decade, but rising costs have pushed operators of all sizes to explore alternatives. DSV’s decision to lean into Tango — the proprietary TMS it inherited through its acquisition of DB Schenker — turns a post-merger integration challenge into a strategic opportunity to reduce dependence on an external platform. For container shipping lines and terminal operators that exchange booking, tracking, and documentation data with DSV, the migration carries practical implications: system interfaces, electronic data interchange links, and application programming interface (API) connections that currently route through CargoWise may need to accommodate Tango endpoints as the transition progresses.