Running a Migration
Executions page
The Executions page lists all your configured migrations and shows the status of their last execution. Use the search field to find a migration by name.
Each entry has an Actions menu with two options:
- Migration steps - View and run the migration for this entry.
- Open log file - Open the log file from the most recent execution. This button is disabled if the migration has never been run. If the log file no longer exists on disk, a warning message is displayed.
Before you run
Before starting a migration, verify the following:
- All connections have had a successful metadata refresh and reflect the current state of the source environment.
- All apps/projects, reports, and tasks you want to migrate are set to Migrate = Yes.
- If the target is Qalyptus Cloud, all connections referenced by reports are mapped to a Qlik Sense application in the Qlik Apps tab.
- If the target is Qalyptus Cloud and you have assigned custom owners to content, those users have synchronized their Qlik Sense apps in their Qalyptus Cloud profile.
- Custom target security roles (Qalyptus Server only) have been created before running, if you want to map custom source roles to specific Qalyptus roles.
Running a migration deletes all existing data in the target environment (except the administrator user linked to the API key) and replaces it with the migrated content. This action cannot be undone.
Do not run a migration against a production environment that contains data you want to keep.
Migration steps
Click Migration steps to open the execution panel. This panel displays all the steps that will be executed, each starting with the Pending status.
The steps are executed in order. If a step fails, its status changes to Error and the migration stops. You can review the log file to identify the cause before retrying.
The steps vary depending on the source and target combination:
| Step | NPrinting to Server | NPrinting to Cloud | Server to Cloud |
|---|---|---|---|
| Migrate Security roles | Yes | - | - |
| Migrate Users and Groups | Yes | Yes | Yes |
| Migrate Apps / Projects | Yes | Yes | Yes |
| Migrate Connections | Yes | - | - |
| Migrate Filters | Yes | Yes | Yes |
| Migrate Conditions | Yes | Yes | Yes |
| Migrate Reports | Yes | Yes | Yes |
| Migrate Destinations | Yes | - | - |
| Migrate Storage services | - | - | Yes |
| Migrate Tasks | Yes | Yes | Yes |
| Migrate SMTP settings | Yes | Yes | Yes |
| Migrate Trusted origins | Yes | - | - |
| Migrate LDAP connections | Yes | - | - |
| Migrate SAML configuration | Yes | - | - |
Steps not applicable to your migration path are automatically marked as Skipped.
Running the migration
Click Run in the migration steps panel. A confirmation prompt is displayed:
Run Migration. Running this migration will:
- Delete ALL existing data in the target application except some technical information.
- Replace everything with migrated content from the source.
This action cannot be undone. Do you want to continue?
Click Confirm to start. The status of each step updates in real time as the migration progresses.
You can stop the migration at any time. This cancels the current step and leaves remaining steps unexecuted. Steps that were already completed are not rolled back.
Understanding migration statuses
| Status | Meaning |
|---|---|
| Pending | Not yet executed. |
| Running | Currently executing. |
| Success | Completed without errors. |
| Skipped | Not applicable to this migration path. |
| Error | Failed. See the log file for details. |
Migration log
Every migration execution generates a log file. The log records:
- The tool version and connection names.
- Every operation performed, with its result.
- Warnings - items that migrated but require manual follow-up (see below).
- Errors - items that failed to migrate.
Log files are saved to the data folder configured in the application settings, using the naming pattern:
QalyptusMigrationTool_YYYYMMDD_HHMMSS.txt
Click Open log file in the Actions menu to open the most recent log for a given migration.
Post-migration actions required
After a successful migration, some items require manual action that cannot be automated:
| Item | Action required |
|---|---|
| User passwords | All migrated user accounts have no password set. Users must use the "Forgot password" flow to set a new password. |
| Administrator account | The administrator linked to the target API key is not modified. Verify their profile manually if needed. |
| SMTP password | The SMTP server password is not migrated. Re-enter it in the target environment's SMTP settings. |
| LDAP password | LDAP connection passwords are not migrated. Re-enter them after migration. |
| Storage service credentials | Some storage services require re-authentication after migration. |
These items are listed as warnings in the migration log so you have a complete record of what needs your attention.