Are you thinking of migrating your Episerver CMS 4 site to Episerver CMS 5? If so, we highly recommend that you first read the information below.

Which version of Episerver CMS 4 must I have to migrate to CMS 5?

The migration tool supports migration of Episerver CMS sites from version CMS 4.62 to CMS 5 SP2.

What if my Episerver CMS site is based on 4.51?

Then you must first upgrade the Episerver CMS site to be migrated to 4.62 using Episerver CMS Manager. Episerver CMS 4.62 is the only supported version for migrating to Episerver CMS 5.

What are the basic steps involved in the migration process?

The Episerver CMS 4.62 database is migrated in place and receives all the necessary configuration on the target CMS 5 site. After migration, the CMS 4.62 database has been converted to the CMS 5 schema, the CMS 5 site has configuration settings that map to the CMS 4.62 configuration, and its connection string points to the converted CMS 4.62 database.

How should I prepare my Episerver CMS 4 site for migration?

The steps that must be carried out before you can migrate your site are explained in the Migration Tool technical note. The article Preparing for Episerver CMS 5 also contains some useful information about what to think about before migrating to Episerver CMS 5. 


During migration if you experience problems and you recieve the message in the migration log: "System.ArgumentException: Cannot widen from source type to target type either because the source type is a not a primitive type or the conversion cannot be accomplished."  This is arises because the server that you are migrating to, does not have EPiServer CMS 4.62 already installed 

Before commencing migration you must install the EPiServer CMS 4.62 assemblies onto the server's GAC.  For further details regarding this, see the EPiServer Migration Tool technical note.

"The partner transaction manager has disabled its support for remote/network transactions"

If you are receiving the exception: "[Error] System.Transactions.TransactionException: The partner transaction manager has disabled its support for remote/network transactions," the following steps may help:

First verify the "Distribute Transaction Coordinator" Service is running on both database server computer and client computers:

  1. Go to "Administrative Tools > Services".
  2. Turn on the "Distribute Transaction Coordinator" Service if it is not running.

If the service is running and the migration tool and the database server are not running on the same machine; try this:

  1. Go to "Administrative Tools > Component Services".
  2. On the left navigation tree, go to "Component Services > Computers > My Computer" (you may need to double click and wait as some nodes need time to expand).
  3. Right click on "My Computer", select "Properties".
  4. Select the "MSDTC" tab.
  5. Click "Security Configuration".
  6. Make sure you check "Network DTC Access", "Allow Remote Client", "Allow Inbound/Outbound", "Enable TIP" (Some option may not be necessary, have a try to get your configuration).
  7. The service will restart; Though you may maay need to reboot the server if it still does not work.

System.Net.WebException: The remote server returned an error: (500) Internal Server Error

When you receive the above error in the migration log, you should turn on EPiServer logging on the R2 site and retry the migration. That will catch the error you get when the migration tool is trying to reach the R2 site.

Further Help with Transactions

There are some tools from Microsoft that can be helpful configuring/testing DTC (Distributed Transaction Coordinator), see the following links: