...

Ekim IT Solutions

Blog / How to Back Up Dental Software Before Switching Platforms
All Dental

How to Back Up Dental Software Before Switching Platforms

Featured image for the dental software backup guide showing a cloud upload icon and a secured database icon representing the process of backing up and verifying dental practice data before switching to a new practice management platform

Before any dental software migration begins there is one step that cannot be skipped: a verified backup. Not a backup that is running. One that has been tested and confirmed restorable.

Dental practices routinely discover on migration day that their backup was running but not actually capturing the right data. A backup that covers the database but misses the imaging folder is not a complete backup. A backup that has never been tested for restoration is a backup that might work.

Here is exactly what to back up before switching platforms and how to confirm it is actually ready.

Most Common Migration Data Loss Event

The most common data loss event in dental software migrations is an incomplete backup discovered too late.

Practices that discover their imaging data was not backed up after the migration has started face permanent loss of historical X-rays. There is no recovery option if the original data is gone and no verified backup exists. The database and the imaging folder are two separate locations that must both be confirmed in the backup before migration begins.

What You Need to Back Up

Four locations that must be confirmed in your backup before migration day. Check each one your IT provider has verified is included and tested.

Backup locations confirmed 0 / 4

All four backup locations confirmed and tested.

Your backup is ready for migration. Confirm the backup ran successfully the night before cutover and that an offsite copy is stored separately from the network. A backup completed two weeks before migration day is not adequate protection for a migration.

Backup gaps remain before migration can safely proceed.

The unchecked locations represent real data loss risk. Imaging data and Document Center files are the most commonly missed. Your IT provider needs to confirm every location is captured before a migration date is scheduled.

Your backup is not ready for migration.

Multiple backup locations are unconfirmed. Scheduling a migration without verifying every data location is confirmed and tested is the scenario that results in permanent data loss. The migration must wait until all locations are confirmed and a restore test has passed.

Talk to Ekim about migration backup verification →
Pre-Migration Verification Checklist

Verify your backup before migration starts

1

Map every backup location: database, imaging folder, and Document Center must all be confirmed covered

Your IT provider documents the exact file path of every data location and confirms each is included in the backup job. This is not an assumption: it is a verified audit of the backup configuration against the actual data locations on the server.

2

Test the restore: IT restores sample files to a test location, no test means no verified backup

A backup that has not been tested for restoration is not a verified backup. Your IT provider restores sample patient records and imaging files to a test location, confirms they open correctly, and documents the result. This step must be completed before migration is scheduled.

3

Check the date: night before cutover is ideal, weeks-old backups are not a safety net

The backup used as migration insurance should be as current as possible. A backup completed the night before cutover gives the practice a restore point that reflects the full current state of the data. A backup from two weeks prior means two weeks of patient records are not protected.

4

Copy it offsite: store a separate copy in the cloud before migration begins

The pre-migration backup should be copied to an offsite or cloud location before any migration work begins on the server. If something goes wrong during migration and the local backup is affected, the offsite copy is the final safety net. This copy should remain accessible for at least 30 days after go-live.

Platform-Specific Backup Notes

Dentrix logo on a dark gradient background representing the platform-specific backup section covering what Dentrix practices must back up before switching dental software including the SQL database, image path folder, and Document Center files

Dentrix stores the database and imaging data separately. The database is managed by SQL Server. The image path is a folder path set in Dentrix Office Manager and is often on a separate drive or network share. Document Center files are also stored outside the database.

All three locations must be included in a complete Dentrix backup. Dentrix's own backup tool only covers the database. It does not automatically back up the image path or Document Center. Your IT provider must add those locations manually to the backup configuration.

Three separate locations to confirm: SQL Server database, image path folder, and Document Center folder.
Eaglesoft by Patterson Technology logo on a dark gradient background representing the platform-specific backup section covering what Eaglesoft practices must back up before switching dental software including the full Eaglesoft data folder and proprietary imaging files

Eaglesoft stores data in a folder called C:\Eaglesoft\Data. Imaging data is stored in a proprietary format within the Eaglesoft folder structure.

Patterson's migration documentation confirms that a database cleanup to disable encryption must happen before data transfer to a new server, with Patterson Technology Support assistance. This step is critical and must happen in the correct sequence. Your IT provider and Patterson support coordinate this together.

Patterson Technology Support must be involved in the database cleanup step before data transfer begins.
Open Dental Software logo on a dark gradient background representing the platform-specific backup section covering what Open Dental practices must back up before switching dental software including the MySQL database and the configurable imaging folder path

Open Dental uses a MySQL database. The imaging folder location is configurable and set within the Open Dental program. If your practice moved the image folder at any point, confirm the current path before backing up.

Open Dental's conversions team retains backup copies of test and final conversion data for approximately two months after migration, which provides an additional safety net during the transition period. This does not replace the practice's own pre-migration backup.

Confirm the current imaging folder path inside Open Dental before assuming the default location is being backed up.

Frequently Asked Questions

Create and verify the backup as close to the migration date as possible. The night before the cutover is ideal. Verify the backup is complete and restorable at that point. Do not rely on an older backup as your migration safety net.
Ask them to prove it. Request a test restore of a specific patient record and an imaging file from the most recent backup. If they cannot demonstrate a successful restore, you do not have a verified backup regardless of what the backup software reports.
Yes, for at least 30 to 60 days. Keep the old server accessible and powered on after go-live. This gives you access to historical data, the ability to run historical reports from the old system, and a fallback if any data was missed during migration. Most practices decommission the old server after confirming all data and configurations are correct in the new system.
Yes. Ekim IT Solutions includes backup verification as a standard part of dental software migration support. We confirm what is and is not covered by your current backup, test restoration before the migration starts, and ensure a complete copy of your data exists before any migration begins. We support practices across all 50 states remotely, with on-site support available in New England and New York.
Switching dental software platforms without a verified backup is how practices lose years of patient data.

Ekim IT Solutions works exclusively with dental practices. We serve New England and New York with on-site support and dental practices nationwide with remote support. We verify, test, and document your backup before any platform switch so your patient records, imaging data, and history are fully protected before anything changes.

Do not switch platforms and hope the backup works. Verify it first with someone who has done this before.
Verify your backup before switching →