The short answer
Switching is mostly about ownership: first make sure your organization, not a provider, holds the administrator accounts, domain, cloud tenants, licenses and backups. Then review the contract, overlap while the new provider documents everything, cut over, rotate every credential the old provider knew and remove its tools and access. Most users notice only a new support number.
Step 1: read the contract before you give notice
- Notice period
- Early termination fees
- Documentation handover
- Credentials returned
- License transfers
- Transition help
- Tools licensed in their name
Before signing with any managed provider, it is sensible to ask who owns your data if the contract is dissolved and how you get it back. If you did not, ask now. Stay professional: most providers handle exits properly when asked clearly in writing.
Step 2: find everything the old provider controls
Switches go wrong here. List who holds the keys:
| Area | What to confirm |
|---|---|
| Domain and DNS | Registrar account in your name and contacts; who hosts and edits DNS |
| Microsoft 365 or Google Workspace | Global admin accounts you own; partner or delegated admin relationships |
| Licenses | Subscriptions billed through the provider; how they transfer |
| Backups | Where stored, in whose account, how to restore |
| Security tools | Endpoint and email security consoles; whose tenant |
More areas to check
| Area | What to confirm |
|---|---|
| Firewall and network | Admin credentials, configuration backups, support contracts |
| Servers and cloud | Hypervisor, Azure or AWS accounts, root and admin credentials |
| Remote management | Agents on your devices; how they are removed |
| Documentation | Network diagrams, password vault, vendor contacts, procedures |
Anything in the provider's name is a transfer task, not a formality. If the old backup subscription ends before the new one starts, you are unprotected.
Step 3: overlap, discover and document
While the old provider still supports users, the new one installs tools, documents and fixes urgent risks:
Inventory
Devices, users, applications, vendors and licenses.
Documentation
Current network and systems.
Urgent security issues
Missing patches, unsupported systems, accounts without multi-factor authentication.
Cut-over plan
Dates, owners and a rollback option.
Rather talk it through? We can review what your current provider controls and outline a handover plan before you give notice. Talk to a Promatics specialist
Step 4: cut over and close the door
- Support routingNew help desk number, email and portal for staff.
- MonitoringMonitoring and security alerts moved and confirmed.
- Rotate credentialsAdmin passwords, service accounts, Wi-Fi, firewall, API keys.
- Remove accessOld accounts, delegated administrator relationships, remote access.
- Remove agentsOnce the new ones are confirmed working.
- Test restoreFrom the new backup system.
Privacy and data you must not forget
The old provider holds staff and client personal information in tickets, logs, backups and email copies. The US has no single federal privacy law, but depending on your sector and state, HIPAA (through business associate agreements), the GLBA Safeguards Rule and state comprehensive privacy laws expect you to oversee service providers that handle personal information, usually through contracts. Start with the FTC's data security guidance; your legal adviser can tell you what applies to you.
Transition checklist
Before notice
- Contract notice period, fees and exit obligations reviewed
- Domain registrar, DNS and cloud tenants confirmed in our name
- Licenses and backups held by the provider identified
Overlap
- New provider's discovery and documentation complete
- Urgent security risks identified and scheduled
- Cut-over date and rollback plan agreed
Cut-over
- Staff told how to get support, and from when
- Monitoring and security alerts confirmed with the new provider
- All administrator and shared credentials rotated
- Old provider accounts, delegated access and agents removed
- Test restore completed from the new backup system
Close-out
- Written confirmation that our data has been returned or destroyed
- Final invoices checked for ended services
Common worries
Most providers cooperate, cut-over can avoid your core hours, and sometimes staying is the right call.
The three worries answered
| Worry | Honest answer |
|---|---|
| "They will not cooperate." | Most do, given a clear written request. If not, platform recovery routes usually work while you control your domain and billing accounts: that is why Step 2 comes first. |
| "We cannot afford downtime." | Cut-over can happen outside core hours, and the overlap means support never stops. |
| "It is easier to stay." | Sometimes. Raise one fixable issue with your provider first. Switch when trust, responsiveness or security practice has broken down. |
When to bring in help
A very small office with a few cloud accounts can often switch with a checklist and an afternoon. Servers, several locations, security tools in the old provider's tenant or regulated data mean bringing the new provider in early: the detective work and credential rotation take experience.
How Promatics handles a switch
Onboarding is a project: we assess your devices, users, applications, vendors and licenses, list everything the outgoing provider controls and agree a cut-over plan with you. Managed-service clients get 24/7 monitoring and support from cut-over. Admin accounts, domains and licenses stay in your name, so you are never locked in, even by us. See managed IT services.
Sources and further reading
Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.
- Secure Our World, Cybersecurity and Infrastructure Security Agency (CISA)
- Data security, Federal Trade Commission
This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.