Business IT support handover checklist
Changing IT support is a transfer of responsibility, not just a new helpdesk number. Gather the ownership, access and recovery information your business needs before agreeing the handover with SCG Solutions.
Establish who owns the accounts
List the Microsoft 365 tenant, domains, DNS, internet services, business applications and software subscriptions. For each, identify the contracting organisation, billing owner, administrator and recovery contact. Ask whether the business can recover access if a supplier or a member of staff becomes unavailable.
Keep credentials out of spreadsheets circulated by email and out of enquiry forms. Agree an approved, secure transfer method for necessary access. The handover should explain how administrator access will be granted, recorded and removed, not leave several suppliers sharing one permanent password.
Define the support boundary before comparing quotes
A managed IT proposal should identify supported users, devices, sites and applications, together with service hours, escalation routes and exclusions. Ask which activities are routine support and which require a separate project: office moves, tenant migrations and specialist application work may have different scope.
The NCSC supply-chain principles encourage organisations to understand supplier risks and establish security expectations. Apply that thinking to the support relationship: ask who may access systems, whether subcontractors are involved and how responsibilities are communicated. A commercial response target should be documented in the agreed service, not inferred from a marketing phrase.
Sources for this section: NCSC — principles of supply chain security
Check devices and recovery before the change
Record laptops, desktops, servers, networking equipment and business-critical applications. Include operating systems, warranty details and software that only one person understands. Keep a separate exception list for unsupported equipment and systems that cannot be changed during normal working hours.
Ask the outgoing and incoming teams to document backup scope, retention, recovery access and the most recent restore evidence. A dashboard showing successful jobs does not answer whether the right files or application can be recovered. Agree which recovery checks are included, who approves them and how failures will be handled.
Plan the handover and first month of support
Schedule a handover meeting with the business owner, the outgoing supplier where appropriate and the new support team. Review outstanding incidents, planned changes, licences, supplier contacts and the systems nobody should touch without approval. Keep one agreed issue list rather than losing the history across several inboxes.
After acceptance, review old administrator accounts, remote-access tools and monitoring agents. Remove or replace access only after confirming dependencies and approval. Explain the new support route to users, test a representative request and agree a follow-up review of unresolved risks. Keep the business in control of the handover decisions.
Questions for the IT support handover
Use these questions to make the service boundary explicit.
| Area | Evidence to gather | Responsibility to agree |
|---|---|---|
| Microsoft 365 and identity | Tenant owner, licences, administrators and recovery contacts | Joiners, leavers, access approvals and licence administration |
| Devices and applications | Asset list, supported versions and business-critical dependencies | Routine support, patching, exceptions and project work |
| Backup and recovery | Protected systems, retention and restore evidence | Monitoring, recovery testing and incident escalation |
IT support handover checklist
Use an agreed secure process for documents and access; this is not a request to submit credentials.
- Name the business owner for each tenant, domain and core application.
- Inventory users, devices, sites, licences and critical dependencies.
- Document support hours, response arrangements, scope and exclusions.
- Agree a secure process for necessary administrator access.
- Confirm backup scope and the available recovery evidence.
- Transfer open incidents, supplier contacts and approved change plans.
- Review and remove outgoing access when the handover has been accepted.
- Tell users how to request support and schedule a follow-up review.
Related services and next steps
Business IT support handover checklist — common questions
Can SCG Solutions work alongside our internal IT team?
Discuss the responsibilities you want to retain and the areas where you need support. The service scope should separate your team’s approvals and duties from the provider’s work before a quote is accepted.
Should we cancel our old IT support before the handover?
Agree the transition and contractual requirements first. A premature cancellation can leave gaps in access, documentation and support. Coordinate the dates with both suppliers and the business owner.
Can we send administrator passwords through the contact form?
No. Describe your requirements without passwords, recovery codes or sensitive documents. Necessary access should be exchanged through an approved secure process after the scope and authorised contacts are established.
Make the IT handover clear
Tell SCG Solutions about your users, sites, Microsoft 365 environment and the responsibilities you want to retain. We can discuss the support scope and the information needed for a quote.
Discuss IT support