# Sage 50 hosting in the UK, on a server we look after.

> Yes, Sage 50 Accounts runs on a hosted Windows server: we install it with your company data on a managed server in London and your team opens it over Remote Desktop. One thing to know up front: Sage says it does not support Sage 50 on virtual machines or Remote Desktop. We support the server and the set-up; Sage may decline problems it puts down to that environment. Read what that means below before you decide.

Source: https://wharfcloud.co.uk/hosted-business-software/sage-50 · Last updated 21 October 2026 · WharfCloud

## At a glance

- **Server location:** London, United Kingdom
- **Server price:** £119/month (list £149/month)
- **Your Sage licence:** Stays yours, used on the server
- **Access:** Remote Desktop with multi-factor sign-in
- **Migration:** Included, free of charge
- **Human support:** Monday to Friday, 08:00 to 18:00 UK time

## Can Sage 50 Accounts run on a hosted server?

Technically, yes. Sage 50 Accounts is a Windows desktop program, so hosting it means running it on a Windows server that your team reaches with Remote Desktop. Sage's own licence allows this: its knowledge base says the current licence agreement lets you run Sage 50 Accounts remotely. Support is a different matter, and Sage has two statements you should read together.

Table: What Sage UK says about remote and virtual set-ups

| 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. |

### What that means for you

- **We support the server and the set-up:** Windows, Remote Desktop, user accounts and permissions, printing to your office, performance of the server, backups and monitoring. These are exactly the areas Sage says it will not cover in a remote set-up.
- **Sage supports Sage 50 itself,** but may decline an issue it attributes to the virtual or Remote Desktop environment. If that happens, we work the problem from the server side, and test on a copy before any change goes live.
- **If you need Sage's full support in every case,** Sage's recommended route is [Remote Data Access](https://wharfcloud.co.uk/guides/sage-50-remote-access-options) on your own PCs. We will tell you if that suits you better.

Sage also notes that anything Sage 50 talks to (Microsoft Office, other Sage products, e-banking software, email) must be installed on the same computer as Sage 50. On a hosted server, that computer is the server.

> **Check your version first** Sage's requirements say Sage 50 Accounts v30.1 and later will not install on Windows Server 2012 or 2012 R2, and list Windows Server 2016 to 2025 (not the Essentials editions) as supported operating systems. We build on a currently supported Windows Server release, so very old Sage versions may need updating before they move.

## How a hosted Sage 50 server works

1. **One server holds the program and the data.** Sage 50 and your company data sit on the same Windows server in London, so there is no file sharing across the internet and no data file on a laptop to lose.
2. **Your team connects with Remote Desktop.** Each person signs in with their own account and sees a Windows desktop or the Sage window. It works from Windows PCs, Macs and tablets with Microsoft's Remote Desktop client.
3. **Access is locked down.** Every Remote Desktop sign-in needs a password and a code from an authenticator app, for your team and for our engineers. No one can start a Remote Desktop session with a password alone, and we can also limit access to your office IP addresses.
4. **We patch, monitor and back up.** Critical and high-risk Windows updates go on within 14 days of release, in an agreed maintenance window outside your working hours. The server is monitored, and backups run on a schedule, with help from us when you need a restore.

Because everything runs on the server, a slow home broadband line affects how quickly the screen updates, not how long a Sage report takes to run. That is usually the main reason firms choose hosting over sharing the data file.

## Licensing checklist before you move

Table: Licences involved in hosting Sage 50 Accounts

| Licence | Who provides it | What to check |
| --- | --- | --- |
| Sage 50 Accounts subscription | You, from Sage or your Sage reseller | Enough users for everyone who will use Sage at the same time |
| Windows Server | Included in our monthly price | Nothing, we handle it |
| Remote Desktop user access | Quoted with your server | One per person who connects; confirmed in the first conversation |
| Microsoft Office on the server | You, through Microsoft 365, or quoted by us | Your Microsoft 365 plan must allow use on a shared server ([see licences](https://wharfcloud.co.uk/hosted-business-software#licensing)) |
| E-banking or other add-ons | You, from the vendor | That the vendor allows installation on a server |

## Moving Sage 50 from your office server

1. We agree a date away from your VAT return, payroll run and month end.
2. We build and secure the server, install your Sage 50 version and any add-ons, and test with a copy of your data.
3. One or two of your users try it for a few days on the copy.
4. On the agreed evening, you take a Sage backup, we restore it on the server and check it with you.
5. Your old copy stays untouched until you are happy, so you can always go back.

Because Sage does not support virtual or Remote Desktop set-ups, the trial on a copy of your data comes before the switch, not after. If something does not work the way your team needs, you find out with nothing at stake. Prefer to keep your own server? Our checklist on [moving Sage 50 to a new server](https://wharfcloud.co.uk/guides/move-sage-50-to-a-new-server) follows Sage UK's own steps.

## Price of the underlying server: Managed Windows Server

- **Standard:** £119/month intro price (first 50 customers), £149/month list price. Windows Server with licence, managed by us. Includes: Free migration from your current host; Critical and high-risk security updates within 14 days; Remote Desktop with multi-factor sign-in; Automated monitoring and recovery; Backups with restore help; Support in UK business hours.

Licensing is confirmed with you before setup.

Prices in GBP. No VAT is added: we are not VAT registered. Talk to us first: https://wharfcloud.co.uk/contact?topic=managed-windows-server

## Questions we get asked

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

Not fully. Sage's current requirements say it does not support Sage 50 Accounts on virtual machines or Remote Desktop. Sage can still help with Sage 50 features, but may decline issues it attributes to the environment; we support the server, Remote Desktop and the set-up.

### Is Sage 50 hosting the same as Sage 50 cloud or Sage Accounting?

No. Sage Accounting is Sage's browser-based product. Hosting keeps the Sage 50 Accounts desktop program you already use and runs it on a server in a data centre instead of in your office.

### Do I need to buy a new Sage licence?

No. You keep your existing Sage 50 subscription and install it on the server. The number of people using Sage 50 at the same time still has to fit within your Sage licence.

### How much does Sage 50 hosting cost?

The managed Windows server is £119/month (list £149/month), with no VAT added. Remote Desktop user licences, and Microsoft Office if you need it on the server, are quoted in writing after a short conversation, before you pay anything.

### Can people work from home?

Yes. Anyone with an account can connect from home over Remote Desktop with their password and an authenticator app code, within any extra restrictions you agree with us at setup. Support hours are in our [support policy](https://wharfcloud.co.uk/support-policy).

### What happens to our data if we leave?

You can take a Sage backup at any time and restore it anywhere. When a service ends we keep the data for 14 days so you can collect it, then delete it.

### Where is the data stored?

On a managed server in London, United Kingdom. Where backups are kept is set out in your service details and our [sub-processors list](https://wharfcloud.co.uk/legal/subprocessors).

## Sources

- [Sage UK knowledge base: Accessing Sage 50 Accounts remotely](https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=200901103316577)
- [Sage UK knowledge base: Check your system requirements (Sage 50 Accounts)](https://gb-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=200427112205533)
- [Microsoft Lifecycle: Windows Server 2016](https://learn.microsoft.com/en-us/lifecycle/products/windows-server-2016)

Sage, Pegasus, Opera, Microsoft and Access are trademarks of their owners. WharfCloud is not affiliated with or endorsed by them.

---

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