Hays

Hays

The zero-disruption playbook: how to deliver a smooth cloud migration

Hays cloud migration | How to achieve zero disruption

When the news arrived, it was not the result of a long planning cycle or a strategic shift that had been months in the making. It was a blunt, non–negotiable reality handed down without warning. The hosting provider supporting a major part of Hays’ environment was exiting the hosting business, which meant the data centres that housed critical systems were due to close within a fixed window. There was no negotiation, no extension and no safety net.

As Simon Gerhardt, IT Operations Director at Hays, a multinational company providing recruitment and human resources services, put it during a conversation about the programme, it was a moment that felt “completely out of the blue” and one that carried very real consequences. The business relied on the systems inside those data centres to operate globally, and any disruption would have been immediately visible to customers, consultants and candidates. The stakes could not have been higher.

Client Profile

  • Customer name Hays
  • Established 1968
  • Customer since January 2024
  • Employees 10,000+
  • Sector Recruitment

For many enterprise technology leaders, this scenario feels uncomfortably familiar. Most organisations do not wake up one day deciding they want to run a large-scale cloud migration. They are pushed into it by a deadline they did not set or by an external pressure they cannot control. The question is never whether the work needs to be done, but how to deliver it without breaking the business in the process. 

What follows is the story of how Hays navigated that challenge, and the lessons that other CIOs and CTOs can take from the experience. 

The honest first reaction

 

 

When Simon was asked how he felt in the moment he learned about the closure, the answer was refreshingly honest. He described his first reaction as “terror”. It was not the technology that sparked that feeling but the reality of the task in front of him. The team now had to move an entire global estate into a new environment, meet an immovable deadline and do so in a way that the business would not feel. 

This is something many leaders recognise. It is not the cloud migration itself that creates anxiety. It is the collision of complexity, time pressure and the expectation of absolute continuity. When nothing in the business is allowed to slow down, the margin for error becomes incredibly thin. What Hays did next is what set this programme apart.

The approach and outcomes

Under heavy time pressure, the natural instinct in most organisations is to start building immediately. Teams spin up environments, draft timelines and begin cutting over early workloads in order to show progress. It creates the appearance of momentum, but it often masks a deeper issue: speed without clarity nearly always leads to delays, rework and risk later on. 

Hays took a different approach. The team deliberately paused and used the early phase of the programme to create a complete and honest understanding of the estate. This meant mapping every connection, every dependency, every hidden service and every system of record. It also meant defining the architectural principles that would guide all subsequent decisions. 

This period laid the foundations for everything that followed. It created a shared understanding of what could be modernised immediately, what needed to move first, what required a more careful sequence and what guardrails could not be compromised under any circumstances. 

As Simon said, they reminded each other regularly that you should “measure twice and cut once”. That mindset provided a sense of control at a time when the situation itself felt anything but controlled.

Beyond the headline: the full story behind Hay’s zero-disruption migration

In this extended interview, Hays goes deeper into the decisions, trade‑offs and delivery approach behind its cloud migration. The discussion explores why Oracle Cloud Infrastructure and Azure were chosen, how key risks were managed, and the lessons learned from delivering change at speed without disrupting the business.

Image text image

Hays met a deadline they did not choose, avoided disruption in a global business and emerged with a modern platform that will support them for years to come. For any CIO or CTO facing similar pressure, their story is a reminder that the path to cloud success is not defined by the technology itself, but by the quality of leadership, engineering culture and decision making that surrounds it.