Guide · Continuity

Your Nextcloud admin quit. Now what?

23 October 2026 · Software by Design

The person who set up your Nextcloud gave notice, or simply stopped answering. The good news first: your data is fine. The server still runs, the apps still work, and nothing is held hostage. Here is what actually needs doing, in order.

Day one: secure the keys, not the data

The data is not going anywhere, Nextcloud stores everything in its own database and on your own storage. What walks out the door is access. The realistic checklist for the first week:

  • Admin accounts: Who else has a Nextcloud admin login? Promote a second person now, a group with one member is an outage waiting for a holiday.
  • Server access: SSH keys, hosting panel, DNS registrar, TLS renewal. These live outside Nextcloud and are easier to lose than the software itself.
  • Licence keys: App licence keys (AZC2, DTY2 and friends) live in the admin settings of each app, visible to any admin, so they survive the departure. Confirm you can find them before you need them.
  • Backups: Does anyone know where the backup job writes and whether it still runs? Test a restore once, not when the disk fails.

What keeps working without any admin at all

Clock-ins keep recording. Rosters keep publishing. The audit trails keep appending. A Nextcloud that is left alone does not decay on a weekly schedule, users can work for months on an unmaintained instance. The risk is not sudden death; it is the slow kind: an unpatched PHP, an expired certificate, a disk that fills up because nobody watches it.

The three options

1. Train a successor internally. The right answer if the Nextcloud serves more than one app and someone is willing. Daily Nextcloud admin work is small, updates, user management, the occasional log look, but it is not zero, and it should be written into someone's role, not absorbed as invisible labor the way the predecessor probably did it.

2. Move to managed Nextcloud hosting. A hosting provider takes over updates, backups, and uptime for roughly €10-30 per month at team sizes that matter here. Your data stays in a datacenter you chose; the apps and licence keys come along unchanged. This is the option most three-to-thirty-person organisations end up on, and it is the one we price into our own total-cost comparisons.

3. Hand operations to us. Check Partner exists for exactly this: we maintain the instance, run updates against a staging copy first, and your organisation keeps a named contact who knows the apps because they wrote them. It costs real money, published on the support page, not hidden behind a call.

What you do not need to do

You do not need to migrate away. Nothing about our apps creates a dependency on the person who installed them: the data model is plain database tables, the exports are open formats, the licences are keyed to your organisation's own instance. The admin leaving is an operations problem, not a platform problem, and operations problems have three boring solutions, listed above.

If you are reading this mid-crisis because the admin already left: start with the day-one list, then pick an option within a month. An unmaintained instance does not get safer with time, but it does not explode either. You have weeks, not hours, use them to choose properly instead of migrating in panic.