Aug 9, 2022
(12 votes)

Deploying your CMS 12 upgrade on DXP

Deploying changes to a DXP cloud service is easy [citation needed] you can use the deployment API or PowerShell module to push packages through your environments directly, or setup an Azure Devops pipeline or similar CI/CD tool once and for all.


If you are upgrading to CMS 12 or to Commerce 14, the underlying infrastructure changes a bit, so there is an extra step and a new “Project Migration” tool available in the portal which guides you through the transition. Read on for a high-speed run-through of the tool and the process as it looks right now.


The “Project Migration” tool creates a set of brand-new environments that you can use in addition to your current environments during migration. Eventually when you feel ready for it, you will move traffic to the new project, and the old project will be reclaimed.



To get started with this process, click the “Project Migration” tab and “Start migration”. Don’t worry about impacting your live site, nothing dangerous is happening here.


Once this part of the process is complete, you get a link to a new project - “teor2mstr” in this example - and the option to copy over content from your current environments.


With the new environments in place, it’s time to put them to use. You may want to setup a new deployment pipeline and a dedicated branch to target the new environments, since you are probably going to deploy many iterations of your upgrade before going live, and the new project will be your permanent home once the migration is done. The “old” environments remain unchanged and completely functional, and you can deploy changes to both throughout this transition.



Once you have an upgraded code package running in the new production environment, and you completed whatever test procedures you have, it’s time to start moving traffic over. You don’t have to move everything all at once; you can start with integration and preproduction before taking the plunge, and you can copy content from the current live environments as many times as you need, to make sure everything is up to date. When you want to move traffic over, you put the old environment in maintenance mode as part of the process..


I hope this lap around the new migration tool was useful, for more details around transitioning DNS records, maintenance mode options and more, check out the docs here.



  • What happens to the old project?
    The project you are currently using will continue to work as-is until after you’ve gone live with the new project. After going live, we retain the old project for some time (currently seven days). When the retention period expires, the old project is deleted.
  • Can we take the opportunity to rebuild the website while migrating?
    That’s up to you, our general advice would be to avoid biting off more than your can chew, take the shortest path to CMS 12 and iterate from there.
  • How long can I keep both projects running?
    Please abort the migration if the project stalls for some reason. You can always restart the migration again later. If the migration isn’t completed within 5 months, we reserve the right to reclaim to abandon the migration on your behalf.
  • Do I have to pay extra for the migration environments?
    At this point there is no additional cost involved in migrating the service.
  • Any changes to the infrastructure?
    The new environments are using to newer, faster instances, and origin shield is on, beyond that, everything should be completely familiar.
  • Any changes to the process?
    Web Deploy is no longer supported, so new packages must go through the deployment API


Aug 09, 2022


Eric Markson
Eric Markson Aug 10, 2022 01:11 PM

I'm so thrilled that this exists! You guys are doing amazing work!!

This will for sure help customers make the decision, now that they will have CMS12 environments to migrate to and test!

KennyG Aug 10, 2022 03:11 PM

This is amazing! Thank you so much for offering this!

Sebbe Aug 11, 2022 10:15 PM

@MartinOttosen if you have a multisite, is it possible to deploy for only one of the sites first, then next etc?

Ove Lartelius
Ove Lartelius Aug 15, 2022 02:35 PM

Wow! I like it a lot! Good job!

MartinOttosen Aug 17, 2022 10:05 AM

Thanks for the kind words all, the team that did the actual work will be thrilled ;)

@Sebbe, right now you migrate traffic for an entire environment at a time, so if you have multiple sites running off a single production environment, they will all be migrated together. We are exploring how we could support migrating smaller chunks of traffic. If this is important to you, we would love to hear about it here.

Please login to comment.
Latest blogs
When best practice isn't the best - Dependency Injection and Optimizely CMS

Some people live and breath 'best practice' development. I am not one of them. Risk is, in-experienced developers (or sometimes experienced) might...

Allan Thraen | Jan 29, 2023 | Syndicated blog

Implementing EmbeddedLocalization in Optimizely CMS 12

My previous post on translation (Translating Optimizely CMS 12 UI components) gives an overview of how to implement the FileXmlLocalizationProvider...

Eric Herlitz | Jan 27, 2023 | Syndicated blog

Breaking changes in EPiServer.CMS.TinyMce 4.0.0

After upgrading to the latest version of EPiServer.CMS.TinyMce, the dropdown with formats disappears. Learn how to get it back!

Tomas Hensrud Gulla | Jan 27, 2023 | Syndicated blog

Translating Optimizely CMS 12 UI components

Optimizely CMS 12 have been out for a while now, but still some elements haven't been properly translated resulting in a GUI defaulting to english....

Eric Herlitz | Jan 26, 2023 | Syndicated blog

Image preview in Optimizely CMS12 all properties view

With these simple steps, you can now see an Image and its Metadata, including size and dimensions, when editing an Image property in Optimizely...

Tomas Hensrud Gulla | Jan 26, 2023 | Syndicated blog

Setting up the ImageEditor in Optimizely CMS 12

Setting up certain configurations on Opimizely CMS 12 differs quite a bit from prior versions of (Episerver CMS 11 and older). Here's a small guide...

Eric Herlitz | Jan 25, 2023 | Syndicated blog