Cloud exit plan: lessons from Nine PBS

Retrospective covering 14 August 2026, written on 9 September 2026. The news event is the reported court-backed retrieval process, not a claim that the original access interruption began that day.

A cloud exit plan should demonstrate that your organisation can retrieve and use its records when the normal supplier relationship stops working. My recommendation is to test that ability with a representative export and a business owner before renewing a service that holds important information.

On 13 August, Current reported that a Denver judge had set a process for Nine PBS to retrieve archival material following a hearing the previous day. The report concerned access to approximately 50 terabytes of material. It did not establish that the archive had been permanently destroyed. Current's court report.

Keep the story's timeline straight

Current's earlier reporting said Nine PBS had brought a lawsuit after losing access through its storage provider, Open Source Storage. The dispute and interruption predated August's coverage. That distinction prevents a retrospective from turning a developing legal process into a newly occurring technical failure. Current's 11 August report.

The follow-up described a chain with three distinct parties: Nine PBS, its contracted storage provider OSS, and Iron Mountain, which supplied infrastructure to OSS. The retrieval framework therefore involved a party outside the broadcaster's direct storage contract. A framework for recovery is not the same as a completed recovery. Current's 13 August update.

For a UK SME, the useful lesson is an operational question: what can your team actually retrieve if the supplier's normal support and administration routes become unavailable? This article proposes a way to answer it, rather than drawing legal conclusions from a US dispute.

Start with the information the business needs

Ask the process owner which records would be needed to continue work elsewhere. Avoid starting with the export button or the largest folder. The important dataset may be a smaller collection containing approvals, customer history or evidence of completed work.

List the context needed to interpret each record. An invoice attachment without its customer relationship may be difficult to use. A project document without a clear version may not support the next decision. These are examples to test in your environment, not claims about the Nine PBS archive.

Agree a minimum useful export with the owner. This creates an acceptance criterion that a technical team can test and a budget holder can understand.

Map the people required for retrieval

My suggested exit record identifies the contracting supplier, the normal administrator, the technical support route and any other party whose cooperation would be needed. Ask the supplier to explain the dependencies rather than guessing from its brand or hosting logo. For the rehearsal, assume the contracting supplier is unavailable: which authorised retrieval steps still work, and which stop because only that supplier can instruct the infrastructure provider?

Record which steps your organisation can perform directly and which require an external person. For each external dependency, ask what happens if that person or company is unavailable. A plan that simply says "contact support" has not answered the difficult part.

Keep the relevant contract and contacts accessible to authorised staff through an agreed route. Have procurement verify the commercial position and obtain appropriate advice for contractual questions. The technical test should establish what works; it should not pretend to settle legal rights.

Run a small exit rehearsal

The following is my proposed exercise for a non-production sample. It is deliberately narrower than migrating the whole service.

Give the exported sample to somebody who was not responsible for creating it. Ask them to perform the agreed task using the supplied instructions. Their questions reveal where the plan depends on knowledge that has not been written down.

Do not use sensitive production records merely to make the exercise realistic. Choose an approved sample and handle it through your existing data controls.

Distinguish retrieval from backup recovery

The NCSC advises organisations to keep backups of important data and understand how to restore them, including checking that the necessary data is present. NCSC backup guidance.

My proposed exit rehearsal asks a related but different question: can the business work with the retrieved material outside the current service? Record the answers separately. You may have a successful recovery procedure for the existing application and still lack an acceptable migration route.

Likewise, an export that opens successfully does not prove that all required records have been captured. Compare it with the scope agreed at the start, and document exclusions explicitly.

Use your disaster recovery plan for restoration responsibilities and the exit record for the supplier transition decision.

Put a realistic cost beside the gaps

Ask the team to estimate the work remaining after the sample exercise. Separate data retrieval, conversion, business checking, replacement service setup and any period of parallel operation.

Keep assumptions visible. If the estimate depends on the supplier completing an export, identify that dependency. If nobody has tested the replacement workflow, record that the time estimate remains provisional.

The aim is a decision that finance can assess, not a reassuring number with no evidence. An expensive exit may still be acceptable, but it should be understood before the organisation becomes more dependent on the service.

This belongs in supplier due diligence and should be revisited when the scope of stored information changes materially.

Use renewal as a decision point

Before renewal, ask whether the tested export still matches the current service. New integrations, record types or business uses may require the acceptance scope to change.

My recommended management question is concise: if the relationship stopped working, which important records could we retrieve and use without improvising? Attach the rehearsal evidence and the unresolved dependencies to the answer.

That gives the business continuity owner a practical action list. The Nine PBS story is a reason to make retrieval demonstrable while the normal supplier relationship is still available to help.