A clean MSP transition is easier when every system, contact, access dependency, and open issue has a named next action. This evidence register gives an SMB team one practical place to record what has been received, what has been tested, and what still needs attention.
Download the blank MSP Transition Evidence Register (CSV)
This is a planning template, not a completed assessment, certification, or guarantee. Store credentials in an approved password manager, never in this spreadsheet.
How to use the register
Create one row for each important system or responsibility. Include Microsoft 365, domains, internet circuits, networks, devices, backup services, line-of-business applications, phone systems, surveillance, access control, and critical vendors when they are in scope.
Update the acceptance status only after the named evidence has been reviewed. A vendor statement that backups exist is different from a dated restore test. An administrator name is different from verified access controlled by the business.
Evidence columns
Scroll horizontally to compare all columns.
| Column | What to record |
|---|---|
| System or responsibility | The service, application, device group, or operating responsibility |
| Current contact/provider | The provider or person currently handling it |
| Business contact | The person who can approve access and business decisions |
| Access confirmed | Whether authorized access has been tested |
| Documentation received | Whether current diagrams, procedures, contracts, or inventories were received |
| Backup/recovery evidence | The dated evidence available for backup and restoration |
| Open issue | A specific gap, dependency, or unresolved question |
| Next action | The concrete action that moves the row forward |
| Acceptance status | Not started, in progress, accepted, accepted with exception, or blocked |
| Notes | Scope boundary, exception, evidence date, or other useful context |
Fictional worked example
Scroll horizontally to compare all columns.
| System or responsibility | Current contact/provider | Business contact | Access confirmed | Documentation received | Backup/recovery evidence | Open issue | Next action | Acceptance status | Notes |
|---|---|---|---|---|---|---|---|---|---|
| Microsoft 365 tenant | Previous provider | Operations manager | Yes | Partial | Not applicable to every workload | Two legacy administrator accounts need review | Confirm approved administrators and remove unneeded access | In progress | Fictional example only |
| File storage | Storage vendor | Finance director | Yes | Yes | Restore test dated September 15 | One archive share is outside the current backup scope | Decide retention and add or formally exclude the share | Blocked | Fictional example only |
The example shows why accepted access and recovery evidence should be separate. A system can be reachable while its recovery process remains untested.
Review before accepting a row
- Confirm the business controls or can recover the relevant account.
- Verify the inventory matches the systems actually in use.
- Test representative access using an authorized identity.
- Review current documentation and record missing items.
- Confirm the backup and recovery boundary where relevant.
- Assign every open issue a next action and business contact.
- Record the evidence date and any approved exception.
Common questions
Should passwords go in the CSV?
No. Record that access was confirmed and keep credentials in an approved secure system.
Does an accepted row guarantee the system will never fail?
No. Acceptance records the evidence reviewed at that point. Ongoing monitoring, maintenance, testing, and business decisions still matter.
Can this replace a transition project plan?
No. Use it as an evidence register alongside the transition schedule, responsibility map, communication plan, and risk decisions.
Plan the transition around evidence
Use the MSP transition timeline guide and the managed IT scope guide with this register.
Request a Free Initial Assessment if you want help identifying the most important gaps before a provider transition.