Versions Compared

Old Version 5

changes.mady.by.user Kristina B.

Saved on

compared with

New Version 6

changes.mady.by.user Kristina B.

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning
  • To upgrade a project by migrating it, you need the Administer Resources, Edit Resources, Edit Resource Properties, and Read Resources permissions.
  • While a project is being migrated, other users are prevented from any modifications in that project. We highly recommend that the same person migrates all projects.
  • To ensure project integrity, it is recommended that you migrate all dependent projects (projects with its used projects) at once. In this case, you will not need to link used projects manually. You can migrate projects in separate batches; however, before migrating, you should identify projects related via the used project. After migration, used projects will end up as separately embedded projects rather than being correctly linked. Thus, you will need to link them manually.

Migrating server projects automatically

To migrate server projects automatically

...

After the project migration is completed, you will either get a message about successful project migration or a list of projects that were not migrated. You must migrate those projects manually.

Migrating server projects manually

To migrate server projects manually (for a user role with the Administer Resources permission)

...