The Cost of Leaving: An Egress Audit for UK Cloud Estates

Cloud platform decisions are often framed as a choice between features, integrations and licence costs. The exit is treated as a later problem. For UK teams, that later problem can arrive quickly: a renewal notice lands, a procurement review begins, or a merger brings two estates together. At that point, the practical question is not whether the new platform looks better, but whether the existing data can leave on acceptable terms.

Egress is more than a bandwidth charge. It covers the formats in which data can be exported, the time required to extract it, the fees attached to bulk transfer, the treatment of backups and the support available after termination. A half-day audit can turn those unknowns into a costed, evidenced position. It does not require a large transformation programme. It requires a structured conversation between IT, finance, legal and the business owners of each system.

Begin with a data map, not a spreadsheet

The first task is to locate the estate. Most organisations underestimate the number of places where business data sits. A primary collaboration platform may hold documents and messages, but attachments are duplicated in storage services, call recordings sit in a communications tool, and customer records live in a CRM with its own export rules. Shared mailboxes, project folders, analytics workspaces and line-of-business applications all need to be in scope.

For each system, record the business owner, the system of record, the approximate volume, the growth rate and any retention or legal hold requirements. Volume should be expressed in both gigabytes or terabytes and object counts. A mailbox estate of two terabytes is not the same migration problem as two million small files. Sensitivity matters as well: personal data, financial records and material subject to a UK GDPR access request or litigation hold require different handling from general team content.

Administrative consoles can provide export reports, but they should not be trusted without a sample check. Pick one department and trace its data across the main systems. This exposes duplicates and orphaned content that a central inventory will miss. The output of this stage is a one-page map showing where data lives, who owns it and which copies are authoritative.

Measure the exit in three currencies

Once the map exists, estimate the exit in money, time and operational effort. Egress fees are the most visible cost, but they are rarely the whole cost. Ask the provider for a written estimate covering bulk export, API calls, archive retrieval, temporary storage and any professional services required. If the provider publishes a fee schedule, check whether it applies to all data types or only to standard storage.

Transfer time is the second currency. A large export may take days or weeks, and the business may need parallel running during that period. Test a representative sample over the same network path that would be used for the full export. Record throughput, failure rates and the labour required to restart incomplete jobs. For very large estates, ask whether encrypted physical media transfer is supported and how the chain of custody is documented.

The third currency is internal effort. Finance should include staff time for validation, reconciliation and user communications. Legal should include review of the exit terms. The business should include the cost of reduced service during cutover. A simple table with three columns — direct fees, internal labour and service risk — is usually enough to show whether a move is worth pursuing. The aim is not a perfect forecast, but a defensible range.

Test export formats before you commit

A provider may say that full export is available. The useful question is: available in what format, with what metadata and under what conditions? For documents, check whether folder structures, permissions, versions and audit trails survive the export. For email, check whether messages export as individual files or a single archive, and whether attachments remain linked. For chat and collaboration tools, check whether threads, reactions and edits are preserved or flattened.

Run a sample export from one team and open it on a clean machine without the source platform installed. This is the quickest way to find missing attachments, broken links and metadata loss. Confirm that the export can be read by the target platform or by a neutral tool. Open formats such as CSV, JSON, MBOX and ICS are preferable to proprietary backups, but they still need testing at realistic scale.

Also check the edges of the estate. Third-party applications connected to the platform may hold data outside the main export. API rate limits may slow bulk extraction. Archive tiers may require a retrieval request before export. Each of these details belongs in the audit notes, with an owner and a follow-up date.

Read the exit clause like a lease

The contractual questions are often the difference between a workable exit and a stalemate. Before renewing or switching, ask for the termination assistance clause, the notice period and the post-termination access window. Confirm how long data remains available after the contract ends, how backups are handled and whether a deletion certificate is provided. Ask whether egress fees change during the notice period and whether any minimum commitment survives termination.

UK teams should also review processor terms, international transfer arrangements and subprocessor lists. The provider should be able to explain how export requests are authenticated and logged. If the service holds personal data, the exit plan should align with the organisation's retention schedule and UK GDPR obligations. Legal and procurement should redline vague phrases such as reasonable assistance and standard export formats. Those phrases need schedules, timescales and named contacts.

A half-day agenda

A practical audit can be completed in one morning. Allocate the first thirty minutes to scope and ownership. Spend the next hour building the data map. Use an hour to estimate volumes, fees and transfer time. After a short break, run a sample export review and agree the format tests that still need to be completed. The final hour should be reserved for contract questions, risk notes and a decision on whether to proceed, pause or negotiate.

The output should be short: a data map, a cost range, a list of format risks, a set of clause redlines and a named owner for follow-up. That pack can support a renewal negotiation or a platform business case without pretending that leaving is free. In 2026, the teams that manage cloud estates well will treat exit as a designed process rather than an emergency. The audit is the first step in that discipline.