Did a dry run of the Stalwart 0.16 -> 1.0 migration with a copy of my server. Went fine, but heads up if you use the admin API
retained text
1.0 is out since Sunday, so I tested the upgrade with a copy of my server first. Heads up: this is not a simple image update. 1.0 has a new db layout and won’t open a 0.16 store. And latest already points to 1.0, so if you use latest or watchtower, pin v0.16 now or the next pull kills your mail server. The upgrade goes through stalwart-migrate (you need 0.16.27 first). It only reads the old store and writes into a new one, so going back is easy. I put last night’s backup on another VM in a docker network without internet (didn’t want the copied queue to send mails, lol). Small setup: 10 accounts, RocksDB. prepare asked 4 questions, I took the defaults. run --final took 41 seconds for 920 mails, verify said 0 mismatches. 1.0 started fine on the copy. What bit me: my little admin app for the JMAP API failed creating a domain with “Invalid key for object”. Domain isEnabled and alias enabled are both called enable now. Annoying part: reading the old name gives no error, the field is just missing. So if you have scripts against the admin API, test writes too, not only reads. SCHEMA\_CHANGES.md in the stalwart-migrate repo has the full list. Also: OAuth clients need to log in again, search index gets rebuilt, IMAP clients don’t redownload everything. I’ll wait for 1.0.1 before doing it for real, but the dry run took maybe half an hour and I’m way less nervous now. Happy to share the commands if anyone wants them.
document fetched 2026-10-28 00:30 · canonical https://reddit.com/r/selfhosted/comments/1xgldsw/did_a_dry_run_of_the_stalwart_016_10_migration