How to properly terminate your contract with an IT contractor and retrieve all your data

Changing the IT contractor for infrastructure support is one of the riskiest processes for business. 

Servers, networks, cloud services, employee workstations — all of it has been under the contractor's management for months or even years. One wrong move during the transition, and the company risks losing access to critical systems, misplacing configurations, or being left without support at the worst possible moment.

This article is a practical guide for executives and business owners. You will learn how to properly terminate a contract with an IT company, recover all your access credentials, data, and infrastructure documentation — without a single minute of downtime. No filler, just concrete steps.

Why Terminating an IT Infrastructure Contract Is a High-Risk Zone

IT infrastructure support is fundamentally different from most other types of outsourcing. Over the course of the engagement, the contractor becomes the only person who truly understands your network architecture, server configurations, backup scheme, and cloud environment logic. This creates a serious dependency.

Common Reasons for Switching an Infrastructure IT Contractor

• Slow incident response and repeated SLA breaches.
• Lack of transparency: unclear what is being done and what you are actually paying for.
• Unjustified cost increases.
• Recurring infrastructure failures that are never resolved systematically.
• A strategic decision to move to a different provider or build an in-house IT team.

What Happens If You Don't Prepare for the Switch in Advance

Leaving a contractor without preparation can result in a situation where nobody knows the router password, the firewall configurations exist only on the former administrator's laptop, and the network diagram lives only in his head. These situations are far from rare, and they can paralyze an office or an entire business for days.

Q: How Do You Know It's Time to Switch IT Contractors?

A: Warning signs include systematic SLA violations, the absence of up-to-date infrastructure documentation, and the inability to get a coherent incident report. If your contractor cannot show exactly what they manage and what state the systems are in — that is already sufficient grounds for making a change.

Legal Preparation: Data Ownership and Terminating the IT Contract

Before initiating the termination of your IT company contract, review the current agreement carefully. In the IT infrastructure outsourcing space, there are several key points you need to verify in advance.

What Should Be Defined in the Contract

1. Data ownership: all data stored on servers and in cloud environments belongs to the client.
2. The procedure for transferring access credentials, documentation, and configurations upon termination.
3. The contractor's responsibility for client data: the obligation to maintain confidentiality and ensure data is returned or destroyed.
4. The duration of the NDA with the IT contractor after contract termination.
5. The timeline and procedure for termination notice (typically 30 days).

If the Required Clauses Are Missing from the Contract

Draft a supplementary agreement or a handover act in which the contractor formally confirms the transfer of all rights, access credentials, and data. Keep a record of all correspondence — it will serve as evidence in the event of a dispute. This is especially important when personal data of your clients is involved: under GDPR, failure to return data or a data breach carries serious penalties.

Termination Notice: Format and Timeline

Send a formal written notice of contract termination to the IT company. State the end date, list all assets and data to be transferred, and specify a concrete transfer deadline. Keep proof of delivery. Once this is done, you are legally protected: the contractor is obligated to complete the handover within the agreed timeframe.

The Complete IT Contractor Transition Checklist: What You Need to Get Back

To avoid losing critical assets during the contractor switch, organize everything that needs to be returned to you into four categories.

Network Infrastructure and Servers

• Administrative accounts on all servers (on-premise and cloud).
• Access to network equipment: routers, switches, firewalls (including configuration files).
• VPN configurations and certificates.
• LAN diagram and IP addressing scheme.

Cloud Environments and Services

• Root/Owner access to cloud consoles: AWS, Azure, Google Cloud, etc.
• Microsoft 365 / Google Workspace accounts: global administrator rights.
• Backup systems: access credentials and backup schedules.
• Monitoring and alerting systems: configurations and credentials.
• Software licenses registered under the contractor's accounts — transfer ownership to the client. Best practice: software licenses should never be registered under a contractor's account in the first place.

Workstations and User Support

• MDM system (Mobile Device Management): access and device management policies.
• Antivirus and endpoint protection solutions: management consoles.
• Active Directory / LDAP: domain administrator rights.

Infrastructure Documentation

• Network and infrastructure architecture diagram.
• Hardware and software inventory with versions and licenses.
• Runbook: step-by-step instructions for routine operations and disaster recovery.

Related: How to choose an IT contractor for your business: 7 questions to ask

How to Reclaim Access from an IT Company: A Step-by-Step Algorithm

Reclaiming access from an IT company must be done in an organized way to avoid disrupting live systems. Changing passwords chaotically without a plan is a reliable way to cause hours of downtime. Here is the correct sequence of actions.

Step 1: Inventory All Access Points

Create a table: system — contractor access level — account owner — transfer status. Include everything: from root server accounts to monitoring system logins. This step is worth spending 1–2 days on — it will save weeks of chaos later.

Step 2: Create Your Own Administrative Accounts

While the current contractor is still working, create your own administrative accounts in all critical systems. The new contractor or your in-house IT specialist must receive full rights before the old contractor loses theirs. Never allow a situation where access is revoked before the new administrator has confirmed readiness to take over.

Step 3: Revoke Access on Day X

Once all systems have been verified as fully operational under the new contractor's management — revoke the old contractor's access. Do this in a single day, across all systems simultaneously. Change passwords, revoke SSH keys, remove VPN certificates, deauthorize devices in MDM. Document each action with a timestamp.

Transferring Documentation When Switching IT Contractors: Standards and Formats

Infrastructure documentation handover is the aspect most often neglected — and then paid for dearly. A new contractor working without documentation will spend weeks reverse-engineering an unfamiliar infrastructure through trial and error. Proper documentation cuts the new partner's onboarding time from two months to two weeks.

The Minimum Required Documentation Package

• Network diagram: topology, IP addressing, VLANs, DMZ.
• Full hardware and software inventory with versions, serial numbers, and end-of-support dates.
• Runbook: step-by-step instructions for routine tasks and disaster recovery.
• Backup policies: schedule, storage location, restore verification procedure.
• Description of known issues and outstanding technical tasks.

How to Verify the Quality of the Transferred Documentation

Validate the documentation independently, not with the contractor: ask a new IT administrator whether they could rebuild the infrastructure from scratch using these materials. If the answer is no — require revisions before the engagement ends. This is your legal right if the contract includes an obligation to maintain documentation.

Live Knowledge Transfer (Handover Sessions)

Organize 2–4 working sessions where administrators from the old and new teams work together. The new specialist needs to see the infrastructure firsthand, ask questions, and get answers. Record these sessions — the recordings become a valuable operational asset during the transition period.

What to Do If the Contractor Refuses to Hand Over Access or Holds Your Infrastructure Hostage

Situations where an IT company has vanished with your money, sabotages the handover, or withholds server access as leverage — are unfortunately real. Here is the action plan:

Pre-Litigation Resolution

1. Send a formal claim demanding that all access credentials and data be transferred within 10 business days.
2. Document all communication attempts: emails, messengers, phone calls.
3. Engage a lawyer to assess the legal options.

Technical Measures During a Conflict

If you still have even partial access to systems — immediately create backups of all data and configurations. Document the current state of the infrastructure with the help of an independent IT auditor: this will strengthen your position and help assess the extent of any damage. In parallel, determine which of your data is physically stored on hardware that is your property — you have the right to access it.

Legal and Administrative Tools

Through court proceedings, you can obtain interim measures — prohibiting the contractor from blocking, deleting, or transferring your data to third parties. If the contractor has violated GDPR requirements regarding personal data, regulatory sanctions may be applied — this is an additional point of leverage even before going to court.

How to Dismiss an Infrastructure Outsourcing Team Without Downtime: A Transition Plan

A well-executed IT contractor switch is a managed project, not a scramble. Below is a transition period structure that minimizes risk and ensures business continuity.

60 Days Before the Transition

• Conduct a full infrastructure audit with an independent specialist.
• Select a new contractor or begin hiring an in-house IT specialist.
• Compile a registry of all assets, access credentials, and systems to be transferred.

30 Days Before the Transition

• Begin parallel onboarding of the new contractor.
• Organize handover sessions between the teams.
• Start creating your own administrative accounts in all critical systems.

Day X and After

• Sign the asset, access, and documentation handover act.
• Revoke all old contractor access simultaneously across all systems.
• Conduct a security audit: change passwords, revoke certificates and keys.
• Verify that monitoring, alerting, and backup systems are operational under the new team.

Questions and Answers

Who owns the data stored on the contractor's servers?

Data always belongs to the client unless the contract explicitly states otherwise. However, this must be clearly defined in the agreement — including data in cloud environments that the contractor rented in their own name. If data is stored in the contractor's cloud account, the handover must either involve transferring account ownership or migrating the data to the client's own account.

What if the contractor holds client personal data and refuses to return it?

This is a potential GDPR violation for companies operating with EU citizens' data. Send a formal request for data return or destruction with proof of delivery. If the contractor ignores it — contact the data protection supervisory authority. In parallel, notify your clients if there is a risk of a data breach.

How long does switching an infrastructure IT contractor take?

With a cooperative transition and proper documentation in place: 4 to 8 weeks. Without documentation, or if the relationship is adversarial: 3 to 6 months. The larger and more complex the infrastructure, the more important it is to start preparing well in advance.

Conclusion: How to Part Ways Professionally and Without Losses

Terminating an IT infrastructure support contract is not a catastrophe — it is a business process that can and should be managed. Key principles for a successful transition:

• Plan the switch in advance — don't wait for a crisis or conflict.
• Establish data ownership and access transfer procedures at the time of signing the contract.
• Use the IT contractor transition checklist and don't miss a single category of assets.
• Infrastructure documentation handover is not a formality — it is business insurance.
• If the contractor is withholding access — don't delay legal action.

The KSK IT team specializes in local and cloud infrastructure support, as well as guiding clients through IT contractor transitions. We conduct technical audits of your infrastructure, build a secure transition plan, and ensure the continuity of your systems throughout the entire handover process.

Want to switch IT contractors without risk? Contact us — we will conduct a free express audit and put together a tailored transition plan.

FAQ: Frequently Asked Questions

1. What should you do if the IT company has disappeared with your money and never handed over access?

Document the failure to fulfill obligations in writing and send a formal claim to the company's registered address. If the company is being liquidated — contact the insolvency administrator with a demand to transfer assets. In parallel, work to recover access through hardware vendors and cloud providers: many of them can help verify ownership of resources.

2. How do you switch IT contractors without interrupting infrastructure operations?

Organize a parallel period during which both contractors work with the infrastructure simultaneously. The new team studies systems and configurations while the old one remains responsible for availability. The handover of responsibility only happens once the new team has confirmed they are ready to take over.

3. What should the handover act include when switching IT contractors?

The act should include: a list of transferred accounts with transfer dates, a list of configuration files and documentation, confirmation of backup transfer, and confirmation that the old contractor's access has been revoked. It must be signed by both parties with a date and company seal.

4. Does the NDA with the IT contractor remain in force after the contract is terminated?

Generally yes — the NDA continues to apply for the duration specified in the agreement (typically 2–5 years). The former contractor is not permitted to disclose information about your infrastructure, the technologies used, or your business processes. Make sure the NDA is signed and kept on file.

5. How do you verify that the former contractor has no residual hidden access?

Conduct a full security audit: check active sessions in cloud consoles, the list of authorized SSH keys on all servers, active VPN users, and accounts in Active Directory and MDM. In cloud environments, use built-in access analysis tools (AWS IAM Access Analyzer, Azure AD Access Reviews). After the review, change all root passwords.