# MSP cutover and rollback log - blank working copy

Prepared by MSP Shortlist, 16 October 2026. Version 1.0. Guide: https://mspshortlist.com/guides/msp-outsourcing-transition/

Adapt this log to your approved scope and agreement. It is an uncompleted planning document, not a performed cutover, provider assessment or legal notice. Set the acceptance conditions before acting. Add observations and references only after the responsible team has checked them.

## Scope and authority

Buyer, provider and proposed service / package:
Client / tenant / queue / asset boundary:
Included duties and retained MSP duties:
Applicable agreement, service schedule and change reference:
Planned start, end, timezone and holiday calendar:
Decision owner, receiving service owner and fallback route:
Approved systems for ticket history and supporting documents:
Customer communication owner and next update deadline:

Use sanitized summaries and references to approved systems. Keep credentials, raw client records and confidential attachments out of this working copy. A named role in the guide is a suggestion; assign an actual accountable person or team.

## T01. Inventory

Deliverable: Clients, assets, users, coverage and exclusions
Hold condition: Counts or tenant mapping disagree
Assigned owner and receiving / cooperating team:
Agreed completion condition and planned date / timezone:
Documents, observations and confirmation references:
Review state: Not reviewed
Open issue, next action, owner and due date:
Reviewer, decision date, time and timezone:
Recheck or changed decision (keep the earlier entry):

## T02. Knowledge

Deliverable: Approved runbooks, owners and escalation paths
Hold condition: Missing instructions for a critical service
Assigned owner and receiving / cooperating team:
Agreed completion condition and planned date / timezone:
Documents, observations and confirmation references:
Review state: Not reviewed
Open issue, next action, owner and due date:
Reviewer, decision date, time and timezone:
Recheck or changed decision (keep the earlier entry):

## T03. Shadow operation

Deliverable: Both teams observe the same cases
Hold condition: Actions or ticket history cannot be reconciled
Assigned owner and receiving / cooperating team:
Agreed completion condition and planned date / timezone:
Documents, observations and confirmation references:
Review state: Not reviewed
Open issue, next action, owner and due date:
Reviewer, decision date, time and timezone:
Recheck or changed decision (keep the earlier entry):

## T04. Limited cutover

Deliverable: One bounded queue or client group transferred
Hold condition: Buyer cannot restore retained coverage
Assigned owner and receiving / cooperating team:
Agreed completion condition and planned date / timezone:
Documents, observations and confirmation references:
Review state: Not reviewed
Open issue, next action, owner and due date:
Reviewer, decision date, time and timezone:
Recheck or changed decision (keep the earlier entry):

## T05. Accepted operation

Deliverable: Outcomes reviewed and residual risks assigned
Hold condition: Blocking pilot failure remains unresolved
Assigned owner and receiving / cooperating team:
Agreed completion condition and planned date / timezone:
Documents, observations and confirmation references:
Review state: Not reviewed
Open issue, next action, owner and due date:
Reviewer, decision date, time and timezone:
Recheck or changed decision (keep the earlier entry):

## Go / hold decision

Decision: Not recorded
Approved workload, window and receiving owner:
Conditions still open, exceptions, owners and due dates:
Retained coverage and authority during the transfer:
Buyer decision, approver, date, time and timezone:
First review and invoice / enrolled-inventory reconciliation date:

Choose Go, Hold or Roll back only after reviewing the gate entries. Keep a previous decision when adding a new one. No gate is marked complete by downloading this file.

## Rollback log - complete only if invoked

Trigger, observation and decision time / timezone:
Authorized decision maker and action-stop instruction:
Provider acknowledgement that new changes have stopped:
New intake routing and receiving-team acceptance:
Open incidents, next actions and accepting owners:
Retained access / approved revocation state and confirmation:
Client communication and next update deadline:
Continuity check and remaining risks with owners:
Correction plan, next review and conditions for another cutover:

Do not run two teams as simultaneous active actors on the same change. Reconcile the ticket history and agree who controls the next action before attempting another transfer.
