Migration from official docker image to AIO questions

Dominus · April 2, 2026, 8:42pm

Support intro

The Basics

Nextcloud Server version (e.g., 29.x.x):
- 33.0.1
Operating system and version (e.g., Ubuntu 24.04):
- official docker image
Web server and version (e.g, Apache 2.4.25):
- official docker image
Reverse proxy and version _(e.g. nginx 1.27.2)
- official docker image
PHP version (e.g, 8.3):
- official docker image
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- official docker image
Are you using CloudfIare, mod_security, or similar? (Yes / No)
- No

Summary of the issue you are facing:

Since I’ve been having several problems now (mostly Segmentation fault for Nextcloud v33 on ARM VPS when installing apps but also some weird cron job not finding the data folder anymore) and having started my nextcloud with version 22 (I think), I’m thinking of migrating my little server to the AIO docker solution.

It’s really just a family server, with only 5 users and the data is easily accessible in a folder outside of the docker container.

So I’ve read the migration document all-in-one/migration.md at main · nextcloud/all-in-one · GitHub and have mostly just one question:

If I were to migrate just the files (easiest solution), does it automagically also migrate contacts and calendar data of the users?

Probably not, as the data is in the database, I guess. So the best way forward is using the migrate_user app?

I’m just trying to be cautious so I’m not losing data on the migration and my family won’t chew me up for this

ernolf · April 2, 2026, 8:53pm

Hi @Dominus,

You should first make an update with the magnificant calcardbackup script

You can then later on import ecerything back with the same tool.

h.t.h.

ernolf

Dominus · April 3, 2026, 1:36pm

Thank you. That’s a good advice and already on it.

But I found my biggest problem on migration is that my whole family is at home, and the new installation instantly goes into brute force protection as there are tons of invalid connections from the same IP (contacts and calendars trying to sync from everyone). This is a bit of problem getting this to work

ernolf · April 3, 2026, 6:16pm

It’s possible to exclude IP addresses/ranges from the brute force protection.

Make sure the bruteforcesettings app is enabled (it is by default)
Login as admin and go to Administration settings → Security

hth,

ernolf

Dominus · April 3, 2026, 9:05pm

Thank you, I got it all working for now.

mikesmith · May 2, 2026, 1:03am

How’d the migration go? I’m trying to migrate from NC 29 to NC AIO just have 2 users and only looking to move files. Any tips would be good

scubamuc · May 2, 2026, 5:50am

Hey @mikesmith and @Dominus waelcome,

try the official migration documentation…

github.com/nextcloud/all-in-one

migration.md

main

# How to migrate from an already existing Nextcloud installation to Nextcloud AIO?

There are basically three ways how to migrate from an already existing Nextcloud installation to Nextcloud AIO (if you ran AIO on the former installation already, you can follow [these steps](https://github.com/nextcloud/all-in-one#how-to-migrate-from-aio-to-aio)):

1. Migrate only the files which is the easiest way (this excludes all calendar data for example)
1. Migrate the files and the database which is much more complicated (with special handling required for former snap installations, see [below](#migrating-from-a-snap-installation))
1. Use the user_migration app that allows to migrate some of the user's data from a former instance to a new instance but needs to be done manually for each user

## Migrate only the files 
**Please note**: If you used groupfolders or encrypted your files before, you will need to restore the database, as well! (This will also exclude all calendar data for example).

The procedure for migrating only the files works like this:
1. Take a backup of your former instance (especially from your datadirectory, see `'datadirectory'` in your `config.php`)
1. Install Nextcloud AIO on a new server/linux installation, enter your domain and wait until all containers are running
1. Recreate all users that were present on your former installation
1. Take a backup using Nextcloud AIO's built-in backup solution (so that you can easily restore to this state again) (Note: this will stop all containers and is expected: don't start the container again at this point!)
1. Restore the datadirectory of your former instance: for `/path/to/old/nextcloud/data/` run `sudo docker cp --follow-link /path/to/old/nextcloud/data/. nextcloud-aio-nextcloud:/mnt/ncdata/` Note: the `/.` and `/` at the end are necessary.
1. Next, run `sudo docker run --rm --volume nextcloud_aio_nextcloud_data:/mnt/ncdata:rw alpine chown -R 33:0 /mnt/ncdata/` and `sudo docker run --rm --volume nextcloud_aio_nextcloud_data:/mnt/ncdata:rw alpine chmod -R 750 /mnt/ncdata/` to apply the correct permissions. (Or if `NEXTCLOUD_DATADIR` was provided, apply `chown -R 33:0` and `chmod -R 750` to the chosen path.)
1. Start the containers again and wait until all containers are running
1. Run `sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ files:scan-app-data && sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ files:scan --all` in order to scan all files in the datadirectory.

This file has been truncated. show original