# Changing IT Providers: A Practical Guide | SmartCloud > A practical guide for changing managed IT providers, covering ownership and access, documentation, continuity, verification, and what you can confirm independently. Source: https://www.smartcloudusa.com/changing-it-providers Changing IT providers # Make the next IT relationship fit where the business is going. A provider change can be planned calmly and respectfully. Start with clear ownership, access, documentation, responsibilities, and a transition sequence everyone can understand. [Request a transition review](https://www.smartcloudusa.com/contact-us?interest=provider_transition) ![Two managed environments connected by a lit transition path carrying identity, documentation, data, and security controls from one to the other](https://www.smartcloudusa.com/images/smartcloud-changing-providers-hero-v1.webp) Where to begin ## Start with what prompted the review. You may be responding to growth, an acquisition, a key-person change, new client or insurance requirements, a shift in service needs, or a relationship that no longer fits the operating model. That context helps define what the next provider needs to own, what should remain internal, and what a successful transition should make easier. What to plan ## Protect continuity while responsibility moves. The goal is not to relitigate the old relationship. It is to give the business, the outgoing provider, and the incoming provider a clear path through the transition. ### Ownership and access Establish who controls what before anything moves. - Domain registrar account and DNS control - Microsoft 365 or Google Workspace tenant global administrator - Cloud platform root or owner accounts - Security tool consoles - Backup platform administration - Line-of-business application administration - Vendor portal logins and account numbers - Where a service was purchased through the provider rather than directly, what transfers and what has to be repurchased ### Documentation Collect what someone would need to operate the environment without asking anyone. - Asset and device inventory - Network diagram and addressing - Firewall and switch configuration - Identity and group structure - Backup schedules, retention, and the last successful restore test - Recurring maintenance procedures - Known issues and workarounds - Support history - Contracts, renewal dates, and notice periods ### Continuity Decide how the work keeps moving while responsibility changes hands. - Where employees go for help on day one, and who tells them - Whether service periods overlap, and for how long - Which changes are frozen during the handover - What happens to in-flight projects - Who holds escalation authority during the transition window ### Verification Confirm the new arrangement works by using it, not by being told it does. - Administrative access confirmed by signing in, not by assurance - Monitoring and alerting arriving at the new provider - A backup restore tested after cutover rather than assumed - Escalation paths exercised once - Remaining dependencies on the previous provider identified and closed Without waiting on anyone ## What you can confirm independently. Not every transition moves at the same pace, and some information takes longer to arrive than planned. Several things can be confirmed by the business itself without waiting. Domain registrar ownership can be verified directly with the registrar. Microsoft 365 and Google Workspace tenant administration can be recovered through the vendor's documented process by a verified owner. Licensing purchased directly is visible in the vendor portal. Contract terms and notice periods are in the agreements already held. Establishing these early removes most of the pressure from the rest of the sequence. How long it takes ## What actually drives the timeline. A transition is paced by a handful of things more than anything else: how many systems and vendors are involved, how much of the environment is already documented, whether the current and incoming service periods overlap, the notice period in the contract, and how quickly administrative access is confirmed. A change where ownership is already clear and documentation is current moves at a very different pace from one where both have to be established first. That is why the items above are worth starting before a decision is final. Take this with you ## Provider transition checklist. Free to use, copy, or pass along, whoever you end up working with. Nothing here requires contacting us. ### Before committing to a change - Confirm domain registrar ownership directly with the registrar - Confirm who holds tenant global administrator access - Locate contracts, renewal dates, and notice periods - List the systems, vendors, and applications actually in use ### While notice runs - Request the documentation set in writing - Identify what was purchased through the provider and what transfers - Agree the overlap period and which changes are frozen - Name who holds escalation authority during the window ### At cutover - Sign in to each administrative account rather than accepting confirmation - Point monitoring and alerting at the incoming provider - Confirm backup jobs are running under the new arrangement - Tell employees where to go for help before day one ### After cutover - Test a restore rather than assuming one - Exercise the escalation path once - Close remaining dependencies on the previous provider - Reconcile licensing and billing A provider change is also the natural moment to establish who owns security, review who holds administrative access, and confirm that backup operations are running as expected. [Explore cybersecurity](https://www.smartcloudusa.com/cybersecurity) The other direction ## If you ever move on from us. We would rather keep a client because the relationship works. If it stops working, or the business changes in a way that calls for something different, the exit should be as clean as the start. ### Ownership sits with the business from day one. Domains, tenants, administrator accounts, and subscriptions are registered to the client wherever the vendor permits it. This is how we set things up initially, not something arranged at the end. ### Documentation stays current as part of normal operations. There is nothing to reconstruct, because it was never allowed to fall behind. ### Everything needed to operate the environment is handed over on request, without conditions. Inventories, diagrams, procedures, credentials, licensing records, and support history. ### We coordinate directly with the incoming provider. We stay available through the handover so continuity is protected while responsibility moves. Start a conversation ## Bring us the priority, constraint, or idea. [Request a transition review](https://www.smartcloudusa.com/contact-us?interest=provider_transition)