Skip to main content
Operations · Managed IT · Transition runbook

How to Switch Dental IT Providers Without Downtime or Disruption: Handover Checklist, Switch Plan and Scorecard

Your IT company has stopped calling back, the same printer and sensor problems keep coming back, and when you asked for the admin passwords you got a vague answer. Or the company told you to start looking elsewhere after you questioned a recommendation. Either way, the worry is the same: if you leave, what stops working?

The most dangerous moment in a provider change is the gap between who still has administrative access and who now owns recovery, monitoring and support. No honest provider can promise that nothing will ever blink. What you can do is take the risk out in the right order. This guide gives you three things to work from: a handover checklist in the order to do it, a week-by-week switch plan with an owner for every step, and a scorecard for judging your current provider and the next one on evidence rather than on promises.

In this guide
  1. This guide assumes you have already decided to change providers
  2. What should you secure before you give notice?
  3. How do you take back Microsoft 365 from your old IT company?
  4. Who owns your dental practice's domain, and how do you move it?
  5. Before notice: read the exit terms and build the dependency list
  6. The safe transition sequence
  7. Phase 1: inventory the current environment before anyone removes anything
  8. Phase 2: confirm who owns every critical account
  9. Phase 3: create a recovery gate before changing tools or credentials
  10. Phase 4: collect the documentation before the relationship becomes tense
  11. Phase 5: plan the overlap between old and new providers
  12. Phase 6: avoid agent conflicts during the tool handoff
  13. Phase 7: schedule material changes around the patient day
  14. Phase 8: introduce the new support process to the dental team
  15. Phase 9: remove former-provider access only after the new environment is validated
  16. Phase 10: run a 30-day acceptance period
  17. Five mistakes that create avoidable transition risk
  18. What if the outgoing provider is uncooperative?
  19. What if your IT company is the one ending the relationship?
  20. Vendor introductions should be part of the handoff
  21. How do you judge the old provider and the new one on evidence?
  22. What to ask your new IT provider before you sign
  23. What happens after the first 30 days?
  24. Where Legend fits
  25. Frequently asked questions
  26. The bottom line

This guide assumes you have already decided to change providers

If the practice is still asking "Should we leave?", start with the signs your dental office needs better IT support. If it is asking "Which company should we hire?", use how to choose a dental IT provider, which carries the 11-criterion scorecard.

This article begins after the decision is substantially made. Its job is the handoff.

If you are still on the fence, put the recurring problems in writing to the provider and give them a fair chance to fix them. If you have raised it, kept a record, and nothing changed, the rest of this page is for you. If you are ready to look elsewhere, our list of the best dental IT companies is a starting shortlist.

There is a second situation this guide covers, and it is more common than people expect: the IT company ends the relationship. Some providers give notice after a practice pushes back on their recommendations. If that is your position, the order of work is the same, but the clock is shorter. Skip to What if your IT company is the one ending the relationship? and then come back to the checklist.

What should you secure before you give notice?

Before notice, secure everything the practice owns but the IT company controls: an emergency admin account you hold, Microsoft 365 global admin, the domain registrar and DNS logins, firewall and Wi-Fi credentials, backup console access with a fresh restore proof, software vendor contacts, ISP and phone accounts, documentation, and the contract and BAA exit terms.

Do these quietly and in this order. Most of them are things you can do yourself, from accounts already in the practice's name, without asking the outgoing company for anything. That matters, because the moment notice goes out is the moment cooperation can slow down.

The handover checklist, in order

#Secure thisWhat "secured" looks likeHow to do it without the old providerPrimary source
1An emergency ("break-glass") admin account the practice controlsTwo cloud-only admin accounts on your *.onmicrosoft.com address, not tied to any one person, with credentials stored where the owner can reach themThe owner or office manager signs in with any existing Global Administrator role and creates them; if nobody at the practice has one, ask for it now, before noticeMicrosoft Learn, emergency access accounts
2Microsoft 365 global adminAt least one person at the practice holds Global Administrator; you know which partner companies have accessAdmin center > Settings > Partner relationships shows every partner and its rolesMicrosoft Learn, partner relationships
3Domain registrar accountThe domain is registered to the practice as the registrant, and the practice can sign in to the registrarLook up the registrar, then use the registrar's account recovery as the registrant if you cannot sign inICANN registrant FAQ
4DNS hostingYou know where DNS is hosted (often not the registrar) and have a login or an export of every recordAsk the DNS host for an export, or record the current records before anything changesGeneral practice
5Firewall, switches and Wi-FiAdmin credentials, the firewall model, and a configuration backup saved somewhere the practice holdsAsk for a configuration export in writing; note the make and model of each device so a reset is possible if it comes to thatCISA AA22-131A (MSP accounts and responsibilities)
6Backup console and restore proofThe practice can sign in to the backup console, and a recent test restore of the practice-management database and images is on recordRequest a supervised restore test now, while the relationship is still working45 CFR 164.308(a)(7); CISA #StopRansomware Guide
7Practice-management and imaging vendorsAccount numbers, support contacts, licence keys and who is the named contact for Dentrix, Eaglesoft, Open Dental, DEXIS or whatever you runCall each vendor as the account holder and confirm the practice is the customer of recordYour vendor agreements
8Internet and phone accountsISP account number and portal login; phone or VoIP portal access, and who holds the number-porting PINCall the ISP and phone provider as the account holderYour carrier agreements
9Documentation and network mapA copy of the network diagram, device list, IP plan and known issues, held by the practiceAsk for it as part of normal business continuity; compare it with what you can see on siteGeneral practice
10Remote-access and management toolsA list of every agent and remote tool on every computer, so each can be removed later on purposeThe incoming provider can scan for installed agents during the overlapCISA AA22-131A
11Contract exit terms and the BAAThe executed agreement, the renewal date, the notice period, any exit fees, and the BAA's termination sectionPull the signed copies from your own files or request them; read the termination clauses before deciding a notice date45 CFR 164.504(e)

When every row has an answer, you are ready to give notice. If a row is still blank, you know exactly what to ask for, and you can ask for it while goodwill still exists.

Why the order matters

The checklist starts with an admin account you control because every other step depends on it. Microsoft's own guidance lists "the person with the most recent Global Administrator access leaves the organization" as one of the ways an organisation gets locked out, and recommends two or more emergency access accounts that are cloud-only, not tied to any individual, and checked at least every 90 days and "when there's a recent change in IT staff." A change of IT provider is exactly that change.

The restore proof comes before any tool change because the old backup system is about to be replaced. If something goes wrong during the swap, the last good backup is your way back, and you want to know it works before you need it.

How do you take back Microsoft 365 from your old IT company?

Make sure someone at the practice holds Global Administrator, then create two emergency access accounts. In the Microsoft 365 admin center, go to Settings, then Partner relationships, to see every partner with access. Remove the old provider's admin roles and granular (GDAP) access once the new provider is set up.

Microsoft 365 is where email, files and often staff sign-ins live, so it deserves its own step. Three details catch practices out.

Removing roles is not the same as ending the relationship. Microsoft states it plainly: "You can remove admin roles from a partner at any time. Removing the admin roles doesn't remove the partner relationship." To end the relationship itself, Microsoft says to contact the partner. You need to be at least a Billing Administrator to manage partner relationships.

Granular delegated admin (GDAP) is removed separately. Many providers now administer tenants through GDAP rather than older delegated rights. Microsoft's customer-led removal guidance says you can see which partners have GDAP and remove it from your tenant; after removal, the partner's mapped security group "no longer" has access to administer services.

Licences may have been bought through the old provider. If your Microsoft 365 licences were purchased through the outgoing company, they are tied to that reseller relationship. Ask the incoming provider how licences will move before you end the old relationship, so mailboxes are not affected by a lapsed subscription.

A safe Microsoft 365 sequence

    1. Confirm one named person at the practice holds Global Administrator.
    1. Create two emergency access accounts on the *.onmicrosoft.com domain, store their credentials securely, and test that they sign in.
    1. Review Settings > Partner relationships and write down each partner and its roles.
    1. Add the incoming provider and confirm it can administer what it needs.
    1. Plan the licence move with the incoming provider.
    1. After the overlap, remove the outgoing provider's admin roles and GDAP access, and remove any accounts it created inside the tenant.
    1. Check sign-in logs for the old provider's accounts in the following weeks.

If your practice uses Google Workspace instead, the same principle applies: someone at the practice holds a super admin role, and outside admins are removed on purpose rather than by accident.

Who owns your dental practice's domain, and how do you move it?

Your domain should be registered with the practice as the registrant, even if the IT company manages it. ICANN says the registrar must give the registrant the transfer authorisation code within five calendar days of a request, and that moving between registrars is the registrant's right. Registrars can also lock transfers after registrant details change, so check before editing anything.

The domain carries your website and your email. If it sits in the IT company's account, or worse, is registered in the IT company's name, it is the single item most likely to cause a real outage during a switch. Here is how to approach it.

    • Find out who the registrant is. Look up the domain's registrar. If you cannot sign in, the registrar's own recovery process is designed for the registrant.
    • Separate the registrar from the DNS host. The registrar holds the name; the DNS host holds the records that point email and the website to the right place. They are often different companies. Changing one does not have to touch the other.
    • Export DNS records before anything moves. Mail, website, and verification records (for Microsoft 365, for example) must be recreated exactly. A missing mail record is how email stops on a Monday morning.
    • Ask for the authorisation code when you are ready to transfer. ICANN's registrant FAQ, read on 21 October 2026, says the registrar "must provide you with the AuthInfo code within five (5) calendar days of your request."
    • Be careful with registrant changes. ICANN describes a period after a change to the registrant name during which a transfer to a different registrar is blocked. ICANN's registrant FAQ, read on 21 October 2026, puts it at 60 days, and ICANN published an updated Transfer Policy in February 2024, so ask your registrar what applies today before you edit the registrant details.

You do not have to transfer the domain at all. Many practices simply make sure the registrar account is in the practice's name, give the new provider its own access, and leave the domain where it is.

Before notice: read the exit terms and build the dependency list

A transition becomes much harder when the practice learns late that the outgoing agreement requires a notice period, charges for data export, controls a domain account, or removes management tools immediately at termination.

Before notice is sent, identify:

  • Notice period and termination mechanics, including any automatic renewal date
  • Who owns documentation and configuration exports
  • How accounts and credentials are returned
  • Whether backup data or cloud services are tied to the provider's tenant
  • How leased or provider-owned hardware is handled
  • Whether RMM, security or backup agents are removed automatically at termination
  • Any Business Associate Agreement or data-handling obligations that must be closed or replaced appropriately

This is operational planning, not legal advice. When contract ownership or data rights are disputed, the practice should obtain appropriate professional guidance.

The notice-date worksheet

Agreements differ, so take the numbers from your signed copy, not from memory or a proposal. Fill this in once and the date to send notice falls out of it.

LineWhere it comes fromYour entry
Current term end or renewal dateExecuted agreement
Notice period requiredExecuted agreement, termination section
Latest date notice can be sentRenewal date minus notice period
Prep time you want before noticeThis checklist: rows 1 to 11 complete
Date to start preparationLatest notice date minus prep time
How notice must be deliveredExecuted agreement (email, letter, portal)
Exit or data-export feesExecuted agreement, fee schedule
What happens to provider-owned hardware and licencesExecuted agreement

If the latest notice date has already passed, the agreement may roll into another term. Read that clause carefully, and get professional advice if the wording is unclear.

What the BAA says about the end of the relationship

An IT company that can reach patient data typically works under a Business Associate Agreement. The HIPAA rule that sets out what those contracts must contain, 45 CFR 164.504(e), includes a termination provision: at the end of the contract, the business associate must, "if feasible, return or destroy all protected health information," keep no copies, or, if return or destruction is not feasible, extend the contract's protections to the information it keeps.

In practical terms, that gives you a reasonable request to make in writing at exit: confirmation of what patient data the outgoing company held (backups, exports, logs, copies on its own systems) and what was returned or destroyed. Check the wording of your own executed BAA; this paragraph describes the regulation text only.

The safe transition sequence

The sequence is the same for a solo office and a multi-chair group: inventory, confirm ownership, validate recovery, collect documentation, stage new access, overlap, cut over, remove old access, then validate for 30 days. Each step has a gate. You do not move to the next until the current one is proven.

Runbook

  1. 1Inventory
  2. 2Confirm Ownership
  3. 3Validate Recovery
  4. 4Collect Documentation
  5. 5Stage New Access
  6. 6Overlap
  7. 7Cut Over
  8. 8Deprovision Old Access
  9. 9Validate for 30 Days

The switch plan, week by week

The table below turns the runbook into a calendar. The weeks are a planning shape, not a promise: a small office with clean records moves faster, and an office whose domain sits in the old provider's name moves slower. The owner column is the part most plans leave out.

StageWhat happensOwnerGate to move on
Weeks before noticeWork the handover checklist; pull the contract and BAA; fill in the notice-date worksheet; choose the incoming providerPractice owner or office managerEvery checklist row answered or listed as missing
NoticeSend notice in the form the contract requires; request documentation, configuration exports and a supervised restore test in writingPracticeWritten acknowledgement from the outgoing provider
DiscoveryIncoming provider inventories devices, accounts, tools and vendors; compares what it finds with the old documentationIncoming providerInventory signed off by the practice
Recovery gateTest restore of the practice-management database and images to a separate location; open a patient chart and an image; record date, who ran it and how long it tookOutgoing or incoming provider, witnessed by the practiceA dated restore record
The overlap weekBoth providers have access; the incoming one stages its tools, sets up ticketing, meets the software vendors, and lists inherited issues; the outgoing one still owns open ticketsBoth, with one named owner per open issueA written cutover plan with a rollback step
Cutover dayRemove the old management agents and install the new ones in a planned order; switch backup jobs; move licences; update who staff call; scheduled outside patient hoursIncoming providerEvery computer visible in the new tools; a new backup job completed; staff know how to ask for help
Old access removedRemove the outgoing provider's accounts, Microsoft 365 roles and GDAP, VPN, firewall logins and remote tools; rotate shared passwordsIncoming provider, confirmed by the practiceA dated removal record
First 30 daysWeekly check-ins on support, stability, backups and documentationIncoming provider and practice30-day acceptance review

Phase 1: inventory the current environment before anyone removes anything

The incoming provider should know what exists before it starts installing agents, changing credentials or redesigning the network.

Current environment inventory

AreaWhat to inventory
Core infrastructureServers, workstations, firewalls, switches, Wi-Fi, printers, storage, internet circuits
Cloud / identityMicrosoft 365 or Google Workspace, DNS, domain registrar, email security, MFA, cloud apps
Dental systemsPractice-management platform, imaging systems, bridges, sensors/scanners, CBCT/panoramic systems, integrations
Support toolingRMM agents, remote access, ticketing integrations, monitoring and automation
ProtectionEndpoint security, backup platforms, recovery documentation, security tools
Vendors / contractsPMS, imaging, ISP, phones, hardware warranties and support agreements

Do not treat the old provider's documentation as the only source of truth. Compare it with what is actually present in the environment. A walk through every operatory, the front desk and the server closet, with a photo of each device label, often finds a forgotten switch, a sensor PC under a counter, or a second internet circuit nobody listed.

Phase 2: confirm who owns every critical account

The dental practice should retain appropriate ownership of its own business accounts. The IT provider should have the access required to perform its role, not become the only party capable of controlling the environment. That principle holds for any provider of IT services for dental offices, so write it into the new agreement before cutover.

CISA's joint advisory on managed service providers makes the same point from the security side: contracts should state "whether the MSP or the customer owns specific responsibilities," customers should ensure MSP accounts "are not assigned to internal administrator groups," and contracts should require MFA "to be enforced on all MSP accounts used to access customer environments."

Critical account ownership worksheet

Critical assetPractice ownership confirmed?Outgoing provider accessIncoming provider access
Domain registrar
DNS
Microsoft 365 / Google tenant
Firewall / network admin
Server / cloud admin
Backup platform
Endpoint / security platform
RMM / remote access
VoIP / phone portal
ISP account
Password vault
Practice-management and imaging vendor portals

If ownership is unclear, resolve it before the transition clock becomes compressed. The vault row matters more than it looks: if every password lives in a password manager the IT company owns, the practice owns none of them. Ask for the credentials to be moved into a vault the practice owns.

Phase 3: create a recovery gate before changing tools or credentials

The incoming provider should not make major changes until the practice understands how it would recover if something goes wrong.

  1. Confirm what data and systems are protected.
  2. Confirm the latest successful backup jobs.
  3. Confirm retention and where protected copies are stored.
  4. Confirm who can administer the backup platform.
  5. Review the most recent restore evidence for critical systems.
  6. Document the recovery path for the systems needed to reopen the practice.
  7. Only then proceed with material tool, account or infrastructure changes.

The broader recovery strategy belongs in the Dental Backup & Disaster Recovery Checklist. Here it functions as a transition gate.

What counts as restore evidence? A dated record that the practice-management database and the imaging store were restored to a separate location, that a real patient chart opened and its images attached to the right patient, who ran the test, and how long it took. A screenshot of green backup jobs is not the same thing.

The HIPAA Security Rule's contingency plan standard, 45 CFR 164.308(a)(7), lists a data backup plan to "create and maintain retrievable exact copies" of electronic patient information as required, with testing and revision procedures as an addressable specification. CISA's ransomware guide recommends that organisations "regularly test the availability and integrity of backups in a disaster recovery scenario." A provider change is a good moment to do that test.

Phase 4: collect the documentation before the relationship becomes tense

  • Network diagram and addressing information
  • Device / asset inventory
  • Firewall, wireless and server documentation
  • Backup and recovery documentation
  • Administrator-account ownership records
  • Vendor contacts and account numbers
  • Licensing information
  • Internet and phone-system details
  • Hardware warranties
  • Known recurring issues
  • Open tickets and planned projects
  • Any documented exceptions or unsupported legacy systems

The goal is not perfect documentation on day one. The goal is to know what is missing before old access disappears.

Put each request in writing and keep the replies. If the outgoing company hands over credentials, ask that the handover be shown live, signing in to each critical system, so you know the credentials work before the relationship ends. Some outgoing providers record that session for their own protection; there is no harm in asking for a copy.

Phase 5: plan the overlap between old and new providers

Where contracts and circumstances allow, a controlled overlap is safer than a hard handoff.

The incoming provider can use the overlap to:

  • Validate the inventory and credentials
  • Confirm backup/recovery access
  • Establish ticketing and support contacts
  • Install or stage its management tools carefully
  • Review open problems
  • Understand dental software and imaging vendor relationships
  • Plan replacement of old remote-access or security agents
  • Define the first 30 days of stabilization work

A short overlap is useful only when responsibilities are explicit. The practice should know which provider owns each open issue during the transition.

Write it down: one line per open issue, one owner per line. When a sensor stops working on the Tuesday of overlap week, the front desk should not have to guess which company to call.

Phase 6: avoid agent conflicts during the tool handoff

MSPs often use RMM agents, endpoint security, backup agents, remote-access software and other management tools. Replacing them all at once without a plan can create conflicts, duplicate alerts or leave a temporary visibility gap.

Two security tools fighting over the same computer can slow it down or block software from starting, and a practice-management workstation that will not open the schedule before the first patient is the downtime everyone is trying to avoid. The order matters as much as the tools.

For each tool, define:

Tool handoff decisions

QuestionDecision
When is the outgoing agent removed?After the incoming provider confirms its replacement is installed and reporting where appropriate
Can both tools coexist temporarily?Verify vendor compatibility rather than assume
Who owns the removal?Name the outgoing or incoming provider explicitly
What is the validation test?Confirm device visibility, policy status and support access
What is the rollback path?Document how to restore access if the new tool fails

Removal sometimes needs a password or an uninstall key that only the outgoing provider holds. Ask for those keys during the overlap, not after.

Phase 7: schedule material changes around the patient day

Controlled change window

  1. 1Confirm patient-hours impact
  2. 2Name the owner
  3. 3Validate the change
  4. 4Keep rollback available
Avoid unnecessary disruptive work during patient hours whenever practical. No provider should offer a literal zero-downtime promise.

Not every provider transition requires downtime. But changes to firewall access, DNS, administrator accounts, security tooling, backup agents or remote-management platforms can create risk.

For any material change, write down:

    • Change window
    • Expected impact
    • Owner
    • Validation test
    • Rollback path
    • Who communicates with the practice
    • Who is available if the change runs long

Whenever practical, avoid unnecessary disruptive work during patient hours. A good cutover window is one where the schedule is light, the office manager is reachable, and there is time to roll back before the first patient the next morning.

Phase 8: introduce the new support process to the dental team

A technical transition can be successful while the staff experience gets worse because nobody knows where to ask for help.

Before cutover, every team member should know:

  • How to open a ticket
  • What number or portal to use for urgent issues
  • What support hours apply
  • What qualifies as an emergency
  • Who the office manager contacts for escalation
  • What changes the team should expect during the first weeks

If the new agreement has specific response commitments, cross-check them against the Dental IT Support SLA & Response Times guide.

A one-page sheet at the front desk and in each operatory does more than an email nobody reads. Ask the incoming provider to supply the wording, then check it against your agreement.

Phase 9: remove former-provider access only after the new environment is validated

Deprovisioning should be systematic. Do not assume changing one password removes all access.

  • User and administrator accounts
  • Microsoft 365 / Google delegated roles, including GDAP
  • VPN access
  • Firewall and network logins
  • Remote-management and remote-access tools
  • Backup administration
  • Endpoint/security platform access
  • Shared passwords
  • API integrations and vendor portals
  • DNS / domain access where delegated

Document what was removed and when. Preserve the evidence needed for business continuity and accountability.

This step is easy to forget once the new provider is running. CISA's advisory names it directly: "Customers should be sure to disable MSP accounts that are no longer managing infrastructure," noting that "disabling MSP accounts can be overlooked when a contract terminates." An account nobody uses is still a way in.

Phase 10: run a 30-day acceptance period

Window

Week 1

Acceptance focus
Can staff get support? Are core systems stable? Are monitoring and backups reporting? Do critical vendor contacts work?
Window

Week 2

Acceptance focus
Close documentation gaps. Resolve inherited high-priority issues. Confirm account ownership and access.
Window

Week 3

Acceptance focus
Review patching, security-tool status, asset inventory and recurring tickets.
Window

Week 4

Acceptance focus
Agree the first technology roadmap: urgent remediation, lifecycle risks, projects and responsibility gaps.

Do not declare onboarding complete because the new provider can log in. A successful handoff ends when support, monitoring, recovery, documentation and ownership are stable enough for the practice to operate confidently. A second restore test, run on the new backup system before day 30, is the cleanest proof that recovery has moved with the provider.

Five mistakes that create avoidable transition risk

  1. Giving notice before confirming account ownership and contract obligations. Work the handover checklist first; notice is step twelve, not step one.
  2. Removing the old provider's tools before recovery and new visibility are validated. The restore record and a full device list in the new tools are the gates.
  3. Changing many unrelated systems during the same transition window. A new firewall, a new phone system and a new provider in the same week make it hard to tell what broke.
  4. Forgetting the dental software, imaging, ISP and phone vendors that depend on the IT environment. Each one needs to know who the new IT contact is.
  5. Treating onboarding as a password exchange instead of a controlled operating handoff. Passwords without documentation, a restore record and an owner for each open issue are only half a handover.

What if the outgoing provider is uncooperative?

Start with what the practice can control alone: the Microsoft 365 tenant, the domain registrar as registrant, the ISP and phone accounts, the software vendor accounts and the contract. Ask for everything else in writing, keep a dated record, and get professional advice for any dispute rather than retaliating technically.

Start with the contract, account ownership, documentation already held by the practice, vendor relationships and the access the practice can independently control.

The incoming provider should document known facts, identify missing information and build a safe replacement path. Contractual, legal or data-access disputes should be handled with appropriate professional advice rather than improvised technical retaliation.

Practical steps that do not depend on the outgoing company:

    • Sign in as the account holder. The ISP, phone carrier, software vendors and domain registrar deal with the customer of record. If that is the practice, you can usually regain access directly.
    • Use the tenant's own controls. With Global Administrator in hand, the practice can review and remove partner access in Microsoft 365.
    • Plan for devices you cannot sign in to. If a firewall's credentials are not handed over, the incoming provider can plan a replacement or a documented reset during a cutover window, with the network design recorded first.
    • Keep the paper trail. Dated, written requests for documentation, credentials and the BAA's return-or-destroy confirmation make any later conversation easier, whether with the provider or with an adviser.

What if your IT company is the one ending the relationship?

If your IT company gives you notice, treat the notice date as your deadline. In the first week, ask in writing for admin credentials, documentation, configuration exports, a restore test and the date its tools and access will be removed. Then work the handover checklist, starting with an admin account the practice controls.

Being dropped by a provider feels personal, especially after months of treading carefully every time something broke. The useful response is procedural. In the first week:

    1. Confirm the end date and what the notice says happens to tools, backups and accounts at that date.
    1. Ask, in writing, for every admin credential, the network documentation, configuration exports and the location of every backup.
    1. Ask for a supervised restore test before the end date.
    1. Create the emergency access accounts in Microsoft 365 and confirm the domain registrant.
    1. Choose the incoming provider quickly enough to allow at least a short overlap.
    1. Ask for written confirmation, at the end, of what patient data was returned or destroyed under the BAA.

The difference from a planned switch is only the timeline. The order of work stays the same.

Vendor introductions should be part of the handoff

The incoming MSP should not discover the imaging vendor, practice-management contact or ISP only after the first incident.

Create a vendor handoff sheet with the vendor, product/service, support number, account identifier, contract owner, last known issue and the systems that depend on it. This is especially important for software/imaging environments where the IT layer and product layer meet.

VendorProduct or serviceSupport contactAccount IDContract ownerLast known issueDepends on
Practice-management vendorDentrix, Eaglesoft, Open Dental or otherServer or cloud host, workstations
Imaging vendorDEXIS, Carestream, Vatech or otherImaging PC, sensors, bridge to the PMS
Internet providerPrimary and backup circuitsFirewall, phones, cloud apps
Phone providerVoIP or hosted phonesInternet, network, caller ID integration
Microsoft 365 resellerLicencesEmail, files, sign-ins
Domain registrar and DNS hostDomain name and recordsWebsite, email

Ask each vendor to add the incoming provider as an authorised contact, and to remove the outgoing one when you say so.

How do you judge the old provider and the new one on evidence?

Judge both providers on records, not promises: ticket reports that separate time to respond from time to resolve, a written escalation path, a definition of business hours, how onsite visits work, a restore-test record, how vendor problems are handed off, the documentation you receive, and a written list of exclusions.

Use the same scorecard twice. First on your current provider, to make the reasons for leaving concrete. Then on each candidate, to make sure you are not swapping one set of gaps for another.

The service-evidence scorecard

Score each line 0 (no evidence), 1 (described but not shown) or 2 (shown in writing or a real record).

AreaEvidence to ask forCurrent providerCandidate
Response vs resolutionA recent ticket report that shows both time to first response and time to resolution, separately
Escalation pathA written path: who handles it first, who it goes to next, and how the office manager escalates
Business hoursA written definition of business hours, after-hours and what counts as urgent, in the agreement
Onsite coverageHow onsite visits are requested, scheduled and billed, and which locations they cover
Restore-test recordA dated restore test of a practice-management database and images, with who ran it and how long it took
Vendor handoffsHow a problem that sits between the IT layer and the software vendor is handled and tracked
DocumentationA sample of what the practice receives: network map, asset list, admin-account register
ExclusionsA written list of what is not covered and how out-of-scope work is quoted
Account ownershipWho will hold Global Administrator, the domain and the password vault
Exit termsNotice period, export of documentation and data, and what happens to tools and licences at exit

A current provider that scores low on records it should already have is your answer about leaving. A candidate that scores low before you sign is unlikely to score higher afterward. For the contract and agreement side, read what a dental IT support agreement should define about response and escalation; for pricing models, see how to compare dental IT support quotes; and if you are also changing the support model, compare managed dental IT vs break-fix support.

What to ask your new IT provider before you sign

Ask the incoming provider how it will run the handover, who holds admin rights afterwards, how it proves recovery before changing tools, and what you get in writing at the end of onboarding. The answers should name people, steps and records, not adjectives.

Bring these questions to every candidate, and ask for the answers in writing:

    1. What do you need from us and from the outgoing provider in the first week, and in what order?
    1. Who at our practice will hold Global Administrator and the domain registrar login when you are finished?
    1. Will you run a test restore of our practice-management database and images before you change any backup or security tool? Who witnesses it?
    1. How long an overlap do you recommend for an office like ours, and what does each provider own during it?
    1. In what order will you remove the old agents and install yours, and what is the rollback if a workstation stops working?
    1. When will you remove the outgoing provider's accounts, Microsoft 365 roles and remote tools, and will we get a dated record?
    1. How do you handle our Microsoft 365 licences if they were bought through the old provider?
    1. Who contacts our software, imaging, internet and phone vendors, and how will we know it is done?
    1. What does our team receive before cutover: how to ask for help, what is urgent, and who the office manager escalates to?
    1. What documentation do we receive at day 30, and can we see a sample now?
    1. What happens at the end of our agreement with you: notice, exports, and the return or destruction of patient data under the BAA?

For the full contract checklist, see 20 questions to ask before signing a dental IT contract.

What happens after the first 30 days?

The first month proves that the handoff works. The next 60 days should turn stabilization into a technology plan: standardise patching and accounts, close the security and backup exceptions found during onboarding, fix recurring issues, and agree a lifecycle roadmap and budget with the new provider, in writing.

Window

Days 0–30

Primary goal
Take control: support path, monitoring, backup, access, documentation, critical inherited issues
Window

Days 31–60

Primary goal
Standardize: patching, account cleanup, security/backup exceptions, recurring issue remediation
Window

Days 61–90

Primary goal
Plan: lifecycle roadmap, projects, budgeting, vendor rationalization and location standards where relevant

This is where the transition starts becoming managed IT rather than simply a new company answering the same tickets. By day 90, you should be able to fill every line of the service-evidence scorecard for the new provider with a 2. If you cannot, you have a specific conversation to have, which is far better than a vague feeling.

Where Legend fits

If you are weighing Legend Networking as the incoming provider, these are the facts we publish:

    • Track record: served over 3,500 practices since 2004
    • Monitoring: 24/7 monitoring
    • Engineers: in-house engineers; no outsourced first-level triage
    • Onsite: onsite dispatch by appointment across served dental markets; remote-first nationwide
    • Practice software: we support the IT environment around Dentrix, Eaglesoft, Open Dental and Archy, and imaging from DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging
    • Reviews: 4.8 rating · 173 Google reviews

Hold us to the same scorecard as everyone else.

This guide was written by Ian Lynch, who has 22 years in dental IT and oversees Legend's NOC, onsite dispatch and client technology roadmaps.

Questions

Frequently asked questions

Can a dental practice switch IT providers without downtime?

Usually, yes, for patients. Most of the work can be staged before cutover: taking back accounts, testing a restore, and preparing the new monitoring and backup tools during an overlap. The few changes that can disrupt the practice, such as swapping security agents or editing DNS, can be scheduled outside patient hours with a rollback step. No provider should promise that a transition will have literally zero interruption.

When should we tell the current provider?

After you have worked the handover checklist and before the notice deadline in your executed agreement. Confirm you hold an admin account, Microsoft 365 global admin and the domain registrar login, request a restore test, and read the termination and BAA sections first. Then send notice in the form the contract requires, early enough to leave room for a short overlap.

Who should own administrator credentials?

The dental practice should own its critical business accounts: Microsoft 365 global admin, the domain registrar, the firewall, the backup console and the password vault. The IT provider receives the access it needs to do the work, through its own named accounts. Microsoft recommends two emergency access accounts that belong to no single person, so the practice is never locked out when a provider changes.

Should the old and new IT companies overlap?

Where the contract allows it, yes. A short overlap lets the incoming provider check the inventory and credentials, confirm backup access, stage its tools and meet your software vendors while the outgoing provider still owns open issues. Write down one owner for each open ticket during the overlap, so staff know which company to call when something breaks that week.

What should be removed after the old provider leaves?

Remove its user and admin accounts, Microsoft 365 admin roles and GDAP access, VPN and firewall logins, remote-management and remote-access tools, backup and security console access, and any shared passwords it knew. CISA notes that disabling a former provider's accounts is easy to overlook when a contract ends. Keep a dated record of what was removed and when.

How long does onboarding take?

It depends on the size of the office and how complete the records are. The technical cutover can be short, but documentation, cleanup of inherited issues and stabilisation continue afterwards. A domain registered in the old provider's name, or missing credentials, adds time. Plan on a defined 30-day acceptance period rather than declaring the transition complete the day the new provider can log in.

What if my current IT provider has all our administrative passwords?

Start with accounts the practice can recover as the customer of record: Microsoft 365, the domain registrar, the ISP, phone and software vendors. Ask the provider in writing for every other credential and for a live handover. For devices you still cannot reach, such as a firewall, the incoming provider can plan a documented reset or replacement during a cutover window.

How much notice do I need to give my IT company?

The notice period is whatever your executed agreement says, so read the termination section of the signed copy rather than relying on memory or the original proposal. Note the renewal date, the notice period, how notice must be delivered and any exit fees. Work backwards from the renewal date to the last day notice can be sent, then start preparing before that.

What happens to our patient data when we leave an IT provider?

The HIPAA rule on business associate contracts, 45 CFR 164.504(e), requires the contract to say that at termination the business associate returns or destroys protected health information if feasible, or extends the contract's protections to anything it keeps. Ask the outgoing company, in writing, to confirm what it held and what was returned or destroyed, and check your own BAA's wording.

Do I need to move my domain to switch IT providers?

No. What matters is that the practice is the registrant and can sign in to the registrar account. You can give the new provider its own access and leave the domain where it is. If you do transfer it, export the DNS records first, request the authorisation code, and ask the registrar about any transfer lock before changing registrant details.

The bottom line

A safe MSP transition is an ownership project before it is a technology project.

Inventory first. Confirm ownership. Validate recovery. Stage the new provider. Remove old access only after the new operating model works. Then use the first 30 days to turn a handoff into a stable managed environment.

If you would like a second set of eyes before you send notice, we invite you to book a consultation: bring this handover checklist and the 11-criterion scorecard from our guide to choosing a dental IT provider, and we will go through them with you against your current setup. You can read how ongoing support works on our managed IT services for dental practices page, or ask for a Free Dental IT Assessment for written findings and prioritized recommendations on your computers, software, network security, backups and performance before the cutover window begins.

Ian Lynch
About the author

Ian Lynch

Owner & Operator, Legend Networking

22 years in dental IT. Oversees the NOC, onsite dispatch and client technology roadmaps for practices nationwide.

  • Operations center

    Dallas, Texas

    Serving dental practices nationwide since 2004

  • NOC hours

    24/7 monitoring

    Helpdesk staffed 24/7 at 1-800-794-1588

  • Engineers

    In-house only

    No outsourced first-level dental IT triage

  • Onsite dispatch

    By appointment

    Technicians deployed across served dental markets

About Legend Networking
Your next step

Build the handoff plan before removing the former provider.

Tell us what you are running and we will review it with you.

Or call 1-800-794-1588

Free IT assessment

Tell us what you are running

Your information is secure and will never be shared.