Businesses migrating from a single, public cloud provider has been the direction of travel of UK digital infrastructure for years.
As far back as 2020, Barclays found that 43% of enterprise CIOs were already planning to bring workloads back from the public cloud to on-premises or private cloud infrastructure1. Since then, IDC, Gartner and a host of vendor surveys have tracked an increase in this intention.
Most recently, research from Vanson Bourne demonstrated that 87% plan to move away partially or fully from the public cloud over the next two years whilst Gartner predicts that organisations are set to migrate 20% of existing workloads from global public clouds to local or regional alternatives by the end of 20262.
The questions now facing the industry are where are these workloads headed, and how are they going to get there?
Whose workload is it anyway? Choosing from hybrid architecture options
Every report reaches the same conclusion: businesses will move to a hybrid architecture, blending public and private cloud, colocation and on-premise infrastructure.
The Vanson Bourne research found that - among those repatriating:
- 54% are considering a hybrid infrastructure led by private cloud
- 38% said they are exploring an increased reliance on their own data centres
- 36% are assessing a blend led by colocation.3
- Cost
- Performance
- Compliance
- The ‘future’ demands of AI
With such a range of blends available, strategies around hybrid workload placement have become critical. Putting the right workload in the right place, in the right way, is now a source of competitive advantage.
1 As reported at Survey says: 83% of CIOs are embracing private cloud. 2 See Gartner Survey Reveals Geopolitics Will Drive 61% of CIOs and IT Leaders in Western Europe toIncrease Reliance on Local Cloud Providers. 3 This research was commissioned by Pulsant and carried out by Vanson Bourne in May 2025, inaccordance with Marketing Research Society (MRS) guidelines. 250 respondents across UK business ofvarious sizes and sectors were interviewed and a full breakdown of the raw data is available on request.58% of respondents represent businesses of less than 1,000 employees.
Defining hybrid cloud workloads
We first need to define what is ‘right’ when it comes to a given workload. While this changes from business to business, there are four main drivers:
- Cost
- Performance
- Compliance
- The ‘future’ demands of AI
When it comes to cost, the most significant driver is the predictability of the compute demand. Accommodating spikes in demand was – and remains – a key selling point for the public cloud as businesses pay for what they consume.
However, businesses have come to realise that ‘always on,’ steady-state workloads are often cheaper on owned or colocated hardware.
Recent repatriation has been driven by enterprises moving such stable workloads to avoid the "cloud tax" of constant uptime. These savings are often then set against the egress fees charged by public cloud providers to move data out of their ecosystem.
Regarding performance, hybrids built around on-premise, colocation or even regionally-based private cloud offer shorter distances for data transit, and thus the low latency that is critical to so many businesses.
Edge computing is built upon processing data closer to where it is collected. This improves throughput and decreases the loads on centralised servers. The speed of response is at the heart of how performance interacts with cost.
‘Lag tax’ is the hidden cost a business pays when data travels further than it should. Most businesses are paying it without knowing – it is typically seen in speeds slower than ten milliseconds. It shows up as delayed decisions, inconsistent performance, inflated bandwidth costs, and compliance exposure.
Compliance has become a dominant factor shaping this spending behind hybrid cloud choices. Vanson Bourne research has found that 79% of businesses cite sovereignty and residency considerations as a major influence upon their digital infrastructure investment.
There is a general increase in the workloads that demand a secure, sovereign private cloud, or even the security that can only be guaranteed by colocation or on-premise infrastructure. In the face of GDPR fines, and increased cyber threats, businesses demand the option of local control of their data.
Lastly, there is the context of the demands of AI. AI has already forced businesses to reassess putting the right workload in the right place. Edge-based private clouds or colocation options suit inference AI (to be near the end-user) but large-scale training for generative AI demands public hyperscale. For AI workloads, the "cost of distance" is high, so any model that prevents the expenses of data replication and transit – such as edge – is welcome.
It is important to remember that businesses adopt hybrid architectures because they perceive a clear set of benefits: flexibility across environments that mitigates operational risk; compliance and data sovereignty; optimised performance; and the modernisation of legacy systems that are both expensive and a single point of failure.
Thus, once the question of where to migrate to has been addressed, the business needs to assess how it will get there.
How to move: hybrid migration strategies
The first step in a placement strategy that decides where workloads should run is a full assessment of existing applications and usage.
Typically, the most common approach for businesses looking to move to a hybrid infrastructure is to identify workloads that have a predictable, consistent resource consumption and migrate them from public cloud to private cloud or colocation.
This reduces ongoing costs and – when using a sovereign provider – keeps the data in-country.
This brings us to the realm of re-platforming. This involves containerising the workload and moving to a regional edge facility closer to the actual users. This allows the app to "burst" to the public cloud for massive scale, but run daily operations on the edge for lower latency.
Migrating workloads out of restrictive public cloud means that databases can exploit high-performance, sovereign private cloud while maintaining the application's core code. Businesses gain much greater cost predictability and control, while keeping the automation benefits of the cloud.
The benefits of modernisation can be realised without excessive development costs. By moving to sovereign, regional infrastructure, the organisation can ensure compliance with necessary legislation, whilst phased migrations reduce operational risk.
Hybrid migration in practice
Once a business has begun a hybrid cloud migration, it faces the immediate concern of managing workloads across multiple environments. Interoperability – in particular making sure systems work together to enable growth and scale – is vital.
The first step in ensuring interoperability is visibility. Single portals are critical tools to enable businesses to manage workloads across private cloud, on-premise hardware, and public hyperscale. Visibility prevents operational "lock-in" because if a workload needs to scale, everything remains consistent.
Next, systems must "work together" at scale. Pulsant has invested extensively in its robust, 400Gbps private network, integrated with Megaport and LINX, to turn an estate of 14 data centres into cloud on-ramps, which deliver consistent scale from anywhere in the UK.
The last step is to foster an ecosystem of service partners who build interoperable solutions on this infrastructure. The goal is that any new business can "plug in and play" new services from the partner community without a full architectural redesign.
A hybrid cloud migration represents a huge opportunity to realign a business and its infrastructure. It should offer the opportunity to cut cost, reduce exposure to risk, improve resilience, and enable a business to focus on scale.
