Warning: a server migration involves stopping the database engine, copying the live database and changing settings on every workstation. A mistake can leave the practice unable to open Eaglesoft. Plan it with your IT provider and Patterson support (800-475-5036), and do it after hours with a rollback plan.
Before migration day
- Check the new server meets Eaglesoft’s hardware requirements (Patterson KB 5073).
- Find your current Eaglesoft version on the old server: Help | About Eaglesoft in the Practice Management screen.
- Get the installation files and licence number for that version (Patterson KB 23400, or Patterson live chat).
- Decide on upgrades. Patterson’s instructions say: if you are upgrading at the same time, migrate to the new server on the existing version first, then update.
- Check for database encryption. If your data is encrypted with the AES-256 option in Eaglesoft 21 or later, Patterson’s support team must run a database cleanup to disable encryption before the transfer. Patterson warns that skipping this will likely stop the database from starting on the new server.
- Set up the new server on the network so workstations can browse to it in File Explorer without being asked for a username or password.
On migration day
- Take the final backup after the last transaction. Patterson’s instructions are to stop the database engine and restart it once (so the log file can reset if it is full), then stop it again and back up the entire Eaglesoft Data folder.
- Disconnect the old server so no workstation can use it: take it off the network or keep its database engine stopped. Confirm the practice has finished seeing patients.
- Install Eaglesoft on the new server. By default it installs to
C:\Eaglesoftwith data inC:\Eaglesoft\Data. If you want the data elsewhere, create the folder before installing. A blank database is loaded after installation. - Stop the database engine on the new server.
- Copy the contents of the Data folder from your final backup into the new server’s Data folder, replacing the blank files.
- Verify the copy. Patterson says to check the sizes of
PattersonPM.DBandPattersonPM.Log, and the size and number of files and folders in the Data folder, against the backup. - Share the Data folder on the new server, then start the database engine.
- Log in to Eaglesoft on the new server with an existing provider.
- Point Eaglesoft at the new data share: File | Preferences | General | Network, select the new server’s Data folder, save, then log out and back in.
- Check the schedule, images and documents open correctly.
Workstations and the old server
- Open Eaglesoft on every workstation and confirm it connects to the new server and can open the schedule, images and documents. If a workstation cannot connect, see our article on “database server not found”.
- Retire the old server safely. Patterson recommends removing it from the network entirely if it will not be used. If it stays for reference, rename its database engine in Technical Reference (for example to
OLDSERVER_Eaglesoft) so workstations cannot connect to it by mistake. - Keep the final backup for some time as a contingency, as Patterson advises.