Orthodontic Practice Management Software Compared: Cloud vs Server, and What Each Needs From Your IT
The renewal notice from your practice software vendor is on your desk, a cloud vendor's demo is booked for Thursday, and your server closet hums the way it has for years. Someone on the team says the cloud version "just works anywhere." Someone else remembers the morning the internet went down and nobody could see the schedule. Before you sign anything, you want to know what each choice will ask of your office.
This guide compares those systems by what each one needs from your IT, using the vendors' own requirement documents: servers and SQL editions, internet per workstation, remote offices, imaging capture and Macs. It sits inside our orthodontic practice technology guide, and the computers, network and backups around the software are what our dental IT support covers. It is written by Ian Lynch, who has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps at Legend Networking. It covers practice management systems only; treatment-planning and aligner-design software is a different category with different hardware needs.
Orthodontic practice management software runs the schedule, contracts, treatment chart and imaging links of an ortho office. The main orthodontic software programs are Dolphin Management, OrthoTrac, Cloud 9, Ortho2 Edge Cloud, Greyfinch, topsOrtho and WaveOrtho. The biggest IT difference between them is where they run: on a server in your office, or in the vendor's cloud.
- The biggest IT difference between orthodontic practice management systems is where they run: OrthoTrac and on-premise Dolphin Management need a Windows server with SQL Server, while Cloud 9, Greyfinch, topsOrtho, Edge Cloud, Sensei Cloud and Dolphin Cloud run in the vendor's cloud; WaveOrtho offers both.
- Cloud 9 asks for at least 1 Mb/s download and 0.5 Mb/s upload per computer, a dedicated connection per office and a static IP; Dolphin Cloud asks for 25x5 Mbps for five logins or fewer, at least 50x10 for 5 to 15 workstations and latency below 85 ms.
- Dolphin's and OrthoTrac's minimum database is still SQL Server 2016, whose extended support ended on July 14, 2026; Windows Server 2016 follows on January 12, 2027.
- Cloud systems still need local capture: Cloud 9's C9 Agent and Dolphin Cloud's TSScan run on Windows PCs with TWAIN drivers, and CBCT or non-TWAIN X-rays may need local imaging software.
- When switching ortho software, confirm in writing whether image conversion is included, and test contracts, payment plans, capture agents and Office versions before the cutover weekend.
In this guide
- Which orthodontic practice management systems are there in 2026?
- Which orthodontic software runs in the cloud, and which needs a server?
- Cloud or server: which fits your practice?
- What does a cloud ortho PMS need from your office?
- What does a server ortho PMS need?
- What happens when the internet or the server goes down, and how do you drill it?
- Switching ortho software: what moves, what doesn't, and the cutover weekend
- What to ask your IT provider about a practice-software change
- Orthodontic offices Legend has set up
- What does IT cost around a PMS change?
- Frequently asked questions
- The bottom line
Which orthodontic practice management systems are there in 2026?
The orthodontic practice management systems this guide compares are Dolphin Management, OrthoTrac (with its cloud successor, Sensei Cloud), Cloud 9, Ortho2's Edge Cloud, Greyfinch, topsOrtho and WaveOrtho. Some run on a server in your office, some run only in the vendor's cloud, and two offer both. That split matters more to your IT than any feature list.
The table below is a shortlist, not a ranking. Every cell comes from the vendor's own page or requirements document, read on October 26, 2026. Where a vendor publishes nothing on a point, the table says so.
| System | Vendor | How it is deployed | Runs on | Vendor source |
|---|---|---|---|---|
| Dolphin Management | Dolphin Imaging & Management Solutions | On a Windows server in your office, or hosted as Dolphin Cloud | Windows workstations; Intel Macs through Boot Camp, Parallels or VMware Fusion | Dolphin System Requirements, rev. 06/25 |
| Dolphin Cloud and Dolphin Blue | Dolphin Imaging & Management Solutions | Hosted by Dolphin, "without the need of a local server" | Windows or Mac (Dolphin Cloud); most devices (Blue) | Dolphin cloud apps page |
| OrthoTrac | Carestream Dental (a Sensei product) | Server-based, on premise | Windows 11 Professional workstations | OrthoTrac v15.7 requirements |
| Sensei Cloud | Carestream Dental (Sensei) | Cloud, "no on-site server required" | Browser and apps | Sensei OrthoTrac FAQ |
| Cloud 9 | Planet DDS | Cloud, in the browser | Windows 11, macOS 12 or later, iPad, Android | Cloud 9 System Requirements |
| Edge Cloud | Ortho2 | Cloud-hosted; an application installed on each computer | Computers and tablets | Edge Cloud FAQ |
| Greyfinch | Greyfinch | "100% web-based and cloud-based" | Any device with a browser | Greyfinch |
| topsOrtho | topsOrtho | Cloud-based | Described as "Mac-based" | topsOrtho |
| WaveOrtho | WaveOrtho | "Cloud-hosted by us, or self-hosted on your own server" | Mac, Windows, iPad, iPhone and browser | WaveOrtho |
Two notes on reading the table. First, Dolphin Management is the practice-management module of the Dolphin suite, the same family as Dolphin Imaging; for Dolphin servers and day-to-day support, see our page on Dolphin Imaging and Management IT support. Second, if your office is a general dental practice or a mixed group comparing Dentrix, Eaglesoft or Open Dental, our guide to general dental practice management software covers that list.
What the table cannot tell you is which system is right. That depends on three things this guide walks through: whether your server and SQL are near the end of support, whether every office has an internet line that can carry a cloud system, and how your X-rays, photos and CBCT get into the chart.
Which orthodontic software runs in the cloud, and which needs a server?
Cloud 9, Greyfinch, topsOrtho, Edge Cloud, Sensei Cloud and Dolphin Cloud run in the vendor's cloud, so the practice software needs no server in your office. OrthoTrac and on-premise Dolphin Management need a Windows server with SQL Server. WaveOrtho offers both. Even cloud systems still need local capture software for X-rays and scanners.
This is the deployment matrix: the grid most comparison pages leave out. Fill in the rows for the two or three systems on your shortlist and send any "not published" cell to the vendor as a written question before you sign.
| System | Server and SQL | Internet the vendor publishes | Remote or satellite office | Imaging capture in the office |
|---|---|---|---|---|
| Dolphin Management (on premise) | Windows Server 2016 Standard minimum, 2022 Standard recommended (Windows 11 only for standalone or five users or fewer); SQL Server 2016 (SP3) Express minimum, SQL Server 2022 Standard recommended; a domain when a server OS is used | Main office 1.5MB down / 512K up; remote workstations 768K/768K for 1–5 and 2.0MB/2.0MB for 5–12 (Dolphin's notation) | "Dolphin Management must be connected via Remote Desktop Services"; capturing images at the remote office needs a local PC and a VPN | Dolphin Imaging on local workstations |
| Dolphin Cloud | No local server | 25 Mbps down x 5 up for 5 logins or fewer; at least 50x10 for 5–15 workstations; 100x20 "may be ideal" for 15 or more; latency below 85 ms | "supports multiple offices" | TSScan agent on a Windows PC for TWAIN devices; non-TWAIN X-ray or CBCT may need Dolphin Imaging run locally |
| OrthoTrac v15.7 | Dedicated server recommended; Windows Server 2022 Standard with SQL Server 2022 Express recommended, Server 2016 with SQL 2016 Express minimum; Small Business Server and Essentials not supported | On premise, "does not require internet connectivity except for integrated services" (Carestream); "High speed broadband" for eClaims, statements, ePayments and verifications | "Remote access requires connecting via a VPN session" (Carestream) | CS Orthodontic Imaging (separate requirements); TWAIN document scanners, network scanners not supported |
| Sensei Cloud | No on-site server | Not published on the page read (ask the vendor) | Described as accessible "from anywhere" | Not published on the page read (ask the vendor) |
| Cloud 9 | No server for the practice software | At least 1 Mb/s down and 0.5 Mb/s up per computer; each office its own dedicated connection; static IP during office hours | Each office on its own internet connection; VPN not recommended; thin clients not supported | C9 Agent with the device's TWAIN driver, Windows only; Cloud 9 does not store 3D images or models |
| Edge Cloud | "No need for a server" | 100 Mbps down and 20 Mbps up or more recommended; more than 25 Mbps down and 5 Mbps up minimum; latency under 100 ms (Edge Cloud System Guidelines) | Supports multiple offices and providers | Most TWAIN-compliant radiography works; Acteon scanners not supported |
| Greyfinch | No server | Not published (ask the vendor) | Browser access from any location | Not published (ask the vendor) |
| topsOrtho | No server (cloud) | Not published (ask the vendor) | Not published (ask the vendor) | Not published (ask the vendor) |
| WaveOrtho | None if cloud-hosted; your own server if self-hosted, specs not published | Not published (ask the vendor) | Access "from any office" | Not published (ask the vendor) |
Sources for each row are the vendor documents linked in the systems table above. Figures are each vendor's own minimums or recommendations as published on October 26, 2026; requirement sheets change, so check the current version before you buy hardware.
A blank row for your own shortlist looks like this: system name · server and SQL edition, or none · internet per workstation and per office · how a second office connects · how X-rays, photos and scans reach the chart · who answers when capture breaks. If the vendor cannot fill a cell in writing, treat it as unknown.
Cloud 9 vs Dolphin: what each needs from your IT
When Cloud 9 and Dolphin are on the same shortlist, they sit at opposite ends of the matrix. Cloud 9 removes the server but leans on every office's internet line. On-premise Dolphin keeps working inside the office when the internet drops, but needs a properly licensed Windows server, SQL Server and a domain. Dolphin Cloud sits between the two.
| What your IT has to provide | Cloud 9 | Dolphin Management (on premise) | Dolphin Cloud |
|---|---|---|---|
| Where it runs | Planet DDS's cloud, in the browser | Your Windows server | Dolphin's hosted environment |
| Server and SQL | None for the practice software | Windows Server 2016 Standard minimum, 2022 Standard recommended; "We do not support Windows Server Essentials editions"; SQL Server 2016 (SP3) Express minimum, SQL 2022 Standard recommended; a domain, plus Microsoft client access licenses for each station | None |
| Internet | 1 Mb/s down and 0.5 Mb/s up per computer, minimum; dedicated line per office; static IP during office hours | Main office 1.5MB/512K or faster; matters mainly for remote offices | 25x5 Mbps (5 logins or fewer) to 100x20 (15+ workstations), reserved for Dolphin |
| Remote or satellite office | Its own internet line; VPN not recommended | Remote Desktop Services, "not supported running through a WAN directly"; a separate RDS server is recommended in an SBS network | Connects over the internet like the main office |
| Imaging capture | C9 Agent plus TWAIN driver, Windows only | Dolphin Imaging on each capture workstation | TSScan agent on Windows; local Dolphin Imaging for non-TWAIN X-ray or CBCT |
| Mac | macOS 12 or later in the browser; the C9 Agent and TWAIN capture are not available on Mac | Intel Macs only, through Boot Camp, Parallels or VMware Fusion; Apple M-series "not been validated" | Native macOS through Microsoft Remote Desktop |
If your team already runs Dolphin Imaging for records and cephalometrics, that capture setup stays in the office whichever practice software you choose, and Legend supports the IT environment for Dolphin Imaging.
Cloud or server: which fits your practice?
Choose cloud when your server is near the end of support, every office can get a dedicated line plus a backup line, and doctors want Mac or home access. Choose a server when your internet is unreliable or you capture CBCT and non-TWAIN X-rays in-house. Some ortho offices end up hybrid: cloud software with local imaging.
Answer these five questions for your main office first, then for each satellite. Three or more answers in one column is a strong lean; a split usually means a hybrid setup.
| Question | Points to cloud | Points to a server |
|---|---|---|
| 1. Is your server or SQL at or near the end of support? (dates in the server section below) | Yes: the replacement money can go to a subscription instead | No: the server is current and under warranty |
| 2. Can every office get a dedicated internet line, preferably cable or fiber, plus a second provider that fails over? | Yes, at every office | No, or one office is on a slow or shared line |
| 3. Do doctors need to work from a Mac or from home? | Yes | No, everyone works on office Windows PCs |
| 4. Do you capture CBCT or non-TWAIN X-rays in the office? | No, or the capture can stay local alongside cloud software | Yes, and you want imaging and practice data on one local server |
| 5. Do you plan to add offices in the next few years? | Yes: cloud systems connect offices over the internet | No, one office for the foreseeable future |
Two cautions. A cloud system does not remove local IT work: capture PCs, printers, the network and the internet line become more important, not less. And a server system is only as safe as its backups and patches, so the "keep the server" answer includes a plan to replace it before its operating system and SQL edition run out. For the general dental version of this decision, see replace the server or move to the cloud.
Not sure your server, SQL or internet can carry the system you're choosing? A Free Dental IT Assessment gives you written findings and prioritized recommendations on your computers, software, network security, backups and performance.
What does a cloud ortho PMS need from your office?
A cloud orthodontic PMS needs a fast, dedicated internet line at each office, a second line that fails over, Windows 11 or current macOS workstations, and a Windows PC with the vendor's capture agent for every X-ray unit and scanner. The vendor runs the server; your office runs everything between the chair and the internet.
Internet: the line becomes the server cable
Cloud 9's requirements page sets the floor most clearly: "1 Mb/s download rate for each computer and 0.5 Mb/s upload per computer are our minimum recommendations." Each office "requires its own dedicated connection to the Internet," the office IP "needs to be static during office hours," and offices on DSL or T1 "should consider switching to cable service." The same page says Cloud 9 "recommends, but does not require" a secondary internet provider and that the two "should not be using the same connection type."
Dolphin Cloud publishes tiers rather than a per-computer figure, and adds a warning worth taping to the network cabinet: the speeds "are meant to be always available for Dolphin Cloud use and do not account for any other needs in the office." Its requirements also say network latency to Dolphin Cloud "should be below 85 msec ideally at all times," and that "A single Ring Video Camera in highest resolution can consume nearly all the upload bandwidth from a Practice without them even realizing it."
Ortho2's Edge Cloud System Guidelines recommend 100 Mbps download and 20 Mbps upload or more, with latency under 100 ms, and set the minimum at more than 25 Mbps down and 5 Mbps up. Ortho2 adds that "meeting minimum Internet speeds results in minimally acceptable performance." Greyfinch, topsOrtho and WaveOrtho publish no figure on the pages we read. For those, ask the vendor for a per-workstation number in writing.
Before a cloud PMS goes live in an office
- A dedicated business internet line at each office, with the upload speed the vendor publishes for your workstation count
- A second internet provider on a different connection type, with a firewall that fails over between them
- A static IP address during office hours, if the vendor requires one (Cloud 9 does), and a written answer on whether the backup line's address must be registered too
- Quality-of-service rules so VoIP phones, cameras and guest Wi-Fi cannot starve the practice software
- Security cameras set to a resolution and upload schedule that leaves room for the PMS
- Workstations on Windows 11 or a current macOS, with the browser the vendor recommends
- A Windows PC for every X-ray unit, photo station and document scanner that needs the capture agent and TWAIN driver
- Clinical cameras set to the photo size the vendor recommends (Dolphin Cloud suggests about 3 megapixels, 2000 x 1500)
- A written list of what still lives locally: capture software, CBCT viewers, printers and label printers
Worked example: a 12-workstation office
This is an example; use your vendor's current figures. A 12-workstation office on Cloud 9 needs at least 12 Mb/s down and 6 Mb/s up for the practice software alone, because Cloud 9's minimum is per computer. Add scanners and phones on top.
| Load on the internet line | Download | Upload | Source of the figure |
|---|---|---|---|
| Cloud 9, 12 computers at the published minimum | 12 Mb/s | 6 Mb/s | Cloud 9 System Requirements (1 down, 0.5 up per computer) |
| Two iTero scanners | not published | 2 Mb/s | Align's iTero Element 5D manual: "upload speed is at least 1Mbps per scanner" |
| VoIP phones | your provider's figure | your provider's figure | Ask the phone provider for its per-call figure |
| Security cameras, guest Wi-Fi, streaming in the waiting room | measure it | measure it | Your firewall's traffic report |
| Same office on Dolphin Cloud instead | at least 50 Mbps | at least 10 Mbps | Dolphin requirements, 5–15 workstations, reserved for Dolphin |
The point of the exercise is the last two rows. The practice software is not the only heavy user of the line, and Dolphin's own document warns that a single Ring video camera at its highest resolution can take nearly all of a practice's upload. Cloud 9 says it does not expect larger offices to need more than 20 Mb/s of upload, and Dolphin says that once there is enough bandwidth for its sessions, more "will not change the speed." Buy the line for the whole office, then reserve a share for the practice software. Scanner bandwidth and Wi-Fi placement are covered in our guide to scanner upload and Wi-Fi requirements.
Workstations and imaging capture still live in the office
Cloud 9 lists 4 GB of RAM as the minimum and 8 GB as recommended, with Windows 11 or Apple OS X 12 and later; it still lists Windows 10 as "Valid until Oct 14, 2025," the date Microsoft ended Windows 10 support. The part to plan for is capture. Cloud 9's C9 Agent "must be installed with the appropriate TWAIN driver" to acquire X-rays and scans directly, the agent is not compatible with Mac, and "Cloud 9 currently does not store 3D images or models." Dolphin Cloud uses a small agent called TSScan for TWAIN pan and ceph units, and says a capture workstation may need Dolphin Imaging run locally for "non-TWAIN compliant X-ray machines or CBCT acquisition." Edge Cloud is "application-based software" installed on each computer, and lists Dolphin Imaging among its imaging partners.
So a cloud move still needs a capture plan per device. For how cloud software changes things in a general dental office, see cloud dental software (general dentistry).
What does a server ortho PMS need?
Beyond the smallest standalone setups, a server-based ortho PMS needs a dedicated Windows Server Standard machine (not Essentials), a supported SQL Server edition sized to your workstation count, a domain, client access licenses, gigabit wiring, SSD storage and a nightly backup that runs after the vendor's database backup step where it has one (OrthoTrac does). Built to the published minimums, that server runs a database edition Microsoft no longer supports.
Dolphin Management on premise
Dolphin's requirements document (rev. 06/25) sets out the server in a few lines. Keep this list next to any server quote:
- Operating system: "Window Server 2016 Standard" minimum, Windows Server 2022 Standard recommended (Windows 11 is accepted only for a standalone setup or five concurrent users or fewer); "We do not support Windows Server Essentials editions." When a server operating system is used, "a Domain is required," with Microsoft client access licenses for each station, and Dolphin "is not designed to work in a multi-domain environment."
- Database: Microsoft SQL Server 2016 (SP3) Express minimum, for a standalone setup or five concurrent users or fewer; SQL Server 2022 Standard recommended.
- Hardware and network: 4 GB RAM minimum, 16 GB or more recommended; an "SSD RAID controller disk highly recommended"; and "Dolphin requires a minimum of Fast Ethernet (100 Mbps). Note: Dolphin recommends 1 Gigabit (1000 Mbps)."
- Backups and remote offices: "You are responsible for making proper backups of your Dolphin data," including database, images, documents and letter templates, with offsite copies. Remote offices connect through Remote Desktop Services; Dolphin recommends 256MB RAM for each remote connection and two servers above 10 simultaneous remote connections, and limits each database to 25 locations.
More detail on running Dolphin servers sits on our Dolphin Imaging and Management IT support page.
OrthoTrac v15.7
Carestream's OrthoTrac v15.7 requirements recommend "using a dedicated server to run OrthoTrac," with Windows Server 2022 Standard and SQL Server 2022 Express on an x64 Core i7 quad-core, 16 GB RAM, 500 GB of free disk and a Gigabit network card. The minimum is a Core i5, 8 GB RAM, 100 GB and Windows Server 2016 Standard with SQL Server 2016 Express. "Small Business Server or Windows Server Essentials are not supported." Workstations run Windows 11 Professional, and OrthoTrac "is not certified for use on virtual machines or emulated operating systems."
Two lines in the same document catch offices out. Microsoft Office integration supports 32-bit Professional versions only; "Microsoft Office 365 is not supported" and "Click-to-Run" versions are not supported either. And because SQL can hold database files locked during a full-system backup, Carestream says to run "Prepare Backup" from the OrthoTrac File menu, or schedule Orthobac.exe, before the nightly backup so that usable .bak files exist.
WaveOrtho self-hosted
WaveOrtho says practices can run it "Cloud-hosted by us, or self-hosted on your own server," with the "Same application, same features." It publishes no server specification on its home page, so ask for the sheet before you budget for hardware.
Is SQL Server Express enough?
Often not for a busy ortho office. Dolphin's requirements say SQL Server Express is limited to 1 GB of RAM and one processor, and that Dolphin's performance "could be adversely impacted" by it; OrthoTrac v15.7 says practices above 15 workstations "may want to upgrade to SQL Server 2022 Standard for best performance." Check your workstation count against your vendor's sheet before you buy a server.
The date that makes this a this-year decision
Both vendors still list SQL Server 2016 as the minimum database, but Microsoft lists SQL Server 2016's extended support as ending on July 14, 2026, and Windows Server 2016 follows on January 12, 2027 (Microsoft Lifecycle). The full list of ortho-relevant dates is in the orthodontic practice technology guide. If you keep a server, size it with our notes on dental office server setup and test it against the backup and disaster recovery checklist.
Server spec sheet to hand to any hardware quote
- Windows Server Standard edition at the vendor's recommended version (not Essentials, not Small Business Server)
- SQL Server edition matched to your workstation count (Express limits checked against the vendor sheet)
- Domain set up, with a Microsoft client access license for every station
- RAM and SSD storage at the vendor's recommended figure, not the minimum
- Gigabit network card, gigabit switch and wired workstations
- Remote Desktop Services server, if remote offices connect, sized per remote connection
- Nightly backup that runs after the vendor's database preparation step, plus an offsite copy
- A restore test of the database and images on a calendar
What happens when the internet or the server goes down, and how do you drill it?
With a cloud PMS, losing the internet stops the schedule, chart and ledger at that office until the line or the backup line is back. With a server PMS, the office keeps working on the local network, but remote offices and online services such as claims and payments stop. A server failure stops every workstation. Carestream, for example, says on-premise OrthoTrac "does not require internet connectivity except for integrated services."
Reviewers describe both sides. One Cloud 9 user wrote, in a TrustRadius review dated January 2021, "Recently we have had a few hiccups with our internet, therefore causing Cloud 9 to be slow." On the server side, a Dolphin user wrote on Capterra in March 2018, "We have had numerous issues with Dolphin suddenly not working, office-wide or workstation specific." These are public reviews, quoted with platform and date; the reviewers are not named here, and both describe what an outage or slowdown looks like in daily use.
| What fails | Cloud PMS | Server PMS |
|---|---|---|
| The office internet line | Schedule, chart and ledger stop at that office unless a backup line takes over; other offices on their own lines keep working | The office keeps working on the local network; remote offices on RDS or VPN, eClaims, statements and online payments stop |
| The server | Not applicable for the practice software; capture PCs and printers still need to work | Every workstation stops until the server is repaired or restored |
| A capture PC or agent | X-ray or scan capture stops on that unit; the rest of the software works | Same |
| The vendor's service | The whole system is down for every office; only the vendor can fix it | Not applicable for the core software; online integrations may stop |
| Who you call first | Your IT provider to check the line and failover, then the vendor | Your IT provider for the server; the vendor for application faults |
None of the vendor pages and documents we read describes an offline or read-only mode for its practice software, so ask each vendor in writing what staff can see when the line is down. If the vendor expects a static IP, ask whether your backup line's address must also be registered.
The internet-down drill (one quiet hour)
- 1Pick the hourChoose a quiet admin block, warn the team and the phone provider, and print today's schedule first.
- 2Pull the primary lineUnplug the main internet connection at the firewall, not at the wall, so you can put it back in seconds.
- 3Time the failoverNote how long the firewall takes to move traffic to the backup line, and whether phones follow.
- 4Log in on three stationsOpen the practice software on the front desk, a clinical station and a doctor's computer, and check card terminals and phones.
- 5Capture one test imageTake one test X-ray or photo through the capture agent and confirm it lands in the chart.
- 6Write down what failedList each failure, who fixes it and by when, then plug the primary line back in and confirm it returns.
Run the drill again after any change to the firewall, the internet provider or the practice software. For the full outage playbook, including backup line options and a failover record, see what to do when the office internet goes down. If your phones still run on copper lines, plan for when the copper phone lines go away at the same time, because the phones and the practice software now share one internet connection.
Switching ortho software: what moves, what doesn't, and the cutover weekend
Switching ortho software moves more than patient demographics: active treatment contracts, payment plans, treatment phases, ceph tracings and years of photos and X-rays. Image conversion is often a separate job from data conversion, and every capture PC needs its agent and drivers reinstalled. Plan and test both before the cutover weekend.
The generic steps are already written up in our full Friday-to-Monday cutover runbook and the dental software migration checklist; timing and budget are in the dental software migration cost and timeline guide. What follows is only what is different in an orthodontic office.
Vendors show how separate the image work is. Ortho2's Edge Cloud onboarding package lists "one data conversion, one image conversion" as separate items, and its FAQ mentions "a one-time onboarding and data conversion fee." Sensei says OrthoTrac users face "no immediate requirement to move" and that migration to Sensei Cloud "can be planned when your practice is ready." Ask your new vendor which items are included before you sign.
Ortho-only cutover checklist
- Active treatment contracts and their remaining balances, checked on a sample of patients in both systems
- Payment schedules and autopay, and any financing or payment-plan integration your practice runs, reconnected and tested
- Treatment phases, appliances and visit sequences mapped field by field
- Ceph tracings and analyses: confirm whether they convert or stay readable in the old imaging software
- Image conversion confirmed in writing as included or separate, with a count of images before and after
- Capture agents and TWAIN drivers reinstalled and tested on every capture PC
- Mac capture limits checked for any doctor or treatment coordinator on a Mac
- Letter templates rebuilt, with desktop Microsoft Word where the software requires it (Dolphin's Letter System does)
- Microsoft Office version checked against the vendor sheet (OrthoTrac supports 32-bit Professional only)
- Printers at satellite offices on a print server where the vendor requires it (Dolphin does)
- Texting, reminders and patient-portal integrations reconnected
- A verified backup of the old system and a test restore before the data freeze
Keep the old system readable, not editable, for as long as you might need to check a contract or an image that did not convert. Decide who owns that read-only copy, and where it lives, before you cancel the old licenses.
Before the freeze date, a Free Dental IT Assessment gives you written findings and prioritized recommendations on your computers, software, network security, backups and performance, so the hardware and network side of the move is known before the vendor's checklist starts.
What to ask your IT provider about a practice-software change
Ask the vendor how its software behaves in your office, and ask your IT provider whether your office can carry it. Get both answers in writing before you sign, and keep them with the contract. The questions below are specific to choosing or switching ortho practice software.
Ask the PMS vendor
- How much internet do you need per workstation and per office, download and upload?
- Do you require a static IP, and must a backup line's address be registered too?
- Do you support VPN, Remote Desktop Services or thin clients, and for which offices?
- Is there an offline or read-only mode when the internet is down?
- Where is our data hosted, and how often is it backed up?
- Is image conversion included, or is it a separate item?
- Which X-ray units, scanners and cameras do you support, and with which drivers?
- Can we capture images on a Mac, or only on Windows?
- Will you sign a business associate agreement, and can every login use multi-factor authentication?
- If we leave, in what format do we get our data and our images?
Ask your IT provider
- Can our internet line meet the vendor's figures, and do we have a second provider that fails over?
- Is our server and SQL edition right for this system and our workstation count?
- Who reinstalls the capture agents and TWAIN drivers, and tests each device?
- When did we last test a restore of the practice software and the images?
For a full provider scorecard, use the one in the orthodontic practice technology guide linked at the top of this page. If a second office will share the system, the connection options are in our guide to IT for an orthodontic satellite office; if you are opening a new office instead, start with the orthodontic office technology checklist. For email that carries patient information, see email security for dental offices.
Orthodontic offices Legend has set up
These are orthodontic practices whose technology Legend set up, each described only as far as its project page states. The practice management system each office runs is not named here.
Luv Braces, Hutto, TX
Legend built the network and installed workstations, imaging and practice management software, audio/video and surveillance for the third Luv Braces location. See the Luv Braces project.
JP Orthodontics, Gunter, TX
From the final stages of the startup build-out to opening, the scope included network infrastructure, workstations, servers, audio/video, security cameras, email systems and Wi-Fi. See the JP Orthodontics project.
Razz Orthodontics, Flower Mound, TX
Legend's posts follow the launch of Razz Orthodontics and describe network infrastructure, technology and daily tech maintenance for the practice. See the Razz Orthodontics project.
What sits behind those projects:
- Served over 3,500 practices since 2004
- 22+ years in dental IT (since 2004)
- 24/7 monitoring
- A staffed 24/7 helpdesk at 1-800-794-1588
- In-house engineers; no outsourced first-level triage
- Onsite dispatch by appointment across served dental markets; remote-first nationwide
Legend supports the IT environment for Dolphin Imaging. If your practice runs Cloud 9, OrthoTrac, Edge Cloud, Greyfinch, topsOrtho or WaveOrtho, that is a system your practice runs: we keep the computers, network, server, backups and accounts around it working, and the vendor supports the application.
What does IT cost around a PMS change?
The software subscription or license is only part of the bill. A PMS change usually brings IT costs of its own: a new server or none, workstations moved to Windows 11, a second internet line, capture PCs and image migration. Pricing for Legend's managed IT: Starting at $360 per month.
Hardware procurement, major cabling projects and software licensing are quoted separately. Backup protection from $39.99 per month (storage-dependent). For an ortho office the cost drivers to list before you compare quotes are:
- Server or subscription: replacing a server and SQL licenses for an on-premise system, against the monthly subscription of a cloud system.
- Workstations: any PC that cannot run Windows 11, or that falls short of the vendor's RAM figure.
- Internet: a second provider on a different connection type, and a firewall that fails over.
- Capture PCs: a Windows PC for every X-ray unit or scanner whose agent does not run on a Mac.
- Image migration: whether the vendor charges image conversion separately.
Frequently asked questions
What is the best software for orthodontics?
There is no single best orthodontic software. The main practice management systems are Dolphin Management, OrthoTrac, Cloud 9, Edge Cloud, Greyfinch, topsOrtho and WaveOrtho. The right fit depends on whether you want a server or cloud system, how reliable the internet is at each office, and how X-rays and photos are captured. Compare those points in a deployment matrix before booking demos.
Which orthodontic software is cloud-based?
Cloud 9 (Planet DDS), Greyfinch, topsOrtho, Ortho2's Edge Cloud, Sensei Cloud and Dolphin Cloud run in the vendor's cloud, so the practice software needs no office server. WaveOrtho can be cloud-hosted or self-hosted. OrthoTrac and on-premise Dolphin Management are server-based. Cloud systems still need local capture software for X-rays and scanners, so check each vendor's capture requirements.
Does a cloud orthodontic PMS still need a server in the office?
Usually not for the practice software itself, but the office still has local work. X-ray and photo capture runs through a Windows agent and TWAIN driver, such as Cloud 9's C9 Agent or Dolphin Cloud's TSScan. Edge Cloud installs as an application on each computer, and CBCT or non-TWAIN X-rays may need local imaging software. Printers and the network stay local too.
How much internet speed does a cloud orthodontic PMS need?
It depends on the vendor. Cloud 9 asks for at least 1 Mb/s download and 0.5 Mb/s upload per computer, a dedicated line per office and a static IP. Dolphin Cloud asks for 25x5 Mbps for five logins or fewer, at least 50x10 for 5 to 15 workstations, and says 100x20 may be ideal for 15 or more. Ortho2 recommends 100 Mbps down and 20 Mbps up for Edge Cloud, with more than 25 and 5 Mbps as the minimum. Add scanners, phones and cameras on top.
What happens to a cloud ortho PMS when the internet goes down?
That office loses the schedule, chart and ledger until the internet returns or a backup line takes over. Other offices on their own lines keep working. None of the vendor documents we read describes an offline mode, so ask the vendor in writing. A second internet provider on a different connection type, with automatic failover, is the usual safeguard. Test it.
Can I run Dolphin, OrthoTrac or Cloud 9 on a Mac?
Partly. On-premise Dolphin runs on Intel Macs through Boot Camp, Parallels or VMware Fusion, and Apple M-series Macs have not been validated; Dolphin Cloud works from macOS through Microsoft Remote Desktop. Cloud 9 runs in Safari or Chrome on macOS 12 or later, but its capture agent is Windows only. OrthoTrac v15.7 lists Windows 11 Professional workstations only.
Is SQL Server Express enough for Dolphin or OrthoTrac?
For a small office it may be the vendor's minimum, but it is often not enough. Dolphin says SQL Server Express is limited to 1 GB of RAM and one processor, which can slow its software, and recommends SQL Server 2022 Standard. OrthoTrac says offices with more than 15 workstations may want SQL Server 2022 Standard. Check your workstation count against the vendor's sheet.
Will my X-rays and photos move when I switch orthodontic software?
Only if image conversion is part of the deal. Some vendors treat it as a separate job from data conversion; Ortho2's Edge Cloud package, for example, lists one data conversion and one image conversion as separate items. Ask for image conversion in writing, count images before and after, and keep the old imaging software readable until every image is checked.
Cloud 9 or Dolphin: which needs more from our IT?
They need different things. Cloud 9 needs no server but asks for a dedicated line at every office, a static IP and a Windows PC with its agent for each capture device. On-premise Dolphin needs Windows Server Standard, SQL Server, a domain and Remote Desktop Services for remote offices. Dolphin Cloud removes the server but publishes internet tiers from 25x5 to 100x20 Mbps, by office size, kept free for it.
Should an orthodontic practice replace its server or move its PMS to the cloud?
Answer five questions first: is your server or SQL near the end of support, can every office get a dedicated line plus a backup line, do doctors need Mac or home access, do you capture CBCT or non-TWAIN X-rays in-house, and will you add offices. If the first three answers are yes, cloud usually fits, while imaging capture often stays local.
The bottom line
A practice-software change is the moment to check the server, the internet lines, the capture PCs and the backups, before the vendor's go-live date fixes them in place. You are welcome to request a Free Dental IT Assessment: written findings and prioritized recommendations on your computers, software, network security, backups and performance. Or call 1-800-794-1588 and ask for a review of your practice-software plans, and see how our dental IT support works for orthodontic offices.

