We are planning to upgrade from Tridion 2011 SP1 to Tridion 2013 SP1. As part of that, we are planning to move our Databases from Oracle to SQL Server. We are planing to maintain parallel environments as we dont want to disturb the existing environments where development is going on.

What is the best way for migrating the content. I am thinking about using content porter. But can we use content porter for porting content between different CM versions such as 2011 SP1 to 2013 SP1?

3 Answers 3


You can Content Port from earlier versions of Tridion in to SDL Tridion 2013 SP1 - I did this recently, between Tridion 2011 SP1 HR1 and Tridion 2013 SP1.

One thing to note is that you will need the Content Porter 2013 SP1 Client to be able to import in to SDL Tridion 2013 SP1. Although SDL Tridion 2013 SP1 now comes with the Import/Export Webservice as part of the Core Content Manager (CM) installer, you will still need to get the Content Porter 2013 SP1 installer to make the Content Porter client available within the Tools menu.

enter image description here

You will need to consider that there is a small list of Known issues (login required) with Content Porter 2013 SP1.

However, the biggest thing to note with this approach of using Content Porter, is that there are a number of items that are not exported when using Content Porter.

The full list can be found on the Non-exportable items page of the SDL Content Porter 2013 SP1 online documentation (login required). However, the main 'non-exportable items' to note in your situation are probably:

  • Publication Targets and Target Types in publishing
  • Page and Component publishing status
  • Users
  • Security settings for Users and Groups
  • Permissions for Publications, Folders, and Structure Groups

You will need to ensure that there is a content freeze in place during the migration period.

It may be worth doing a few 'dry runs' on the migration, and saving the Content Porter configuration each time (and possibly scripting the migration), so that you can reduce the chance of forgetting something.

You may want to discuss your situation with Tridion Support or Professional Services, as they may have encountered this situation before.

  • 1
    Also worth noting, content porting the entire Tridion BluePrint might have some pain points and will definitely take a bit of time. You will need to increase timeout and package size settings to allow this size of import/export. Commented Jul 2, 2014 at 18:23
  • A very good point, Chris. Thanks for the input. Commented Jul 3, 2014 at 5:52
  • @Jonathan & Chris, What about Content Data Store. Need to republish all sites once content is successfully moved? Commented Jul 11, 2014 at 8:49
  • @user1453602 Yes, you will need to re-populate the Broker database with a re-publish. This is the most reliable way of keeping your Content Manager and Broker databases consistent (with what has been published to where). Also, when you Content Port, your IDs will be different, so the old (Oracle) Broker database information won't relate to your new (SQL Server) content. Commented Jul 11, 2014 at 9:11
  • @Jonathan, Our new environment will be on cloud. We will be exporting content from current PROD (Tridion 2011 SP1)which is hosted in house. Do we need content porter client 2013 sp1 in our current PROD to be able to export content? Or export taken using current content port can be imported using Content porter 2013 SP1on cloud environment. ? Commented Aug 1, 2014 at 9:53

I've never heard of a switch between oracle and sql server before.

I doubt it's possible to content port from 2011 SP1 over to 2013 SP1, but certainly worth a trail run, it it works great.

If it doesn't work, then you're best best is to upgrade your existing CM and CM DB up to 2013 SP1 and then from there you can use Content Porter to move the publications and content from your old CMS (using oracle) over to your new CMS based on SQL server.

  • It really depends on the version of Content Porter, but ports across Tridion versions is generally possible with two catches. 1. It's typically allowed for the latest major or service pack versions so sometimes an upgrade is needed. 2. All the functionality in later versions can't be kept for an older version. For example Bundles can't be ported into a Tridion version before 2013. Commented Jul 3, 2014 at 17:52

Traditionally I thought you've only been able to content port to/from the same version.

According to the 2013SP1 doc you can Content Porter supports transfer between different versions of Content Manager


Content Porter 2013 SP1 can connect to any Tridion server version as of 2011 SP1 HR1 (so, 2011 SP1 HR1, HR2 and 2013 GA and SP1).

  • Thanks, Dylan. I updated the first link to the specific SDL Live Content topic that describes transfers between Tridion versions. I kept your original overview link but moved it to the edited section. Commented Jul 2, 2014 at 17:27
  • Thanks Alvin - a few interesting 'reminder' points throughout this thread overall! Commented Jul 3, 2014 at 7:53
  • Hello, I have tried to export content from Tridion 2011 SP1 HR1 using Content Porter 2013 SP1. Then, I have tried to import that file in a Tridion 2013 SP1 using Content Porter 2013 SP1. I have got an error message: Version of the package c:\..... is not supported. ¿Do I have to do the export using other version of Content Porter? Commented Jun 17, 2015 at 14:09

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.