Overview

The purpose of the migration is to import the historical recordings from the Verint v11, v15.1 Legacy, and v15.2 solutions to the Verba system.

The migration offers the following features:

Supported platforms:
- IMR Financial Trading Recorder (IPC Media Recorder)
- BT Financial Trading Recorder
- Verint Financial Trading Recorder
Migration of historical recordings from Verint v11.1 and v11.2 and v15.1 Legacy and v15.2 systems
Support for archived calls only
Supported archive mediums: SMB folder, EMC Centera, Hitachi Content Platform (tapes, DVDs, or any other removable media is not supported)
Storage targets are automatically created based on the archive configuration in Verint
All Verint file formats and codecs are supported: wave file using G.729, G.723.1, or G.726
Encrypted calls are not supported
Both back office and front office (trader voice) calls can be imported
Users, Groups, and Extension can be migrated only from v15.2 systems. The Users' conversation access scope is not migrated.
Migrated calls are assigned to users defined in Verba based on their associated recorded extensions (Trader ID / Extension or Phone Number / SIP URI)

Migration process

The migration consists of multiple steps, outlined below:

Phase: Install Verba side by side to the Verint system
In this phase, a complete Verba system is deployed to allow recording of the communication platforms (both trader voice and telephony or unified communication). The Verba system is deployed on new servers, side-by-side to the existing Verint installation. Certain parts of the existing infrastructure can be reused potentially. This includes the SQL Server, where the Verba database is hosted and the storage infrastructure where the recordings will be stored. The Verint and Verba software applications cannot be installed on the same operating system.
Phase: Fully configure the Verba system for recording
In this phase, the Verba system is fully configured for recording and archiving. All users are configured, including any historical user and recorded extension (trader ID, phone number, SIP URI) configuration which is necessary to assign the imported calls to users. Access control settings have to be recreated or Active Directory synchronization should be enabled. If the Verint system version is 15.2 then User, Groups, and Extensions can be pulled from the Verint database at this phase, before the actual call migration started. The system has to be fully tested after completing this stage.
Phase: Switch over to Verba for recording
Once everything is configured and tested, the recording is cut over to the new Verba platform. The recording on the Verint system is turned off. This step has to be carefully designed with the appropriate fallback plans in place. This might be done in multiple phases and gradually moving users over to the new Verba platform if the integration allows using multiple recording systems at once.
Phase: Migrate calls to Verba from Verint
After the Verint system stops recording calls, the historical calls can be imported to the Verba system.

Archive considerations

During migration, the system imports call data into the Verba database. However, media files stay on their existing location in the Verint archives. The system imports the references to the files (*.tar) and the Verba system has new features that allow accessing these files without the need to move, copy, untar or transcode them. Because of the different archiving and storage concepts in the two systems, certain features are not available for the imported calls. The following table provides an overview of the differences.

	Verba recordings	Recordings imported from Verint, stored in Verint Archive	Notes
Archive Format	Individual file for each call	TAR files grouping several calls together	The TAR file concept introduces multiple limitations because the files cannot be managed individually in the TAR. This is the reason for not supporting all storage/archive features for imported calls.
Multiple Archives	No	Yes	The Verint system allows archiving the same call multiple times, while the Verba system only supports a single copy in the archive. During migration, all archive entries are imported, but the oldest archive is selected as the primary archive which is then linked with the CDR entry in the database, which is used for playback, download, and export (to be compatible with Verba). Subsequent archive copies are not accessible through the Verba system, but the system manages the retention period settings and attempts to delete the copies after the retention period expires. If for some reason, the primary copy is selected for deletion, the system chooses the next available archive copy as the primary automatically.
Playback	Yes	Yes
Playback multiple files at once	Yes	Yes
Playback marked segment	Yes	Yes
Download	Yes	Yes
Download multiple files at once	Yes	Yes
Export	Yes	Yes
Copy Media	Yes	No	The system filters out imported calls for the policy automatically
Move Media	Yes	No	The system filters out imported calls for the policy automatically
Upload	Yes	No	The system filters out imported calls for the policy automatically
Archive in DB and Move Media	Yes	No	The system filters out imported calls for the policy automatically
Archive in DB	Yes	Yes
Delete, Policy-based	Yes	Yes	The system will delete the CDRs, but only delete the TAR files once all calls are deleted
Delete, Manual	Yes	Yes	The system will delete the CDRs, but only delete the TAR files once all calls are deleted
Legal Hold	Yes	Yes	For imported calls, the system is not able to set the legal hold flag on EMC Centera, only in the Verba system. Only the primary archive location is marked with the legal hold flag.
File Verification	Yes	No	The system filters out imported calls for the policy automatically
Increase Retention Period	Yes	No	Custom SQL script can be used to update the retention in the Verba database
Deduplicate Recordings	Yes	No	The system filters out imported calls for the policy automatically
Encrypt and Sign	Yes	No	The system filters out imported calls for the policy automatically
Voice Quality Check	Yes	Yes
Transcode	Yes	No	The system filters out imported calls for the policy automatically
Transcription	Yes	No	The system filters out imported calls for the policy automatically
Phonetic Indexing	Yes	No	The system filters out imported calls for the policy automatically

Configuring the migrating from Verint systems

The configuration of the migration is slightly different for v11/v15.1 Legacy and v15.2 systems. Follow the instructions of the related guides specific to your environment:

Browser not supported