Supported migration paths

Migration is supported between equivalent offerings. For example, we can migrate from WebSphere Portal Enable v7.0 to WebSphere Portal Enable v8.5, but not from WebSphere Portal Express v7.0 to WebSphere Portal Extend v8.5.

Prerequisites

WebSphere Portal detailed system requirements

Supported migration paths...

Offering	Portal Express v8.5	Portal v8.5 (Server)	Portal v8.5 (Enable, Extend)	WCM v8.5
WebSphere Portal Express v7.x	Supported	Not Supported	Not Supported	Not Supported
WebSphere Portal Server v7.x (Server)	Not Supported	Supported	Supported	Not Supported
WebSphere Portal Server v7.x (Enable, Extend)	Not Supported	Not Supported	Supported	Not Supported
Web Content Manager v7.x	Not Supported	Not Supported	Not Supported	Supported
WebSphere Portal Express v8.0 on WAS v8.0	Supported	Not Supported	Not Supported	Not Supported
WebSphere Portal Server v8.0 (Server) on WAS v8.0	Not Supported	Supported	Supported	Not Supported
WebSphere Portal Server v8.0 (Enable, Extend) on WAS v8.0	Not Supported	Not Supported	Supported	Not Supported
Web Content Manager v8.0 on WAS v8.0	Not Supported	Not Supported	Not Supported	Supported
WebSphere Portal Server v8.0 (Server) on WAS v8.5.0	Not Supported	Supported	Supported	Not Supported
WebSphere Portal Server v8.0 (Enable, Extend) on WAS v8.5.0	Not Supported	Not Supported	Supported	Not Supported
Web Content Manager v8.0 on WAS v8.5.0	Not Supported	Not Supported	Not Supported	Supported

We can also migrate from a Server install to the Enable or Extend versions of IBM WebSphere Portal.

Fix Pack Requirements: Migration is supported from the two most recent fix packs for WebSphere Portal v7.0.0.x and v8.0.0.x. However, apply the latest cumulative fix to the source environment. Your target environment must also have the latest cumulative fix and the most recent fix pack applied.

To determine version...

WP_PROFILE/PortalServer/bin/WPVersionInfo.sh

When we migrate to v8.5, WebSphere Portal automatically migrates the following applications and configuration data:

• Security configuration
• Access control
• Portal behavior
• Portlet applications
• Customized portal resources, such as themes and skins, pages, and portlets
• Personalized content
• Virtual portals

We cannot upgrade the source portal with a fix pack after migration if you intend to remigrate the JCR. For example, if the source portal is v7.0.0.4 and you migrate it to v8.5, we cannot then upgrade the source portal to v7.0.0.5 and remigrate the JCR. This path is not supported.

Parent Plan for migration