Practical guide
Before giving notice: confirm ownership and documentation
Before giving notice, check renewal and notice dates, exit terms and what support the outgoing provider will offer. Name an internal coordinator, then build a shared list of services, systems, suppliers and business contacts. Record who owns each relationship, who can approve changes and where current documentation is held.
Useful information may include asset and user lists, network diagrams, configuration records, support procedures, open issues, maintenance windows, warranties and renewal dates. Protect sensitive material and transfer credentials through an agreed secure process rather than ordinary email.
- Identify who in your organisation can coordinate the transition and make decisions.
- Agree with both providers what records will be shared, in what format and by when.
- List known issues, ongoing projects, exceptions and tasks that must not be lost.
- Keep an agreed record of questions, decisions, owners and target dates.
Before handover: confirm administrative access and ownership
Make sure the organisation, not an individual employee or supplier account, owns the domains, cloud tenants, key subscriptions and business-critical administrator relationships wherever possible. Confirm that at least one authorised business representative can access these services.
Review privileged accounts, recovery methods, multi-factor authentication and break-glass arrangements. Coordinate any transfer of provider accounts or credentials carefully; changing access too early can interrupt support, while changing it too late can leave unclear responsibilities.
Before handover: document domains, cloud services and licensing
Domains and DNS influence websites, email, identity and external services. Record registrar details, renewal dates, DNS zones, mail routing and any third-party services that depend on those records. Plan changes with the people responsible and avoid changing nameservers or records without a tested reason.
For cloud services, document tenants, subscriptions, integrations, administrator roles, backup and security settings. Check licence ownership, renewal dates, quantities and dependencies. A provider handover should establish who administers the existing environment before anyone proposes a migration.
The same principle applies to software and cloud platforms: understand what is in use, what the organisation owns and what a proposed change would affect. Verify service access and support routes before removing any account or licence.
Before handover: check backup, security and recovery
Before responsibilities change, establish what is backed up, where copies are held, how long data is retained, who can restore it and whether a recent restore test succeeded. Agree how existing backup jobs and alerting will be monitored during the transition so there is no ownership gap.
Review endpoint protection, email security, identity controls, update processes, alert handling and supplier access. Avoid disabling a protection or monitoring service until a replacement responsibility is understood and agreed.
A clear business continuity and recovery plan helps identify which services need priority, who communicates and how the organisation will continue work if a system is unavailable. For broader planning, see the cyber security measures to carry through a provider change.
Before handover: list suppliers, connectivity and equipment
List internet circuits, telephone services, domain registrars, software vendors, line-of-business systems, print services and specialist support. Record account references, contract terms, fault routes, renewal dates and whether a supplier needs to be notified of the provider change.
Document network equipment, locations, configurations, warranties and any support dependencies. Check which devices are owned, leased or supplied by a provider. The incoming team should assess existing equipment and its condition; replacing working infrastructure is not an automatic part of a transition.
Internet and voice
Confirm account ownership, circuit references, contract dates, fault contacts and any static addressing or routing dependencies.
Network and infrastructure
Record firewalls, switches, wireless access points, servers, remote access and any known configuration exceptions.
Equipment
List devices, ownership, warranty, lifecycle status and whether they should remain in use.
Business suppliers
Identify who can approve access, support requests, DNS changes and integrations for each critical supplier.
During the handover: transfer knowledge and agree a staged transition
Agree the handover sequence, communication plan, change windows and escalation contacts. Where possible, schedule discovery and access checks before a cutover. Make sure users know how to raise support requests at each stage and which provider owns an issue while the handover is in progress.
The incoming provider should verify the environment and identify risks before recommending changes. Some changes may be appropriate, but they should have a reason, an owner, a rollback plan where relevant and an agreed impact. A staged approach is often easier to understand than changing several connected services at once.
Our guide to switching IT provider explores how to make the decision and plan a controlled move. If the current state is unclear, begin with a review of the existing IT environment.
After the switch: check the essentials
- Can authorised staff access business-owned domains, cloud services and administrator accounts?
- Are support routes, escalation contacts, open requests and responsibilities clear to staff?
- Are backup monitoring and restore responsibilities active, with a restore test planned?
- Have outgoing-provider accounts and access been removed at the agreed time, after handover duties are complete?
- Can staff find current documentation and the new support and update process?
