What Should Be Backed Up Before a Dental Software Migration? PMS Data, Images, Documents and Recovery Testing

Most dental practices do not start looking for IT support when everything is working. They start looking after the third morning an operatory computer freezes. Or when a sensor suddenly stops acquiring images and the imaging company says it is the network. Or when the network company says it is the software.

In dentistry, technology is not a corporate back-office function. It is a live component of the clinical day. If a workstation in operatory four cannot pull up Dentrix or display a CBCT scan, that room is functionally closed. Production halts, staff sit idle, and patients leave frustrated.

This guide breaks down exactly what reliable dental software migration and backup checklists look like in 2026—explaining how to coordinate multiple software platforms, imaging bridges, and strict security compliance without constant operational friction.

Separate “Data Being Converted” from “Data Needed to Recover”

The conversion vendor may need only a database export. A rollback may require more: application data, images, configuration, shared documents, server state, credentials and vendor access. Protect for recovery, not only conversion.

“An export file proves you can attempt a conversion. A recovery plan proves you can return to production if the attempt fails.”

Protect the PMS Database Using Current Vendor Guidance

Follow the current vendor’s supported backup/export procedure for the exact version. Do not assume a file-copy or snapshot is application-consistent unless the vendor documents it.

Record the source system/version, export/backup method, timestamp, database size, storage location and the person/vendor who verified it. If the PMS vendor supplies an export, retain the original protected copy in addition to any transformed conversion files.

PMS Backup Evidence Card

Treat Dental Imaging as a Separate Protected Data Set

Images frequently live outside the PMS database. Identify the imaging application, database/index, underlying image files and storage location before migration day.

• DEXIS or other imaging database/index files
• 2D image repositories (raw x-rays, intraoral photos)
• CBCT / 3D high-density study storage
• Acquisition workstation local data/cache directories
• Specific imaging bridge configuration variables mapping patients to images

Protect Documents, Attachments and Workflow Assets

Clinical and business workflows may rely on files that are not inside the core PMS database: scanned documents, claims attachments, forms, templates, exports and shared folders. Inventory what staff would miss on Monday.

1. 01

   Scanned documents

   Are they stored inside PMS, document manager or a shared folder?

2. 02

   Claim attachments

   Where are the original images and active linkage records?

3. 03

   Templates/forms

   Are custom consents database content or local files?

4. 04

   Reports/exports

   Are historical financial reports archived for business continuity?

5. 05

   Shared folders

   Do third-party integrations depend on specific local directory paths?

Create Two Recovery Points: Planning Snapshot & Final Cutover Copy

A pre-project snapshot protects against preparation mistakes; the final cutover backup represents the last authoritative state before data entry freezes. Label them clearly so nobody restores the wrong point.

Migration Chronology Checkpoints

Test Recovery Before the Practice Needs It

A backup success notification is not proof that the practice can recover. At minimum, validate that the protected data is readable and the recovery method is documented; for critical systems, perform restore testing according to the practice's recovery plan.

Define Rollback Before the Migration Begins

Rollback needs a decision owner, deadline and sequence. “We will decide if something goes wrong” is not a plan when multiple vendors are working at midnight. Use a rollback clock, not an open-ended promise.

Keep Source-System Access Until Conversion is Validated

Do not decommission the old PMS or imaging environment because the new login works. Validate records, historical images, documents, reporting and retention needs; keep read-only access if contracts and policy allow.

1. Ensure representative patient charts match historical expectations.
2. Verify old x-rays and CBCT studies remain diagnostic and accessible.
3. Confirm required scanned documents have carried over cleanly.
4. Validate past financial balances before closing old accounts.

For DSOs: Protect Every Location & Standardize Evidence

A multi-location conversion needs a consistent backup/restore evidence packet per location or database. One successful pilot does not prove every acquired environment is recoverable.

DSO Compliance Checklist

• Location-specific database credentials isolated from production
• Individual PMS and imaging version mappings recorded
• Standardized, validated daily backup restore logs signed by lead engineers
• Rollback escalation protocol agreed by regional managers

Your Practice Needs Clear Technology Ownership

Technology is an investment that should secure your patient schedule, not disrupt it. Without clear, professional ownership of your clinical technology dependencies, your team remains exposed to constant operational friction and compliance risk.

By establishing structured, proactive safeguards and validating restore metrics prior to cutover, your practice can run reliably under any operational pressure.

Related Guides

Continue learning about clinical technology, compliance, and dental software integrations.