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.
In this guide
- Know why you are moving the server
- Inventory the Dentrix environment before touching it
- Confirm requirements and build the target environment
- Create a migration backup you can actually roll back to
- Decide who owns each part of the migration
- Reconnect workstations in a controlled sequence
- Run the cutover around patient production
- Related Guides
- Frequently asked questions
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.
Server migration triggers
| 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
Dentrix migration control status
| Stage | Status |
|---|---|
| 1. Current Server | VERIFIED |
| 2. Protected Backup | VERIFIED |
| 3. New Server | READY |
| 4. Workstations | PENDING |
| 5. DEXIS Imaging | PENDING |
| 6. Go-Live | HOLD |
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
1.
Server OS, storage, RAM, and exact model.
Software & Bridge
2.
Dentrix G7 & DEXIS integration paths.
local Backup Jobs
3.
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.
Target environment readiness
| 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.
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.
Migration task responsibilities
| 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 |
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.
Related Guides
Continue learning about clinical technology, compliance, and dental software integrations.
Dental Cyber Defense Checklist
HIPAA
A practical guide to securing active patient records.
Dentrix G7 Upgrade Roadmap
Software
How to avoid sensor imaging bridge errors.
Clinic Network Topology Design
Network
VLAN mapping configurations for operatory traffic.
Frequently asked questions
Can Legend move Dentrix to a new server?
Legend can manage the IT-infrastructure side of the migration: target server, backup, network, workstation reconnects, imaging/integration validation, cutover and documentation.
Does Dentrix need to be involved?
Usually the exact level of vendor involvement depends on version, licensing and application-specific migration steps.
Will DEXIS break when the server changes?
It should not if dependencies are mapped and validated, but changes to server names, paths, permissions or workstation configuration can affect imaging workflows.