Lagoon Migration: Everything You Need to Know

If you’ve seen us at events or been keeping up with us on the blog, you know that we’ve been gearing up for Lagoon, our next generation, open source hosting environment. We are excited to share that the great migration is underway. Here’s everything you need to know about how the migration to Lagoon will happen. will be migrating every single project to the new system over the next few months. If you’re a client at, your contract has already been updated to reflect this. Although we recognize that it’s ambitious to touch every single project hosted on, we know that by migrating to Lagoon we are updating our systems for years to come.

How will the migration work?

The migration will proceed country by country, with the U.S. and Switzerland up first over the next few weeks. Clients in the UK, Germany, Finland, South Africa, Japan, and all other countries are expected to be migrated throughout 2018.

We will need to change some code in every project, and have migration scripts to make things go smoothly. We will communicate with each client individually throughout the process to organize and transition each project. After we’ve made a plan and run the migration scripts, we keep your traffic going to the old system while you test out Lagoon. Once you’re comfortable, we can divert traffic to the new system and we will ask you to change the DNS settings.

A new chat system

While we migrate projects to Lagoon, we will also migrate client support and deployment information to RocketChat. It was important to us to move to an open-source chat platform that enables us to continue to provide the high quality of support our clients depend on. Our public channels will move over next week, and everyone will have an account created for them automatically. When we contact you to begin the migration process, we will create your private client channel at that time as well.

Lagoon Migration — Step by Step

Phase One — Planning

About two weeks before we want to migrate your projects, we will contact you to let you know we are getting ready. You will receive a document with all of your projects. We will ask you to look it over and let us know about any special circumstances we should know about when migrating these projects: critical sites, any expected high traffic, planned updates, etc. will work with you within the general timeline to migrate projects when it makes sense for your team for each one. We will continue to communicate with you and work as a team, but the migration itself is very straightforward. When everyone is ready we will run the migration scripts on all projects and create a Lagoon environment for each of them.

Phase Two — Testing

After the Lagoon environments are created, traffic will still flow to your old site so you can test out the new environments. During this time, we give you and your team about a week to try everything out. You can check on each project and give your developers time to test out a few changes to processes and local environments. For a full rundown of the changes, and a more technical explanation of the Lagoon Migration, check out this article in our documentation.

This is also the point during the migration where we will create a new private channel for you in Rocket Chat. The new deployments will be posted there.

Phase Three — Migration

After a week of testing, once you’ve confirmed everything looks great, we will ask you to change the DNS settings. We keep the old environments running to create an overlap that ensures everything works smoothly without downtime. This also means that while updates to the DNS settings should happen promptly, we don’t need to specify the exact moment it happens.


We are confident the migration will run smoothly with clear communication and no downtime. We built this process to give you the flexibility to make sure all your projects, and your team, have everything they need to thrive on Lagoon. If you want to know more or have specific questions, just give us a shout in Slack.