CASE STUDY
Replacing BizTalk in Production —
The Transdev Migration
Replacing BizTalk in Production —
The Transdev Migration
How to replace BizTalk without disrupting operations.
Transdev operates large public transport systems where vehicles, operational platforms and passenger services constantly exchange data.
In Sweden alone, thousands of vehicles depend on integrations running reliably behind the scenes.
Keeping that digital infrastructure stable is just as critical as keeping the buses running.
CLIENT: Transdev Sverige AB (www.transdev.se)
INDUSTRY: Public Transport & Mobility Services
IMPLEMENTED PRODUCTS/SERVICES:
Integration platform modernization (BizTalk transition)
OUTCOME IN SHORT:
- 300+ BizTalk integrations transitioned in production
- 40+ connected systems kept running
- Legacy middleware dependency reduced
- Gradual transition — no disruptive cutover
- A modern integration backbone established
THE BACKGROUND
When the backbone starts showing its age.
For organizations operating large-scale public transport systems, digital infrastructure is as critical as the vehicles themselves.
At Transdev, hundreds of operational systems exchange information continuously — from planning and ticketing to vehicle data and reporting.
For many years, BizTalk handled a large share of these integrations.
It worked well.
Until the environment started showing the usual signs of age.
Changes became slower.
Deployments became heavier.
And the platform itself was approaching the end of its lifecycle.
With 300+ integrations and more than 40 connected systems, replacing the integration backbone was not something you schedule for a quiet weekend.
Large integration environments rarely appreciate surprises.
THE CHALLENGE
When a big-bang migration is just too big a bang.
When integration platforms grow over many years they tend to accumulate…character.
New systems appear.
Old integrations stay because they still serve a purpose.
Dependencies quietly multiply.
Eventually, the architecture becomes something that works — but nobody is particularly eager to touch.
For Transdev, the situation looked roughly like this:
- hundreds of integrations running in production
- operational systems depending on real-time data
- vehicle platforms continuously sending events and status updates
- multiple business systems connected through the same integration backbone
A traditional big-bang migration would have introduced significant operational risk — something a public transport system cannot easily absorb.
Transport systems run every day.
Passengers tend to notice when they don’t.
The real challenge therefore wasn’t just replacing BizTalk.
It was how to evolve the integration architecture without disrupting operations.
Operations tend to prefer continuity..
THE APPROACH
Replace the platform. Keep the operations.
Instead of replacing the platform in one step, Transdev adopted a controlled transition model.
Ghost Nodes was introduced alongside the existing BizTalk environment, allowing both platforms to run in parallel.
New integrations and automation flows were implemented in Ghost Nodes while existing BizTalk integrations continued operating.
This made it possible to move gradually:
- new integrations could be built without touching existing ones
- legacy flows could be redesigned one by one
- traffic could be shifted only after validation in production
Instead of rebuilding hundreds of integrations at once, the architecture evolved step by step.
BizTalk remained operational throughout the transition — until fewer and fewer flows actually depended on it.
In the migration, roughly 70 % of the transition from BizTalk was handled by Transdev’s own IT team — not because they had to, but because they could.
Ghost Nodes made it possible to move integrations step by step, without relying on external consultants for every change.
Eventually the old backbone simply faded out of daily operations.
Which is usually how infrastructure transitions work best.
THE RESULT
From risky migration to controlled transition.
The transition created a more flexible and future-ready integration environment without interrupting ongoing operations.
Key outcomes included:
- gradual replacement of 300+ legacy integrations without a disruptive migration project
- Around 70 % of the migration was handled by Transdev’s own IT team — not as a burden, but as a result of a platform designed to be operated, not outsourced.
- reduced operational complexity across the integration layer
- improved visibility across integration flows
- faster implementation of new integrations and automation
Most importantly, the transition proved something many organizations struggle with:
Replacing BizTalk does not require a disruptive migration project.
Operational systems continued running throughout the transition — meaning passengers, drivers and control centers never noticed the change.
With the right architecture, the platform can be phased out while the business continues running.
In other words: the infrastructure changed — while operations simply continued.
Replacing BizTalk rarely happens overnight.
it doesn’t have to become a high-risk migration project.
Planning a BizTalk migration?
Large integration environments rarely allow a clean cutover.
Ghost Nodes introduces a transition layer that lets you:
- move integrations gradually
- validate flows before switching traffic
- keep core systems running during the transition
- reduce migration risk instead of concentrating it
Not convinced yet?
Have a look at some of our other case studies.
