Guide
Sage 50 remote access: three options compared
Published · 6 min read
Short answer
There are three practical ways to use Sage 50 Accounts away from the office. Remote Data Access, Sage's own recommended option, shares your company data over the internet with Sage 50 installed on each computer, and is the route Sage fully supports. Remote desktop or VPN into the office lets people use the office copy; Sage helps with Sage 50 itself but not with the remote set-up, its speed or its connectivity. A hosted Windows server runs Sage 50 and the data in a data centre and everyone connects by Remote Desktop; Sage's current requirements say it does not support Sage 50 on virtual machines or Remote Desktop, so the hosting provider supports the environment. Small teams with simple needs often manage with Remote Data Access; teams that share one company file heavily, or rely on Excel, e-banking or other add-ons, usually do better on a hosted server.
What Sage recommends and supports
Sage UK has two knowledge base articles on this, and they need to be read together.
| Sage article | What it says |
|---|---|
| Check your system requirements (last modified 1 September 2026) | "We don't support Sage 50 Accounts on virtual environments like Virtual Machines or Remote Desktop, as they're outside our support scope." |
| Accessing Sage 50 Accounts remotely (last modified 14 October 2022) | Recommends Remote Data Access. Sage can help with installing Sage 50 on Terminal Server and with Sage 50 features, but not with speed or performance, setting up remote access and the network, remote connectivity, remote printing, or Windows user accounts and permissions. The current licence agreement allows running Sage 50 remotely. |
In practice: Remote Data Access is the only route Sage supports end to end. With remote desktop, VPN or a hosted server, Sage still helps with Sage 50 features but may decline problems it attributes to the environment, so whoever runs that environment (you, your IT firm or a hosting provider) has to support it. The older article also lists what to expect in a remote set-up:
- Slower performance in a remote access or wide area network set-up.
- Integrations that only work on the same computer: other Sage software, Microsoft Office and e-banking software must be installed on the computer where Sage 50 runs.
- Email and website links that only work if email and internet access are set up on that same computer.
Sage's system requirements add that if you use Remote Data Access, a broadband connection of at least 4 Mbps download and 2 Mbps upload is suggested.
The three options side by side
| Remote Data Access | Remote desktop or VPN to the office | Hosted Windows server | |
|---|---|---|---|
| Where Sage 50 runs | On every user's computer | On the office PC or server | On a server in a data centre |
| Where the data lives | Shared between computers by Sage's service | Office server | The hosted server |
| Office PC or server must stay on | No | Yes | No |
| Excel, e-banking, other Sage add-ons | On each computer | On the office machine | On the hosted server |
| Main risk | Sync issues and everyone on the same version | Office power, broadband and an exposed remote access port | Licensing for Remote Desktop and Office, set up correctly |
| Who looks after it | Sage plus each user | You or your IT firm | The hosting provider |
| Sage support for the set-up | Yes, Sage's recommended route | Sage 50 features only | Sage 50 features only; Sage says it does not support virtual machines or Remote Desktop |
How to choose
- One or two people, occasional remote work, little use of add-ons: start with Remote Data Access. It is Sage's own route.
- A team working in the same company file at the same time, plus Excel reports or e-banking: a hosted server keeps everything on one machine, which is where Sage says those integrations need to be.
- An office server that is old or on Windows Server 2016: Microsoft ends extended support on 12 January 2027, and Sage 50 Accounts v30.1 and later need Windows Server 2016 or newer anyway. Replacing the server is the moment to consider hosting.
- Remote desktop straight to an office PC over the internet: avoid exposing Remote Desktop directly to the internet. If you must use it, put it behind a VPN or gateway with multi-factor sign-in; our guide is RDP safe over the internet sets out what the NCSC and Cyber Essentials ask for.
Licensing traps to check first
- Sage 50 user count. Whatever route you choose, the number of people using Sage at the same time must fit your Sage licence.
- Microsoft 365 on a shared server. Not every Microsoft 365 plan allows Office on a Remote Desktop server; see the licensing notes on our hosted software page.
- Remote Desktop access licences. Each person who connects to a Windows server with Remote Desktop needs an access licence, on top of the Windows Server licence.
Sources
Facts were checked against these sources on 21 October 2026. Vendor terms change; check the source before relying on a detail.