Changing Your IT Support Provider Without Risk

Changing your IT support provider without risk is possible when the transition follows a clear plan: first the incoming provider audits the IT estate it is about to take on, then all access credentials and documentation are taken over, knowledge is transferred, a parallel running period is set aside — and only then is the outgoing vendor disconnected. The biggest problems arise not from the new provider’s competence but from a chaotic handover, when a company is left without passwords, licences or knowledge of its own systems.

The decision to switch providers is often postponed for years: things sort of work, the new vendor might be even worse, it all sounds like too much disruption. The fear is understandable, but it rests on the assumption that a transition must be painful. It does not have to be — a well-planned takeover is barely noticeable to employees, and for the company it often becomes an opportunity not only to get better service quality, but also to put documentation and access ownership in order.

Below are the signs that a change is worth making, the most common mistakes to avoid, and a phased transition plan you can use as a checklist.

When it is worth changing your IT support provider

One bad month is not yet a reason. But if the signs below keep recurring, the provider is no longer doing its job:

• Slow responses. Requests hang for days, you have to chase several times, and in an emergency it is unclear who to even call.
• No reporting. You receive no regular information on what was done, what incidents occurred and what state your systems are in — you are paying for silence.
• No initiative. The vendor only reacts to failures and never proposes prevention, upgrades, security improvements or budget planning insights.
• Dependence on one person. Everything sits with a single specialist — when they are on holiday or off sick, support stops; there is no documentation anyone else could pick up.
• Unclear responsibility. The contract defines no commitments, so every dispute ends with the claim that it was never agreed. What the contract should contain is covered on the page What belongs in an IT support contract.

The most common mistakes when switching providers

Almost every painful transition story stems from the same few mistakes:

• Access and documentation never reclaimed. Administrator passwords, domain management, cloud accounts and network equipment credentials stay with the old vendor. The company formally owns its IT estate but in practice cannot get into it.
• No handover plan. The transition happens ad hoc: who hands over what and when is never agreed, so part of the knowledge and configuration simply gets lost or takes far longer to recover.
• A single-cutover switch. The old vendor is disconnected on Friday and the new one starts on Monday, with no overlap. The first serious incident lands on a team that does not yet know the systems. And it can get worse than that.
• Licence ownership left unresolved. Software and cloud subscriptions are registered in the vendor’s name. On termination, the company risks losing licences or data, or at the very least facing urgent re-registration work.
• Escalating conflict before the handover. Keep the relationship with the outgoing vendor businesslike to the very end — the quality of the handover depends directly on their cooperation.

A phased plan for a smooth transition

The transition is easiest to manage as a project with clear phases and a defined outcome for each. The first phase, the audit, is carried out by the incoming provider — taking over an IT estate from another vendor or from an in-house team, it has to know the real state it is assuming responsibility for and will have to put right. This is standard takeover practice, included in the takeover work rather than a separate concern for the client or a service ordered on its own. A typical sequence looks like this:

The response times and coverage that should apply from the new provider’s first working day are worth defining in advance — the page What SLA does your company need will help.

What to require from the outgoing vendor

During the handover you are entitled to everything connected with your company’s IT estate. A checklist:

1. A list of all administrative accounts and their credentials: servers, file services, network equipment, cloud platforms, domains, certificates, the email system;
2. A list of licences and subscriptions, including whose name they are registered in and when they expire;
3. All existing documentation: infrastructure diagrams, configuration descriptions, standard procedures;
4. Backup details: where copies are stored, how they are restored, who owns the storage;
5. The incident and request history, if one was kept;
6. Written confirmation that, after the handover, the vendor retains no active access to your systems.

Reality often looks different from this list. An outgoing vendor rarely goes out of its way to help its successor, and anything that is not strictly obligatory frequently never arrives — from configuration descriptions to incident history. Handover items are therefore worth demanding in writing, on the basis of the contract: with a specific list, deadlines and a record of what was received and what was not. Some companies bring in legal advisers at this stage. That is not to say every vendor behaves this way — but it is safer to plan the transition around this scenario.

This is exactly why ownership of access credentials, licences and documentation should be established in the contract in advance, right at the start of the relationship. When the contract states clearly that accounts and licences are registered in the company’s name, that documentation is the client’s property, and that the scope and deadlines for handing it over are defined, the handover becomes a technical task rather than a negotiation. What else needs to be covered there is set out on the page What belongs in an IT support contract.

If the outgoing vendor cannot or will not produce some of these items, that is itself an important finding the new partner needs to know about before assuming responsibility. This is exactly why a takeover starts with an audit — described in detail on the page IT infrastructure audit: what is checked and how to prepare.

How Altic IT takes over IT estates

Our practice, shaped by many takeovers, rests on three principles. First, we start with an audit: when taking over an IT estate from another vendor or from an in-house team, we record the real state of the infrastructure, security and documentation before assuming responsibility — so we know what we are taking over and you know what you have. We present the findings and agree them with you, so the audit ends not with a report but with an agreed action plan: what we fix immediately and what we schedule for later. Second, we reduce incidents systematically: by fixing the root causes of the most frequent failures and deploying automated monitoring, we cut the number of incidents for our clients by up to five times within the first three months. Third, we assign an experienced external IT manager who takes responsibility for your entire IT estate, including managing third-party vendors — your employees keep a single point of contact for every IT matter.

After the takeover, day-to-day operations run through our IT support services: automated monitoring, workplace support and regular reporting, so you always see what you are paying for. To see what such takeovers look like in practice, read our success stories.

Why Altic IT

Switching providers is a question of trust, so the new partner needs both experience and verifiable safeguards:

• 180+ clients served, around 3,500 computers and mobile devices and around 350 servers under management;
• ISO 27001, ISO 20000 and ISO 14001 certifications — takeover and support processes meet international standards;
• Professional liability and cyber risk insurance of EUR 2 million;
• IT estate management according to ITSM, ITIL and COBIT good practice;
• Open-ended contracts — we stay as long as you are happy, so no client is held by termination penalties;
• A team made up predominantly of experienced senior-level IT specialists; Microsoft Solutions Partner for Data and AI and Sophos Gold Partner status;
• The vast majority of our clients came through referrals — among them the Verslo zinios media group, CityBee, Tele2 and Vilnius City Municipality.

Frequently asked questions

• Will our business stop while we switch providers?

  No — not if the transition is planned in phases with a parallel running period. For employees, the only change is the contact they turn to for help; the systems keep working as usual. The bulk of the handover work happens in the background and does not disturb daily operations.

• What if the outgoing vendor refuses to cooperate?

  This is a fairly common situation, so it is best treated as an expected scenario: an outgoing vendor often hands over only what it is strictly obliged to. Transferring credentials, licences and documentation is normally the vendor’s contractual duty, so put the demand in writing, with a specific list and deadlines. Whatever cannot be obtained, the new provider reconstructs itself during the audit and access takeover phases, and prepares the missing documentation anew — that takes longer, but it does not stop the transition. In extreme cases, legal assistance is brought in as well.

• How long does the transition to a new provider take?

  It depends on the size of the IT estate, the state of the documentation and the outgoing vendor’s cooperation. In the simplest cases a short overlap period is enough; more complex estates need a longer parallel phase. It usually takes from a few weeks to a month, and in complex, large-scale cases it can run to several months when the estate is taken over in stages. We set out and agree the concrete duration after an initial discussion of your current situation.

• Do we need a new IT support contract?

  Yes — the transition is the right moment to fix what the old contract lacked: a clear service scope, responsibilities, reporting and access ownership. Altic IT contracts are open-ended, so you are not locked in — the partnership continues for as long as you are satisfied.

• Will the new provider also take over relationships with our other IT vendors?

  Yes. Altic IT clients get a single point of contact that extends to third-party vendor management: internet providers, business software and other system implementers, telephony and printing service suppliers. Your employees no longer need to work out which vendor owns a given problem — we sort that out with them on your behalf.

Discuss a smooth transition

If you are considering a change of IT support provider, let us look at your situation together: we will assess the current state, propose a phased takeover plan and explain what the first months would look like. Get in touch via our contact page or by phone at +370 5 2032018 — we will plan the transition so your team barely notices it.

Contact Altic IT