NEW RELEASE! The 2022x Refresh2 Hot Fix 3 was released on February 28, 2025. For more information, see 2022x Refresh2 Hot Fix 3 Version News.

On this page


After upgrading your modeling tool, you need to migrate the projects and standard profiles stored in the 3DEXPERIENCE platform to the new version as well.

Migration workflow

There are two workflows you can follow to migrate the projects and standard profiles in the 3DEXPERIENCE platform. Choose the workflow that is best suited for your situation and follow all the steps to make sure that the migration is successful.

Prerequisites

  • To migrate standard profiles, you need to have write permissions in the collaborative space where profiles are stored.
  • To migrate a project, you need to have write permissions on its branch/revision and maturity to allow iterations to be created.

Certain standard profiles cannot and do not need to be migrated, for example, those that have been discontinued or renamed. It is acceptable to leave these profiles unmigrated. For a complete list of standard profiles that do not require migration, see Standard profiles that cannot be migrated.


To migrate all database (projects and standard profiles) at once

  1. Migrate all projects and standard profiles on the server. It is OK if you get an error that some projects or standard profiles are not migrated
  2. Add all standard profiles to the 3DEXPERIENCE platform.

    This step is necessary because standard profiles can change with each version, and new ones may be introduced. If a new standard profile exists in your modelling tool installation and other profiles depend on it, it must be added to the 3DEXPERIENCE platform before migrating the dependent profiles.

  3. Migrate all projects and standard profiles on the server.
  4. Add all standard profiles to the 3DEXPERIENCE platform.
  5. Migrate all projects and standard profiles on the server.
  6. If some standard profiles are still not migrated, check the Standard profiles that cannot be migrated list. The profiles on that list do need to be migrated.


To migrate standard profiles and projects separately

  1. Migrate all standard profiles on the server. It is OK if you get an error that some standard profiles are not migrated, go to the next step.
  2. Add all standard profiles to the 3DEXPERIENCE platform.

    This step is necessary because standard profiles can change with each version, and new ones may be introduced. If a new standard profile exists in your modelling tool installation and other profiles depend on it, it must be added to the 3DEXPERIENCE platform before migrating the dependent profiles.

  3. Migrate all standard profiles on the server.
  4. Add all standard profiles to the 3DEXPERIENCE platform.
  5. Migrate all standard profiles on the server.
  6. If some standard profiles are still not migrated, check the Standard profiles that cannot be migrated list. The profiles on that list do need to be migrated.
  7. Migrate the projects on the server.


  • When migrating standard profiles, a revision is created for each profile that is migrated.

  • When migrating projects, an iteration is created for each branch/revision of a migrated project.

  • If the 3DEXPERIENCE platform is upgraded, but you still use the same version of a modeling tool, standard profiles do not change and you do not need to migrate them.
  • You can only migrate projects to the version of your modeling tool.
  • You can migrate projects partially to allow users to work on both an earlier version and the version you are migrating to. However, if you start working and creating projects on a later version, you cannot migrate or add projects to an earlier version.

Migrating all projects and standard profiles at once

You can migrate projects and standard profiles all at once.


To migrate all projects and standard profiles at once

  1. In the main menu, select Collaborate > Migrate Projects to Version <version number>.

  2. In the Show drop-down menu of the open dialog, select All Projects. It will display all projects and standard profiles on the server.

  3. Click on the left side of the dialog to select all projects and standard profiles.



  4. Click OK.

Migrating standard profiles

To migrate projects separately from standard profiles, you must first migrate the standard profiles.


To migrate standard profiles

  1.  Log in to the 3DEXPERIENCE platform.

    Make sure to select a public collaborative space that everyone can access. To learn how to create a collaborative space for standard profiles, see Creating public collaborative spaces.

  2. In the main menu, select Collaborate > Migrate Projects to Version <version number>.

  3. In the Show drop-down menu of the open dialog, select Standard Profiles. It will display all standard profiles on the server.

  4. Select the standard profiles you want to migrate or click on the left side of the dialog to select all standard profiles.



  5. Click OK.

Migrating projects

You can migrate projects either automatically through the dedicated dialog or manually by opening a project that has not yet been migrated. Please note that for either of these methods to work you have to migrate standard profiles beforehand.

Migrating projects automatically

If you migrate projects automatically through the dedicated dialog, all branches of the projects are migrated as well.


To migrate projects automatically

  1. In the main menu, select Collaborate > Migrate Projects to Version <version number>.

  2. In the Show drop-down menu of the open dialog, select Projects. It will display all projects on the server.

  3. Select the projects you want to migrate or click on the left side of the dialog to select all projects.



  4. Click OK.

Migrating projects manually

If you choose to migrate a project that you are opening, only the branch that you are opening will be migrated.


To migrate a project manually

  1. On the main menu, click Collaborate > Projects.
  2. In the Manage projects dialog, select a project and click Open. A dialog opens telling you to update the System/Standard Profiles in the project.



  3. Click Continue.


After the System/Standard Profiles are updated, you get a notification saying that the model was successfully updated. 

Standard profiles that cannot be migrated

The following standard profiles can not and do not need to be migrated:

  • UML_Testing_Profile - A new version of this profile does not exist. You do not need to migrate it. 
  • MD_customization_for_UML_Testing_Profile -  A new version of this profile does not exist. You do not need to migrate it.
  • SPEM 2.0 Profile - The profile is discontinued. You do not need to migrate it.
  • RUP_Extensions_Profile - The profile is discontinued. You do not need to migrate it.
  • RM_ODP_Profile - The profile is discontinued. You do not need to migrate it.
  • ParametricExecutionProfile  - The profile is discontinued. You do not need to migrate it.
  • Java_SE_7_Library_Full - The profile is discontinued. You do not need to migrate it.
  • Java Wireless Toolkit 2.5 - The profile is discontinued. You do not need to migrate it.
  • ISO-26262 Profile - This profile was renamed to ISO26262. A new profile should be added to the server and used instead of the old one.
  • FTALib - The profile has a bug and cannot be migrated. You need to upgrade your modeling tool to a later version once it is released.
  • FTA_Customization - The profile has a bug and cannot be migrated. You need to upgrade your modeling tool to a later version once it is released.

The following UPDM profiles cannot be migrated because they contain bugs (you need to wait for fixes in the upcoming versions):

  • UPDM Profile
  • BPMN2 Customization
  • XPDL Profile
  • BPMN-SOAML Integration Profile
  • UPDM Constraints

Activity

All
Popular
Personal filters
All
Inga A.