Sales & Conversion· 3 min read· By The SpideyChat Team

Exit and Handover Questions When Changing Provider

Leaving an IT provider is easy until you need the passwords. A checklist for the exit nobody plans.


A business decides to change provider. The relationship is amicable and everybody is professional about it.

Then the practical work begins. The domain is registered in the outgoing provider's name, the software licences were bought through their account, the firewall has an administrative password nobody else knows, and there is no documentation of anything.

Six weeks later the transfer is still incomplete. Nobody behaved badly. The business simply never established ownership of its own systems.

1. Establish ownership before you ever need to leave

Domains, licences, cloud tenancies and administrative accounts in the business's name. This is the single decision that makes any future exit straightforward.

2. Hold your own domain registration

In the business's account, with the business as registrant. A domain held by a provider is the most common and most damaging version of this problem.

3. Hold your own cloud tenancy

With a business owned global administrator account that the provider is granted access to rather than owns. This distinction matters enormously at exit.

4. Get the documentation written as you go

Network, systems, credentials, configurations and anything specific. Documentation produced during a notice period is produced reluctantly and is usually thin.

5. Put handover obligations in the contract

What must be provided at exit, in what format and within what period. Almost no small business agreement contains this and it is a short clause.

6. Agree the notice period both ways

And what happens during it. A provider working a notice period has no incentive to invest, and what is expected should be written down.

7. Make an inventory before serving notice

Every system, licence, subscription and credential you are aware of, so that you can identify what is missing rather than discovering it later.

8. Plan the credential transfer specifically

A list, a secure transfer method and verification that each one works. A password list handed over and never tested is the commonest failure.

9. Change everything after the handover

Every administrative credential, as a matter of routine rather than suspicion. This is normal practice and it should be expected on both sides.

10. Check the licence position carefully

Licences purchased through a provider may need transferring or repurchasing, which is a real cost that should be identified before notice is served.

11. Keep the relationship professional

The outgoing provider's cooperation determines how long this takes, and an acrimonious exit costs the business more than it costs them.

12. Expect the incoming provider to audit

Which is a genuine piece of work and should be scoped and paid for, and is the ground in onboarding and documentation questions from new clients.

13. Do not leave during a critical period

Year end, a peak trading period or immediately before a project. The transition needs attention that a busy month will not allow.

14. Publish your own exit terms if you are the provider

An assistant that explains what a client would receive at exit, what they own, how credentials are transferred and how long it takes is a genuine differentiator, because a provider confident about its exit terms is telling a prospect something important. The same switching anxiety appears in payroll enquiries from businesses changing provider, the incident load in outage questions that flood an it provider at once, and the commercial handling in how to handle discount and coupon questions with a. See pricing, run the numbers on the chatbot ROI calculator, and the sector view sits under it services.

Frequently asked questions

What should happen when an IT provider is replaced?
A documented handover of all administrative credentials, domain and licence ownership, documentation of the environment, and a defined period during which questions can be asked.
What usually goes wrong?
Credentials held under the provider's own accounts, domains registered in their name, licences purchased through them, and no documentation that anybody else can use.
How should this be avoided?
By establishing ownership at the start rather than the end, with the business holding its own domains, licences and administrative access independently of any provider.

Want a 24/7 AI Employee for Your Website?

See how SpideyChat can answer customer questions, capture leads and handle enquiries while your team is offline.

No obligation. We will review your website and show you how SpideyChat could work for your business.

Keep reading