The group's Treasury platform was hosted at Kyndryl. The hosting wasn't keeping up. Updates needed too much support and took too long. Application skills were thin. Responsibilities between host and client had blurred.

Treasury is a Priority 1 application. It was getting Priority 2 service.

The fix wasn't to negotiate harder with the host. It was to move to one built around the application itself.

Challenge

Treasury isn't an application you can casually relocate.

The platform sits at the centre of group financial operations. It moves real money through SWIFT, runs on scripts the operation has trusted for years, and reports into systems that don't tolerate unplanned outages. When the move from Kyndryl to ION was approved in May 2023, the engineering question wasn't whether the host change would deliver - ION's update model and response times were clear. The question was whether Treasury could keep running while it moved.

Three things were non-negotiable.

SWIFT stayed where it was. The payment infrastructure is too critical to touch during a host migration. Any change to SWIFT during the move multiplies risk for no benefit.

The scripts stayed. Years of operational knowledge live in those scripts. Rewriting them inside a hosting migration would have been two projects pretending to be one.

Configuration stayed. No re-tuning, no re-tweaking. The database moved. The file-structure moved. Everything else stood still.

The constraint, then, was geometric: the application had to function from both environments while the move happened, with full data continuity, without changing anything that wasn't explicitly in scope.

Solution

The instinct on a project like this is to plan for cutover as a single moment - a flag-day weekend where everything moves. For Priority 1 Treasury, that's the riskiest possible design. One bad migration window and you've lost reconciliations, missed reporting deadlines, or worse.

We took the other route: build a bridge between the environments and live on it.

IGT Systems built and operated the cross-environment file-structure sync between Kyndryl and ION. Both environments held the live file-structure through the migration window. Both were kept synchronised. Operations could run from either side without discontinuity.

Through the migration window, the bridge ran at 111 sync executions per minute, every file movement logged end-to-end. Nothing in the pipeline ran on manual triggers. Nothing moved without an audit record.

The migration of the database and file-structure itself was performed by ION with MM Group support. The bridge that kept everything running while that happened was the piece IGT owned end-to-end.

Delivery Approach

The risk profile of this project was unusual: low technical complexity per individual component, but extremely high blast radius if anything went wrong.

That shape changes how you deliver.

The sync wasn't a one-shot tool. It was an operational system that had to stay reliable for the entire duration of the migration. So it was built and run as an operating asset, not a project artefact - monitored, supported, and tuned the same way the production systems on either side were.

What stayed strictly out of scope stayed out of scope. No opportunistic refactoring of the scripts. No "while we're in there" SWIFT improvements. No configuration drift. The discipline of doing only what was scoped and protecting the rest was as much of the project as the engineering itself.

Approved May 2023. Closed November 2023. Treasury never paused.

Results

Treasury moved hosts. The application now runs at ION, with the update model and response times that drove the move in the first place. Kyndryl is out of the picture for Treasury.

SWIFT continues to operate where it always did. Payment infrastructure was preserved unchanged through the entire migration window.

The scripts the operation trusted before the move still run. No rewrite, no parallel logic, no behavioural drift.

The sync did its job invisibly. 111 executions per minute across the migration window, every transfer logged, no manual intervention required.

The migration closed in November 2023, six months after approval. No part of the operation paused. No scope crept outward. No collateral systems were disturbed.

The thing the business case was nervous about - downtime during the move didn't happen.