IT Transition & Turnaround

Changing providers is easy. Transferring ownership isn't.

Major IT changes create a temporary ownership problem. The old provider knows what exists but is on the way out. The new provider has an onboarding plan but cannot yet see everything it is inheriting. During a platform migration, responsibilities are split between the old and the new environment. And when an IT function is already in trouble, ownership may not be clear at all. In every case, you are the one carrying the consequences if something is missed.

The problem rarely is the change itself. The problem is everything that has to survive it: services, accounts, licences, devices, integrations, documentation, supplier responsibilities and operational knowledge. The cut-over date may be fixed by a contract or project plan, but that does not mean any of these are actually ready. That is how transitions produce outages, lost licences, orphaned access and months of finger-pointing.

Turnarounds expose the same problem from the opposite direction. There may be no new provider and no planned migration — just recurring outages, systems nobody owns, undocumented dependencies, or one person who knows how everything works and is about to leave. Before the service can improve, somebody has to establish what exists, who owns it and how it should operate.

In six steps, over eight to twelve weeks.

1. Mobilisation Duration: one week. We start with an onsite kick-off with the sponsor and the people who actually know the service. We establish direct contact with the providers and other parties involved, agree how decisions and escalations will work throughout the transition, and secure access to the contracts, service descriptions, existing documentation and relevant systems we will need during the assessment.
2. Discovery and inventory Duration: Two weeks. With access established, we analyze what is really there. Over the next two weeks we examine the available documentation, compare it with the live environment and build the working inventory of systems, data, accounts and privileged access, licences, contracts, integrations, devices, runbooks, supplier dependencies and operational responsibilities. Where the documentation is incomplete, outdated or simply wrong, interviews with the people running the service are used to fill the gaps and uncover the dependencies, workarounds and operational knowledge that only live in people’s heads. The result is the first reliable picture of what must actually be transferred, replaced, retained or explicitly retired.
3. Scope Statement and transition plan Duration: One week and a meeting. We start by taking the findings from discovery back to the sponsor and agreeing exactly what this engagement will cover. The resulting Scope Statement records the systems, services and organisational areas in scope, the parties we will work with, the work Interpunct will perform and the deliverables we will produce, as well as anything explicitly excluded. Once agreed on, this scope is fixed and any subsequent addition is handled through a written change order. With the engagement boundary established, we build the transition plan itself: what has to move or change, in what sequence, who is responsible for each activity, which dependencies have to be resolved first, and what milestones lead to cut-over. The plan also defines the RACI, readiness and acceptance criteria and, where applicable, the conditions for proceeding with or rolling back the cut-over.
4. Execution Duration: Three to six weeks. For the next three to six weeks we run the transition. A weekly transition board brings the responsible parties together around the same plan, with dependencies, risks, decisions and overdue actions visible to everyone. Knowledge-transfer sessions are scheduled against the inventory, and the resulting operational knowledge is turned into a usable runbook pack. Access, licences, integrations and responsibilities are checked as they move. Where the service allows it, we rehearse the cut-over before the real date so that missing information and assumptions are discovered while there is still time to do something about them.
5. Cut-over and verification The cut-over is treated as an operational event. We are onsite for the change, coordinate the parties against the agreed plan and acceptance criteria, and keep ownership of open decisions and issues clear while the service moves into its new state. Afterwards, we verify that what was supposed to move actually moved and that what was supposed to disappear actually disappeared. The removal of the outgoing provider’s privileged access, for example, gets verified and documented. At the same time we begin measuring the service against an agreed baseline, so that the new setup can be judged on evidence.
6. Hand-over Duration: One week. Once the cut-over has been completed and the agreed acceptance criteria have been verified, we formally close the transition and hand the service back to its operational owners. We produce the acceptance report and hand over the final inventory, runbooks, responsibility model and transition documentation, together with the initial KPI baseline established after cut-over. Any issue that remains open is documented with its current status, a named owner and an agreed target date, so there is no ambiguity about what the transition has completed and what remains for normal service management to resolve.

For turnaround engagements where there is no provider or platform change, the same structure is used to establish control and stabilise the service; cut-over becomes the agreed point at which the recovered operating state takes effect. Premium adds twelve weeks of hypercare after hand-over. During that period we hold fortnightly service reviews, track the new service against the KPI baseline established during the transition, follow through on unresolved actions and make sure that problems inherited from the transition do not quietly become the new normal.

• Entry — Transition Health Check Before you commit to a date — or if the transition is already causing concern — we establish what has to move what your contracts actually oblige the outgoing provider to do, where the transition risks are, and whether the current plan is viable. You leave with a documented assessment and a clear recommendation on what needs to happen next.
• Standard — the transition itself The complete transition engagement, from discovery and inventory through planning and execution to cut-over, verification and formal hand-over.
• Premium — with hypercare Standard plus twelve weeks of post-transition stabilisation. We remain on the client side, hold fortnightly service reviews with the new provider, track performance against the post-cut-over baseline, and follow outstanding transition items and emerging service issues through to closure.
• Custom Some transitions do not fit into a single 8–12 week engagement. If several providers or sites have to move at the same time, or the transition is part of a merger, acquisition or wider transformation, we first establish the dependencies, parties involved and realistic sequencing of the work. Based on that, we define the scope, timeline and level of involvement required and quote the engagement individually.