Migrating to the new Umbraco Cloud infrastruture
In this article, you’ll find all relevant information to be aware of when a site is migrated from the old to the new Umbraco Cloud infrastructure. This article is kept up-to-date should any new information arise.
Schedule and timing
Projects are scheduled for migration through Q3, 2021. When a project is scheduled the project owner and technical contacts will receive direct communication via email 2 weeks in advance with the specific date and time.
In case the timing of the migration schedule does not work for you, it is possible to reschedule by reaching out to [email protected].
Minimum requirements for migration
In order for an Umbraco Cloud project to be scheduled for migration, the following requirements need to be fulfilled.
Minimum version requirements
The new infrastructure comes with minimum requirements on what version of Umbraco CMS and add-ons. In order to be scheduled for migration projects must run:
|Minimum required version|
|Minimum required version|
You can find the Umbraco CMS, Forms and Deploy version for each environment listed on the project page in the Umbraco Cloud Portal:
More information on upgrading can be found in the documentation article for upgrading to the latest minor or if you’re using the UaaS.cmd tool refer to the manual upgrade documentation.
Projects that do not meet the requirements, cannot be scheduled for migration to the new infrastructure.
Updated DNS settings - you might need to update settings
Your projects need to be updated to use the new Cloudflare DNS settings.
All CNAME records must point to dns.umbraco.io. If you require an A-Record this must point to
184.108.40.206. See the Manage Hostnames documentation for detailed instructions.
You can see if you are using the new Cloudflare DNS settings or the “old” Let’s Encrypt under Project settings -> Hostnames:
Before the migration
A project is only scheduled for migration when all the requirements are met. If outgoing IP addresses on Umbraco Cloud are being used, i.e. adding them to an allow list, note that these will change when the project is migrated to the new infrastructure. In this case, it is recommended to add the new outgoing IP addresses to the allow-list prior to the migration. See the Using external services with Umbraco Cloud documentation for the full list and more information.
No other actions are required prior to migration.
During the migration
We kindly ask users to hold off working on the project during the 4-hour migration window to ensure that deployments and other Umbraco Cloud services are not interrupted.
Please do not:
- Interact with the backoffice on Dev/Stage/Live env.
- Update schema in the backoffice on Dev/Stage/Live env.
- Update project settings in the Cloud portal
- Initiate deployments between environments in the Cloud portal
- Interact with Git repositories(sync/push/pull)
Work on the project(s) can resume immediately after receiving confirmation of a successful migration.
After the migration
New Umbraco Cloud project URL
The project URL will change from
my-project-alias.euwest01.umbraco.io. It is only the project URL that changes. Custom hostnames will continue to work as before.
New outgoing IP addresses (for allow lists)
The outgoing IP addresses on Umbraco Cloud will be changed once the projects are running on the new infrastructure. This is only relevant if you are working with an allow list. In this case, please add the new outgoing IPs prior to migration.
Several blog posts has been published detailing the journey to the new and improved infrastructure:
- The future of Umbraco Cloud (December 2020)
- New DNS settings and requirements - Status on new Umbraco Cloud infrastructure, February 2021
- New infrastructure is ready - Status on new Umbraco Cloud infrastructure, March 2021
- Migration process - Status on new Umbraco Cloud infrastructure, April 2021
- Migration schedule - Status on new Umbraco Cloud infrastructure, June 2021