Sage 50 Server Migration Checklist

Preparing before the migration

• Take a full backup of the Sage 50 company data using Sage's built-in backup feature, stored independently of the server being replaced
• Document the exact share name, folder path, and permission structure on the current server
• Record which workstations connect via mapped drive versus direct UNC path
• Confirm the Sage 50 version and any installed tax or payroll modules match what needs to be reinstalled or reconfigured on the new server

Migration steps

1. Ensure all users are out of Sage 50 before starting the data copy
2. Copy the company data folder to the new server's storage
3. Recreate the share with the same or an updated name, matching the required permission levels for staff accounts
4. Set NTFS permissions on the folder to align with the share permissions, avoiding the common mistake of leaving one more restrictive than the other
5. Update each workstation's mapped drive or connection path to point at the new server
6. Open the company data from at least two workstations simultaneously to confirm multi-user access works correctly

Avoiding the most common migration mistakes

The most frequent issue after a Sage 50 server migration is a workstation still pointing at the old server's path, either through a stale mapped drive or a hardcoded shortcut, which produces confusing access errors that look like a Sage 50 problem. Walking through each workstation individually after the migration, rather than assuming a group policy or script updated every path, catches this quickly. The general access troubleshooting steps in our Sage 50 multi-user network problems guide apply directly here if any workstation still has trouble after reconnection.

Antivirus and backup software on the new server

Configure antivirus exclusions for the Sage 50 data folder and processes on the new server before staff resume regular use, following the same scoped approach covered in our Sage 50 network performance guide. This is also the right time to confirm the new server's backup schedule is active and tested, not simply assumed to be running because it was configured on the old server.

Timing the migration around the firm's workload

Server migrations should be scheduled for a low-activity period, ideally a weekend, and never during the concentrated workload of tax season. Our tax season IT readiness guide outlines the broader planning window firms should use for infrastructure changes like this one.

Keeping a rollback option available

Leave the old server powered on and untouched, with its data folder intact, for several business days after the migration. If an unexpected issue surfaces once staff resume normal work, this gives a fast way to roll back rather than troubleshooting under pressure with no fallback available.

Where Sage support fits in versus infrastructure work

Sage can assist with application licensing and module activation questions that come up during a migration, but the server build, sharing configuration, and permissions are entirely an infrastructure task. A migration planned and executed by an experienced IT provider avoids the multi-day access disruptions firms sometimes experience attempting this without that expertise.

Frequently asked questions