# Move Sage 50 to a new server: a UK checklist

> How to move Sage 50 Accounts data to a new server, step by step from Sage UK's own guidance, which Windows Server to pick, and when hosting is the better move.

Source: https://wharfcloud.co.uk/guides/move-sage-50-to-a-new-server · Last updated 21 October 2026 · WharfCloud

Published 21 October 2026. Reading time about 7 minutes.

## Short answer

Moving Sage 50 Accounts to a new server is mostly a data move, and Sage UK publishes the procedure: back up every company, remove it from Remote Data Access if you use that, copy the company folder that holds ACCDATA into a shared folder on the new server, install the Sage Data Service there if Sage 50 itself is not installed on it, then change the data path in the COMPANY file on every computer that runs Sage. Check the new server first: Sage supports Windows Server 2016 to 2025 (not the Essentials editions) and needs at least a 100Mbps network to share data. Windows Server 2016 loses support on 12 January 2027, so a new server should run 2022 or 2025.

## Before you start

- **Your Sage 50 version.** Sage UK's requirements page lists the versions it currently supports, from v26.3 up to v34, and says it cannot give technical support for older versions even with a valid support contract. Sage 50 Accounts v30.1 and later will not install on Windows Server 2012 or 2012 R2.
- **Your licence details.** Have your serial number, activation key and account number ready; Sage says you can find them in your My Sage account.
- **Admin rights.** Sage asks you to log on to each computer as an administrator for installation.
- **The network.** Sage asks for at least a 100Mbps connection to share data over a network.
- **The date.** Pick a day away from your VAT return, payroll run and month end, and tell everyone to close Sage before you start.

## Which Windows Server to put Sage 50 on

Table: Windows Server versions for Sage 50 Accounts (Sage UK requirements and Microsoft lifecycle pages, checked 21 October 2026)

| Windows Server | Sage 50 Accounts | Microsoft support |
| --- | --- | --- |
| 2025 | Supported, except Essentials | Mainstream until 13 November 2029, extended until 14 November 2034 |
| 2022 | Supported, except Essentials | Mainstream ended 13 October 2026, extended until 14 October 2031 |
| 2019 | Supported, except Essentials | Mainstream ended 9 January 2024, extended until 9 January 2029 |
| 2016 | Supported, except Essentials | Extended support ends 12 January 2027 |
| 2012 and 2012 R2 | v30.1 and later will not install | Out of support |

A new server that will run for several years should be on Windows Server 2022 or 2025. Moving onto 2016 now means a second move within months; our [Windows Server 2016 guide](https://wharfcloud.co.uk/guides/windows-server-2016-end-of-support-uk) explains the deadline.

> **Virtual servers and Remote Desktop** Most new servers are virtual machines. Sage's requirements page says: "We don't support Sage 50 Accounts on virtual environments like Virtual Machines or Remote Desktop, as they're outside our support scope." Sage 50 still runs there, but Sage may decline problems it puts down to that environment. Know this before you choose.

## Moving the data, step by step

This follows Sage UK's knowledge base article "How do I move my Sage 50 Accounts data?" (last modified 10 November 2025). Read the article itself for screenshots and the exact folder list for your version.

1. **Back up every company.** Take a backup of each company, including all file types.
2. **Take companies off Remote Data Access.** If you use Remote Data Access, remove the company from it before you move the data. You upload it again and reconnect remote devices afterwards.
3. **Create and share a folder on the new server.** This is where the company data will live. Set the share and folder permissions for the people who use Sage.
4. **Install the Data Service if needed.** If Sage 50 is not installed on the server that holds the data, install the Sage Data Service on it.
5. **Copy the company folder.** Find your current data directory and copy the company folder that contains ACCDATA (for example Company.000) into the new shared folder. Repeat for each company.
6. **Point every PC at the new location.** On each computer that runs Sage 50, open the COMPANY file in the Sage Accounts folder under C:\ProgramData for your version (the folder is named after a year, for example 2026 for v32), change the paths to the new UNC path (\\server\share\...), and save.
7. **Check before you switch off the old server.** Open each company from two or three computers and compare a few balances and reports with the old copy. Keep the old server untouched until you are sure.

## If the new server is for people working from home

The procedure above assumes every computer that runs Sage is on the same network as the server. If people work from home, a shared folder over a VPN is usually the slow, fragile option. Sage's own recommended route for remote work is Remote Data Access; the other is to run Sage 50 on a server next to the data and connect with Remote Desktop. Our [Sage 50 remote access guide](https://wharfcloud.co.uk/guides/sage-50-remote-access-options) compares the three.

## When hosting is the better move

If the reason you need a new server is that the old one is ageing or runs Windows Server 2016, ask whether you want to own a server at all. With [Sage 50 hosting](https://wharfcloud.co.uk/hosted-business-software/sage-50), Sage 50 and your company data sit on a managed Windows server in London that we patch, monitor and back up, and your team uses it over Remote Desktop. The move is included, follows the same Sage backup and restore steps, and starts with a trial on a copy of your data.

## Frequently asked questions

### Can I move Sage 50 to a new server myself?

Yes. Sage UK publishes the procedure: back up each company, copy the company folder containing ACCDATA to a shared folder on the new server, install the Data Service there if Sage 50 is not installed on it, and update the COMPANY file on every computer.

### Do I need to install Sage 50 on the server?

Not necessarily. Sage's article says that if the software is not on the computer that holds your data, you install the Sage Data Service on that computer instead.

### Do I have to reinstall Sage on every PC?

Not for a data move. Sage's steps change the data path in the COMPANY file on each computer that accesses Sage 50 Accounts, so every PC looks at the new server.

### Which Windows Server versions does Sage 50 support?

Sage UK lists Windows Server 2016, 2019, 2022 and 2025, except the Essentials editions. Sage 50 Accounts v30.1 and later will not install on Windows Server 2012 or 2012 R2.

### What about Remote Data Access?

Sage says to remove the company from Remote Data Access before you relocate the data, then upload it again and reconnect remote devices afterwards.

### Does Sage support Sage 50 on a virtual server?

Sage's requirements page says it does not support Sage 50 Accounts on virtual environments such as virtual machines or Remote Desktop, as they are outside its support scope.

## Sources

- [Sage UK knowledge base: How do I move my Sage 50 Accounts data? (last modified 10 November 2025)](https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=200427112243724)
- [Sage UK knowledge base: Check your system requirements (last modified 1 September 2026)](https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=200427112205533)
- [Sage UK knowledge base: Accessing Sage 50 Accounts remotely](https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=200901103316577)
- [Microsoft Lifecycle: Windows Server 2025](https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2025)
- [Microsoft Lifecycle: Windows Server 2022](https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2022)
- [Microsoft Lifecycle: Windows Server 2019](https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2019)
- [Microsoft Lifecycle: Windows Server 2016](https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2016)

---

WharfCloud is a trading name of Sunucu Internet Services Consultancy Ltd, registered in England and Wales, company number 12963678. Not VAT registered.
Support: engineers Monday to Friday, 08:00 to 18:00 UK time. Critical incidents: A person responds to critical incidents within 1 hour (Every day, 07:00 to 23:00 UK time). Automated monitoring and automated recovery overnight and at weekends.
Contact: hello@wharfcloud.co.uk · https://wharfcloud.co.uk/contact