Every system has a right season. This page lists the signs that your office has outgrown self-hosting, and the exit routes that keep your data, your habits and your dignity intact.
Self-hosting guides never write this chapter, which is a shame, because outgrowing your own server is a success story, not a defeat. The office that started with 8 people and a spare PC is now 60 people across three cities — of course the answer changed. Here are the signs that it has, and what to do next.
None of these is a failure. They are what growth looks like from inside a server cupboard.
Self-hosting’s great advantages are local: LAN speed, working through internet cuts, data on your premises. A team that is now mostly remote uses none of them — every byte crosses the public internet to reach a box in an office with a consumer-grade connection and a consumer-grade power supply. At that point a professional cloud, or at least a proper data-centre VPS, is simply the better-placed computer. The rule: host the system near the users, and the users moved.
Big clients and regulated industries ask for things: uptime commitments, security certifications, audit reports, data-processing agreements. A small self-run server produces honest shrugs, not documents. When "where is our data and who certifies it" starts appearing in client questionnaires — and costing you contracts — the managed services stop looking expensive. This is the cloud’s home ground, and pretending otherwise loses business.
If the person who ran the system has left and, six months later, updates are behind and nobody has tested a restore, the system is not self-hosted any more — it is unhosted and hoping. You have three honest moves: appoint and train a real replacement, hand the same Nextcloud to a managed host or IT provider, or migrate to a full cloud suite. The dishonest move — letting it drift because it still mostly works — is how offices end up in the news section of this blog series.
Every rule of arriving applies in reverse: audit first, pilot a group, run both systems briefly in parallel, make the old one read-only, then close it. Keep a full exported archive and the runbook. And say the true thing to the team: the system served the office well for its season, the office outgrew it, and that is what growth means. Offices that frame the exit honestly keep their staff’s trust for the next change too.
However your office journey goes, the video above shows the system at its best — the season this whole series is about making long and happy.
Watch Full VideoNot on headcount alone. The real tests are the ones on this page: simultaneous editors straining the box, remote share rising, compliance questions arriving, admin cover thinning. If it genuinely still fits, upgrade the hardware and keep going — the signs, not a number, decide.
No — that is its charm. It is the same Nextcloud, professionally run. Files, accounts, shares and staff habits carry across; what changes is who patches, backs up and answers at 2 am. It is the exit that feels least like an exit.
A complete exported archive of the data, the runbook, and the backup history — stored somewhere findable, labelled with dates. Audits, tax questions and "do you still have that 2023 file" requests arrive for years, and the archive is cheap to keep and priceless to have.