Count the whole cost of the box
A server quote usually shows the hardware and the operating system licence. The real cost is wider. Add client access licences, a UPS to ride out power cuts, backup software and a backup destination, installation and migration labour, warranty extensions, and the time someone spends patching, monitoring and replacing failed drives. Then remember that the hardware will need replacing in five to seven years, with another migration attached.
A modest small-business server project in New Zealand, once all those pieces are included, commonly lands in the range of several thousand to the low tens of thousands of dollars ex GST, depending on storage, redundancy and software. Prices vary a lot, so ask for a written quote that lists every component and the expected life of each.
Count the whole cost of the cloud
Cloud costs arrive as subscriptions. For files and email, the main cost is usually the per-user productivity licence you may already be paying. For an application that needs a real server, you rent a virtual machine by the hour or month, plus storage, backup and sometimes a remote desktop service so staff can use the application. Those rented servers can cost more over five years than the equivalent hardware, especially if they run around the clock at a size bigger than needed.
Add the internet side too. Relying on the cloud justifies a better fibre plan and a backup connection, and those monthly costs belong in the comparison. The fair way to compare is total spend over five years for each option, including labour, rather than a hardware invoice against one month of subscriptions.
The risks of keeping it onsite
A server in the office is exposed to everything that can happen to the office: theft, fire, water leaks from the floor above, overheating in a cupboard with no ventilation, and power spikes. Drives and power supplies fail, often without warning once a machine passes five years. If the person who understood the setup has moved on, recovering from a failure can take days.
Security is the other large risk. A server that misses updates, has a remote access port open to the internet or shares an administrator password with every PC is a common way for ransomware to spread through a small business. None of that is inevitable, but keeping an onsite server safe takes steady, unglamorous work every month.
The risks of moving to the cloud
The cloud swaps hardware risk for different ones. A slow or unreliable connection makes everyday work frustrating. Monthly costs can drift upward without anyone noticing. Data is often stored in Australia or further away, which matters to some clients and contracts. Accounts become the attack target, so poor sign-in security exposes everything at once rather than one building.
There is also the risk of lock-in. Once years of files and workflows sit in one platform, leaving is harder. That is not a reason to avoid it, but it is a reason to know how you would export your data before you commit, and to keep an independent backup.
When onsite still wins
Some situations favour keeping a server. Architects, engineers and video teams working with very large files can find cloud sync painfully slow unless they have excellent fibre. Some older accounting, practice management and manufacturing systems only run on a local Windows server and their vendors do not support hosting them elsewhere. Sites with poor internet, such as rural premises, may struggle to rely on the cloud at all. A hybrid answer is common: everyday documents and email in the cloud, a small server or network storage box kept onsite for the one system that needs it, and everything backed up off site. That is a perfectly respectable outcome rather than a half-finished migration.
How to make the decision
Start from what you run, not from a preference. List each workload, such as shared files, email, the accounting database or the design archive, and decide where each fits best. Price both options over five years, ask your software vendors in writing whether they support cloud hosting, and test your internet speed at the busiest time of day. The answer is often clear once each workload is considered on its own rather than as one big server decision.
Also think about who will look after each option. An onsite server needs monthly patching, backup checks and someone to respond when a drive fails at 7am. A cloud setup needs someone to manage accounts, review subscriptions and keep sign-in security tight. Both take ongoing effort; they just take different kinds. If nobody inside the business has time for either, factor the cost of outside support into each column of your five-year comparison so the numbers reflect how the system will really be run.
In short
- Compare five-year totals, including labour, backup and replacement, not one invoice against one bill.
- Onsite servers carry physical, hardware and patching risks that small offices often underestimate.
- Cloud risks are internet dependence, cost creep, data location and account security.
- A hybrid setup is a sensible answer when one application still needs a local server.