Dental Server Replacement vs Cloud Migration: Which Path Makes Sense for Your Practice?

The quote is on your desk: a new server, licences, installation, maybe phones and offsite backup in one number. The old server is slow in the mornings, its warranty has lapsed, and a colleague says moving to the cloud solved everything for them.

Replace the server if you are keeping software that runs on it, the slowdown is genuinely hardware, imaging needs local speed and your internet has no backup line. Move to a hosted version if you are ready to change workflows, can run two independent internet circuits and the hosted product's limits fit your team. Many practices end up hybrid.

This guide gives you a way to decide on evidence rather than on whichever salesperson called last: a first check of whether the slowdown needs new hardware at all, the dates that put a deadline on older servers, what the software vendors themselves require for each path, a decision table by type of practice, and a worksheet you can fill in with your office manager in under an hour.

The server replacement event is really an architecture decision

Yes. An ageing dental server forces a bigger question than which model to buy: will the practice stay on the same practice management software and hosting model for the next five or more years? If the answer is uncertain, evaluate the software and hosting path first, so you do not pay for infrastructure you plan to retire.

The server is rarely the only thing that is ageing. The practice management system (PMS) on it has its own roadmap, the imaging software has its own database and capture stations, and the internet line has its own weak points. A replacement quote treats the server as a part to swap. An architecture decision asks what the server is for and whether it still needs to exist in that form. Whichever path you choose, someone still has to run the result, and knowing how managed IT works for dentists helps you decide who that should be.

Start with the comparison below. Find the rows that describe your practice today.

If two or more rows point in different directions, that is normal. It usually means a hybrid answer: the PMS moves or stays, and imaging is decided on its own terms. The worksheet further down turns these rows into answers you can write down and compare.

Does the slowdown actually need a new server?

Often it does not, and that is the first thing to check. A slow schedule, a chart that hangs or a morning freeze can come from the network, an outdated software version, database maintenance that has not run, antivirus interference or one bad workstation. Confirm the cause before buying hardware, because a new server will not fix any of those.

Open Dental's own troubleshooting manual (v24.4, read 21 October 2026) lists causes that have nothing to do with server age: an out-of-date build, a MySQL 5.5 database it describes as "32 bit and may create a processing bottleneck", database maintenance and optimise tools that have not been run, antivirus and firewall software, Topaz signature pads, network printers and an images folder reached over a VPN. Dentrix practices see a similar mix of causes, which our guide on why Dentrix is slow and what to check first walks through step by step.

Use this table before you approve a quote. Each row is a symptom an owner describes, the non-hardware cause to rule out, and the evidence that would point to the server itself.

What to collect before anyone quotes: the server's age and warranty status, its Windows Server version, free disk space on each drive, the PMS and imaging versions, the number of workstations, and two or three specific moments when the team noticed slowness. If your IT provider cannot produce that list, the quote is a guess.

If the evidence does point to the server, the rest of this guide applies. If it points elsewhere, a fix may buy you time to make the server-or-cloud decision on your schedule rather than in a hurry.

What does Windows Server end of support mean for a dental server?

When Microsoft's extended support ends, a Windows Server version stops receiving security updates unless the owner buys a paid extension where one is offered. Windows Server 2016's extended support ends 12 January 2027. A server running it, or anything older, needs a dated plan: upgrade in place, replace the server, or move the workload off it.

These dates come from Microsoft's lifecycle pages, read on 21 October 2026. Microsoft lists end times in Pacific time, early on the morning of the date shown, so the last full day of support is the day before.

The software vendors have already moved. Henry Schein One's Dentrix system requirements for 2026 (publication date April 2026) list Windows Server 2016, 2019, 2022 and 2025 as supported server systems, and note that Windows Server 2016 extended support "continues until 1/12/2027". Open Dental's computer requirements list Windows Server 2025, 2022, 2019 and 2016, and state that support for Windows Server 2012 was suspended on 10 October 2023. A server on 2012 R2 is outside both vendors' supported lists today.

The database layer can carry its own deadline. Microsoft lists SQL Server 2016's extended support as ending 7/15/2026, with paid Extended Security Updates offered after that. This matters only if an application on your server uses SQL Server 2016; ask your IT provider which database engines are installed, because imaging and third-party add-ons sometimes bring their own.

Why it matters beyond the vendor's support desk: the Cybersecurity and Infrastructure Security Agency (CISA) lists the use of unsupported or end-of-life software as a "bad practice". Its wording is aimed at critical infrastructure and national critical functions, not dental offices specifically, but its reasoning applies to any server holding patient records: the risk is "especially egregious in technologies accessible from the Internet." A server reachable through remote access or an open port is exactly that.

An end-of-support date does not force the cloud. It forces a decision. A server running 2016 can be upgraded or replaced with a supported version, or the PMS can move to a hosted service and the server retired or reduced to imaging. The worksheet below helps you choose which.

Understand what “cloud dental software” actually changes

Moving the PMS to a hosted version changes who runs the application server and database, and who takes the backups of that database. It does not remove the office network, workstations, printers, scanners, imaging capture stations, sign-in security or the dependence on internet. Someone still owns each of those after go-live.

"Cloud" covers several different arrangements, and the differences matter when you compare quotes:

• • A cloud-native PMS such as Dentrix Ascend runs in a web browser. Henry Schein One's Dentrix Ascend requirements list the latest Google Chrome on a computer and Chrome or Safari on an iPad, and an internet connection of 50 Mbps download and 10 Mbps upload, "assuming that 10 logon IDs are being used at one time and at one location."
• • A vendor-hosted version of a server-based PMS, such as Open Dental Cloud, which Open Dental describes as "a hosted solution managed by Open Dental Software" and, when read on 21 October 2026, as "currently in limited release". Its requirements page asks for "20 mbps download. 10 mbps upload." and an ODCloudClient on a Windows machine to bridge to third-party software "such as imaging software, credit card processing".
• • A server-based PMS on a server hosted elsewhere, run by a hosting or IT provider rather than the software vendor. This keeps the same software and moves the hardware. Check the vendor's requirements first: the Dentrix 2026 requirements, for example, list thin-client setups (Terminal Services and Citrix) as not supported.
• • A server-based PMS on a server in your office, such as Dentrix G-series or self-hosted Open Dental. This is the replacement path.

Here is how responsibility shifts between the two ends of that range.

The column that does not change is the one most quotes leave out. Whichever way you go, the practice still needs someone to look after the network, the workstations, the imaging stations and the internet line, and to coordinate with the software vendor when something crosses a boundary. That ongoing work is what IT services for dental offices are meant to cover, whichever hosting model the practice chooses.

What limits does a hosted PMS carry that a local server does not?

Hosted versions of server-based software can drop features the local version has. Open Dental lists its cloud differences publicly: the images folder is not stored locally, Video Capture and Import Automatically are unavailable in imaging, Letter Merge and Voice Perio Charting are unavailable, and updates install automatically. Check every feature your team uses against that list first.

Open Dental's cloud differences page, read on 21 October 2026, also lists the Backup Tool and Supplemental Backups as unavailable (because backups are automatic), touch-screen signatures as not supported, the Replication Setup and HL7 message structure windows as not available, and Choose Database settings as read-only. Its Report Server manual page states the Report Server tab is unavailable to Open Dental Cloud users, which matters if your reports are slow today and a report server was the planned fix. The main cloud page adds that "There are some limitations on interoperability with third-party solutions."

There is a counterweight. The same page says Open Dental Cloud backups "are encrypted, tested for integrity nightly, and stored off-site", that imaging can either stay on separate local software or be hosted, and that a practice is "Not stuck: easily switch from Cloud to Local host or vice-versa." That last point is worth getting in writing for your own account, with the steps and any fee.

A practical way to run this check: ask the office manager, the lead assistant and the billing coordinator each to list the ten things they do every day in the PMS, including add-ons, letters, imaging imports and signature capture. Put each item against the vendor's differences list. Any match is either a workflow to change or a reason to stay local.

For a side-by-side of the two most common platforms, including how hosting affects each, see Dentrix vs Open Dental for dental practices.

Imaging can turn a “cloud migration” into a hybrid environment

Imaging is the clinical dependency most likely to keep hardware in the building. Sensors and intraoral cameras plug into operatory computers through local drivers, CBCT units have their own capture stations and large files, and some imaging software needs a local database. A PMS can move to the cloud while imaging stays local or hybrid.

ACTIVE CLINICAL PIPELINE CONFIGURATION

Map imaging as its own system, not as a line in the PMS decision. For each device, write down where images are captured, where they are stored, how the PMS opens them (the bridge) and what happens when the internet drops.

Open Dental's cloud differences list matters here too: Video Capture and Import Automatically are not available in the hosted imaging module, and the images folder is not stored locally. If your team uses either feature, plan the alternative before migration, not after.

Legend supports the IT environment for DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, alongside the practice software. For a step-by-step test of the full image path from sensor to chart, see our dental imaging integration troubleshooting guide.

Treat internet as production infrastructure if the PMS is cloud-first

As production infrastructure. With a hosted PMS, a cut fibre line or a failed modem stops scheduling, charting and checkout even when the vendor's systems are running normally. Plan a second circuit from a different provider and a different path into the building, set to fail over automatically, and test it before go-live.

On a local server, an internet outage stops email, eServices, insurance eligibility checks and remote access, but the schedule and charts keep working inside the office. On a hosted PMS, the same outage stops the clinical day. That is the trade at the heart of this decision, and the fear most owners voice first: what happens when the internet goes down for an hour?

Answer it with tests rather than opinions:

1. 1. Measure your real speed against the vendor's figure: Open Dental Cloud asks for 20 Mbps download and 10 Mbps upload; Dentrix Ascend lists 50 Mbps download and 10 Mbps upload for 10 logon IDs at one time and one location. Measure at the busiest hour, not on a quiet Sunday.
2. 1. Check that the backup circuit is truly independent. Two services from the same provider over the same cable fail together.
3. 1. Pull the primary cable during a quiet hour and time how long the PMS takes to recover on the backup line. Write the result down.
4. 1. Check what else rides on the line: cloud phones, card terminals, imaging uploads and guest Wi-Fi all compete for the same bandwidth.
5. 1. Agree a downtime procedure: how the front desk sees tomorrow's schedule, takes payments and records treatment if both lines fail.

If your office has a single line with no realistic second option, that row of the worksheet points strongly toward a local PMS. For the first checks when a line does drop, see dental office internet down: what to check.

Compare total cost, not server price versus subscription price

Compare the same cost categories over the same period, not a server quote against a monthly subscription. A server is mostly capital spent at once plus support; a hosted PMS is mostly recurring cost plus a migration project. Write both paths out line by line over five years, including the costs each path adds outside the server.

This guide does not quote prices: hardware, licences and subscriptions change too often, and any figure here would be out of date before you read it. What does not change is the structure. Ask each vendor and your IT provider to fill in every row below, in writing, for the same five-year period.

Two rows decide most comparisons. The first is the end-of-cycle row: a server path repeats its hardware cost at each replacement, while a hosted path carries an exit cost only if you leave. The second is the internet row, which owners often leave out of the cloud column until the first outage.

A bundled quote that combines a server, phones and cloud backup in one figure is hard to compare with anything. Ask for each part to be priced separately so you can see which parts the decision actually depends on.

Which path fits which kind of practice?

It depends mostly on four things: how many locations you run, how much imaging you depend on, how resilient your internet can be, and whether you are keeping your current software. The table below gives the usual starting point for four common practice types, and what to test before you commit.

For a startup, the decision sits inside the wider opening plan; see Legend's page for dental startups for how technology planning fits the build.

What changes when a DSO or multi-location group moves to the cloud?

For a group, the main benefit of a hosted PMS is one database and one set of settings across every site, so reporting, scheduling across locations and adding a new office get simpler. The main risk is that every site now depends on its own internet line. Pilot one location before migrating the rest.

Open Dental's multiple locations page lists twelve ways to run several offices, from separate databases to a single database over a VPN (it typically recommends fewer than five locations for that option), remote access, terminal servers, replication and Open Dental Cloud. It also says "It is recommended to have a capable IT set up and maintain any network settings." In other words, the hosted option is one of several, and the right one depends on how many sites you have and how they connect.

Questions a group should settle before a cloud migration:

• • Standards first: are user roles, fee schedules, appointment types and templates the same across sites, or will migration force those decisions?
• • Internet at every site: which locations have a realistic second circuit, and what is the downtime procedure at the ones that do not?
• • Imaging per site: which offices have CBCT, which imaging software each uses, and whether images stay local per site or centralise.
• • Acquisitions: how a newly acquired office's data will be converted into the standard platform, and who owns that project.
• • Order of migration: which site goes first, what acceptance tests it must pass, and who signs off before the next site moves.

See also dental IT support for DSOs and multi-location groups.

What should you check before replacing a server in place?

Check that the new server meets the PMS vendor's current requirements, that the database and images will move with matching versions, and that every workstation, bridge and service is repointed afterwards. Replacing a server is a migration in its own right, with its own test list, even when the software stays the same.

The vendors publish what a server needs. Two examples, both read in October 2026:

• • Dentrix (2026 requirements, April 2026): Windows Server 2016, 2019, 2022 or 2025 in Standard or Datacenter edition, with Essentials, Small Business and Server Core not supported; 16 GB of memory, with more possibly needed above 10 workstations; 4 or more cores at 2.4 GHz; 60 GB free on an SSD or NVMe drive; a 1 Gbps network. The same document says that after 30 June 2026, Henry Schein One no longer supports installing Dentrix on Windows 10, which affects the workstations too.
• • Open Dental: "We recommend having a dedicated server to protect data." Its hardware requirements PDF (last updated August 2026) sizes database and file servers by workstation count, notes that "Windows 11 Professional allows up to 20 concurrent connections", and advises allowing 20 to 25 percent more connections than workstations. Its computer requirements page calls SSD or NVMe drives "recommended, but not required" and a UPS "optional but recommended".

A quote that does not mention these requirements, or that proposes a desktop edition of Windows as the server for a practice near the connection limit, deserves a second look.

For an Open Dental server migration, Open Dental's own server migration page says plainly: "This information is for advanced IT users only." It requires the same MariaDB or MySQL version on the new server as the old, backups of the OpenDentImages folder and the database (for InnoDB, the entire data folder and my.ini), stopping the MySQL, OpenDentalService, eConnector and API services on the old server, and repointing data paths, the update server and every workstation's Choose Database setting. HL7 users are told to schedule the move with Open Dental support. For the service side, see Open Dental IT support.

For Dentrix, our Dentrix server migration checklist covers the move step by step, including imaging bridges. Before the old server is switched off for good, read the dental server shutdown and UPS checklist.

How do you know the migration worked?

By testing the real workflows before the team relies on them, and signing off each one. Whether you replace the server or move to the cloud, the first clinic morning should not be the first time anyone opens a chart, captures an X-ray or runs a claim on the new setup.

Open Dental's cloud signup process includes a test environment, or a test migration for existing customers, and a review before the final migration is scheduled. Use that step fully. The list below is the minimum acceptance test for either path.

The full go-live process, including rehearsal and a rollback trigger, is in our dental PMS migration cutover plan, and the broader software-change steps are in the dental software migration checklist. Backup and restore testing has its own guide: the dental backup and disaster recovery checklist.

Ask about data ownership, export and exit before signing

Ask how you get a complete copy of your data out, not only how it goes in. Before signing a hosted PMS agreement, get in writing the export format, whether images and documents are included, how long an export takes, what it costs, and what happens to your data after you leave.

Moving in is the vendor's sales process; moving out is yours. Ask these questions while you still have leverage:

The same questions apply to a server path, in a different form: who holds the server's administrator passwords, where the backups live, and whether a new IT provider could take over without the old one's help.

Use a scored decision framework

ARCHITECTURAL FIT SCORECARD

Your worksheet: replace the server or move to the cloud?

Fill this in with your office manager and your IT provider. For each line, write your answer and circle where it points: S (replace the server), C (hosted or cloud PMS) or H (hybrid). The pattern of answers, not a single row, is your decision. Keep the completed sheet with the quotes.

A. Current symptoms

B. Software and hosting options

C. Imaging, bridges and devices

D. Outage tolerance and internet resilience

E. Data ownership and exit terms

F. Migration acceptance

G. Capital vs recurring cost

Reading the result. Mostly S: replace or upgrade the server, on a supported version, and use the acceptance tests above. Mostly C with resilient internet and no blocking feature gaps: evaluate the hosted PMS properly, starting with a test migration. A mix of S and C with imaging rows marked H: plan a hybrid, deciding the PMS and imaging separately. Any "not yet" answer means the decision is not ready to make.

What to ask your IT provider

Use these questions to test any server or cloud proposal, including one from Legend. A good provider answers them in writing without hesitation.

1. 1. What evidence shows our slowdown needs a new server rather than a software, network or workstation fix?
2. 1. Which Windows Server version will the new server run, and what is its Microsoft end-of-support date?
3. 1. Does the proposed server meet our PMS vendor's current published requirements? Show me the line items.
4. 1. Which of our daily tasks would change, or stop working, on the hosted version of our PMS?
5. 1. Which imaging devices and bridges stay local, and how will each be tested after the change?
6. 1. What internet speed does the hosted option need, what do we have at our busiest hour, and what is the plan for a second circuit?
7. 1. Can you split this quote into hardware, licensing, labour, backup and phones, over the same five-year period for both paths?
8. 1. Who backs up our CBCT data, scanner files and any local documents after a cloud move?
9. 1. What acceptance tests will you run before our first clinic day, and who signs them off?
10. 1. If we leave the hosted vendor, or you as our IT provider, how do we get a complete copy of our data and our administrator access?

Your Practice Needs Clear Technology Ownership

Whichever path you choose, the decision is really about ownership: who owns each system, each dependency and each test once the change is made. A new server without a restore test, or a cloud PMS without a second internet line, moves the risk somewhere nobody is watching.

Technology should protect the schedule, not disrupt it. With clear ownership of the server or the hosted service, the imaging chain, the internet line and the vendor relationships, a failure becomes a ticket someone owns rather than a lost morning, and the next server-or-cloud question arrives with the facts already gathered.

Legend Networking has 22+ years in dental IT (since 2004) and has served over 3,500 practices since 2004. Legend supports the IT environment for Dentrix, Eaglesoft, Open Dental and Archy, with 24/7 monitoring and in-house engineers; no outsourced first-level triage. Legend holds a 4.8 rating · 173 Google reviews. Legend's operations are led by Ian Lynch: 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps.

Your next step

If you are holding a server quote or weighing a move to the cloud, start with the guide for your software change and the support page for your platform: the dental software migration checklist, then Dentrix IT support or Open Dental IT support. For the hardware side, see Legend's dental server and workstation services; for hosted options, see cloud solutions for dental practices.