Migration day..
The day is getting closer, and it is time to talk about what is going to happen on the actual day. Let’s start here:
As our old hardware is running out of warranty, Kolab Now is going to migrate to a brand new fine set of hardware. As the old hardware, the new environment is located in a datacenter in Bern, Switzerland. The migration is going to happen on:
Monday 23rd of March, 2026.
Prior to the migration day we have done a lot of preparation, and the complete migration is tested in a live exercize. To avoid some complexity, which potentially could make troubles for the migration, we have stopped the signup pages during the migration period. If you tried to signup Thursday or Friday, you will have seen that it did not succeed. Please try again on Tuesday.
On the day, we will start move over jobs to the new environment at 09:00 CET. This should not cause any downtime for users, but there might be some slowness, irregularities and unexpected behavior. Emails will however still be delivered and users will be able to use the features they love.
At 13:00 CET we will switch over the database and the main DNS.
This will cause downtime that can last up to 20 – 30 minutes.
After this switch, Kolab Now is running in the new environment, and the old environment is disconnected.
A short reminder about the new Single Sign Ono solution that will be in place. You can read about it in this blog post.
This blog is going to be live all the way during the migration. We will keep you updated through updates to this post.
We are looking forward to welcome you on to the new environment.
——————————————————————————————————————————————–
Update 2026-03-23 @ 09:00 CET: This update is just a short note to let y’all know, that the migration work has started. Where as you might experience some irregularities during the day, the real downtime will be at 13:00. This blog will stay online during the migration, and we will update it with any news.
Update 2026-03-23 @ 13:00 CET: We seem to be running into DNS issues that we did not experience during the test migration. It might be external, but until we have it fully investigated, the 13:00 time window is moved down the line to 14:00 (so far). More updates and situation reports to come here.
Update 2026-03-23 @ 14:30 CET: We got a step further in the investigation of the DNS issues. We believe that we found the cause, and we are running tests at this time to check the corrections. At this time we would like to run another test migration and monitor the systems. we therefore have decided to postpone the migration until:
Tomorrow, Tuesday March 24, 2026 @ 13:00 CET.
We apologize for any inconvenience.