Migration from Pro/INTLALINK 3.x to the next generation of Pro/INTRALINK or Windchill PDMLink is not as simple as the upgrades that you may have experienced when moving from Pro/INTRALINK 3.1 to 3.2, or 3.3 to 3.4. There is a substantial amount of System Design, Configuration, and Use-Case Testing that needs to be done on the new system, before you can begin migrating. When you install and configure your new system, you will want to take into consideration the existing configuration in your 3.x system, since you will be mapping many items from 3.x during your migration. Since Roles, Folder Authorizations, Release Procedures, Preferences, Table Displays, Locate Searches, and Replication settings are not migrated, they will need to be re-created (in as much as there are equivalents) and thoroughly tested before going live on the new system. Of the items that are migrated by the Pro/INTRALINK Data Migrator, some things to consider in your System Design should include:

• Version Sequence - Probably needs to match your existing Pro/INTRALINK 3.x Revision Sequence
• Lifecycles and States - OOTB defaults may need to be reconfigured, in order to enable mapping of 3.x Release Scheme(s) and Release Levels
• Instance Based Attributes - May need to be created to enable User Defined Attribute mapping.
• Product & Library Containers/Folders - Folder Mapping activities may enable you to leverage existing Folder Structure to a great degree, however some consideration should be given to Product and Library Container behavior.

As you can see, there is a lot to think about when planning your move to. If you've got questions about any of the items I've mentioned in this blog, I encourage you to ask them in the Pro/INTRALINK Upgrade Advisor Forum.