Changing your IT service provider in Geneva is prepared according to your contract and your IT environment: in Switzerland, most contracts are terminated at their annual expiry, with one to three months' notice. For an SME with 10 to 20 positions, the transition takes around a month between the first exchange and complete handling. Advance preparation limits service interruptions and loss of access.
You are right to be concerned about the contract, the data and the continuity of work. Accounts, email boxes and files often remain in their location: it is their administration that changes hands. Their recovery depends in particular on the terms of termination, the reversibility clause and the access held by the outgoing service provider.
This guide helps you identify the contractual elements to review, organize the migration and retrieve the necessary information and data. You will also see what factors influence the budget, how to plan the recovery without haste and what criteria to prioritize when choosing a local IT partner in Geneva, Meyrin, Vernier, Eaux-Vives, Cologny, Grand-Lancy or Petit-Lancy.
Key Points
- Find the termination deadline and the notice period in your contract: in Switzerland, most contracts are terminated at the annual deadline, with one to three months' notice.
- Prepare the restitution of access and documentation so that the recovery can take place without losing control of your IT environment.
- Before any modernization, take inventory of equipment, software, network and backups, then plan changes according to your priorities.
- For data hosted by the outgoing service provider, examine the reversibility clause and define the transfer terms with the new partner.
- Compare Geneva service providers according to their organization, security, documentation and ability to support your teams remotely or on site.
Table of contents
What is the minimum contract size and duration?
The size of your SME does not alone determine the time required to restore access and documentation. The schedule depends mainly on the number of services administered, their organization and the availability of information. A company that uses a single messaging environment will not have the same transfer to organize as a structure with several sites, servers and business tools. Before the end of the mandate, clarify the steps and those responsible.
The restitution must allow the company to control its environment on a daily basis. Beyond the identifiers, ask for the information necessary to understand their use: which account administers which service, what rights it has and which address allows access to be regained. For each essential account, record its owner, function and authorization level. This documentation avoids depending on an isolated password, impossible to link to a specific service.
Control administrator access separately. Verify that the company has a primary account under its own control and an associated means of recovery. Then have the connections tested by the person who will take over administration. If an account is shared, plan for its replacement and record it in the access log. Distinguish the personal accounts of outgoing technicians from those that belong to the company.
The documentation provided may include service parameters, common procedures and contact information for suppliers related to IT tools. Request editable files when they will make updates easier. For example, an account creation procedure must remain understandable without an oral explanation from the person who wrote it. Also note any missing or obsolete elements so that the new manager can complete them.
For backups, don't just rely on the name of the solution. Specify the systems covered, the expected frequency, the storage location and the restoration procedure. A test on a file chosen by the company verifies that access works and that the content opens correctly. Record the result, any errors, and the person authorized to initiate a restore. This transforms the provision of information into practical verification.
Organize the transmission with a report or a shared register, then have each category validated by the person responsible internally. It can track access provided, documents received, tests carried out and points to be addressed. Transmit secrets over a secure channel, separate from general documentation. At closing, remove permissions that are no longer needed and keep a record of the changes. This method helps a small team such as a more structured SME to take over management without losing track of responsibilities.
Verification of the contract and termination terms
Before setting the resumption date, identify in the contract the expiry date, the notice period, the form of notification and the renewal rules. In Switzerland, most IT service provider contracts are terminated at their annual expiration, with one to three months' notice. You can prepare for the recovery during this period; the transfer generally waits until the end of the contract, unless an early exit is agreed.
Also identify the clauses which specify the end of the services: support end date, access to monitoring tools, delivery of documents and processing of current requests. A clearly dated termination helps coordinate these elements with the start of the new partner. Keep the contract, its annexes and the notification sent, then record the exchanges which modify the schedule.
To define the scope, establish an inventory linking each workstation, server, account and software to its professional use. Add the associated contracts, their holder and their next expiry date. This overview highlights the elements administered by the outgoing supplier, those that belong directly to the company and those to be maintained during the transition. It also makes it possible to identify services used without a clearly identified contract.
- Associate each extension with its user and location.
- Identify the servers and applications that teams depend on.
- Note the cloud accounts and services administered by the provider.
- Classify each contract according to whether it is to be retained, transferred or terminated.
For licenses, check the holder, the renewal method and the account to which each subscription is attached. A license held by the company is not managed like a subscription taken out in the name of the service provider. Make a list of essential tools, including messaging and business software, then plan their continuity before any contract closure. This verification avoids discovering a deadline when an employee needs to access a tool.
Finally, reread the managed IT services scope: user assistance, maintenance, monitoring or account management. Distinguish between included tasks and separately billed interventions and responsibilities kept in-house. For example, a company can entrust the maintenance of servers while keeping the creation of user accounts to its administrative team. Those approving requests must understand this breakdown.
To prepare this review, gather the contract, annexes and inventory of services; A discussion on your IT transition can help you structure the points to be covered.
Migration and modernization of network and servers
A successful migration begins with a choice: take over the existing infrastructure or evolve it. Have hardware and software audited before modifying the network or servers. The analysis must link each piece of equipment to its use, its condition and the applications it hosts. This will allow you to keep what still meets needs and identify elements that create dependency or a risk of interruption.
Do not automatically replace all equipment by changing partners. An SME can keep its switches, stations and software, then plan renewals according to obsolescence and the validated budget. This approach distinguishes the recovery of infrastructure from a broader modernization project. It also clarifies responsibilities: the new manager first takes over operations, then implements the approved changes.
Before any network modification, define the services that must remain available during the intervention. A Wi-Fi outage does not have the same effect as a loss of connection to business applications. Specify the areas affected, the users affected and the operations to be tested after each change. To intervene in an active SME, choose a window that limits disruptions and inform the teams of planned interruptions.
A step-by-step procedure makes the intervention easier to control:
- Collect the initial state of the network and servers before any changes.
- Define the expected change and the services that depend on it.
- Test the new configuration with a pilot user group or service.
- Validate the result before extending the change to the rest of the company.
To troubleshoot the network, work by zone rather than changing multiple settings at once. If a team loses access to an application, compare its connection to that of a working workstation, then check the affected network path. Record the configuration before the intervention and the changes made. This method helps to find the cause of the problem and return to the previous state if the expected result is not obtained.
A cloud or network project can also be broken down by service. A company can, for example, move an independent application before touching the tools used by the entire team. Define the validation criteria for each step: functional access, sufficient performance for use and compatibility with the software in place. If Microsoft 365 or messaging is part of the project, schedule sending, receiving and access tests from the affected workstations.
Finally, distinguish one-off operations from regular maintenance. After recovery, define who tracks equipment status, handles alerts, and organizes updates. A maintenance schedule helps anticipate interventions instead of waiting for a breakdown. After each development, update the network diagram and the technical architecture file. These documents give the next responder a reliable view of the infrastructure.
Recovery of data hosted by the outgoing service provider
The reversibility clause specifies how to transmit data, accounts and information to the new partner. To organize the overlap, agree on a transfer schedule, the responsibilities of each stakeholder and the tests to be carried out before the end of the contract.
Transferring Emails and Files
Start by listing the email boxes, shared folders and files hosted by the current provider. Accounts and files often remain in their location: only their administration then changes hands. If a migration is necessary, define the elements to be transferred, the method and the intervention window. Data hosted without direct access for the company is delivered, at the end of the contract, in the native format of the solution used.
To limit problems, test access to email boxes and files after each step. Verify that a collaborator can open a recent message, view a shared folder and find an essential document. Note the results and anomalies to correct. Continuity also depends on user accounts, access rights and licenses associated with messaging or storage tools.
Data protection during migration
Before any transfer, determine what data is involved and where it is hosted. Request a transmission method that protects files and access information from unauthorized viewing. Limit access to those involved in the migration, then revoke those who are no longer needed. For cloud hosting, document the location of the data and how it will be retained after release.
Cybersecurity must accompany every step, not just the implementation of the new environment. Before moving data, check administrator accounts, temporary rights and available backups. A restoration test on a representative file helps identify an access or format problem. Record the files transferred, the accounts involved and the checks carried out, so that the organization has an actionable trace.
Organization of the overlap period
Plan the overlap with specific dates and responsibilities. The outgoing service provider can prepare the delivery of data during the notice period; the transfer generally waits until the end of the contract, unless an early exit is agreed. Plan a period during which the old environment remains accessible and the new partner carries out its checks. Also designate an internal contact to centralize decisions and report incidents.
Before closing, verify that users can log in, send and receive emails, and access necessary files. Confirm that useful accounts and licenses remain active during the transition. If an anomaly appears, record the service affected, the time and the expected action. A checklist validated by stakeholders clarifies the handover and avoids confusing data recovery with closing old access.
IT service providers in Geneva and neighboring towns
To choose in Geneva, compare the organization, skills, support times, documentation and security approach. The cost depends on the scope, number of users, hardware, licenses and planned interventions. It is defined according to the project, after a request for an offer.
Geographic proximity matters when your systems require intervention on your premises. In Geneva, Meyrin, Vernier, Eaux-Vives, Cologny, Grand-Lancy and Petit-Lancy, Flux Group operates remotely and on site. Specify the sites concerned, the activity times and the equipment present on each. You will thus be able to distinguish needs handled remotely from those that require an on-site presence.
Then compare the organization of IT support. The contract must specify how users report an outage, how requests are prioritized and what deadlines apply depending on their severity. An email problem does not necessarily block the entire company; a file server outage can interrupt multiple teams. Check that the planned organization takes these different situations into account.
Documentation is another concrete criterion. A partner should be able to describe your network, servers, accounts and software used. To understand its method, look at an example deliverable: network diagram, equipment inventory or incident management procedure. Actionable documentation makes it easier to recover systems and plan for maintenance, rather than making you dependent on the knowledge of a single person.
- Compare the exact scope of support and the exclusions of the contract.
- Check how incidents are recorded, tracked and communicated to teams.
- Assess the skills needed to manage your servers, network, and cloud tools.
- Review access protection, backups and where data is hosted.
For data hosted in Switzerland, ask where it resides and how its protection fits into your organization. Localization contributes to digital sovereignty, but does not replace access control, backup management, or system monitoring. Compare these practices to your operational needs and data protection commitments.
Finally, evaluate the quality of the working relationship. Identify your contact, the monitoring method and the frequency of discussions on incidents or developments. An SME in Grand-Lancy can, for example, retain an internal referent while entrusting the maintenance of certain systems to a partner. Document this sharing to avoid lost requests and unclear responsibilities.
For an SME, the cost varies depending on the IT perimeter, the number of users, hardware, licenses and planned interventions. Request an offer tailored to the project.
Flux Group SARL: Flux ICT
Flux Group SARL supports SMEs who wish to resume their IT with a clear framework and controlled continuity. Flux ICT and IT support meet daily systems management needs. Cybersecurity helps protect access and reduce risk during the transition. If the change also concerns business calls, VoIP telephony and telecommunications solutions can be part of the thinking.
You can request Flux Group when you are preparing for recovery, want to clarify your priorities or need an IT support partner. Present your environment, contractual deadlines and sensitive points, such as accounts, messaging or backups. Contact Flux Group SARL to discuss your IT transition.
Transform the transition into a new stage for your SME
Changing your IT provider in Geneva can also be an opportunity to better align your systems with your business priorities. Define responsibilities after takeover, decisions that remain internal and improvements to plan. A realistic roadmap avoids launching too many changes at once.
To move forward, appoint an internal referent and agree with your partner on an initial operational assessment. Rely on concrete elements: recurring requests from teams, essential tools and points that slow down work. You will be able to distinguish urgent actions from developments that can wait, then gradually adjust your IT organization.
A well-managed transition is not limited to technical transfer. It gives your teams a clear framework to work and develop their tools methodically.
Prepare for this new stage calmly and stay focused on your activities.
Frequently asked questions about changing IT service provider
How quickly do you respond in the event of a breakdown?
The average response time for Flux Group technical support is less than 9.3 minutes. To effectively address an outage, describe the service affected, the users affected, and when the problem started. An error limited to one position cannot be diagnosed as an outage affecting the entire company. These elements help the team to qualify the incident and direct assistance.
Do you work on site or is everything done remotely?
Flux Group operates remotely and on site. Remote troubleshooting is suitable for account or software issues, while faulty network equipment may require service on your premises. For a company in Geneva, Meyrin, Vernier, Eaux-Vives, Cologny, Grand-Lancy or Petit-Lancy, specify the location concerned and the equipment affected when you report the problem. This information helps guide treatment.
How to change IT service provider in Geneva step by step?
Start by appointing an internal referent, then gather contracts, information on your systems and the priorities of your activity. Prepare the transition schedule with the new partner taking into account the contractual deadline. Organize the resumption of access, test essential services and inform the teams of the new support channel. Once the transition has stabilized, plan a review with the people involved.
How long should you expect to transfer your IT to a new service provider?
The time frame depends on the number of systems involved, their documentation and the migrations required. A recovery with clearly identified accounts and accessible services is simpler to plan than an environment whose dependencies remain unknown. Integrate email, file and backup validations into the calendar. Depending on the conditions of the current contract, the notice period can be used to prepare for the steps.
How to recover access, passwords and licenses from the old service provider?
Request a structured transmission of administrator accounts, necessary identifiers and licenses linked to the company. Avoid sending passwords in a regular email: use a secure channel and limit recipients. Then check that the access works with the new partner. Replace shared identifiers and clarify who owns subscriptions, especially for business software and email.
How to transfer data, backups, domains and messaging without interruption?
Organize the transfer by service and plan for testing before deactivating the current environment. For messaging, check sending and receiving; for files, test document opening and access rights. Also confirm domain name management and email settings. For backups, check their accessibility and test restoring a useful file.
What clauses should be checked in the contract and the termination conditions of the former service provider?
Identify the expiry date, notice period, notification method and renewal rules. Also examine the reversibility clause, which specifies the terms of handing over data and assets to the new partner. Distinguish between included services and separate interventions, then check the processing of licenses and access at the end of the contract. Keep a copy of the contract and the notice of termination.
Which Swiss data protection obligations apply when changing IT service providers?
In Switzerland, FADP regulates the processing of personal data. During the transition, identify what data is affected, who is accessing it, and where it is hosted. Limit their transmission to the stakeholders concerned, then withdraw the rights that have become unnecessary. If data is hosted abroad or used in the European Union, also examine the processing context and the commitments applicable to your organization.
Article by
Delyan TZONEV
Passionate entrepreneur and manager, I am CEO of Flux Group and Hype Swiss. I support companies in their digital transformation thanks to innovative solutions in IT, telecommunications and software development. My goal is to design high-performance technologies that simplify the daily lives of businesses and support their growth.
Disclaimer
The articles published on the Flux Group blog aim to share our expertise, our field experience and best practices in IT, cybersecurity, cloud, telecommunications and digital transformation of SMEs.
We strive to provide reliable, up-to-date and relevant information at the time of publication. However, technologies, regulations and service offerings are evolving rapidly. The published content is therefore provided for informational purposes and does not constitute personalized, legal, tax, financial or technical advice.
Each company has specific needs, we recommend that you seek professional support before making a decision or implementing a solution presented in our articles.
The opinions, recommendations and comparisons published on this blog reflect our analysis and experience. When we talk about partners or publishers such as Microsoft, Swisscom or Infomaniak, our objective is to present the solutions objectively, highlighting their advantages as well as their limitations according to the different contexts of use.
Flux Group cannot be held responsible for any direct or indirect consequences resulting from the use of the information published on this blog. Links to external sites are provided to complete the information; their content is the responsibility of their respective publishers.
© Flux Group – All rights reserved.
Our services
If you wish to be supported in the choice, deployment or optimization of your IT solutions, the Flux Group experts are at your disposal. We support SMEs in Geneva, Switzerland and Pays de Gex in their Microsoft 365, cybersecurity, cloud, telecommunications, managed IT services and IT infrastructure projects.
Questions fréquentes
How quickly do you respond in the event of a breakdown?
The average response time for Flux Group technical support is less than 9.3 minutes. To effectively address an outage, describe the service affected, the users affected, and when the problem started. An error limited to one position cannot be diagnosed as an outage affecting the entire company. These elements help the team to qualify the incident and direct assistance.
Do you work on site or is everything done remotely?
Flux Group operates remotely and on site. Remote troubleshooting is suitable for account or software issues, while faulty network equipment may require service on your premises. For a company in Geneva, Meyrin, Vernier, Eaux-Vives, Cologny, Grand-Lancy or Petit-Lancy, specify the location concerned and the equipment affected when you report the problem. This information helps guide treatment.
How to change IT service provider in Geneva step by step?
Start by appointing an internal referent, then gather contracts, information on your systems and the priorities of your activity. Prepare the transition schedule with the new partner taking into account the contractual deadline. Organize the resumption of access, test essential services and inform the teams of the new support channel. Once the transition has stabilized, plan a review with the people involved.
How long should you expect to transfer your IT to a new service provider?
The time frame depends on the number of systems involved, their documentation and the migrations required. A recovery with clearly identified accounts and accessible services is simpler to plan than an environment whose dependencies remain unknown. Integrate email, file and backup validations into the calendar. Depending on the conditions of the current contract, the notice period can be used to prepare for the steps.
How to recover access, passwords and licenses from the old service provider?
Request a structured transmission of administrator accounts, necessary identifiers and licenses linked to the company. Avoid sending passwords in a regular email: use a secure channel and limit recipients. Then check that the access works with the new partner. Replace shared identifiers and clarify who owns subscriptions, especially for business software and email.
How to transfer data, backups, domains and messaging without interruption?
Organize the transfer by service and plan for testing before deactivating the current environment. For messaging, check sending and receiving; for files, test document opening and access rights. Also confirm domain name management and email settings. For backups, check their accessibility and test restoring a useful file.
What clauses should be checked in the contract and the termination conditions of the former service provider?
Identify the expiry date, notice period, notification method and renewal rules. Also examine the reversibility clause, which specifies the terms of handing over data and assets to the new partner. Distinguish between included services and separate interventions, then check the processing of licenses and access at the end of the contract. Keep a copy of the contract and the notice of termination.
Which Swiss data protection obligations apply when changing IT service providers?
In Switzerland, FADP regulates the processing of personal data. During the transition, identify what data is affected, who is accessing it, and where it is hosted. Limit their transmission to the stakeholders concerned, then withdraw the rights that have become unnecessary. If data is hosted abroad or used in the European Union, also examine the processing context and the commitments applicable to your organization.
Besoin d'un accompagnement IT à Genève ?
Parlons de votre infrastructure, de votre sécurité ou de votre téléphonie. Sans engagement.
Contacter Flux Group