When to use Content Porter

Use Content Porter to transfer selected items from one Content Manager instance to another. You can also build a custom import/export client yourself for this purpose. Do not use Content Porter for upgrading, backing up or restoring all of your Content Manager data.

Content Porter lets users transfer items between instances of Content Manager which can have different versions. A typical example of this use of Content Porter is the transfer of implementation code, such as Schemas, Templates, and Keywords, from a special development Content Manager server to a number of other Content Manager servers (typically following the sequence known as DTAP: Development, Testing, Acceptance, Production).

Instead of using Content Porter, you can also choose to implement a custom client that talks to the Import and Export service of SDL Tridion Sites (or of its predecessor, SDL Tridion). Content Porter is easy to get up and running, and offers the person performing the transfer a great deal of control over the import and export processes. But if you want to limit the user's ability to control these processes, and if you are willing to spend the implementation effort, such a custom client could be a better choice. Note that you cannot use such a custom client to export content from, or import content into, a Content Manager instance belonging an SDL Tridion release older than SDL Tridion 2013 SP1.

Do not use Content Porter for the following tasks:
  • Upgrading your content database to a new version of Content Manager. To perform this task, refer to the upgrading documentation.
  • Creating or restoring a backup of your content. To perform this task, use a normal database backup and restore instead.