Cloud Dental Software in 2026: What Moving Practice Management to the Cloud Changes for Your IT
The office server is five years old, its warranty has run out, and a software rep has just told you that with cloud dental software you will never buy another one. Then the questions start. Will the x-ray sensors still work? What happens on the morning the internet goes down? Who keeps the backups now, and can you get your data back if you ever leave?
This guide is written for the practice owner making that call. It explains what actually moves to the cloud and what stays in the office, compares Dentrix Ascend, Open Dental Cloud, Curve, Denticon, tab32 and Archy by their IT impact using only the vendors' own documentation, and shows who is responsible for what once the server is gone. It also covers outages, backups, getting your data out, the cost model, the Texas data-location law and a step-by-step migration plan. It names no favorite product and it is not legal advice.
Move when your internet, imaging computers and team are ready, not when the server fails. Cloud based dental practice management software removes the practice-management server, but not the IT. You still need fast primary and backup internet, local imaging PCs, secure logins, your own backups of local files, a signed BAA and a tested outage plan.
- Cloud dental software moves the practice management database to the vendor's data center; imaging devices, workstations, printers and the network stay in the office.
- Move when there is a reason to change, the office meets the vendor's published internet and computer requirements, and the team has time to learn the new system.
- The vendor runs the application and its backups; the practice still owns its internet, computers, imaging PCs, user accounts, local files and outage plan.
- Every cloud system has outages, and claims can stop when a clearinghouse has trouble, so write a downtime plan before the cutover.
- Texas SB 1188 requires electronic health records stored from January 1, 2026 to be kept in the United States; confirm with your vendor and counsel how it applies to you.
In this guide
- What is cloud dental software, and what actually leaves your office?
- Should your practice move to cloud based dental practice management software?
- Which cloud dental software options are there, and how do they differ for your IT?
- Archy and Legend Networking: who looks after what
- Who is responsible for what once the software is in the cloud?
- Is your office ready for cloud dental software?
- What happens to imaging and bridges in a cloud setup?
- What happens when the cloud system or the clearinghouse is down?
- Does the cloud vendor's backup replace your own?
- Who owns your data in cloud dental software, and how do you get it out?
- What does cloud dental software cost compared with replacing a server?
- Does Texas SB 1188 affect where your cloud dental data is stored?
- How do you move to cloud dental software without losing a day?
- Why do practices still need dental IT consulting after moving to the cloud?
- What to ask your IT provider about cloud dental software
- How Legend Networking can help
- Ask for a review of your practice before a cloud dental software move
- Frequently asked questions
What is cloud dental software, and what actually leaves your office?
Cloud dental software is practice management software that runs on servers in the vendor's data center, which your team opens through a browser or a small installed app over the internet. The scheduling, charting, billing and patient database move out of the office. Imaging devices, workstations, printers, the network and the internet connection stay with you.
That is the honest meaning of "dental software no server". There is no practice-management server in the closet, but there is still a building full of technology the software depends on. A cloud dental solution changes where the database lives and who patches it; it does not change the fact that every chair needs a working computer, a sensor that talks to that computer, and a connection that does not drop at 8 a.m.
There are three common shapes of cloud set-up in dentistry, and they behave differently on the day something goes wrong. If you are weighing them, our page on cloud solutions for dental practices describes the office side of the move.
Browser-native cloud PMS
The software was written to run in the vendor's data center and is opened in a web browser. Dentrix Ascend, Curve, Denticon, tab32 and Archy describe themselves this way; imaging is usually built in or bridged through a local capture app.
Vendor-hosted desktop PMS
The vendor runs its familiar desktop program on its own servers for you. Open Dental Cloud is the example here: Open Dental says it "looks and feels just like our local version", with a small client on Windows PCs for bridges and imaging devices.
Hybrid office
The practice management system is in the cloud, but a local computer or small server still holds large imaging files, CBCT data or a legacy archive. This is common in practices with 3D imaging, and it means local backups still matter.
The shape matters more than the brand name. A browser-native system depends entirely on the internet for the schedule; a hosted desktop system may give you a path back to a local server; a hybrid office keeps one foot in each world and needs both kinds of care.
Should your practice move to cloud based dental practice management software?
Move when three things line up: a reason to change (a server due for replacement, several locations, remote access), an office that meets the vendor's internet and computer requirements, and a team with time to learn a new system. Wait if your internet is unreliable or your imaging depends on software the new vendor cannot bridge.
Most practices meet this question at the end of a server's life. Before you compare quotes, write down the signals for and against. The table below is a neutral starting point; it is not a scorecard for any product.
| Signal in your practice | Points toward | Why it matters |
|---|---|---|
| Office server out of warranty or due for replacement in the next 12 months | Decide now | The cost of a new server is the moment to compare it with a subscription |
| Two or more locations, or a second office planned | Cloud | Every site reaches the same database without a site-to-site link to one office |
| Owners or billing staff work from home | Cloud | Remote access is built in rather than added through remote-desktop tools |
| Only one internet provider at the office, with outages in the past year | Wait | A cloud schedule stops with the line unless a second connection is in place |
| CBCT or 3D imaging used daily | Hybrid | Large imaging files usually still need fast local storage |
| Imaging or specialty software with no bridge to the new system | Wait | Clinical workflow breaks if the bridge is missing on day one |
| Team already stretched, a hire or a move planned | Wait | A new practice management system means weeks of retraining |
| Happy with your current software and its on-premise version is still sold and supported | Stay or hosted | A hosted version of the same software can avoid retraining entirely |
If the cost question is the deciding one, our comparison of dental server replacement vs cloud migration walks through the server side in detail. This guide stays with what changes for your IT once the decision is made.
Which cloud dental software options are there, and how do they differ for your IT?
The cloud dental software most often shortlisted by US practices includes Dentrix Ascend, Open Dental Cloud, Curve, Denticon, tab32 and Archy. For IT, they differ in how they are hosted, what internet speed the vendor publishes, how imaging devices connect, and how data moves in and out. Several of those details are not published, so ask for them in writing.
The table compares them by IT impact only, from each vendor's own pages as read on October 25, 2026. "Not published" means we did not find it on the vendor pages we read, not that the feature is missing. It is not a ranking, and features change; check the vendor's current documentation before you sign.
| Product | Hosting model (vendor's words) | Internet the vendor publishes | Imaging approach | Moving in and out |
|---|---|---|---|---|
| Dentrix Ascend (Henry Schein One) | A "cloud-based application" that "stores your practice data remotely" (Dentrix Ascend resources) | Not published on the pages we read | Built-in imaging; images "acquired and analyzed using Dentrix imaging" | Onboarding described; data export terms not published |
| Open Dental Cloud | "A hosted solution managed by Open Dental Software", US customers only, limited release | 20 Mbps down and 10 Mbps up for each workstation (Open Dental Cloud requirements) | Separate imaging can stay on your systems or be hosted by Open Dental; bridges need the ODCloudClient on Windows | Vendor says you can switch from cloud to local hosting or back; one-time migration fee |
| Curve | Cloud practice management in the browser; Chrome is the only fully supported browser | 10 Mbps down and 5 Mbps up for 1 to 10 users; satellite and wireless not recommended (Curve system requirements) | Curve Capture needs "direct, local access to imaging devices" and does not run on terminal servers | Not published on the pages we read |
| Denticon (Planet DDS) | Browser-based; Chrome or Edge | 6 Mbps down and 2 Mbps up recommended, 3 and 1 minimum (Denticon system requirements) | Not covered on the requirements page | Not published on the pages we read; public status page for incidents |
| tab32 | "Built on Google Cloud", no local servers | Not published on the pages we read | "Fully integrated cloud-native dental imaging" | Not published on the pages we read |
| Archy | Cloud system; "No server needed" | Not published on the pages we read | Built-in imaging; native Schick integration and TWAIN for other sensors; vendor says x-rays can be taken when the internet is down | Trial data extraction, a sample account with your converted data to audit, final conversion while the practice is closed |
Three things stand out for IT. First, published internet figures differ a lot, and Open Dental's is per workstation, so a ten-chair office multiplies it. Second, every option still needs local software or drivers somewhere to talk to sensors and cameras. Third, the exit path is the least documented part of every product. That is where your questions should go.
Dentrix vs Dentrix Ascend: what changes for IT?
Dentrix is installed on a server and workstations in your office; Dentrix Ascend is Henry Schein One's cloud system, which it calls a "native cloud platform". For IT, moving between them is a change of system, not an upgrade: new logins, new imaging workflow, a data conversion and retraining. Henry Schein One's August 2025 release describes a dental group moving to Ascend "as part of a strategic move away from on-premise software" after eight years on Dentrix Enterprise. No end of support for on-premise Dentrix has been announced that we could find.
Choosing cloud dental software for a DSO or group
For multi-location groups, the IT questions grow: how users and roles are managed across sites, whether the vendor supports single sign-on, how reporting spans locations, and how each office's imaging connects. Ask each vendor for its group or enterprise documentation, and test with two sites before rolling out. For a wider look at features, see how to compare dental practice management software; if you are weighing the two most common desktop systems first, read our Dentrix vs Open Dental comparison.
Archy and Legend Networking: who looks after what
Legend Networking supports the IT environment of practices running Archy, alongside Dentrix, Eaglesoft and Open Dental. Archy provides the software and hosts the data; the practice and its IT provider look after everything the software runs on inside the office. The table splits the work the way it falls in a practice.
| What Archy provides | What Legend Networking provides |
|---|---|
| Cloud practice management software, hosted by Archy | IT support for the practice's Archy environment: workstations, users and the office network |
| Online scheduling and billing tools | Network design and administration for the office, including the internet connection and Wi-Fi |
| Built-in imaging and clinical charting, with native Schick integration and TWAIN for other sensors | Set-up and support of imaging workstations and sensor drivers on the practice's computers |
| Real-time access to the practice's data from any signed-in device | Cybersecurity safeguards for the computers and accounts that open patient data |
| Automatic software updates delivered by Archy | Backup and recovery for files kept in the office, plus 24/7 monitoring of the systems we manage |
The split above applies to any cloud system: the vendor runs the application; someone still has to run the office. Our Archy IT support page covers the platform side for Archy practices.
Who is responsible for what once the software is in the cloud?
The vendor is responsible for the application, its servers, its database backups and its uptime. The practice stays responsible for everything on its side of the internet: connection, computers, imaging PCs and drivers, user accounts and multi-factor sign-in, local files, printers, the business associate agreement and its own outage plan. Write the split down before you sign.
HHS is clear that a cloud provider holding patient data for a practice is a business associate. Its guidance on HIPAA and cloud computing says this applies "even if the CSP processes or stores only encrypted ePHI and lacks an encryption key for the data", so the practice and the vendor sign a BAA. HHS also lists what a service level agreement can cover, including "System availability and reliability", "Back-up and data recovery" and the "Manner in which data will be returned to the customer after service use termination". The table turns that into a working split.
| Area | Cloud vendor handles | Practice and its IT still own |
|---|---|---|
| Application and database | Hosting, patches, version upgrades, database backups | Choosing settings, user roles and who can see what |
| Internet | Its own data center connectivity | The office connection, a second line, the router and firewall |
| Workstations | Nothing on your computers, beyond a browser or small client app | Windows updates, antivirus, browser versions, replacing old PCs |
| Imaging | The cloud image store, if imaging is built in | Sensors, cameras, capture PCs, drivers, CBCT and any local image server |
| Bridges | The integration on its side | Installing and updating bridge clients on each PC |
| User accounts | The sign-in system | Creating and removing staff accounts, multi-factor sign-in, no shared logins |
| Backups | Backups of its own systems | Backups of local images, scans, documents and any exported data |
| Printers and scanners | Nothing | Drivers, label and receipt printers, document scanners |
| Contracts | Offering a BAA and its terms | Signing the BAA, filing it, reading the SLA and export terms |
| Outages | Fixing its own service and posting status | A written plan for running the day without the system |

A good test: for every row in the right-hand column, write a name next to it. Rows without a name are where problems start.
Is your office ready for cloud dental software?
Your office is ready when each workstation's share of the internet meets the vendor's published figure, a second internet line can take over, computers run a supported version of Windows, imaging PCs are documented, and every staff member has their own login with multi-factor sign-in. If two or more of these are missing, fix them before the cutover date.
Use the scorecard below on a normal busy morning, not on a quiet afternoon. Speed tests at 4 p.m. hide the problems that appear when ten people open charts and images at 8 a.m.
| Check | Ready looks like | Source of the figure |
|---|---|---|
| Internet speed | Meets the chosen vendor's figure, multiplied by workstations where the vendor says so; for example 20 Mbps down and 10 up per workstation for Open Dental Cloud | Vendor requirement pages, read October 25, 2026 |
| Type of connection | Wired business broadband or fiber; Curve says satellite and wireless service are not recommended | Curve system requirements |
| Second internet line | A different provider or technology that takes over automatically | Your outage plan |
| Firewall and router | Business-grade, supported, firmware current, able to switch to the second line | Your IT provider |
| Operating system | Windows 11 on every PC; Microsoft ended Windows 10 support on October 14, 2025 | Microsoft |
| Browser | The vendor's supported browser, current version (Chrome for Curve; Chrome or Edge for Denticon) | Vendor requirement pages |
| Imaging PCs | Each capture PC listed with its sensor, driver version and bridge client | Your equipment list |
| Staff logins | One account per person, multi-factor sign-in, accounts removed the day someone leaves | Your access policy |
| Printers and scanners | Every device listed with its driver and a test print from the new system | Your equipment list |
| Local files | Shared folders, scanned documents and old archives found and assigned a home | Your data audit |
Two rows deserve extra attention. Microsoft says Windows 10 support has ended, so old PCs that the server used to hide become your biggest risk when everything runs through a browser. And internet speed is not just a number on a bill: Wi-Fi, an old router or a busy guest network can cut what each workstation really gets. Our guide to dental software system requirements covers the computer side, and dental office network design covers the wiring and connection behind it.
What happens to imaging and bridges in a cloud setup?
Imaging rarely moves to the cloud as completely as the schedule does. Sensors and intraoral cameras still plug into a local computer with drivers and a capture app or bridge client. CBCT and 3D files are large, so many practices keep a local imaging computer. Plan imaging first; it is what most often slows a cutover.
Each vendor handles this differently, and the details come from their own pages. Open Dental says Open Dental Cloud "requires the OpenDentalCloudClient to launch third-party integrations", and that the client gives Open Dental access to TWAIN drivers for acquiring images. Curve says Curve Capture "requires direct, local access to imaging devices" and is not supported on terminal servers. Archy describes native Schick integration and TWAIN compatibility so existing sensors can be used. Dentrix Ascend and tab32 describe imaging built into the platform.
What this means for your IT:
- List every imaging device. Sensor make and model, the PC it plugs into, the driver version, and the software that captures the image today.
- Ask how each one connects. Native integration, TWAIN, a bridge to third-party imaging software, or not supported. Get the answer in writing for each device.
- Decide where large files live. If you take CBCT scans, ask whether the vendor stores them, whether your 3D viewer stays local, and how the two link.
- Test on one operatory first. Capture, view and re-open an image from a second workstation before the cutover.
- Plan for slow images. Image-heavy screens are where a weak connection shows first.
When bridges misbehave after a move, the cause is usually the local client, a driver or a Windows update rather than the cloud itself. Our guide to dental imaging integration troubleshooting walks through those checks, and the same diagnosis applies when people ask why Open Dental is slow on a local network.
What happens when the cloud system or the clearinghouse is down?
When a cloud practice management system is down, nobody can open the schedule, charts or ledger until the vendor restores it or your internet returns. Claims can also stop when a clearinghouse has trouble, even if the software is up. Every cloud system has outages, so the practice needs a written plan for the day.
This is not a criticism of any vendor; it is the trade you make for not running a server. Planet DDS publishes its incidents on a public status page, which shows what these events look like. On September 11, 2026 it reported that "some users may be experiencing difficulty in accessing Denticon", resolved about 13 minutes later. On September 28, 2026 it reported that its clearinghouse partner DentalXChange was "undergoing an incident" affecting claims and attachments in Denticon and Cloud 9, with "No workaround is available while the vendor investigates"; the incident was marked resolved a little over two hours later. Publishing incidents openly is useful to customers, and it is a good question to ask any vendor: where do we see your status?
There are two kinds of outage to plan for. In the first, your own internet fails while the vendor is fine; a second line fixes most of it. In the second, the vendor or one of its partners has a problem; no amount of internet helps, so paper and patience do.
Outage playbook for cloud dental software
- Before any outage: print or save tomorrow's schedule each evening, with patient phone numbers, to a file on a local PC.
- Before any outage: keep blank paper forms for exam notes, treatment, payments and new patients in a labeled folder at the front desk.
- Before any outage: install a second internet line from a different provider, set to take over automatically, and test it once a quarter.
- Before any outage: bookmark the vendor's status page and its clearinghouse's status page on every front-desk PC.
- In the first 10 minutes: check whether other websites load. If they do not, it is your internet; switch to the backup line or call your IT provider.
- In the first 10 minutes: if the internet works but the software does not, check the vendor's status page before anyone reboots anything.
- During the outage: see scheduled patients from the printed list, write notes on paper, and take card payments on a standalone terminal if you have one.
- During the outage: if only claims are down, keep treating and queue claims for later; do not re-send the same claim repeatedly.
- Afterwards: enter paper notes and payments into the system the same day, and file the paper as your records policy says.
- Afterwards: write two lines on what happened, how long it lasted and what you would change, and review them with your IT provider.
The HIPAA Security Rule's contingency plan standard asks practices to have an "Emergency mode operation plan", described as procedures "to enable continuation of critical business processes for protection of the security of electronic protected health information while operating in emergency mode" (45 CFR 164.308(a)(7)). A cloud outage is one of the situations that plan is for. If the problem is your own connection, our guide to what to do when the dental office internet is down covers the first hour step by step.
Does the cloud vendor's backup replace your own?
Not completely. The vendor's backups protect its copy of your database, which is useful, but they do not cover the images, scans and documents still in your office, and they are not under your control if you leave. Keep your own backups of local data, and know how you would get a copy of the cloud data.
Open Dental, for example, says of Open Dental Cloud that "The backups are encrypted, tested for integrity nightly, and stored off-site", and that it restores the most recent backup to a new server if one fails. That is a real benefit, and it removes the daily backup job most practices did badly on their own server. But the Security Rule asks practices to "Establish and implement procedures to create and maintain retrievable exact copies of electronic protected health information" and to "restore any loss of data" (45 CFR 164.308(a)(7)). The practice still needs to know where every copy is.
What usually stays local after a cloud move, and still needs a backup:
- CBCT and 3D scan files, and any local imaging archive.
- Intraoral scanner files and lab case files.
- Scanned paper documents and consent forms kept in shared folders.
- The retired server's database, kept read-only for a period after the move.
- Spreadsheets, reports and exports the team saves to desktops.
The vendor's backup and yours answer different questions. Theirs answers "can the service recover from a failure?"; yours answers "can the practice recover its own records if the service, the contract or a local machine is lost?". Our dental backup and recovery service page covers the local side, and the dental backup and disaster recovery checklist helps you test it.
Who owns your data in cloud dental software, and how do you get it out?
The practice remains responsible for its patient records, but the vendor holds the database, so getting a full copy depends on the contract. Before you sign, ask what export the vendor provides, in what format, how often, at what cost and for how long after cancellation. HHS names the return of data as an item a cloud agreement can cover.
Exit terms are the least published part of every product in the comparison table. A few vendors say something useful. Open Dental says a practice can "easily switch from Cloud to Local host or vice-versa". Archy describes how it brings data in: a trial data extraction, then a sample account with your converted data so you can audit it before the final conversion. Neither of those is a promise about leaving, which is why the questions below matter.
Ask each vendor, and keep the answers with the contract:
- Can we download a complete copy of our database, including images and documents, whenever we want, or only on request?
- What format is the export in, and has another vendor converted from it before?
- Is there a fee for an export, and how many can we have during a migration away?
- How long after cancellation can we still sign in and export?
- Where is our data stored, and in which country are the servers?
- Will you sign a BAA, and what does it say about returning or destroying data at the end?
If the answers are vague, treat that as information. A system you cannot leave cleanly is harder to manage than a server you own, however good the software is.
What does cloud dental software cost compared with replacing a server?
Cloud dental software turns a large, occasional server purchase into a monthly subscription, but the subscription is not the whole cost. Add migration and conversion fees, training time, internet upgrades, a second line, newer workstations and imaging changes, then compare that with a new server, its licenses, its backup and the IT time to run it.
Only one of the six vendors we read publishes its cloud prices. As read on October 25, 2026, Open Dental's fee page lists a US support fee of $199 per month per location for the first 12 months (offices that started before February 2, 2026 at $179 keep that rate for their first 12 months), with a reduced rate of $149 after 12 consecutive months. Its Open Dental Cloud page lists hosting plans from $250 per month for 7 concurrent sessions and a $400 one-time migration fee, and the fee page says cloud fees are "in addition to" the license and support fees. For Dentrix Ascend, Curve and Denticon we did not find a price on the vendors' own pages, so ask each for a written quote that names every item in the table below.
| Cost category | Server refresh (stay on premises) | Cloud subscription | One-time move to cloud |
|---|---|---|---|
| Software | Existing licenses and annual support | Monthly fee per location, provider or session | Conversion or migration fee |
| Hardware | New server, storage, a battery backup unit | Fewer servers; maybe a local imaging box | Replacing PCs that fail the vendor's requirements |
| Internet | Existing line is often enough | Faster primary line and a second line | Installation of the second line |
| Backups | Local and off-site backup of the server | Vendor backup plus backup of local files | Archiving the old server's data |
| IT time | Patching, monitoring and backups of the server | Workstations, network, accounts, bridges | Data audit, testing, cutover weekend |
| Staff time | None beyond normal | Ongoing learning of updates | Training and a slower first few weeks |
| Exit | Data stays on your server | Export fees or terms, if any | Not applicable |
The fairest comparison runs over five years, the usual life of a server, and counts staff time honestly. Our guide to dental software migration cost and timeline shows how to build that comparison without guessing.
Does Texas SB 1188 affect where your cloud dental data is stored?
Texas Senate Bill 1188 added chapter 183 to the Health and Safety Code. It requires covered entities to keep electronic health records with patient information "physically maintained in the United States or a territory of the United States", including in the cloud, for records stored from January 1, 2026. How it applies to your practice is a question for counsel.
The Act took effect on September 1, 2025. Its storage rule applies to the storage of an electronic health record on or after January 1, 2026, whenever the record was prepared. Confirm with counsel how it applies to your practice.
The enrolled bill text defines the covered entity by reference to section 181.001 and says the term "includes a health care practitioner", which it defines as a person "licensed, certified, or otherwise authorized to provide health care services in this state". Section 183.002 extends the storage rule to records stored by a "third-party or subcontracted computing facility" or an entity providing "cloud computing services". The same chapter also says a covered entity "may not collect, store, or share any information regarding an individual's credit score" or voter registration status in the record. We quote the statute; we do not interpret it for your practice.
Some vendors have published notes on the law. Open Dental's Texas regulatory page says "Any Protected Health Information (PHI) stored by Open Dental from US-based customers is maintained in the United States." HHS, for its part, says HIPAA itself allows a cloud provider that stores patient data outside the United States, provided a BAA is in place and the practice otherwise follows the HIPAA Rules, while noting that offshore storage "may increase the risks". Texas practices now have a state rule on top.
Questions to ask your cloud vendor about data location:
- In which countries are our database, images, backups and disaster-recovery copies stored?
- Do any subcontractors store or process our data outside the United States?
- Will you put the storage location in writing, in the contract or the BAA?
- Do any credit-score or voter-registration fields exist in the system, and can they be turned off?
- How will you tell us if the storage location changes?
How do you move to cloud dental software without losing a day?
Treat the move as a project with six stages: decide, audit your data, let the vendor convert it, test in parallel, cut over on a weekend, and retire the old server safely. The vendor converts the database; the practice and its IT prepare the office, check the converted data, set up every workstation and keep old data reachable.
Six stages of a move to cloud dental software
- 1DecideWeeks 1–2Choose the system, sign the contract and BAA, and record the export and data-location answers in writing.
- 2Data auditWeeks 2–4List every database, imaging archive, shared folder, bridge and printer the old server touches, and decide where each one goes.
- 3Vendor conversionWeeks 4–8Give the vendor access for a trial conversion, then check a sample of patients, balances, appointments and images against the old system.
- 4Parallel testWeeks 6–9Set up workstations, browsers, bridge clients and imaging on a test operatory, train the team, and run real tasks side by side.
- 5Cutover weekendWeek 10Final conversion while the office is closed, then a checklist of logins, images, printers and claims before Monday's first patient.
- 6Retire the serverWeeks 10–16Keep the old server read-only for a set period, take a final backup, then wipe or destroy its drives and record how.
Timing varies by vendor and practice size; the weeks above are an example to plan around, not a vendor commitment. The two stages practices most often rush are the data audit and the parallel test, and they are the two that prevent a bad Monday. For the detail behind each stage, use our cutover plan for a practice management software switch, the dental software migration checklist, and, if you are leaving an office Dentrix server, the Dentrix server migration checklist.
Retiring the server deserves its own line on the plan. It may still hold years of patient data, old images and scanned documents. Keep it powered off but recoverable until you are sure nothing is missing, take a final backup, and dispose of the drives securely with a record of what was done.
Why do practices still need dental IT consulting after moving to the cloud?
Because the cloud moves one server, not the rest of the office. Someone still has to test the internet, patch workstations and imaging PCs, manage staff accounts and multi-factor sign-in, back up local files, run the outage plan and read the vendor's terms. Dental IT consulting plans that work; ongoing IT support does it day to day.
Dental IT consulting and cloud software work together. A cloud vendor answers questions about its software. It does not usually look at your router, your sensor drivers, the receptionist's six-year-old PC or the scanner that stopped working after an update. Those questions land on whoever looks after the office's technology.
In practice, the IT work after a cloud move tends to shift rather than shrink:
- Less server work: no database patches, no server backups, no server hardware to replace.
- More network work: a second line, failover testing, Wi-Fi that keeps up with image-heavy screens.
- More workstation work: every PC is now the front door to patient data, so updates, browser versions and security tools matter more.
- More account work: cloud sign-ins can be reached from anywhere, so joiners, leavers and multi-factor sign-in need a routine.
- Ongoing vendor coordination: status pages, release notes and bridge updates have to be watched by someone.
AI features are arriving inside cloud dental software too: scheduling suggestions, claim checks, imaging analysis and note drafting. Each one is another place patient data travels, so the same questions apply about who can see the data and whether a business associate agreement covers it. We cover those questions in AI tools in dental practices and their HIPAA risk.
That is why many practices pair a cloud system with managed IT services for dentists, and why the dental workstations and servers side of the office still needs a plan even when the main server is gone.
What to ask your IT provider about cloud dental software
Your IT provider should be able to answer these before you sign with a cloud vendor, and in writing. If it cannot, the move will expose the gaps on the first busy Monday.
Internet and network
- Does our internet meet the vendor's published figure for the number of workstations we have, on a busy morning?
- Do we have a second internet line from a different provider, and does it take over automatically?
- Is our firewall and router supported, current and able to handle the switch?
Computers and imaging
- Which of our PCs fail the vendor's requirements, including Windows 11 and the supported browser?
- Which imaging devices, bridges and drivers will work with the new system, and which need replacing?
- Where will CBCT and other large imaging files live after the move?
Accounts and security
- How will staff accounts, multi-factor sign-in and leaver removal work in the new system?
- Which security tools protect the workstations that now open patient data in a browser?
Backups, data and contracts
- What local data still needs backing up after the move, and how will you test the restore?
- Have you read the vendor's export and data-location terms, and what did you find?
- Where is the signed BAA filed?
Cutover and outages
- Who runs the data audit and the parallel test, and who is on hand for the cutover weekend?
- What is our written outage plan, and when will we test it?
- How will the old server be retired and its drives disposed of?
How Legend Networking can help
Legend Networking is a dental IT provider. We have served over 3,500 practices since 2004, and we support the IT environment of practices running Dentrix, Eaglesoft, Open Dental and Archy, and imaging systems including DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging. The office side of a cloud move is the work we do: the network, workstations, imaging PCs, accounts, backups of local data and 24/7 monitoring of the systems we manage.
- How we work: in-house engineers; no outsourced first-level triage.
- On Google: 4.8 rating · 173 Google reviews.
- Who leads it: Ian Lynch, 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps.
This guide does not recommend one cloud product over another. If you are comparing systems, the requirement pages and quotes the vendors give you are the most useful things to bring to that first conversation.

Ask for a review of your practice before a cloud dental software move
If a server replacement or a vendor demo has put cloud dental software on the table, ask us for a Free Dental IT Assessment before you sign. Tell us which systems you are considering and we will review your office with you. Start with our dental cloud services, or call 1-800-794-1588.
Frequently asked questions
What is cloud dental software?
Cloud dental software, sometimes called a cloud dental solution, is practice management software that runs in the vendor's data center rather than on a server in your office. Your team opens it through a browser or a small app over the internet. Scheduling, charting and billing move to the cloud, while workstations, imaging devices, printers and the internet connection stay the practice's responsibility.
What are the benefits of cloud based dental practice management software?
The main benefits are no practice-management server to buy or patch, access from any location with internet, vendor-run database backups and updates, and one system for several offices. The trade-offs are dependence on the internet and the vendor, a monthly subscription, and a data conversion with retraining. It suits practices whose internet, computers and imaging are ready.
Can a dental practice run with no server in the office?
Often, but not always. A cloud practice management system removes the main database server. Many practices still keep a local computer or small server for CBCT and 3D imaging files, imaging software, scanned documents or an archive of the old system. Plan where each of those will live before you retire the server, and back up whatever stays local.
What happens to cloud dental software when the internet goes down?
If your office internet fails, staff cannot open the schedule, charts or ledger until the connection returns, unless a second internet line takes over. Some systems offer limited offline features such as x-ray capture. Keep a printed or saved schedule for the next day, paper forms at the front desk, and a written outage plan that the team has practiced.
Is patient data safe in cloud-based dental software?
It can be well protected, but safety depends on both sides. HHS treats a cloud provider holding patient data as a business associate, so the vendor should sign a BAA. The practice still controls user accounts, multi-factor sign-in, workstation security and who sees what. Read the BAA and service terms, and keep local devices patched and secured.
Does the cloud vendor's backup replace our own backups?
Not completely. The vendor backs up its copy of your database, which protects against failures on its side. It does not cover CBCT files, scanned documents or other data still in your office, and it is not under your control if you leave. Keep your own backups of local data and know how to obtain a full export.
Does Texas SB 1188 apply to dental practices using cloud software?
The statute's covered entity "includes a health care practitioner", defined as a person licensed or otherwise authorized to provide health care services in Texas. Its storage rule requires electronic health records stored on or after January 1, 2026 to be kept in the United States or its territories, including cloud storage. Confirm with counsel how it applies to your practice.
What is the difference between Dentrix and Dentrix Ascend?
Dentrix is installed on a server and workstations in the office. Dentrix Ascend is Henry Schein One's cloud system, used through the internet, which the company calls a native cloud platform. Moving from one to the other is a change of system: new logins, a data conversion, a new imaging workflow and staff retraining, rather than a simple upgrade.
How much does cloud dental software cost?
It depends on the vendor, the number of locations, providers or sessions, and add-ons. As read on October 25, 2026, Open Dental publishes cloud hosting from $250 per month plus its support fee and a $400 migration fee. Dentrix Ascend, Curve and Denticon did not publish prices on the pages we read, so ask for written quotes.
Why do dental practices still need IT support after moving to the cloud?
The cloud vendor runs its software, not your office. Someone still has to manage the internet and a backup line, keep workstations and imaging PCs updated, set up bridges and drivers, control staff accounts, back up local files and run the outage plan. Dental IT consulting plans that work; ongoing IT support keeps it running day to day.

