Skip to content

Migrations

In this section, we can see all the migration processes that are currently taking place or have already been completed on the platform.

In this section, we can see a table with different columns:

  • Origin user: The original user, from whom the data is extracted.
  • Target user: The final or target user, where the data will be saved.
  • Category: The user's category. Only users from the same category can be migrated.

  • Status: The status of the selected action.

  • Exported: The user has been successfully exported.

  • Imported: The user has been successfully imported.
  • Migrated: The user has been successfully migrated.

  • Revoked: The request has been cancelled.

  • Created time: Shows when the action was created.

  • Import time: Shows when the action was imported.
  • Migration start time: Shows when the action started.
  • Migration end time: Shows when the action ended.

  • Action: Possible operations for the selected action.

  • Delete: {width="7%"} Used to delete the selected action.

  • Revoke: Used to revoke or cancel the selected action.

Important

This table only shows migrations between accounts with different authentication methods: Local - Google; SAML - Google; Local - SAML.

If a migration is done from Local - Local, it will not appear in the table.

If we expand any migration using the button , we can see what has been moved to the new user.

We can also see if any element failed and, if available, the reason for the failure.

How to perform a migration

To perform a migration, you need to consider the following points:

  • Any desktop that is turned on will be shut down.
  • The user's recycle bin will be emptied.
  • The user's reservations will be deleted.
  • Non-persistent desktops will be DELETED.
  • The co-owner list in deployments will be cleared.
  • Desktops that belong to other users in the migrated deployments will remain intact.
  • Resources not allowed for the new user will be removed or restricted.