Switching practice-management software is the single most disruptive IT event most dental practices will ever go through — bigger than a server replacement, bigger than opening a second operatory. The software vendors will tell you about the data conversion. Almost nobody tells you about the twenty other things that break, slow down or quietly stop being HIPAA-compliant on the day you cut over. This is the checklist we run for practices moving between Dentrix, Eaglesoft, Open Dental and Curve Dental, in the order the problems actually show up.
It applies whether you are moving server-to-server (Dentrix to Eaglesoft), on-premise to cloud (Eaglesoft to Curve, Dentrix to Dentrix Ascend), or from a DSO’s system back to your own after a de-affiliation. Read it before you sign the conversion contract, not after.
Before you sign: the questions the vendor won’t volunteer
What exactly converts, and what doesn’t? Every vendor converts patient demographics, appointments and ledgers. The things that commonly do not convert cleanly: clinical notes with formatting, perio charting history, treatment-plan phasing, insurance fee schedules, attached documents and scanned forms, and — critically — imaging links. Get the exclusions in writing.
Who owns the old data after cutover? Your HIPAA retention obligation does not end because you changed software. You need read access to the legacy database for the retention period (six years for HIPAA documentation; longer under some state dental-board rules). Ask whether the old vendor will keep a read-only license alive, what it costs, and whether you can export a full backup you control.
Is the new platform’s Business Associate Agreement actually signed? Cloud PMS vendors are business associates. A BAA that exists as a link in a click-through EULA is still a BAA, but you need a copy in your compliance binder. If you are moving to cloud, also ask where the data is hosted, whether it is encrypted at rest, and how you retrieve it if you leave.
The imaging problem — plan for it first
Practice-management software and imaging software are two different systems that pretend to be one. Dentrix talks to Dexis; Eaglesoft talks to Patterson Imaging and Schick; Open Dental bridges to almost anything; Curve integrates with a specific list. When you switch PMS, the bridge between the chart and the images is what breaks. Patients still exist in both systems, but the link that opens the right radiograph from the right chart may not.
- Inventory every imaging source: sensors, pano/ceph, CBCT (Carestream CS 8100/9600, Planmeca), intraoral cameras, and any legacy film scans. Note which software each writes to.
- Confirm the new PMS bridges to your imaging software version — not just the brand. A Dexis 9 bridge is not a Dexis 10 bridge.
- Decide whether images migrate into a new imaging platform or stay put with a new bridge. Migrating gigabytes of DICOM is a separate project with its own timeline.
- Test the bridge on a real patient record in the sandbox before conversion day. Open chart → open image → confirm the right patient, right tooth, right date.
If the practice runs heavy 3D — oral surgery, implants, ortho — this section is the whole project. See our page on IT for oral surgery practices for why.
The server and network questions
Moving to another on-premise system? Check the new vendor’s server spec against what you have. Eaglesoft and Dentrix both publish minimums, and a server that ran the old system fine may be under-spec for the new one’s SQL requirements. This is the moment to decide whether the server gets replaced — doing it mid-conversion is far worse than doing it a month before.
Moving to cloud? Your internet connection just became a clinical dependency. Three things to verify before cutover: (1) actual measured upload and download at the busiest hour, not the plan speed; (2) a failover connection — a second ISP or an LTE/5G failover router — because a cloud PMS with no internet is a practice with no schedule; (3) workstation age, since browser-based PMS platforms are heavier on RAM than the old thick client. Our HIPAA-compliant dental cloud migration page walks through the network side.
Either way: the PMS server, imaging, front desk and guest WiFi should be on separate network segments. A conversion is the cheapest time to fix that if it isn’t already true.
Backups: the part that protects you from the conversion itself
Take a full, verified, restorable backup of the legacy system the night before conversion, and keep it somewhere the conversion process cannot touch. Then test the restore — actually restore it to a spare machine and open a chart. Conversions fail, get partially applied, or reveal data-quality problems days later. The backup you can prove restores is your undo button.
After cutover, backups need to be re-pointed. A backup job that was faithfully backing up the old Dentrix database folder will keep doing exactly that, forever, while the new system’s data goes unprotected. This is one of the most common findings when we take over a practice: the backup is running, green, and backing up nothing that matters. A backup you have never restored is not a backup — see our dental practice backup and disaster recovery guide.
The integrations nobody lists
Write down every system that talks to the PMS today, because each one has to be re-connected or replaced:
- Patient communication — Weave, RevenueWell, Lighthouse 360, Solutionreach. These sync appointments and recall; a broken sync means missed reminders and empty chairs.
- Insurance and claims — clearinghouse credentials, eligibility lookups, electronic attachments.
- Payments — integrated card terminals, text-to-pay, patient financing.
- Online forms and scheduling — the website widget that writes into the PMS.
- Phones — screen-pop and call-logging integrations, and the AI phone receptionist if you run one; it books directly into the PMS and needs the new connection.
- Analytics and dashboards — Dental Intelligence, Practice by Numbers, any KPI tool reading the database.
Each vendor has its own re-integration steps and its own timeline. Start these two weeks out, not on conversion day.
Access, identity and security at cutover
- User accounts. Build every team member’s account in the new system with the correct role before go-live, and make sure the roles match the minimum-necessary principle. A conversion often quietly gives everyone admin.
- MFA. Turn it on for the new platform on day one. Cloud PMS logins are a phishing target; the MFA deployment guide for dental practices covers the rollout.
- Audit logs. Confirm the new system’s access logging is on and that you know how to pull a report. HIPAA requires it; auditors ask for it.
- The old system. Disable user logins on the legacy platform after the retention copy is secured. A forgotten Dentrix server with a shared password is a breach waiting for a date.
- Tell your compliance advisor. A new PMS is a material change to the environment; whoever maintains your risk assessment needs to update it. We hand them the technical inventory; the document is theirs.
Conversion week, hour by hour
- T-14 days: sandbox conversion complete; imaging bridge tested; integrations queued; new server or failover internet in place.
- T-7: team training on the new system using converted sandbox data — real patient names, real schedules, so the front desk isn’t learning on live patients.
- T-1 (evening): final legacy backup, restore-tested. Legacy system frozen — no new entries.
- Conversion day: vendor runs the final delta conversion. IT validates: patient count matches, today’s schedule matches, ledger totals reconcile, a sample of charts opens with the right images.
- Day 1 live: light schedule if you can manage it. Someone from IT on-site or on a standing call for the whole day. Every integration exercised once — a reminder sent, a claim submitted, a card run.
- Days 2–14: daily check on backups of the new system, recall and reminder volumes, and claim rejection rates — the three places conversion problems surface late.
Frequently asked questions
How long does a dental PMS conversion take?
Vendors quote four to eight weeks from contract to go-live for a single-location practice. Add time for imaging migration, a server replacement, or a multi-location rollout. The conversion itself usually happens over a weekend; the preparation is what takes the weeks.
Should we replace the server at the same time?
If the server is near end-of-life, replace it before the conversion — a month ahead if possible — so you are not troubleshooting two changes at once. If you are moving to cloud, the old server becomes the legacy read-only archive and can stay until the retention period ends.
What happens to our old data?
You still own it and you still have to retain it. Keep a read-only copy under your control for the full retention period, secured and backed up like any other ePHI.
Can we switch PMS without an IT provider?
Practices do. The ones that go badly are almost always the ones where the software vendor was the only technical party involved — because the vendor’s scope ends at their application, and everything in this checklist sits outside it.
Does switching to a cloud PMS make us HIPAA compliant?
No. It moves some safeguards to the vendor and adds new ones for you — internet redundancy, endpoint security on the browsers, MFA, a signed BAA. Compliance is the practice’s obligation regardless of where the software runs.
When you want it run for you
ClearMax runs PMS conversions as part of dental managed IT — we sit between the practice and the vendor, own the imaging bridge, the network and the backups, and stay on the account afterward. Start at Dental IT Support, or if you are in Kentucky, the Louisville and I-65 corridor page. Call (833) 306-3168 — you reach the engineer, not a sales desk.