- The Verba system is deployed, configured, and tested.
- The Verba database is properly sized to accommodate the imported calls. Sizing estimate: ~5 KByte / imported call
- Sufficient time is planned for the migration. We recommend running the migration tool out of business hours to minimize the impact on the Verba database.
Front-office migration time estimate: ~5 million calls / hour
Back-office migration time estimate: ~3.5 million calls / hour
- All calls in Verint are archived, calls cannot be in the call buffer on the Verint recorders.
- The user configuration is complete in the Verba system for historical calls.
- The metadata mapping is checked and confirmed for both front-office and back-office calls.
The SQL Servers are linked:The Verint database has to be configured as a linked server on the Verba database server so the system can run queries on both systems during the migration. Server Options / RPC Out needs to be set to True in the Linked Server configuration. Once the migration is finished, the linked server configuration can be removed.
Alternatively, the Verint databases (Archive, BPMAINDB, CentralContact, and CommonDB) can be backed up and restored on the Verba database server.
For more information on configuring a linked server, see https://docs.microsoft.com/en-us/sql/relational-databases/linked-servers/create-linked-servers-sql-server-database-engine
- The recording functionality is turned off on the Verint recorders. This step is to ensure that no new calls are created on the Verint platform, so the system can migrate all historical calls. The migration supports partial migrations by defining date ranges. However, it has to be very carefully designed and tested to ensure all calls are migrated.
- All 3rd party database maintenance tools are disabled on both the Verint and the Verba database servers.
- The Verba Maintenance Job is disabled. For more information on disabling SQL Server jobs, see https://docs.microsoft.com/en-us/sql/ssms/agent/disable-or-enable-a-job.
- Verba database backup is created to be able to restore the system in the event of a fatal system error during the migration
- The necessary SQL scripts are executed on the Verba and the Verint databases (see below).
When the Linked Server is empty, then the Verint databases (Archive, BPMAINDB, CentralContact, and CommonDB) have to be on the same server where the Verba database is. This can speed up the migration dramatically.