OrthoTrac Support and Migration in 2026: Stay, Host, Cloud or Switch

The server rebooted after Tuesday night's updates and nobody logged its console back in, so OrthoTrac was down in every chair until the office manager walked to the records room. The machine is older than your newest associate, the front-desk computers stopped getting Windows updates a year ago, and Sensei keeps mentioning the cloud. Someone has finally asked out loud: is OrthoTrac going away, and do we have to move?

This guide is written for the orthodontist who owns an OrthoTrac office and has to choose between four paths: stay and replace the server, move to OrthoTrac Hosted, move to Sensei Cloud, or change to another orthodontic system. It uses only what Sensei and Carestream Dental publish (the support page, the v15.7 and Hosted requirements, the Sensei Cloud requirements and the June 2024 Technician's Installation Guide, all read on 6 November 2026) and Microsoft's own lifecycle pages. Then it covers the part the vendor hands to your IT provider: the server, SQL Server, Office, backups, the two-office question and the server move.

Is OrthoTrac end of life? What Sensei actually says

No. Sensei's OrthoTrac support page, read on 6 November 2026, answers the question directly: "If your practice is already using OrthoTrac™ software, you can continue using the software. There is no immediate requirement to move to another system." It publishes no end-of-support date, and the product received a 15.8.1 release in 2026 with security fixes.

The same page is clear about what OrthoTrac is and where Sensei wants it to go. OrthoTrac "is a server-based, Sensei product for managing orthodontic practices" that "relies on in-office servers and local hardware rather than cloud infrastructure." Sensei Cloud is described as "cloud-based, with no on-site server required," and the FAQ says many practices move "to reduce reliance on local servers and hardware, improve accessibility across locations, simplify updates, security, and maintenance." The page adds that "Migration can be planned when your practice is ready" and that Sensei "can help you review your current OrthoTrac™ software environment, explore enhancement options, and plan a future transition to Sensei Cloud at your own pace."

Read those sentences as a vendor would write them: the product is maintained, the cloud product is where new investment goes, and the timing is yours. The 15.8.1 release notes (2026) say the update brings "important security enhancements" and "resolution of customer-reported performance issues," which is what a maintained server product looks like. OrthoTrac is a trademark of Carestream Dental, Sensei sells and supports it as "a Sensei product," and Carestream Dental marked its 30th anniversary in 2012, so the product has been in orthodontic offices for more than four decades.

What "no immediate requirement" does not cover is everything underneath the application. The v15.7 requirements still list Windows Server 2016 with SQL Server 2016 Express as the minimum, and both are now past or within weeks of Microsoft's end of support. An office built to that minimum column has a vendor-supported application on an unsupported database and a server with a hard date. That, not an announcement from Sensei, is what makes 2026 the year to decide.

Which path should an OrthoTrac office take in 2026?

Choose by what you want left in the building. Staying keeps everything local and needs a new Windows Server 2022 machine. OrthoTrac Hosted keeps the screens your team knows and removes the data server. Sensei Cloud changes the software and keeps only imaging capture local. Another orthodontic system changes everything, including who converts your treatment cards.

Vendor documents read 6 November 2026. Requirements change; confirm the current sheet before you buy anything.

Stay and replace the server

Best for the office whose team is productive in OrthoTrac and whose complaints are about speed and reliability, not features. One reviewer on a software-review site put the complaint plainly: OrthoTrac "became very slow" and complicated for a busy office. Slowness in a server product is usually the server, the SQL edition or the network, and all three are in your control. You buy a dedicated Windows Server 2022 Standard machine, let the installer put SQL Server 2022 on it (or Standard edition if you run more than 15 workstations), refresh the Windows 10 computers, and plan the move for a long weekend with a Sensei migration appointment booked. Nothing changes for staff on Monday.

OrthoTrac Hosted

Best for the office that wants to stop owning a database server but is not ready to retrain on new software. OrthoTrac runs in Sensei's hosted environment and your team reaches it through Citrix Workspace on ordinary Windows 11 PCs; the Hosted requirements call these "modestly-configured" machines for scheduling, billing and payments. Two things stay local and often get forgotten in the quote: imaging capture, because "it is not suitable for image acquisition," and the printers, because "host-based printers are not compatible." Your internet line becomes the server cable.

Sensei Cloud

Best for the practice that has decided to change software and would rather move inside the vendor's family than start a new relationship. The screens are new, the data converts through Sensei, and the office keeps only what imaging capture needs: a Windows PC running CS Imaging Version 8. The Sensei Cloud requirements are short, which is the point: Chrome or Edge, an "actively supported version of Windows 10 or higher," and 10 Mbps each way. They also carry a sentence that matters for any ortho office: "If using an integrated product or service with Sensei Cloud, you must meet the system requirements of that product or service" as well.

Another orthodontic system

Best for the office changing for reasons OrthoTrac cannot fix: a second or third location, an owner who wants a browser-based system from any device, or a team that has already picked a favourite. A reviewer on a software-advice site wrote, "My office switched from OrthoTrac to Cloud 9 in 2019, and we are chugging along happily!" The comparison of Cloud 9, Dolphin, Edge Cloud, Greyfinch, topsOrtho and WaveOrtho from the IT side is in our guide to orthodontic practice management software compared, cloud vs server; this page covers only what leaving OrthoTrac involves.

What server and workstations does OrthoTrac v15.7 need?

OrthoTrac v15.7 wants a dedicated server: Carestream Dental "recommends using a dedicated server to run OrthoTrac," and "Small Business Server or Windows Server Essentials are not supported." The recommended build is Windows Server 2022 Standard with SQL Server 2022 Express on a quad-core Core i7, 16 GB of RAM, 500 GB free and Gigabit Ethernet. Workstations run Windows 11 Professional.

Two more rules sit in the Technician's Installation Guide rather than the requirements sheet. First, if the office runs CS Orthodontic Imaging, the vendor wants the imaging data on a second, physical server, and it would rather see two separate boxes than both systems virtualised on one host. Second, the guide warns that the free Express editions of SQL Server cap database size and the RAM and CPU they will use, which is the vendor's way of saying a busy ortho office with years of treatment-card history may outgrow the free edition. Size the box with what we cover under dental servers and workstations and the dental software system requirements roundup, which puts other practice systems beside OrthoTrac.

Which Microsoft dates matter for an OrthoTrac office?

Three dates decide the timetable. SQL Server 2016, OrthoTrac's minimum database, left Microsoft support on 14 July 2026. Windows Server 2016, the minimum server, ends on 12 January 2027. Windows 10, which the v15.7 sheet no longer lists for workstations, ended on 14 October 2025. The vendor's own compatibility grid tells you which replacements it supports.

OrthoTrac's v15.7 sheet carries a SQL Server and Windows Server grid that most offices never see. It says SQL Server 2005, 2008 and 2008 R2 are not supported, that "OrthoTrac no longer supports SQL Server 2014 after July 9, 2024," and that 64-bit SQL Server 2022 has been supported since OrthoTrac 15.5 and is what new v15.x installs get by default. SQL Server 2022 is marked supported on Windows Server 2016 and 2019 and not supported on Server 2008 or 2012. The Technician's Installation Guide adds the history that explains many ageing offices: versions 12 and 14 installed SQL Server 2008 Express by default, and early version 15 installs put SQL Server 2014 Express on the server. If your server was built in the v12 or v14 era and never upgraded, the database under it may be one the vendor dropped two years ago.

Microsoft's lifecycle pages stamp each end as the early hours of the following day in Pacific time; the dates above are the last full day of support in the United States. The wider calendar for every system in an ortho office is in our orthodontic practice technology guide; the server-specific version of this problem, written for any dental office, is our guide to Windows Server 2016 end of support for a dental office.

Why does OrthoTrac break after a Windows or Office change?

Because OrthoTrac is built on a specific Windows and Office arrangement that modern defaults undo. It needs 32-bit desktop Office with macros allowed, a server console that stays logged in, antivirus that leaves the OMS folders alone, printer-specific drivers and a mapped U: drive. A Windows update, a new PC or a new antivirus product changes any of them silently.

The most common break is letters. The Technician's Installation Guide is blunt about it: Office Home and Student editions and web-based Word (Office 365) do not work at all, and because the letters run on extensive Word macros, macros must be allowed in the Word installation. The requirements add that Click-to-Run editions are not supported and that storing and editing posted letters depends on CS Orthodontic Imaging. A front-desk PC bought with Microsoft 365 preinstalled, or an Office update that switched to 64-bit, is enough to stop every posted letter in the office.

The second is the server itself. OrthoTrac's licensing runs as an application in the server's console session, so the workstations only work while someone is logged in at the server desktop; the guide says the session may be locked but "should never be completely logged out." A reboot after patching, with nobody to log the console back in, takes every workstation down until someone walks to the records room. The guide also says OrthoTrac is built to run under a Windows account with administrative rights, so an IT provider tightening user rights has to apply the vendor's non-admin permission changes rather than simply removing admin.

The third is security software. The guide suggests switching off active scanning of macros and of .doc and .dot files, because it can interrupt automated letter printing, and excluding the OMS folder (on every workstation and the server) and OMS-SPEC (on the server), because some antivirus products still flag OrthoTrac files as "false positives" and quarantine them. That exclusion list has to be written into whatever endpoint product your IT provider runs, and rewritten when the product changes. The firewall rule is simpler: filter traffic to and from the internet, never traffic inside the office network, and Windows Firewall should be on during the install so the SQL exceptions are created.

The rest is peripherals and paths. Printers need HP PCL 6 or PCL 5E drivers, not universal ones; Dymo label printers do not work over the network; scanners must be TWAIN and directly attached; monitors above 1920 x 1080 "may cause display problems." Workstations reach the data through a mapped drive, and Sensei's support team expects it to be the U: drive. When something stops after a change, these are the first places a specialist looks, and our guide to dental software support vs IT support explains why Sensei will send you back to your IT provider for most of them.

How do you back up OrthoTrac properly?

OrthoTrac has five SQL databases and a set of folders, and SQL holds the live database files open. The vendor's method is to run Prepare Backup (or schedule Orthobac.exe) so that .bak files land in the OMS backup folder, then back up that folder and the listed data folders off the server every day, and read the log each morning.

The requirements sheet explains why a plain file backup of the server fails: "During many full system backups, SQL may hold .MDF and .LDF files open with a system lock, thereby rendering these files unusable for data restoration purposes." Prepare Backup creates proper database files for the five OrthoTrac databases (Audit, CommCat, DelOMS, OMS and TxCard) in the Most_Recent folder, and the Technician's Installation Guide says to skip the .MDF and .LDF files in the system backup and copy the backup folder instead. Then it adds the line every owner should remember: a backup file sitting on the same drive as the original "is not a 'true' backup."

What the vendor expects of the office, in its own order:

1. 1. Run File > Prepare Backup before each backup, or schedule OMS\Orthobac.exe in Windows ahead of the backup job.
2. 1. Back up at least twice a day: once at lunch and once when the day ends.
3. 1. Lunch backup: the Most_Recent folder. Daily: add Fingerprint.mdb, Daysheet, Docs, Snapshot, Toothcht, ECS, ICCPS and ACH. Weekly: the whole OMS folder. Monthly: OMS and OMS-Spec.
4. 1. Use "online backup services and tape backup"; the vendor found flash drives and CD-RWs "inconsistent in testing due to degradation."
5. 1. Get the media out of the building at the end of each day, or into a fireproof safe.
6. 1. Read the backup log every morning to confirm last night's job ran.

Three gaps in that list are the IT provider's to close. The vendor says plainly that its backup advice leaves out Carestream Dental Orthodontic Imaging, so the imaging database and image folders need their own job, tested separately. The licence lives in the PWSVR folder, and without a current copy of that file the only route is a call to Sensei support, which is not where you want to be on a Saturday. And none of it is a backup until someone restores it onto another machine and opens a patient; the Technician's Installation Guide says Sensei "does not train offices on configuring the backup system or restoring a database," so that test is yours. Our dental data backup guide covers how a restore test is run and recorded, and the dental software migration backup checklist is the version to use the week before any server move.

How does OrthoTrac work across two offices?

Through Remote Desktop, not a VPN. The Technician's Installation Guide puts the OrthoTrac data server, plus a Remote Desktop or Citrix server, in the largest office, and the remote office runs OrthoTrac through that session rather than locally. It also states that Carestream Dental "has not tested running OrthoTrac between two offices using a VPN connection."

That changes what the second office needs. Its workstations become thin clients for OrthoTrac, so the satellite's internet line and the main office's upload speed carry every click, and the Remote Desktop server in the main office has to be sized, licensed and patched like a second server. Word in that environment has its own rules (a per-user W: drive, the AWPSUTILITY tool and a capital-letters warning that two users must never share a data path or session), which is why letters are the first thing to test after any terminal-server change.

Imaging is the harder half. The vendor's own pre-install questions for a second office are the right ones: must images taken in one office open in the other, what imaging equipment each office uses, and what internet line and bandwidth each office has. If the answer to the first is yes, the imaging server, not OrthoTrac, usually decides the design. The network plan for a part-time satellite, including what must work on day one, is in our orthodontic satellite office IT plan. For many two-office OrthoTrac practices, Hosted is the simpler answer: both offices reach the same hosted system and the Remote Desktop server disappears.

OrthoTrac Hosted or Sensei Cloud: what changes for IT?

Both remove the OrthoTrac data server, and both leave imaging capture local. Hosted keeps the OrthoTrac application and reaches it through Citrix, with a wired bandwidth table from 15 to 80 Mbps by user count. Sensei Cloud is a browser product that needs 10 Mbps each way and CS Imaging Version 8 on a Windows PC for capture.

The Hosted sheet carries two warnings worth repeating to whoever quotes your internet. "Sharing bandwidth with other internet-intensive services such as video streaming or VOIP could affect OrthoTrac Hosted performance," which in an orthodontic office means the parent lounge Wi-Fi and the phones compete with the schedule. And "Due to the large size of dental images, Carestream Dental Imaging users should consider upgrading to a higher-speed service (download and upload)." Both products make the internet line the single point of failure, so the question to settle before signing is what happens in the open bay when it drops. The broader trade-off between keeping a server and moving to a vendor's cloud is in dental server replacement vs cloud migration, and the oral-surgery version of this exact decision, on the same vendor platform, is in WinOMS server vs hosted vs cloud.

How do you move OrthoTrac to a new server?

Follow the vendor's sequence and book the appointment first. The Technician's Installation Guide says to call Sensei support a few days ahead so a representative is booked for the move, to install OrthoTrac before CS Orthodontic Imaging, to keep the shared folder structure the installer creates, and to copy the licence folder before touching the old server.

The vendor's steps for moving a version 11 or newer server, in plain language:

1. 1. Everyone logs out of OrthoTrac. A staff member logs in on the server and runs File > Prepare Backup.
2. 1. In Options > Environment, note the Server Path (default C:\OMS) and the Database Prefix (default Main), then confirm a .bak file exists in the backup folder for each of the five databases. If the office runs CS Orthodontic Imaging v10 or newer, run pwisetloc.exe and confirm the PWImage backup is there too.
3. 1. Close OrthoTrac and exit the PracticeWorks Server from the system tray.
4. 1. Install OrthoTrac on the new server where the data will live. The guide warns against installing to C:\OMS and moving the folders afterwards: it breaks workstation backups and later updates. If the data belongs on another drive, install to that drive's oms and oms-spec folders and share the parent.
5. 1. Copy the licence and data files the guide lists (pwsvr\pwlf.dat, the hidden .000 and .001 files, filelist.nrl, Fingerprint.mdb, roll files and AuditTx.dat) and the folders ACH, Backup, Daysheet, Docs, ECS, Epayment, ICCPS, Snapshot, ToothCht and Orthometrics. If the new server is also the imaging server, copy the image folder.
6. 1. Run the URestore utility against the Most_Recent folder you copied.
7. 1. Point every workstation at the new server: remap the U: drive to the parent of the OMS folder, fix every old server name in OMS.ini, check the pwclient options and run pwisetloc.exe.
8. 1. Retire the old server, or at the very least stop its OrthoTrac SQL instance, so nobody saves a patient to the wrong machine on Monday.

Version 10 data is different: those releases predate modern Windows, and the guide says Sensei support has to update the datasets by hand. If your office never left version 10, the move is a support project, not a weekend.

The IT side wraps around those steps. Before: a tested restore of the Prepare Backup files onto the new hardware, the Windows Firewall on during install so the SQL exceptions are created, the antivirus exclusions written in, the console auto-logon configured, Office 32-bit and macros checked on every PC, and a copy of the PWSVR folder somewhere that is not the old server. After: letters printed from two workstations, a scan, a label, an eClaim, a payment, and the imaging bridge opened from a chair. The generic version of that acceptance list is the dental PMS migration cutover plan; the OrthoTrac-specific items above are what to add to it.

How do you leave OrthoTrac for another orthodontic system?

Leaving is a data-conversion project run by the new vendor and an IT project run by yours. The new vendor converts the five OrthoTrac databases and, usually as a separate item, the images. Your IT provider readies the PCs and line, keeps an OrthoTrac server readable for records lookups, and retires it only when the office has stopped opening it.

Start with what exists. OrthoTrac keeps its data in five SQL databases (Audit, CommCat, DelOMS, OMS and TxCard), the Docs, Daysheet, Snapshot and ToothCht folders, posted letters that depend on CS Orthodontic Imaging, and the images themselves in the imaging database and the OMS image folder. Ask the new vendor, in writing, which of those it converts, which it imports as documents, and which it leaves behind. Treatment cards, contracts and payment plans are where orthodontic conversions go wrong, because they are structured data in OrthoTrac and may land as PDFs elsewhere. Insist on a test conversion you can check against live OrthoTrac for a handful of real patients before the cutover date is fixed.

Then decide what to keep readable. A read-only OrthoTrac server, with the console logged in and the licence file in place, is the cheapest way to answer "what did we charge this family in 2019" for as long as your state's record-retention rules require; the vendor's own guide shows the licence running in the server's console session, so the old server cannot simply be powered off and forgotten. If you prefer not to keep a Windows server alive, the alternative is exporting the records the new system did not take as PDFs and images before the licence lapses, and testing that export the same way you test a backup.

The order of work, the eight to twelve weeks of inventory and decisions before the first export, and the acceptance tests for Monday morning are in our dental software migration checklist. What the move costs beyond the software fee, including the imaging line and downtime, is in dental software migration cost and timeline, which separates the subscription from the project. One more family decision belongs here: if your general-dentistry colleagues run SoftDent or the oral surgeon you refer to runs WinOMS, they are on the same vendor platform and face the same choice; the SoftDent version is in SoftDent software support and migration.

The IT side: who owns what around OrthoTrac

Sensei supports the OrthoTrac application and nothing underneath it. The Technician's Installation Guide makes the local technician "fully responsible for the configuration, installation, and maintenance" of the practice's network, and says the vendor does not support that network, printers included. Backups, Windows, SQL and imaging are the practice's and its IT provider's.

This is the environment a specialist orthodontic IT company looks after around a server-based practice system, and it is the same environment whether the application is OrthoTrac, Dolphin or Cloud 9. If you want it handled as one agreement rather than ticket by ticket, see what IT support for orthodontic practices covers, how dental practice management software support treats the application layer, and how Carestream Dental IT support handles the imaging side of the same office. For the whole-practice contract, managed IT services for dental practices is where to compare scope. Legend is remote-first nationwide with onsite dispatch by appointment across served dental markets; find your market under dental IT support in your city.

What to ask your IT provider about OrthoTrac

How Legend Networking can help

Legend Networking is a Dallas-based dental IT company with 22+ years in dental IT (since 2004) that has served over 3,500 practices since 2004. Legend supports the IT environment for the imaging systems DEXIS, Vatech, Carestream, Planmeca/Romexis and Dolphin Imaging, and for the practice software Dentrix, Eaglesoft, Open Dental and Archy. The server, Windows, SQL, backup and network work this guide describes is that environment: the part of an OrthoTrac office the vendor's own guide hands to the local technician.

The author, Ian Lynch, has 22 years in dental IT and oversees the NOC, onsite dispatch and client technology roadmaps. Legend holds a 4.8 rating from 173 Google reviews. You can see the shape of orthodontic work on a third-location orthodontic build covering the network, workstations, imaging and practice management software.