Versions Compared

Key

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

...

The menu opens the list of the Verint Migration Source Databases. In most of the cases, there will be one Source Database, but the system allows migrating from multiple databases.

...

Click on the Add New Verint Migration Source Database link at the top right folder to add a new source database. First of all, the Verint version has to be specified: "Verint v11.1 and v11.2 and v15.1 Legacy" or "Verint v15.2 and Above".

When the Linked Server is empty, then the Verint databases (EWareCalls, Archive, BPMAINDB, EWareConfig BPMAINDB, and in case of v11 and v15.1 systems the EWareCalls and EWareConfig, in case of v15.2 CentralContact and CommonDB) have to be on the same server where the Verba database is. This can speed up the migration dramatically.

...

The setup, the log entries, the calculated numbers, and basically everything is stored in database tables and will not be deleted after completing the migration.

...

The source data is divided into Subsets. A Subset can be either Back Office or Front Office, and only one Subset may run at a time. The v15.2 User migration also creates a new Subset in order to simply track the process and the log.

The “Total” and “Source” numbers will be calculated either when the subset runs for the first time, or when you click on the Update Numbers button.

...

If a process is still running, then starting another one will throw an error: “Error during pr_verintmig_bo: Cannot acquire lock (Lock State: -1), probably another migration is still running (16, 1)”


Users, Extensions, and Groups from v15.2


When migrating from Verint v15.2, the Users, Extensions, and Groups can be pulled from the Verint database. The process can be initiated by clicking on the Synchronize Users button on the Source Database details screen. The details (should Groups and Extension be pulled or not) can be configured on a new Subset configuration screen:

Image Added

After the Subset saved, use the Save and Run button to start the migration.

Users

The created Users will inherit the Language and Timezone settings from the User who is running the migration, and the Standard User Role will be granted to them.

The Verint identifier will be stored in the Verba database, so during call migration, the process will try to assign the calls to a User based on this information. If no migrated User found for a call, then the Extension and User setup will be used for user association.

Extensions

The Verint Users' Extensions can be migrated too, will be set up as Number/Address type with Voice recording enabled.

Groups

The Verba groups are not sorted in a hierarchy tree, so the Group Name will contain the full path to the groups:

Image Added

The User-Group membership information is also migrated, but the call visibility scope is not. No migrated user will be a Supervisor in Verba.

Post-migration tasks

After the migration completed, the following items must be completed and checked:

...