Dentrix Server Migration Checklist: Move Servers Without Breaking DEXIS, Workstations or Backups
Replacing the server under Dentrix is not a hardware swap. The server may hold or support the practice-management database, shared configuration, user access, imaging bridges, backup jobs and paths used by every operatory. A safe migration treats the change as a clinical-continuity project with a tested rollback path.
Short Answer
A safe Dentrix server migration verifies the current Dentrix version and official requirements, captures a protected recoverable backup, builds the new server, coordinates vendor application steps, reconnects workstations and imaging integrations, validates real clinical workflows, and preserves a rollback option until the new environment is proven.
Know why you are moving the server
Server age alone does not define the project. The migration plan changes depending on whether the driver is end-of-life hardware, unsupported Windows Server, capacity, performance, practice relocation, acquisition, network redesign or a move toward cloud software.
| Trigger | Migration Implication |
|---|---|
| Aging Server | Prioritize lifecycle, warranty, OS and recovery readiness |
| Performance Pressure | Measure workload before sizing replacement |
| Office Move | Coordinate internet, cabling, network and physical logistics |
LEGEND // DENTRIX MIGRATION CONTROL
SYSTEM AUDIT READY
Inventory the Dentrix environment before touching it
Document the current server, Dentrix version, workstations, imaging products, storage paths, printers, scanners, backup jobs, remote access and vendor contacts. Migration day is not the time to discover an undocumented bridge or shared folder.
Hardware Inventory
Server OS, storage, RAM, and exact model.
Software & Bridge
Dentrix G7 & DEXIS integration paths.
local Backup Jobs
Active external drives and remote storage.
Confirm requirements and build the target environment
Use the current Dentrix requirements for the exact version being installed. Minimum specifications are only the starting point; size the environment for the practice’s workload, imaging growth, backup, security tooling and expected lifecycle.
| Readiness Layer | What to Verify |
|---|---|
| Server Layer | Supported OS/version, compute, RAM, storage, warranty, recovery plan |
| Workstations | Supported Windows versions, performance, drivers, local devices |
Create a migration backup you can actually roll back to
A green backup status is not enough. Before migration, confirm what data and configuration are protected, when the restore point was taken, where it is stored and how the old environment would be restored if the new server cannot go live.
HARD STOP
No destructive server migration begins without a known-good recovery point and a named rollback decision maker.
Decide who owns each part of the migration
The software vendor should own product-specific database conversion and application setup steps. The dental IT partner owns the devices, local servers, security configurations, cutover coordination and network readiness around that application.
| Task Description | Responsible Party |
|---|---|
| Licensing & PMS Application Setup | Dentrix Vendor |
| Server Hardware & Recovery Prep | Legend Network |
| DEXIS/Imaging Bridge Config | Imaging Vendor |
| Workstation Rollout & Local Printers | Legend Network |
| Workflow Acceptance & Signoff | Practice Manager |
Already paying for IT support but unsure about the actual recovery plan?
Legend can audit your current backups and simulate a dry recovery to ensure your database holds during a real emergency.
Get a Free IT Assessment →Reconnect workstations in a controlled sequence
Standardize workstation reconnects instead of fixing operatories one at a time under pressure. Start with a representative workstation, verify the workflow, then repeat the documented process across the office.
PILOT ROLLOUT PROGRESSION
- Step 1: Select a pilot front-desk or operatory workstation to test name resolution.
- Step 2: Confirm Dentrix client and local imaging bridges launch reliably.
Run the cutover around patient production
Define the freeze time, final backup, vendor handoffs, validation order and rollback deadline before the weekend begins. The practice should know who can call “stop” if a critical workflow does not pass.
Friday-to-Monday Timeline
Stop data changes and perform full validation before clinical hours resume Monday morning.
Frequently Asked Questions
Can Legend move Dentrix to a new server?
Does Dentrix need to be involved?
Will DEXIS break when the server changes?
Get a Second Opinion on Your Dental IT
Tell Legend about your dental IT support needs, technology environment, or clinic growth plans. Start with an objective, zero-obligation assessment.
Or call 1-800-794-1588
Related Guides
Continue learning about clinical technology, compliance, and dental software integrations.