Migrate projects with the Tosca Administration Console

The Tosca Administration Console helps you create an efficient and scalable testing infrastructure. Take advantage of one of its biggest benefits: the migration feature, which saves a lot of time and effort during the upgrade process.

There are two types of migrations during a Tricentis Tosca upgrade:

  • A schema migration, which updates your repository database schema to the latest version.

  • An XEngine migration, which updates existing Standard subset Modules and their connected TestCases to the latest version.

You may not need both types of migration every time you upgrade Tricentis Tosca. For detailed information on when you need which, check out "Schema migrations" and "XEngine migrations".

This topic explains how to perform migrations in the Tosca Administration Console.

Before you start

Before you can migrate projects, you need to have a few things in place:

  • You're an administrator. Only administrators can trigger migrations.

  • All users have checked in their local changes. You can always revoke checked-out objects during the migration, but then you lose all local changes that the user has made.

  • When you migrate projects, the console creates a new workspace to fetch and update the objects in your repository. The console needs Tricentis User Administration user credentials to access that workspace. You can use your own credentials, or that of any other admin user.

Migrate projects

You can either migrate a specific project, or you can migrate all projects in the console. To migrate, follow these steps:

  1. Open the console and trigger the migration: 

    • To migrate all projects, select Migrate all in the header. Depending on the individual project, this either triggers a schema migration and an XEngine migration, or just the XEngine migration.

    • To migrate a specific project, select Migrate or Migrate TestCases in the row of the project.

      • Migrate triggers a schema migration and an XEngine migration.

      • Migrate TestCases triggers an XEngine migration only.

  2. In the subsequent Migration Options dialog, enter the following information: 

    • User credentials for the workspace that the Tosca Administration Console creates during the migration.

    • Whether you want to revoke objects that are currently checked out by other users.

    • Whether you want to create a backup before the migration. We recommend that you do. The console saves the backup to %TRICENTIS_ALLUSERS_APPDATA%\Automation\MigrationBackup.

      Please note, this backup is just for safety. If the migration is successful, you don't need to restore anything.

Trigger a migration that creates a backup, but doesn't revoke objects checked out by other users.

  1. Select Start migration.

Once the migration has finished successfully, the Last Migration Status column shows the message Ready to go.

Check your logs

The migration creates a log with detailed information on migration tasks and errors. To see what happened during the migration and fix potential issues, select the icon in the Actions column.

What's next

The migration's done, and you're ready for the next step? If that's the case, these topics might interest you:

  • This section guides you through the rest of the upgrade, so your QA teams can enjoy the great new things this Tosca version has in store for them.

  • If you created a safety backup and something went wrong during the migration, learn how to restore your repository with minimal fuss.