Strategic Infrastructure Liquidity: The Data Centre Exit Opportunity

For many enterprises, a data centre exit is treated as the final stage of a transformation programme.

Workloads migrate. Hardware is decommissioned. Contracts close. The facility is exited.

But viewed through the lens of Strategic Infrastructure Liquidity, a data centre exit is not simply the end of an infrastructure lifecycle. It is a capital event.

It is the nexus where infrastructure value, migration timing, support obligations, colocation commitments, compliance requirements, and transformation funding all converge. Managed well, a data centre exit can help preserve value, reduce avoidable spend, and strengthen the business case for transformation. Managed too late, it can create cost, delayed projects, and dependency at the very moment the organisation is trying to move forward.

A data centre exit is not just about migrating to the cloud and clearing the data centre. It is about what value, risk, and capital decisions are carried into the next phase of transformation.

The Final Step in the Infrastructure Liquidity Journey

In the first article of RTK’s Strategic Infrastructure Liquidity series, we explored why enterprise infrastructure should be managed beyond depreciation. Hardware may sit on the balance sheet, but too often it is managed passively through accounting schedules, vendor refresh cycles, and operational necessity.

In the second article, we examined how existing infrastructure can shape transformation funding. The estate an organisation already owns can influence timing, sequencing, risk, and the strength of the business case before new budget is committed.

This final article looks at one of the most important moments in that lifecycle: the data centre exit, where infrastructure liquidity becomes a live, very real, executive issue.

Decisions made before the DC exit determine whether organisations preserve value, maintain control, and accelerate transformation, or absorb unnecessary cost at the point of transition, diverting critical resources from innovative, future-state IT.

Why Data Centre Exit Timing Matters

Data centre exits rarely fail because leaders do not want to leave or do not have a plan for cloud. They fail commercially because the decisions that shape the exit are made too late.

A hardware or software support contract gets renewed before the migration window is settled. An infrastructure refresh is approved to maintain operational resilience or compliance. A colocation agreement rolls over because workloads are not yet ready to move. Each decision may appear sensible in isolation. Together, they recommit capital to environments the organisation is actively trying to exit.

This creates a familiar problem. The transformation plan moves forward on paper, but execution is pulled backwards by the estate being left behind.

Timing matters because data centre exits sit at the intersection of multiple decision points:

• Contract timing
  Colocation, facilities, support, and maintenance agreements may renew or extend before migration plans are fully executable.
  
  
• Refresh timing
  End-of-service-life milestones or support constraints can trigger capital expenditure into infrastructure marked for exit.
  
  
• Migration timing
  Workloads may still require continuity, temporary capacity, or bridging support while the target environment is prepared.
  
  
• Value timing
  Hardware may still retain residual market value, but that value can narrow if assessed only after disposal decisions have already been made.
  
  
• Risk timing
  Data-bearing assets, chain of custody, secure erasure, audit evidence, and compliance obligations all need to be planned before the final exit window.
  
  
• Book value timing
  Owned infrastructure has not fully depreciated, leaving finance teams facing write-down exposure, slowing approval or delaying the transformation timeline.

The issue isn’t whether the organisation can exit the data centre, it’s whether the exit can be sequenced in a way that protects transformation economics.

Data Centre Exit Is Not a Decommissioning Problem

One of the biggest mistakes enterprises make is treating a data centre exit as a late-stage decommissioning task.

By the time a site is being cleared, many of the most important commercial decisions may already have been made. Support may have been extended. Hardware may have been refreshed. Contracts may have rolled over. Migration timelines may have shifted. Residual value may have declined.

At that point, the organisation is no longer shaping the exit. It is managing the consequences of earlier decisions.

A better approach is to treat data centre exit as a strategic inflection point. That means asking earlier:

• What infrastructure is still business-critical?
• What can be bridged rather than refreshed?
• Which contracts, renewals, or colocation commitments create timing pressure?
• Where could OEM support extensions lock the organisation into infrastructure marked for exit?
• Which assets still hold recoverable value?
• Could owned infrastructure create write-down exposure if exited before it is fully depreciated?
• What decommissioning, audit, security, and ESG evidence will be required?
• Which decisions could create avoidable cost if made before the migration plan is settled?

This is the difference between exiting reactively and exiting strategically.

The goal is not to rush the migration. It is to create enough visibility and runway to make the right decisions before the exit window closes.

Guest Perspective: Why Data Centre Exits Are Won or Lost Before Decommissioning

To add an independent perspective, we spoke with Alex Watson-Jackson, an independent data centre consultant with more than 25 years’ experience building, acquiring, and leading migration programmes for some of the world’s largest enterprises.

Alex previously held senior infrastructure and business development roles at Amazon Web Services (AWS), including EMEA Lead, Infrastructure Strategic Collaboration, and Principal Business Development Manager, DC Divest, where he supported large-scale migrations from on-premises environments to the cloud.

We asked Alex about where data centre exit programmes typically lose value, and what enterprise leaders should consider before committing to an exit path.

Q1. From your experience, where do data centre exit programmes typically lose value?

“When you have made a decision to exit a data centre, whether that is to restructure the DC portfolio, reduce the DC owned estate or stop owning your own DC’s completely, you need stop ‘Business as Usual’ processes and build a DC exit strategy based on evidence.

I have seen the consequences when companies don’t do this.  Recently a multi-national European bank’s team managing a cloud migration found that an IT team purchased several hundred replacement servers to support an application which the cloud migration team were planning to move in 12 months’ time, creating multi-million Euro book value problem.  Early identification of that team’s refresh plan would have caught this before it became a problem.  In another case an educational media company lost an expected cost saving in their cloud migration business case when a colocation contract rolled over to a further 2-year term. 

Involving the real estate manager at the start of the project would have surfaced this issue in time could have allowed the business to negotiate an alternative end of contract deal with the colocation company. There are hundreds of cases that I have seen, but the underlying issue is not knowing the real situation of your IT estate, not stopping BAU processes such as local hardware refresh and not planning early enough to avoid issues.”

Q2. What decisions do organisations usually make too late?

“Late decisions usually result in increased delays and costs to transformation projects.  One financial services cloud migration team was made aware of the contract end date for leased Power-Series servers supporting key banking applications just 6 months before the deadline. This caused an immediate problem for the project as 6 months was not enough time to move the application. 

This type of problem is seen with contracted services of all kinds from real estate/colo leases, through to hardware support contracts.  Project executives need to be made aware of key issues early, so they have enough time to solve it internally or find external solutions from consultants or suppliers.”

Q3. How should CIOs and CFOs think differently about the exit window?

“The CIO and CFO must recognise that IT transformations that change where applications are run and by whom are critical business change programmes. They can transform productivity, but they also challenge or disrupt existing investments, systems, tools, policies and processes. 

As senior executives the CIO and CFO have to lead these change processes. They cannot do that without a clear qualitative and quantitative understanding of the current situation. Once they have that clear picture, they need to ensure it does not get changed without their explicit agreement. There are two key actions to take:

1. Trigger a full audit review of the affected IT and DC estate.   Without accurate data the executives leading the project cannot make the required decisions.  Few if any organisations have a comprehensive and validated list of their IT assets and associated contracts.  An urgent first step is a full audit of assets and review of contracts for terms and critical dates.  Alongside this is a similar audit of the DC real estate assets you are exiting and the associated contracts.  If you own the real estate you should also get a professional opinion about the highest value next use for the site and likely sale price to that market.
   
2. Stop BAU actions like hardware procurements or service contract renewals.  Any change to the estate should be a formal project change under the control of the migration/transformation project team.  This will prevent decisions being made by other parts of your organisation who don’t understand the consequences to the IT transformation strategy.”

Q4. Can you share an example of where early infrastructure planning helped improve a data centre exit or migration outcome?

“A large multi-national financial services company in Australia planned to exit two data centres, for an AWS cloud solution that would create a approximate 30% cost saving from the current circa A$20M annual cost. As part of their project initiation the CIO recognised that multiple phases of IT change as well as growth through M&A had left him with a fragmented knowledge of the hardware estate. 

He contracted RTK to perform a Deep Dive Assessment across the estate.  The assessment uncovered A$7.4M in hardware refresh costs that the business would have faced during the migration if it continued Business-As-Usual operations.  Had this not been spotted that cost would have been more than the planned savings from the first year of cloud operations – a significant blow to the CIO’s business case. The results led the company to extend Deep Dive Assessments to its Southeast Asia data centres, resulting in further savings for the cloud transformation programme.”

Q5. What advice would you give leaders before they commit to a final data centre exit date?

“The issue at the heart of most cloud/hybrid-cloud/DC exit IT transformation projects is the failure to recognise that this is not just another IT project with the CIO reporting progress periodically to executives and the board. This is a strategic change for the business and requires active engagement from multiple executives from the outset and probably the most important executive who I see absent in these projects is the CFO. To address this, I recommend two key actions:

First, you should address one of the most common reasons for projects failing; not all stakeholders had the same understanding about the objectives of the project. One of the best ways to address this is to hold a workshop with all stakeholders and executive leaders: CFO, head of legal, head of real estate, head of HR and so on. This is a strategic alignment workshop run to discover what stakeholders expect from this IT transformation project, driving debate that surfaces issues, discovers misalignments and concludes with all stakeholders clear on goals and responsibilities. By forcing transparent discovery and debate it identifies the key decisions that need to be made across the organisation and prevents conflicts driven by different strategic visions.

The second key action is to form a governance board from the key stakeholders. That will maintain alignment around the strategic vision formed in the first workshop and support the CIO in validating the plan and its associated key deliverables through to final exit date.”

Three Questions Leaders Should Ask Before an On-Prem Exit

For CIOs, CFOs, infrastructure leaders, and transformation teams, the starting point is not a decommissioning checklist. It is a clearer view of the estate, the timeline, and the decisions that could influence transformation outcomes.

1. Do we have enough runway to make infrastructure decisions strategically?

A data centre exit needs time and shouldn’t be conducted under duress.

Not just time to migrate workloads, but time to assess infrastructure value, contract exposure, support requirements, capacity gaps, and operational dependencies. If the organisation only evaluates these issues near the end of the programme, many options may already have narrowed.

Runway creates choice. It gives leaders the ability to bridge infrastructure where needed, avoid unnecessary refreshes, plan secure exit routes, and preserve value before market or contractual conditions change.

2. Is the exit timeline commercially and operationally realistic?

A rushed exit can create as much risk as a delayed one.

If workloads are moved before the business is ready, operational resilience can be affected. If migration runs late, the organisation may extend support, renew contracts, or maintain parallel environments for longer than planned.

The strongest exit plans balance ambition with commercial reality.

They recognise that some systems may need to remain operational for a period of time, but they avoid turning temporary continuity needs into long-term infrastructure commitments.

3. Do we know where the estate stands today?

Leaders need a current view of the infrastructure estate before making exit decisions.

That includes understanding which assets are still critical, which are underutilised, which are approaching support or lifecycle pressure, which carry residual value, and which contracts could affect exit timing.

Without that view, the estate remains a source of uncertainty. With it, infrastructure becomes part of the transformation plan.

The RTK Perspective: Aligning Infrastructure, Finance, and Transformation

RTK works with enterprises at the intersection of infrastructure, finance, and transformation.

In the context of data centre exit, that means helping leaders understand what they own, what value remains, where contractual or lifecycle decisions may create avoidable cost, and how the estate can be managed to support the wider transformation plan.

This is not a late-stage hardware disposal conversation. It is a strategic infrastructure advisory conversation.

A data centre exit may require secure decommissioning, chain of custody, certified erasure, remarketing, and ESG evidence. But the value of those activities is greatest when they are connected to the broader transformation strategy early enough to influence decisions.

The principle is simple: Do not refresh what you are trying to exit.

Assess it. Bridge it where necessary. Exit cleanly. Recover value where possible.

When approached this way, the data centre exit becomes more than a technical endpoint. It becomes a controlled transition from legacy infrastructure into the next operating model.

Infrastructure Liquidity as a Leadership Discipline

Strategic Infrastructure Liquidity is ultimately a leadership discipline. It asks organisations to view infrastructure not only as technology to operate, but as capital to manage, value to preserve, and timing to align with transformation.

Across our series, we have explored three connected ideas:

• Infrastructure should be managed beyond depreciation.
• Existing estates can shape transformation funding and business-case readiness.
• Data centre exits are financial transition points, not just technical decommissioning projects.

For IT leadership, the message is clear. Infrastructure decisions made early can preserve value, reduce avoidable spend, and create greater confidence in the transformation journey.

Data centre exit is not the end of the infrastructure story, instead it’s the point where infrastructure decisions become transformation outcomes.

For leaders looking for a deeper end-to-end view of how legacy infrastructure economics affect cloud migration, our Executive Playbook explores the financial and operational barriers that can slow transformation, from trapped capital and refresh pressure to migration continuity and exit complexity.

For organisations preparing for a data centre exit, cloud migration, or major infrastructure transition, the next step is a practical conversation: understanding the current estate, where value or risk may sit, and whether RTK can help create a cleaner path forward.

Explore the Executive Playbook
For a deeper view of how legacy infrastructure economics can affect cloud migration, RTK’s Executive Playbook examines the financial and operational barriers that can slow transformation, and how leaders can identify constraints before they affect delivery.

Speak with an RTK Strategic Infrastructure Advisor
If you are preparing for a data centre exit, cloud migration, or major infrastructure transition, RTK can help assess whether your estate contains value, risk, or timing pressure that should be addressed before key decisions are made.