Mar 23, 2010
visibility 21559
star star star star star
(2 votes)

How to Upgrade an EPiServer CMS 5 Site to CMS 6

The EPiServer Deployment Center can be used to upgrade an EPiServer CMS 5 R2 SP2 site to CMS 6.  The upgrade process is quite simple and converts the site content, settings, and form data, in place, from the old format to the new.  The upgrade process upgrades the EPiServer user interface, assemblies, and converts database objects and data as needed. 

If you have multiple sites, each site can be upgraded one at a time as long as they are in separate CMS instances / databases.  If you are running an enterprise configuration where multiple sites are managed from the same CMS instance / database, all of the sites will be upgraded at the same time.

The EPiServer Deployment Center will take care of upgrading the content and the EPiServer components, but it is strongly recommended that you thoroughly test your Page Templates, Dynamic Content, Plug-ins, and any other modules that reference the EPiServer API or web services to ensure that there are no compatibility issues with the latest version.

For more details on what the upgrade process does, check out Per Bjurström’s blog entry, Upgrading to CMS 6 RC1.

Upgrading an EPiServer CMS 5 R2 SP2 site to CMS 6.0

The image below depicts the CMS 5 R2 SP2 site prior to the upgrade.

image

1. Launch the EPiServer Deployment Center.

2. Navigate the tree to Installed Products > EPiServer CMS > Version 6.0.530.0.

3. Select Upgrade Site with SQL Server database. 

4. Click the Run button.

image

5. On the Upgrade an existing EPiServer web site – Step 1 of 2 dialog, select the CMS 5 site that you wish to upgrade.

image

6. Click the Next button.

7. Verify your settings on the Upgrade an existing EPiServer web site – Step 2 of 2 dialog, and click the Upgrade button.

image

8.  The EPiServer Deployment Center progress dialog will be displayed showing the progress of the upgrade. Click the Close button when it has finished.

image

9.  Close the EPiServer Deployment Center.

10. Clear your temporary internet files as many of the Edit and Admin Mode images from CMS 5 will be cached in Internet Explorer.

image

11. Navigate to the upgraded site to verify the upgrade.

image

Mar 23, 2010

Comments

Jeff Wallace
Jeff Wallace Sep 21, 2010 10:33 AM

Nice and simple process. :)

Sep 21, 2010 10:33 AM

Hi,

In Step 7 I get an this error on the Database Settings:
Database Name : Error {Namespace prefix 'epi' is not defined.}
Database Server Name : Error {Namespace prefix 'epi' is not defined.}

Does anybody got an idea what the error is trying to tell me?

Thanks!

Tommy.Bryntse@creuna.se
Tommy.Bryntse@creuna.se Sep 21, 2010 10:33 AM

Will this work with a "EPiServer CMS 5 SP3" site too?

Stephan Lonntorp
Stephan Lonntorp Oct 25, 2010 03:59 PM

I also get the Database Name : Error {Namespace prefix 'epi' is not defined.} error, does anyone know how to resolve it? Mark, did you get around it somehow?

Stephan Lonntorp
Stephan Lonntorp Oct 25, 2010 04:18 PM

I had an error in my web.config, so the site wouldn't start. So I guess the "Database Name : Error {Namespace prefix 'epi' is not defined.}" error message is trying to tell me that I need to check that the original site is working before I expect the upgrade process to work.

error Please login to comment.
Latest blogs
You’re not headless. You’re hybrid — and that’s the CMS 12 default.

For CMS 12 / Commerce teams with a React (or similar) storefront who keep hearing “just go headless” or “just move to Graph.” This is Part 1 of Fin...

Hanskumar Tripathi | Aug 13, 2026

Stott Security for Optimizely SaaS CMS

Introduction Stott Security  has been helping developers and editors manage Content Security Policies and security headers on  Optimizely PaaS CMS...

Mark Stott | Aug 13, 2026

Optimizely XML Resource Builder: A Visual Studio Extension for Language Resource Files

Anyone who has worked on a larger Optimizely solution will know the feeling. You add or update a page type, block type, or shared base class,

Adnan Zameer | Aug 13, 2026 |

Optimizely SaaS CMS Management API: The Write Side of Headless

Everything I’ve written in this series so far has been about reading content — Optimizely Graph, webhooks, ISR, caching layers. But at some point y...

Kiran Patil | Aug 12, 2026 |