Enterprise Intelligence Solutions

Custom Data Migration Mapper

Guide
Version 11.2

Document Revision 1.01

Confidential and Proprietary Information of Verint Systems Inc.

© 1992–2015 Verint Systems Inc. All Rights Reserved Worldwide.
Confidential and Proprietary Information of Verint Systems Inc.

All materials (regardless of form and including, without limitation, software applications,
documentation, and any other information relating to Verint Systems, its products or services) are
the exclusive property of Verint Systems Inc. Only expressly authorized individuals under
obligations of confidentiality are permitted to review materials in this document. By reviewing
these materials, you agree to not disclose these materials to any third party unless expressly
authorized by Verint Systems, and to protect the materials as confidential and trade secret
information. Any unauthorized review, retransmission, dissemination or other use of these
materials is strictly prohibited. If you are not authorized to review these materials, please return
these materials (and any copies) from where they were obtained. All materials found herein are
provided “AS IS” and without warranty of any kind.
Verint Systems Inc. does not warrant, guarantee or make any representation regarding the use or
the results of the use of the information, links, tools, and materials in terms of the accuracy,
reliability, quality, validity, stability, completeness, currentness, or otherwise of its content or
products. The entire risk as to the use, results and performance of information, links, tools and
materials provided or referenced herein is assumed by the user. Verint Systems Inc. shall not be
liable for damages resulting from the use, misuse or unlawful use of the information, links, tools,
and materials contained or referenced herein.
Any third party technology that may be appropriate or necessary for use with the Verint Product is
licensed to you only for use with the Verint Product under the terms of the third party license
agreement specified in the Documentation, the Software or as provided online at
http://verint.com/thirdpartylicense. You may not take any action that would separate the third
party technology from the Verint Product. Unless otherwise permitted under the terms of the third
party license agreement, you agree to only use the third party technology in conjunction with the
Verint Product.
The Verint Systems Inc. products are protected by one or more U.S., European or International
Patents and other U.S. and International Patents and Patents Pending.

All marks referenced herein with the ® or ™ symbol are registered trademarks or trademarks of
Verint Systems Inc. or its subsidiaries. All rights reserved. All other marks are trademarks of their
respective owners.

Visit our website at www.verint.com/intellectualpropertynotice for updated information on Verint

Intellectual Property.

Document Revision 1.01

Published September 18, 2015
 Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Custom Data Migration Mapper Overview. . . . . . . . . . . . . . . . . . . . . . . . . . 10

System Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Custom Data Migration Mapper Role in the Migration Process . . . . . . . . . . . . . . . . . . 12
Output Files Created by the Custom Data Migration Mapper . . . . . . . . . . . . . . . . . 12
What You Need to Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Supported Databases and Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . 16
Understanding the Mapping Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Planning for Multi-Site Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Target System Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Source System Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Quality Monitoring System Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Full-time Recording System Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Defining Source Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Mapping Source Attributes to Target Attributes . . . . . . . . . . . . . . . . . . . . . . . 21
Exceptions to Default Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Quality Monitoring Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Full-time Recording Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Target System Rediscovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Edited Captions for Custom Data Fields and Evaluation Custom Data Fields . . . . . . . . . 24
Finalizing the Mapping Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
About Custom Data Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Migration Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Overbooked User Data Fields in Full-time Recording Systems. . . . . . . . . . . . . . . . . 29
Project Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Field Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Field Captions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Locked (In Use) Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Stale Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Full-time Recording Systems and eWare Views . . . . . . . . . . . . . . . . . . . . . . . . . 36
Rules for Migration Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Recommended eWare Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
 Contents

2 Custom Data Migration Mapper Workflows . . . . . . . . . . . . . . . . . . . . . . . . . 37

Primary Migration Process Workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Advanced eWare Migration Process Workflows . . . . . . . . . . . . . . . . . . . . . . . . . 43
TDM Recorder Converted to IP with Same Serial Number . . . . . . . . . . . . . . . . . . 44
TDM Recorder Switched to IP Recorder with New Serial Number . . . . . . . . . . . . . . . 45
Mixed Environment Using TDM Recorder and IP Recorder . . . . . . . . . . . . . . . . . . 46

3 Installing the Custom Data Migration Mapper . . . . . . . . . . . . . . . . . . . . . . . 47

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Install the Custom Data Migration Mapper . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Launch the Custom Data Migration Mapper . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Remove the Custom Data Migration Mapper . . . . . . . . . . . . . . . . . . . . . . . . . . 51

4 Configuring the Custom Data Migration Mapper . . . . . . . . . . . . . . . . . . . . . . 52

Update System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5 Managing Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Create a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Project Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Open a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Delete a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Review Project Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
View Project Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Status Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Contact Mapping Summary Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
User Mapping Summary Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Evaluation Mapping Summary Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Unmapped Attributes Summary Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Copy a Project to Another Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

6 Working with a Full-time Recording System . . . . . . . . . . . . . . . . . . . . . . . . 64

Create a Migration View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Discover a Full-time Recording System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Full-time Recording Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Attribute Definitions for the Full-time Recording System . . . . . . . . . . . . . . . . . . . . 72
About Rediscovery of the Full-time Recording Fields . . . . . . . . . . . . . . . . . . . . . 72
Define Full-time Recording Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Full-time Recording Attribute Definition Settings . . . . . . . . . . . . . . . . . . . . . 73
Show Full-time Recording Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Initiate Full-time Recording Field Discovery . . . . . . . . . . . . . . . . . . . . . . . . . 75
Select the Full-time Recording Source Field Attribute Types . . . . . . . . . . . . . . . . . 75
Initiate Rediscovery of the Full-time Recording Fields. . . . . . . . . . . . . . . . . . . . . . 77
Remove a Full-time Recording Attribute Definition . . . . . . . . . . . . . . . . . . . . . . . 78
Full-time Recording Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Default Full-time Recording Mapping Logic . . . . . . . . . . . . . . . . . . . . . . . . . 79
Full-time Recording Default Custom Data Captions . . . . . . . . . . . . . . . . . . . . 81
Potential Truncation of Source Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Map Full-time Recording Fields to the Target System . . . . . . . . . . . . . . . . . . . . 81

Custom Data Migration Mapper Guide 4

Confidential and Proprietary Information of Verint Systems, Inc.

 Contents

Unlock Full-time Recording Contact Attributes In Use . . . . . . . . . . . . . . . . . . . . 82

Preview Full-time Recording Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Remove a Full-time Recording Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Default IP Mapping When Default Tagging Is Used . . . . . . . . . . . . . . . . . . . . . . 84
Sample Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Modifications to Sample Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

7 Working with a Quality Monitoring System . . . . . . . . . . . . . . . . . . . . . . . . . 86

Discover a Quality Monitoring System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Source System Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Attribute Definitions for the Quality Monitoring System . . . . . . . . . . . . . . . . . . . . . 89
Rediscovery of the Quality Monitoring Fields . . . . . . . . . . . . . . . . . . . . . . . . 89
Define Quality Monitoring Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Quality Monitoring Attribute Definition Settings . . . . . . . . . . . . . . . . . . . . . . 90
Show Quality Monitoring Contacts, Users or Evaluations . . . . . . . . . . . . . . . . . . . 92
Initiate Quality Monitoring Field Discovery . . . . . . . . . . . . . . . . . . . . . . . . . 93
Initiate Rediscovery of the Quality Monitoring Fields . . . . . . . . . . . . . . . . . . . . . . 94
Remove a Quality Monitoring Attribute Definition. . . . . . . . . . . . . . . . . . . . . . . . 95
Quality Monitoring Contact Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Default Contact Attribute Mapping Logic . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Map Quality Monitoring Contacts to the Target System. . . . . . . . . . . . . . . . . . . . 97
Unlock Quality Monitoring Contact Attributes In Use . . . . . . . . . . . . . . . . . . . . . 98
Preview Quality Monitoring Contact Mapping . . . . . . . . . . . . . . . . . . . . . . . . 98
Remove a Quality Monitoring Contact Mapping . . . . . . . . . . . . . . . . . . . . . . . 99
Quality Monitoring User-Defined Field Mapping . . . . . . . . . . . . . . . . . . . . . . . . 100
Map Quality Monitoring User-Defined Fields to the Target System. . . . . . . . . . . . . . . 100
Unlock User-Defined Fields in Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Preview Quality Monitoring User-Defined Field Mapping . . . . . . . . . . . . . . . . . . . 101
Remove a Quality Monitoring User-Defined Field Mapping . . . . . . . . . . . . . . . . . . 102
Quality Monitoring Evaluation Attribute Mapping . . . . . . . . . . . . . . . . . . . . . . . . 103
Default Evaluation Attribute Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Default Captions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Map Quality Monitoring Evaluation Attributes to the Target System . . . . . . . . . . . . . .104
Unlock Evaluation Custom Data Fields In Use . . . . . . . . . . . . . . . . . . . . . . . . 105
Preview Quality Monitoring Evaluation Attribute Mapping. . . . . . . . . . . . . . . . . . . 106
Remove a Quality Monitoring Evaluation Attribute Mapping. . . . . . . . . . . . . . . . . . 106

8 Discovering a Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Configure Target System Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . 109
Target System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Field Discovery for the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
About Rediscovery of the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Discovery Rules for Existing Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Discovery Rules for Custom Data Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Discovery Rules for Evaluation Custom Data and User-Defined Fields . . . . . . . . . . . . .116
Initiate Rediscovery of the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Remove a Discovered Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Custom Data Migration Mapper Guide 5

Confidential and Proprietary Information of Verint Systems, Inc.

 Contents

Configure SSL Communication with the Target System . . . . . . . . . . . . . . . . . . . . . 120

Export the Root CA certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Install the Certificate for Custom Data Migration Mapper . . . . . . . . . . . . . . . . . . . 121

9 Completing the Mapping Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Review Mapping Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Prerequisites to Completing the Mapping Process . . . . . . . . . . . . . . . . . . . . . . . 124
Generate Migration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Unmapped Attributes Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

A Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Print from Your Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Custom Data Migration Mapper Guide 6

Confidential and Proprietary Information of Verint Systems, Inc.

 Preface

About This Guide

This guide provides you with step-by-step instructions for using the Custom Data
Migration Mapper Tool. The Custom Data Migration Mapper facilitates migration of
custom data from prior versions of Quality Monitoring, Full-time Recording, and Quality
Monitoring with Full-time Recording to your 11.x system.
For Quality Monitoring systems, custom data refers to contact custom attributes and
also includes user-defined fields (UDF) and evaluation custom data (ECD). For Full-time
Recording systems, custom data refers to standard data field and user data fields.

Intended Audience for This Guide

This guide is designed for users responsible for migrating custom data into a 11.x
system, including:
 Project managers
 Application consultants
 Field engineers
 Partners

Related Documents
This guide is one of a set of documents designed to help you deploy and use the
Enterprise suite of products. The following table lists the related documents in the set
and shows the relationship of those guides to this guide.
Preface About This Guide

Document Category Document Title

Deployment Reference Upgrade and Migration Package Workflow Guide

Deployment Reference Guide

Enterprise Suite Technical Overview

Enterprise Security Guide

Site Preparation Checklist

Installation & Configuration Report

SR Validator Tool Guide

Site Acceptance Test

Installation Custom Data Migration Mapper Guide

User Migration Tool Guide

Recorder Upgrade and Migration Guide

Installation Guide

Workforce Optimization Installation Guide

Configuration Enterprise Manager Configuration and

Administration Guide

Administration System Administration Guide

Recorder Administration Guide

Security Configuration Guide

Custom Data Migration Mapper Guide 8

Confidential and Proprietary Information of Verint Systems, Inc.

Preface About This Guide

Documentation Feedback
We strive to produce the highest quality documentation products and welcome your
feedback. If you have comments or suggestions about our guides or online help, you can
email us. Please include the following information with your feedback:
 Product name and version number
 Name of online help or guide
 Topic name and page number (if applicable)
 Brief description of content
 Your suggestion for correcting or improving the documentation
Please send your messages to [email protected].
The email address is only for documentation feedback. If you have a technical question,
please contact Technical Support.

Technical Support
Our goal is to provide you with the best products backed by a high-quality support
network with a variety of resource options. Verint Systems Technical Support services
include email and telephone support.
To learn more about the support options that best suit your needs, visit us at
verint.com/EISsupport.

Verint University
In addition to documentation, online Help, and support services, Verint Systems also
offers both classroom-based and online learning alternatives to suit your specific needs.
To learn more about available training options from Verint Systems, visit us at
verint.com/training.

Custom Data Migration Mapper Guide 9

Confidential and Proprietary Information of Verint Systems, Inc.

 Chapter 1

Custom Data Migration

Mapper Overview

The Custom Data Migration Mapper tool maps earlier versions of Quality Monitoring and
Full-Time Recording custom data to the target system. You must use this tool when
planning your data migration.
See:
 System Terminology on page 11
 Custom Data Migration Mapper Role in the Migration Process on page 12
 What You Need to Know on page 15
 Supported Databases and Backward Compatibility on page 16
 Understanding the Mapping Process on page 17
 About Custom Data Fields on page 26
 Project Icons on page 31
 Field Status on page 32
 Field Captions on page 33
 Locked (In Use) Fields on page 34
 Full-time Recording Systems and eWare Views on page 36
Chapter 1 - Custom Data Migration Mapper Overview System Terminology

System Terminology
Migration of custom data refers to mapping the following source entities to your target
system:
 Quality Monitoring contact custom attributes, user-defined fields, and evaluation
custom data
 Full-time Recording standard contact fields and user data fields

This guide deals with custom data across multiple systems, each of which has its own
field designations. Use the table in this topic to help you to clarify the usage and context
for system-specific terms.
NOTE For clarity, when referring to contact custom attributes, user-defined
fields, evaluation custom data, or standard contact fields and user data
fields, this document refers collectively to these entities henceforth as
“custom data,” unless otherwise noted. See “System Terminology” on
page 11 for term correspondence.

Systems Source Fields Target Fields

Quality Monitoring  Contact Custom Attribute  Custom Data (CD)

 User-Defined Field (UDF)  User-Defined Field (UDF)

 Evaluation Custom Attribute  Evaluation Custom Data

(ECD)

Full-time Recording  Standard Field  Custom Data (CD)

 User Data Field  Session Attribute

Custom Data Migration Mapper Guide 11

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Custom Data Migration Mapper Role in the Migration Process

Custom Data Migration Mapper Role in the

Migration Process
Plan to begin using the Custom Data Migration Mapper several weeks prior to the
upgrade and migration of the system to the target system. The tool enables you to map
source data elements to the target metadata. You need to plan to use the tool prior to
the upgrade in order to identify any data mapping issues or conflicts that may arise, and
to provide sufficient time to reconcile those issues or conflicts. Refer to “Related
Documents” on page 7 to see how the this guide fits with your other product
documentation.
After you have completed the mapping of custom data, you will have a compressed
archive file (.zip) containing several XML files. The XML files detail the mapping of the
source attributes to the target system. The archive file is used by the upgrade process
to actually perform the data migration.

NOTE The Custom Data Migration Mapper can be installed on any machine
meeting the system requirements, as detailed in Custom Data Migration
Mapper Release Notes. The tool can connect remotely to the required
database servers and need not be installed on an server.

Output Files Created by the Custom Data Migration

Mapper
The Custom Data Migration Mapper generates XML files used subsequently by the
migration process. All output files are delivered to you in a single, compressed archive
(.zip). A single archive corresponds to a single project. See Chapter 5 “Managing
Projects” to learn more about projects.
The archive contains the following files:

Custom Data Migration Mapper Guide 12

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Output Files Created by the Custom Data Migration Mapper

Path in File Description

Archive

. n/a Parent folder.

V11CDConfiguration.xml Contains the custom data status and

captions for the entire project.

V11CDConfiguration.xsd XML schema for the

V11CDConfiguration.xml file.

V11EMAttributes.xml Contains the target Enterprise

Manager attributes for the entire
project. These attributes will be
created or receive updated custom
data mapping.

V11EMAttributes.xsd XML schema for the

V11EMAttributes.xml file.

V11ECDUDFConfiguration.xml Contains statuses and captions for

the entire project with respect to the
evaluation custom data and the user
data fields. These items will be set in
the target system.

V11ECDUDFConfiguration.xsd XML schema for the

V11ECDUDFConfiguration.xml file

./CS n/a Full-time Recording-specific folder.

AllCSMigration.xml Contains the contact migration

system metadata for all the Full-time
Recording systems in the migration
project. This file enables full
enterprise migration.

<system name>-CSMigration.xml Where <system name> corresponds

to the database server name defined
in the Custom Data Migration
Mapper. You will find a separate file
for each Full-time Recording system,
thus enabling execution of site-by-
site migration.

Custom Data Migration Mapper Guide 13

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Output Files Created by the Custom Data Migration Mapper

Path in File Description(Continued)

Archive

./QM Quality Monitoring-specific folder.

<system name>- Where <system name> corresponds

BalanceMigrationMapping.xml to the system name defined in the
Custom Data Migration Mapper. You
will find a separate file for each
Quality Monitoring system, thus
enabling execution of site-by-site
migration.
This file will contain the mapping for
contacts, user-defined fields, and
evaluations.

Custom Data Migration Mapper Guide 14

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview What You Need to Know

What You Need to Know

Although the Custom Data Migration Mapper enables you to map source attributes to
the target system, the tool is not intended to be a solution that eliminates user
interaction with the data. It is imperative that the individuals involved in the data
mapping process are intimately familiar with the source data.
Issues, conflicts, and other mapping decisions that must be made require both historical
knowledge of how the source data has been used as well as how it will be used in the
target system.
Without detailed knowledge of the source data, and planned data usage in the target
system, effective use of the Custom Data Migration Mapper cannot be achieved and may
result in an unsatisfactory migration scenario.

Custom Data Migration Mapper Guide 15

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Supported Databases and Backward Compatibility

Supported Databases and Backward

Compatibility
The Custom Data Migration Mapper supports major versions of the databases for source
systems, as detailed below.
Quality Monitoring
 QM 6.5.x (SQL Server 2000)
 QM 7.6.x (SQL Server 2000)
 QM 7.7.x (SQL Server 2000)
 QM 7.8.1 (SQL Server 2005)
 QM 7.8.2 (SQL Server 2005)
 QM 7.8.3 (SQL Server 2005, SQL Server 2008)
 Avaya QM 10.1.0 (SQL Server 2005)
 Avaya QM 10.1.1 (SQL Server 2005)
 Avaya QM 10.1.2 and 11.0.0 (SQL Server 2005, SQL Server 2008)

Full-time Recording (eWare)

 FTR 7.7 (SQL 2000)
 FTR 7.8 (SQL 2000, 2005)

Custom Data Migration Mapper Guide 16

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Understanding the Mapping Process

Understanding the Mapping Process

As previously discussed, the mapping process is an iterative, multi-stage sequence of
events that should begin several weeks prior to the upgrade. This section provides you
with a high-level overview of the mapping process to help you to understand what
happens at each stage.
The mapping process follows the following steps.

Refer to the topics indicated for additional details.

1 Planning on page 18
2 Target System Discovery on page 19
3 Source System Discovery on page 19
4 Defining Source Attributes on page 20
5 Mapping Source Attributes to Target Attributes on page 21
6 Target System Rediscovery on page 24
7 Finalizing the Mapping Process on page 25

Custom Data Migration Mapper Guide 17

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Planning

Planning
The planning phase should begin prior to any attempt to begin using the Custom Data
Migration Mapper. Planning should take into account:
 The date that the use of the Custom Data Migration Mapper begins.
 The customer’s source data, with the determination if additional mapping effort
from professional services will be required; scenarios requiring additional effort are
detailed in this guide.
 A sufficient time interval to complete the mapping process, which includes resolving
any data conflicts or data issues that may arise.
 Coordination of the mapping process with the target date for the upgrade, including
all personnel involved with the upgrade.
 Allocation of customer resources for the migration.
 Allocation of Verint or partner resources for the migration, including the Project
Manager, as well as any designated representatives for the Project Manager.
 Installation of the Custom Data Migration Mapper.

Planning for Multi-Site Systems

If you have multiple Quality Monitoring or Full-time Recording systems, you should plan
to use one of the following methods with the Custom Data Migration Mapper:

IMPORTANT We strongly recommend that you select enterprise mapping for systems
with multiple sites. Use of the enterprise mapping method enables you to
see the effects of your mapping decisions across the enterprise.

 Enterprise mapping: in this approach, you can create a single project which
contains all sites. Refer to “Managing Projects” on page 54 to learn more about
projects. The advantage to this approach is that you will be able to see all your
mapping decisions in a single project.

Although you can plan on an enterprise level, the execution of the actual migration
will differ by the type of system being migrated. For Quality Monitoring sites, you
must migrate on a site-by-site basis. For Full-time Recording sites, you can migrate
site-by-site or all sites at once.
 Phased mapping: in this approach, you will plan and execute the migration on a
site-by-site basis. The actual migration period may span some time frame
determined during the planning phase. For example, you will perform the planning
and mapping for the first site and execute its migration; then, after some period,
you can perform the planning and mapping for the second site and execute its
migration, and so on. The advantage to this approach is that you have a broader
time frame in which to plan, map and migrate each site.
You should plan to map the Full-time Recording system prior to mapping the Quality
Monitoring system.

Custom Data Migration Mapper Guide 18

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Target System Discovery

NOTE For multiple site systems, you should plan on “freezing” the custom data in
the source systems. “Freezing” refers to not making any changes in the
custom data. The freeze should be enforced until the entire migration is
completed. Failure to freeze the source data will require running the tool
again against the system to acquire the changes to the custom data.

Target System Discovery

NOTE At this point in the process, the target system may or may not be
installed. If present, the target system should be discovered. However,
you can proceed if the system has not yet been installed. The target
system will again be discovered during “Target System Rediscovery” on
page 24.

Target system discovery refers to connecting to the target system to determine what
custom data fields are currently in use. A live connection to the target system is
required to perform target system discovery.
You should run discovery on the target system to enable the tool to determine which
custom data fields are currently available. The result of system discovery provides you
with details of how the attributes are used in the target system.
Discovery of the target system is always required. What varies is when you discover the
target system. You can discover the target system now, or just prior to finalizing the
mapping project.
The following scenarios also make discovery of the target system required:
 You have installed a new target system and added a new site to it prior to migrating
from the source system.
 You are utilizing the phased approach, discussed in “Planning for Multi-Site
Systems” on page 18. In addition, if you have a Quality Monitoring with Full-time
Recording system, you must run the target system discovery after migrating Full-
time Recording but before migrating Quality Monitoring; in this way, you will be able
to determine which custom data fields are available to Quality Monitoring after the
Full-time Recording migration.

Source System Discovery

After you have your migration planned and the Custom Data Migration Mapper installed,
you are ready to begin system discovery.
Discovery refers to connecting to the source system(s) to determine what custom data
fields are currently in use. System discovery applies to both the source system and the
target system. A live connection to the source system or the target system is required to
perform system discovery.

Custom Data Migration Mapper Guide 19

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Quality Monitoring System Discovery

System discovery on the source system is required and enables the tool to extract the
custom metadata. The result of discovery on the source system is an XML file that
describes the source data.

Quality Monitoring System Discovery

The Custom Data Migration Mapper supports multiple Quality Monitoring sites. You
should plan to run the system discovery for each site, since each site can have different
field mappings. The upgrade will support consolidation of the site data into the target
system.
Each project will have its own set of output files from the Custom Data Migration
Mapper. A single project may contain multiple Quality Monitoring sites -- in which case,
each site will have a separate migration mapping file within the exported archive. See
“Output Files Created by the Custom Data Migration Mapper” on page 12 to learn more.

Full-time Recording System Discovery

The Custom Data Migration Mapper supports multiple eWare systems. Since each eWare
database may utilize several database views to access custom data, you will be able to
select the view you need when mapping to the target system.

Defining Source Attributes

After discovering the target system (optional) and source systems, the next step in the
process is definition of source attributes. Source attribute definition must occur when
connected to the relevant source system.
Definition of source attributes is necessary to determine the meaning and function of the
custom data in the source system. The meaning of the data refers to identifying each
custom data field as to its function, such as ANI, DNIS, etc. It is at this stage that the
tool will determine the data types, actual data lengths, and frequency of usage from the
source system.
Also note that:
 For Quality Monitoring systems, you can specify the date range of data eligible for
migration.
 For Full-time Recording systems, you can select the view. Each selection (view)
contributes to determining the data eligible for migration.

IMPORTANT It is critical that this phase of the process be performed by an individual

who is knowledgeable about the source custom data.

Custom Data Migration Mapper Guide 20

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Mapping Source Attributes to Target Attributes

Mapping Source Attributes to Target Attributes

After you have successfully created the source attribute definitions, you may proceed to
the mapping phase. Most of the mapping phase may be completed offline (when not
connected to the source system and target system).
Mapping refers to associating the source data with specific target system attributes. In
many instances, the default mapping provided by the tool should suffice and no added
effort is required during this phase. The tool does provide validation to determine if
problems may result from the mapping.
For default mapping, the system attempts to locate the first available custom data field
whose length accommodates the source attribute data length. If no target custom data
field can accommodate the source attribute, no default mapping will occur.
It is as this stage that the mapping preview feature should be used to test the current
mapping against sample data, if provided by the customer. However, for the mapping
preview you must be connected to the source system when performing a preview for the
first time. The initial preview is the only step of the mapping process that requires a live
connection to the source system.

IMPORTANT It is critical that this phase of the process be performed by an individual

who is knowledgeable about the source custom data.

Exceptions to Default Mapping

Some scenarios exist were the default mapping provided does not work and which may
require additional involvement from professional services or application consultants:
 Since the target system provides 25 fields for containing migrated custom data, if
more than 25 fields are required in the target system then the default mapping will
not suffice.
 If the length of source data exceeds the number of characters provided for migrated
custom data, the default mapping will not suffice.
 If the source system utilizes “overbooking,” and the system does not already have
views defined to extract the overbooked fields, then the default mapping will not
suffice. “Overbooking” refers to storing multiple data items in a single custom data
field (usually comma-delimited).

If multiple views are utilized to access different data from the same custom data
field, the views will extract the data correctly for mapping.

Quality Monitoring Mapping

Mapping for Quality Monitoring systems includes contact custom attributes, user-defined
data, and evaluation custom data.

Custom Data Migration Mapper Guide 21

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Full-time Recording Mapping

NOTE No default mapping is provided for user-defined data fields.

Full-time Recording Mapping

Since source attribute definition is by view, you should plan to separately map each view
you intend to use with the Custom Data Migration Mapper.

eWare Migration Standard Mapping

Refer to the following table to familiarize yourself with the standard mapping required by
the Custom Data Migration Mapper when migrating eWare data. The migration mapping
defined below cannot be altered. Refer to Notes for any explanation or deviation from
expected behavior.

Source eWare Field Target System Notes

INum (15)  Module (6) The 15-digit INum from the eWare database is
 Channel (9) split into two fields, six digits and 9 digits
respectively, in the target system.

StartedAt Local Start Time

StartedAtUTC Start Time

Duration Duration

Duration+StartedAtUT EndTime
C

Duration+StartedAt Local end time

n/a Wrapup time

n/a Type

ContactID This is a computed value.

n/a Personal tag Default value is zero.

n/a Num of ccq equals Default value is zero.

n/a Il_id Same as ContactID

n/a Num of agent cross Default value is zero.

n/a Num of other cross Default value is zero.

n/a Percent of agent call Default value is zero.

n/a Percent of other call Default value is zero.

Custom Data Migration Mapper Guide 22

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Full-time Recording Mapping

Source eWare Target System Notes

n/a Percent of mutual Default value is zero.

silence

n/a Msg time stamp Default value is null.

MONTH(StartedAtUTC) Month of year

ItemModifiedDateTime Dbs end time

ItemModifiedDateTime Last update

n/a DWH Lut This is a computed value.

Digits ANI

eWare Migration Required Mapping

The following values from the eWare database must be mapped to custom data fields in
the target system if you want them to be migrated. If you fail to map these fields, the
values will be lost during migration.

Source eWare Field Target System Notes

Direction Custom Data Field If you want this value in the target system, it
must be mapped to a custom data field.
IMPORTANT: The eWare Direction field will
not be migrated into the target Direction field.

Channel Custom Data Field If you want this value in the target system, it
must be mapped to a custom data field.
IMPORTANT: The eWare Channel field will not
be migrated into the target system Channel
field.

eWare Fields You Should Not Map

The following eWare fields commonly appear in eWare views. These are internal fields
that have no meaning in the target system. These fields can be ignored during the
mapping process. You should not map these fields as doing so will use custom data
fields unnecessarily.
 FormatId
 EndDate
 NextINum
 PrevINum
 NoCallEnd
 NoCallStart
 Barreplay

Custom Data Migration Mapper Guide 23

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Target System Rediscovery

 Extradata
 Warntoneapplied
 Callparty
 Originalinum
 Length
 UID
 Startdate
 Starttime
 ItemModifiedDate
 ItemModifiedDateTime
 SourceType

Target System Rediscovery

Target system rediscovery refers to connecting to the target system to determine what
custom data fields are currently in use. A live connection to the target system is
required to perform target system discovery.
You must run rediscovery on the target system to enable the tool to determine which
custom data fields are currently available. The result of system rediscovery provides you
with details of how the attributes are used in the target system.
Discovery of the target system is always required. What varies is when you discover the
target system. You can discover the target system early in the mapping process, or just
prior to finalizing the mapping project.
The following scenarios also make discovery of the target system required:
 You have installed a new target system and added a new site to it prior to migrating
from the source system.
 You are utilizing the phased approach, discussed in “Planning for Multi-Site
Systems” on page 18. In addition, if you have a Quality Monitoring with Full-time
Recording system, you must run target system discovery after migrating Full-time
Recording but before migrating Quality Monitoring; in this way, you will be able to
determine which custom data fields are available to Quality Monitoring after the
Full-time Recording migration.

Edited Captions for Custom Data Fields and Evaluation Custom Data
Fields
In the target system, users have the ability to use the Caption Editor to edit captions for
custom data fields and evaluation custom data fields for applications such as Portal,
Form Designer, and several others. Each customization of the caption is maintained
separately.

Custom Data Migration Mapper Guide 24

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Finalizing the Mapping Process

To see the Caption Editor, select Organization Management > Interactions and
Analytics > Caption Editor from your target system portal.

It is vital that you synchronize your Portal captions with edits made to captions from
other applications, such as Form Designer.

CAUTION During discovery of the target system, the Custom Data Migration Mapper
does not access captions for custom data fields and evaluation custom
data fields modified by the Form Designer application. Discovery only
accesses captions modified by the Portal application.

If captions have been modified using the Form Designer application, you
must manually synchronize the captions using the target system.
Otherwise, the Custom Data Migration Mapper will not retrieve the correct
captions.
Refer to “Field Discovery for the Target System” on page 113 to learn
more about discovery.

Finalizing the Mapping Process

After having successfully completed the mapping phase of the process, you are ready to
finalize your mappings. Finalization refers to exporting the mappings, which are then
used by the upgrade process. Finalization creates a zip archive of files, which you can
learn about in “Output Files Created by the Custom Data Migration Mapper” on page 12.

Custom Data Migration Mapper Guide 25

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview About Custom Data Fields

About Custom Data Fields

Custom data fields function differently in the Quality Monitoring system, the Full-time
Recording system, and in the target system. The purpose of this section is to define the
migration attributes you will commonly be using, as well as to discuss some customers’
non-standard usage of source custom data fields that you may need to consider.

NOTE The target system provides 25 custom data fields. 23 fields have a data
type of string. Two fields have a data type of integer.

Therefore only 23 custom data fields are available for migrated contacts
from Quality Monitoring. The two integer custom data fields cannot accept
the string values from Quality Monitoring.

If more than 25 custom data fields are required, a professional services

engagement is required to support the additional custom data fields for
migration.

Migration Attributes
Use the attributes information in this section when planning the mapping from source
systems to the target system, which provides the following attributes:
NOTE Two fields have a data type integer.
Therefore only 23 custom data fields are available for migrated contacts
from Quality Monitoring. The two integer custom data fields cannot accept
the string values from Quality Monitoring.
If more than 25 custom data fields are required, a professional services
engagement is required to support the additional custom data fields for
migration.

Supported by Custom Data

Migration Mapper?
Source Target Target
Attribute Attribute System Field Target Full-time Quality
Type Name Data Type Recording Monitoring

Agent ID PBX Login ID Session.pbx_login String [15] Yes No

_id

Agent Agent: Agent Custom Data Custom Yes No

Name Name Data

ANI ANI Session.ani String [15] Yes No

Custom Data Migration Mapper Guide 26

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Migration Attributes

Supported by Custom Data

Migration Mapper?
Source Target Target
Attribute Attribute System Field Target Full-time Quality
Type Name Data Type Recording Monitoring

Call CTI: Call Custom Data Custom Yes No

Direction Direction Data

Call n/a n/a n/a No No

Duration

Call ID Switch Call ID Session. String [16] Yes No

switch_call_id

Call CTI: Call ID Custom Data Custom Yes No

Reference Data

Call Type CTI: Call Custom Data Custom Yes No

Direction Data

Called Party CTI: DNIS Custom Data Custom Yes No

Data

Called Party CTI: Called Custom Data Custom Yes No

Name Party Name Data

Calling CTI: ANI Custom Data Custom Yes No

Party Data

Calling CTI: Calling Custom Data Custom Yes No

Party Name Party Name Data

Channel CTI: Channel Custom Data Custom Yes No

Name Name Data

Custom Custom Data Custom Data Custom Yes Yes

Data

Data CTI: Data Custom Data Custom Yes No

Source Source Name Data
Name

Device CTI: Device Custom Data Custom Yes No

Name Name Data

DNIS DNIS Session. dnis_code String [15] Yes No

DTMF Digits CTI: DTMF Custom Data Custom Yes No

Digits Data

Event Type CTI: Event Custom Data Custom Yes No

Type Data

Custom Data Migration Mapper Guide 27

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Migration Attributes

Supported by Custom Data

Migration Mapper?
Source Target Target
Attribute Attribute System Field Target Full-time Quality
Type Name Data Type Recording Monitoring

Extended CTI: Extended Custom Data Custom Yes No

Call History Call History Data

Extension Extension Session. String Yes No

extensions [256]

Fired CTI: Fired Custom Data Custom Yes No

Business Business Data
Rules Rules

First CTI: First Custom Data Custom Yes No

Message Message Data

Global Call CTI: Global Custom Data Custom Yes No

ID Call ID Data

Integration Custom Data Custom Data Custom Yes Yes

Services Data
Custom
Attribute
from
Enterprise
Manager

Last CTI: Last Custom Data Custom Yes No

Message Message Data

Logged On Agent: Logged Custom Data Custom Yes No

Duration On Duration Data

Network ID Agent: Custom Data Custom Yes No

Network ID Data

Number CTI: Number Custom Data Custom Yes No

Dialed Dialed Data

Number of Number of Contact. Small No No

Conference Conferences number_of_confer Integer
s ences

Number of Number of Session. Small Yes No

Holds Holds number_of_holds Integer

Number of Number of Contact. Small No No

Transfers Transfers number_of_transfe Integer
rs

Custom Data Migration Mapper Guide 28

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Overbooked User Data Fields in Full-time Recording Systems

Supported by Custom Data

Migration Mapper?
Source Target Target
Attribute Attribute System Field Target Full-time Quality
Type Name Data Type Recording Monitoring

Organizatio Agent: Custom Data Custom Yes No

n Organization Data

Parties CTI: Parties Custom Data Custom Yes No

Data

Pause Contact: Custom Data Custom Yes No

Duration Pause Data
Duration

Queue CTI: Queue Custom Data Custom Yes No

Data

Serial CTI: Serial Custom Data Custom Yes No

Number Number Data

Skill Agent: Skill Custom Data Custom Yes No

Data

Supervisor Agent: Custom Data Custom Yes No

Name Supervisor Data
Name

Third Party CTI: Third Custom Data Custom Yes No

Party Data

Time on Total Hold Session. Integer Yes No

Hold Time total_hold_time

Trunk CTI: Trunk Custom Data Custom Yes No

Data

Trunk CTI: Trunk Custom Data Custom Yes No

Group Group Data

Workstation CTI: Custom Data Custom Yes No

Workstation Data

Overbooked User Data Fields in Full-time Recording

Systems
Some Full-time Recording systems may have “overbooked” user data fields. This refers
to the practice of using a single field for multiple purposes. For some sites, overbooking
may be achieved by storing multiple data values in a single field, separated by commas.

Custom Data Migration Mapper Guide 29

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Overbooked User Data Fields in Full-time Recording Systems

For other sites, overbooking may be achieved by using two views, each of which
accesses the same user data field for a different purpose.
If the source system utilizes “overbooking,” and the system contains views designed to
extract the overbooked fields, then the views will extract the data correctly for mapping.

Custom Data Migration Mapper Guide 30

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Project Icons

Project Icons
When working with projects, the left pane’s tree view uses the following icons to enable
you to quickly identify items in the tree.

Icon Description

Migration project.

Target system. A system is always a child of a project.

Target Quality Monitoring system. A system is always a

child of a project.

Target Full-time Recording system. A system is always a

child of a project.

Attribute definition, which is always a child of either a

Quality Monitoring or a Full-time Recording system.

Contact mapping, which is always a child of an attribute

definition.

User-defined field mapping, which can only be a child of

an attribute definition for a Quality Monitoring system.

Evaluation mapping, which can only be a child of an

attribute definition for a Quality Monitoring system.

Custom Data Migration Mapper Guide 31

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Field Status

Field Status
When mapping custom data fields to attributes in the target system, the Custom Data
Migration Mapper automatically validates the mapping for each field as you change it.

TIP Click the field status icon in the Custom Data Migration Mapper to see a tip
that describes the status condition.

The following status icons are displayed:

Icon Description

Valid mapping.

Potentially invalid mapping.

Current mapping should be checked to ensure data loss
will not occur. Scenarios where you will have a
potentially valid mapping include:
 Mapping a string field into an integer field, such as
for contact statistics.
 Mapping a source string field whose data length
exceeds the field length of the target field.

Invalid mapping.
An invalid mapping condition occurs when:
 The target field is too short to hold the source data.
 Converting a long string to an integer.
 Using a target system field more than once within a
single mapping.

Custom Data Migration Mapper Guide 32

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Field Captions

Field Captions
The term caption refers to the display label, and thus corresponds to the function of a
custom data field in the target system. You can use the Custom Data Migration Mapper
to assign captions to custom data fields, based on the meaning of the data from the
source system.

IMPORTANT In all comparisons of field captions between systems, the Custom Data
Migration Mapper does not consider case. In other words, “Agent Name” is
considered identical to “agent name” or “Agent name” or “Agent NAME”.

Custom Data Migration Mapper Guide 33

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Locked (In Use) Fields

Locked (In Use) Fields

After you have selected a mapping for a field, the Custom Data Migration Mapper will
lock the target system field. A locked field means that its caption cannot be edited again
since it is in use and its function has been determined. Any other mapping that uses that
custom data field must use it for the same function; in other words, its semantic value
must be same.
Note that:
 A custom data field that is in use in the target system will be locked automatically.
 A clean installation of a target system will provide all custom data fields in an
unlocked state.
Although you can unlock a field, the Custom Data Migration Mapper will provide a
warning that doing so may result in inconsistencies in the target system.
The following icons may be displayed in the In Use column of the Custom Data
Migration Mapper:

Icon Description

Field is in use by another mapping and has been locked

by the Custom Data Migration Mapper. You can still map
data to the field, but the definition of its caption is
determined by the mapping that has locked it.
NOTE: To unlock the field, you can click the lock icon.
When you unlock a field, the definition of its caption is
then determined by the mapping in which you unlock it.
See the locking topics in “Working with a Quality
Monitoring System” on page 86 and “Working with a
Full-time Recording System” on page 64 to learn more.

Field is not in use and is available for use by the current

mapping.

Additional information available about the locked status.

Click this information icon to learn about where the field
is in use.

Custom Data Migration Mapper Guide 34

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Stale Mappings

Stale Mappings
A concept that you should understand prior to working with the Custom Data Migration
Mapper is how a mapping can become “stale”. A stale mapping refers to a mapping that
is based on source or target data that has changed since the mapping was created. In
short, if a mapping does not match the data on which it is based, then the mapping is
said to be stale.
When a mapping becomes stale, the Custom Data Migration Mapper will provide you
with a notification message and automatically highlight the affected items in the
attribute or mapping.
A stale mapping can occur for several reasons:
 The Custom Data Migration Mapper has detected changes in the target system with
which the mapping is associated.
 The Custom Data Migration Mapper has detected changes in one of the source
systems on which the mapping is based.
To correct a stale mapping, you should review and possibly correct the existing
mappings based on the changes detected by the Custom Data Migration Mapper.

Custom Data Migration Mapper Guide 35

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 1 - Custom Data Migration Mapper Overview Full-time Recording Systems and eWare Views

Full-time Recording Systems and eWare

Views
For Full-time Recording systems, it’s important that you understand that the Custom
Data Migration Mapper is designed to use database views to access all data.
To enable the Custom Data Migration Mapper to work with the eWare database you can
modify one or more existing views via the SQL Server Management Studio, which is
provided with your database installation. For assistance using the SQL Server
Management Studio, consult that product’s documentation.

Rules for Migration Views

If you are not using one of the eWare views automatically installed, it is recommended
that you open an existing eWare view, modify it for use with Custom Data Migration
Mapper, and then save it under a new name.

NOTE Refer to “Create a Migration View” on page 65 for a step-by-step

procedure for modifying a view to work with the Custom Data Migration
Mapper.

Any view used for migration must meet the following conditions:

Applies To Rule

Referenced Table The view definition must use the table tblCalls.

Required Fields The view must include the following columns from the tblCalls
table:
 INum
 StartedAt
 Duration
 StartedAtUTC
 FormatId
 ItemModifiedDatetime
 Digits
 SCData

Recommended eWare Views

To identify the views that need to be used for custom data mapping with eWare, use the
views that users of the viewer application use to search for calls.

Custom Data Migration Mapper Guide 36

Confidential and Proprietary Information of Verint Systems, Inc.

 Chapter 2

Custom Data Migration

Mapper Workflows

This chapter details the primary upgrade and migration procedural workflows to follow
when using the Custom Data Migration Mapper. It is essential that you follow precisely
the processes outlined in this chapter.
In addition to the basic workflow, you will also find advanced workflows for scenarios not
covered by the primary workflow. The advanced workflows supplement the primary
workflow.
The following topics are covered:
 Primary Migration Process Workflow on page 38
 Advanced eWare Migration Process Workflows on page 43

NOTE For Quality Monitoring with Full-time Recording environments, it is

recommended that you complete the mapping process for the Full-time
Recording systems before proceeding with the Quality Monitoring mapping
process. This enables the Full-time Recording system to use the custom
data fields utilizing one of the standard attribute types.
Chapter 2 - Custom Data Migration Mapper Workflows Primary Migration Process Workflow

Primary Migration Process Workflow

The Custom Data Migration Mapper’s usage is a multi-stage process that consists of
several discrete steps, often performed by different parties.
NOTE For advanced workflow scenarios involving eWare recorders, refer to
“Advanced eWare Migration Process Workflows” on page 43.

The primary workflow process consists of the following stages:

Custom Data Migration Mapping Process Content Location

1 Discover source system(s), extract data, and  Working with a Full-

define attributes time Recording
System on page 64
a. Identify a prior version system, such as Quality
Monitoring.  Working with a
Quality Monitoring
b. Extract the source custom metadata, which is System on page 86
later used for data mapping. For Quality
Monitoring systems, this includes evaluation
custom data and user-defined data.
c. Define source attributes, which will be mapped to
the target system.

2 Discover target system Discovering a Target

a. Identify an existing installation of the target System on page 108
system to which the custom data will be mapped.
b. Discovery will load the system metadata used for
data mapping.
c. This step is optional if the target system is not yet
available.
IMPORTANT: Before attempting to discover a target
system, your target system’s Data Center server
must be installed, configured, and running. Refer to
the Glossary to learn about performing the
installation.

Custom Data Migration Mapper Guide 38

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 2 - Custom Data Migration Mapper Workflows Primary Migration Process Workflow

Custom Data Migration Mapping Content Location

3 For Full-time Recording systems or Quality

Monitoring with Full-time Recording systems
where Integration Service is used and the Enterprise Manager
target system is available: Configuration and
Administration Guide
a. Using the Target Enterprise Manager,
identify any custom attributes defined on Map Full-time Recording
the Attributes page. Fields to the Target
Print out the names of any custom attributes. System on page 81
b. Configure the custom attribute names in
Custom Data Migration Mapper
Configure the custom data captions in the Custom
Data Migration Mapper. Completing this step
ensures that the migration will not create new
attributes but will use the existing attributes.
Configuration must be completed using the
generic “Custom” attribute type.

4 Mapping source data  Full-time Recording

Mapping on page 79
a. Map source data to attributes and fields in the
target system.  Quality Monitoring
Contact Mapping on
b. Resolve any issues or conflicts between systems. page 96
This step can be performed while not connected to  Quality Monitoring
either the target system or the source system. User-Defined Field
Mapping on page 100
 Quality Monitoring
Evaluation Attribute
Mapping on page 103

5 Mapping Preview  Preview Full-time

Recording
Check your mapping using a subset of actual data
Mapping on page 83
from the source system.
 Preview Quality
Monitoring Contact
Mapping on page 98
 Preview Quality
Monitoring User-
Defined Field
Mapping on page 101
 Preview Quality
Monitoring Evaluation
Attribute Mapping on
page 106

Custom Data Migration Mapper Guide 39

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 2 - Custom Data Migration Mapper Workflows Primary Migration Process Workflow

Custom Data Migration Mapping Content Location

6 Review Mapping Summary View Project Status on

page 58
Check the status of your mapping project to ensure
that no issues exist.

7 For phased Quality Monitoring upgrades only,

test the upgraded Recorder at the site:
Print from Your Project on
a. Print mappings page 129
Generate hardcopy for of your mappings, which
you will use in the next step for configuring Enterprise Manager
Enterprise Manager. Configuration and
Administration Guide
b. Configure contact attributes and custom
data fields in Enterprise Manager Enterprise Manager
Use the hardcopy of the mapping you created in Configuration and
the previous step to configure attributes and Administration Guide
custom data fields in the target system Enterprise
Manager.
 To complete this step you must have the
target system installed and working. Refer to
the Installation Guide for installation
instructions.
c. Place test calls to confirm recording is
working properly
Test the recording functionality of the target
system to ensure that attributes and custom data
fields are working properly.

8 Rediscover target system Initiate Rediscovery of the

 Identify an existing installation of the target Target System on
system to which the custom data will be mapped. page 118

 Discovery will load the system metadata used for

data mapping.
IMPORTANT: Before attempting to discover an
target system, your target system Data Center
server must be installed, configured, and running.
Refer to the Installation Guide (for NG Recorders) to
learn about performing the installation.
At this point, you must synchronize source data
mappings you manually created prior to target
system discovery with the actual data discovered in
the target system.

Custom Data Migration Mapper Guide 40

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 2 - Custom Data Migration Mapper Workflows Primary Migration Process Workflow

Custom Data Migration Mapping Content Location

9 Mapping Preview  Preview Full-time

Recording
Check your mapping using a subset of actual data
Mapping on page 83
from the source system.
 Preview Quality
Monitoring Contact
Mapping on page 98
 Preview Quality
Monitoring User-
Defined Field
Mapping on page 101
 Preview Quality
Monitoring Evaluation
Attribute Mapping on
page 106

10 Review Mapping Summary View Project Status on

page 58
Check the status of your mapping project to ensure
that no issues exist.

11 Create Archive Completing the Mapping

Create a compressed archive file (.zip) containing the Process on page 122
XML mapping data used by the migration process.
Note: After you have created the archive file, it is
required by the migration tool used during the
upgrade and migration process to complete the data
migration to the target system.

12 Migrate Data Recorder Upgrade &

Uses the archive created in the previous to perform Migration Guide
the data migration to the target system.

Custom Data Migration Mapper Guide 41

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 2 - Custom Data Migration Mapper Workflows Advanced eWare Migration Process Workflows

Advanced eWare Migration Process Workflows

To complete these upgrade scenarios, use the workflow detailed in “Primary Migration
Process Workflow” on page 38, with the following supplementary processes:
 TDM Recorder Converted to IP with Same Serial Number on page 44
 TDM Recorder Switched to IP Recorder with New Serial Number on page 45
 Mixed Environment Using TDM Recorder and IP Recorder on page 46

Custom Data Migration Mapper Guide 42

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 2 - Custom Data Migration Mapper Workflows TDM Recorder Converted to IP with Same Serial Number

TDM Recorder Converted to IP with Same Serial

Number
1 The Recorder began as a TDM Recorder.
2 The Recorder was converted to an IP Recorder utilizing the same serial number.
3 You need to migrate both the TDM Recorder calls and the IP Recorder calls.

Custom Data Migration Mapping Process Content Location

1 Discover source system(s), extract data, and Working with a Full-time

define attributes Recording System on
a. Define attributes for TDM calls page 64
When completing this step in the workflow,
ensure that you:
- Select the view associated with TDM calls.

Custom Data Migration Mapping Process Content Location

b. Define attributes for IP calls Working with a Full-time

Recording System on
When completing this step in the workflow, ensure page 64
that you:
- Select the view associated with IP calls.

2 Continue with the primary workflow. Primary Migration Process

Workflow on page 38

Custom Data Migration Mapper Guide 43

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 2 - Custom Data Migration Mapper Workflows TDM Recorder Switched to IP Recorder with New Serial Number

TDM Recorder Switched to IP Recorder with New Serial

Number
1 The Recorder began as a TDM Recorder.
2 The Recorder was converted to an IP Recorder. A new serial number was used for
the IP Recorder.
3 You need to migrate both the TDM Recorder calls and the IP Recorder calls.

Custom Data Migration Mapping Process Content Location

1 Discover source system(s), extract data, and Working with a Full-time

define attributes Recording System on
a. Define attributes for TDM calls page 64

When completing this step in the workflow,

ensure that you:
- Select the view associated with TDM calls.
- Select the TDM Recorder.

b. Define attributes for IP calls Working with a Full-time

Recording System on
When completing this step in the workflow, ensure page 64
that you:
- Select the view associated with IP calls.
- Select the IP Recorder.
NOTE: The recorder shown may be identified
as a TDM Recorder. This is normal.

2 Continue with the primary workflow. Primary Migration Process

Workflow on page 38

Custom Data Migration Mapper Guide 44

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 2 - Custom Data Migration Mapper Workflows Mixed Environment Using TDM Recorder and IP Recorder

Mixed Environment Using TDM Recorder and IP

Recorder
1 The eWare site simultaneously uses both a TDM Recorder and an IP Recorder.
2 The customer wants to convert both the TDM Recorder calls and the IP Recorder
calls.

Custom Data Migration Mapping Process Content Location

3 Discover source system(s) and extract data. Working with a Full-time

a. Define attributes for TDM calls Recording System on
page 64
When completing this step in the workflow,
ensure that you:
- Select the view associated with the TDM calls.
- Select the TDM Recorder.

b. Define attributes for IP calls Working with a Full-time

Recording System on
When completing this step in the workflow, ensure page 64
that you:
- Select the view associated with the IP calls.
- Select the IP Recorder.

4 Continue with the primary workflow. Primary Migration Process

Workflow on page 38

Custom Data Migration Mapper Guide 45

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 2 - Custom Data Migration Mapper Workflows Mixed Environment Using TDM Recorder and IP Recorder

Custom Data Migration Mapper Guide 46

Confidential and Proprietary Information of Verint Systems, Inc.

 Chapter 3

Installing the Custom Data

Migration Mapper

The Custom Data Migration Mapper runs independently of other programs and is not
connected to other system installation scripts. The Custom Data Migration Mapper
automatically installs the directory structure where its components reside.
Topics:
 Prerequisites on page 48
 Install the Custom Data Migration Mapper on page 49
 Launch the Custom Data Migration Mapper on page 50
 Remove the Custom Data Migration Mapper on page 51
Chapter 3 - Installing the Custom Data Migration Mapper Prerequisites

Prerequisites
No prerequisite steps are necessary before installing the Custom Data Migration Mapper.

Custom Data Migration Mapper Guide 48

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 3 - Installing the Custom Data Migration Mapper Install the Custom Data Migration Mapper

Install the Custom Data Migration Mapper

TIP It is strongly recommended as a best practice to install the Custom Data
Migration Mapper on your laptop.

To install the Custom Data Migration Mapper:

1 Open the Verint Portal, go to the migration tools area.
a. Select the Custom Data Migration Mapper folder.
b. Download the installation archive and extract its contents to a location on your
file system.

2 From the downloaded installation, launch CDMMInstall.msi. The installation

wizard displays the welcome screen.
3 Click Next. The Destination Folder screen displays.
4 Select the location where you wish to install the Custom Data Migration Mapper, and
then click Next. The Ready to Install the Program screen displays.
5 Click Install. The installation wizard installs the Custom Data Migration Mapper.
You can observe the installation progress by observing the status bar. When the
installation completes:
 A shortcut is placed on your desktop
 The Custom Data Migration Mapper service is automatically started on the
machine where you installed it.
You are ready to begin using the Custom Data Migration Mapper.

Custom Data Migration Mapper Guide 49

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 3 - Installing the Custom Data Migration Mapper Launch the Custom Data Migration Mapper

Launch the Custom Data Migration Mapper

Before attempting to launch the Custom Data Migration Mapper, make sure that you
have made the following configuration changes in your browser:
 Disable all pop-up blockers currently enabled in the browser.
 Add the Custom Data Migration Mapper server URL to the list of trusted sites.
Trusted sites are configured in Internet Explorer via Tools > Internet Options.
Select the Security tab and then add the site address to the Trusted sites zone.
You can obtain the site address from the shortcut placed on your desktop during
installation.
To launch the Custom Data Migration Mapper:
1 Double click the Custom Data Migration Mapper shortcut placed on your desktop
by the installation wizard.
You can also launch the Custom Data Migration Mapper by providing the following
address in your browser:
http://<HostName>:29680/cdmm
Where <HostName> should be replaced with the actual host name where the
Custom Data Migration Mapper was installed.
The log in page displays in a browser window.
2 Enter your Username and Password, then click Login.
Log in using the default Username and Password provided with the application.

Custom Data Migration Mapper Guide 50

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 3 - Installing the Custom Data Migration Mapper Remove the Custom Data Migration Mapper

Remove the Custom Data Migration Mapper

To remove the Custom Data Migration Mapper from a system, use the following
procedure. Note that you can remove the application while preserving the current
configuration and mapping details.
You should remove the Custom Data Migration Mapper when you have completed all
mapping and migration activity. Removal includes the deletion of the Custom Data
Migration Mapper service, which should not be left running after migration activity has
concluded.
If you do not wish to remove the application after completing all migration work, you
should at least disable the Custom Data Migration Mapper service in the Windows
Services Control Panel.
To remove the Custom Data Migration Mapper:
1 From the Windows Control Panel, launch Add or Remove Programs.
2 From the list of currently installed programs, select Custom Data Migration
Mapper, and then click Remove. Please wait while the program is removed from
the system.

Custom Data Migration Mapper Guide 51

Confidential and Proprietary Information of Verint Systems, Inc.

 Chapter 4

Configuring the Custom Data

Migration Mapper

After you have installed the Custom Data Migration Mapper, you are ready to configure
the system settings and any user accounts you need to complete the mapping process
Chapter 4 - Configuring the Custom Data Migration Mapper Update System Settings

Update System Settings

System settings provides you with the ability to configure global options that apply to all
users and all migration projects.

To update system settings:

1 Launch the Custom Data Migration Mapper.
2 Click System > Settings.

3 Update the following settings:

Setting Description

FTR Discovery Period Applies to the discovery of source attribute definitions

(days) in the source system. Number of days the system
considers when determining data types and field
lengths during discovery for the latest calls.
Default: 30 days
Minimum period: 1 day.
Maximum period: 3,650 days.
NOTE: The discovery period applies only to Full-time
Recording systems.

Preview Size (rows) Applies to previewing the mapping. After configuring

your custom data mapping, you can test the
migration on a subset of data. Use this parameter to
define the number of rows from the database you
wish to preview.
The minimum preview size allowed is 1 row.
The maximum preview size allowed is 1,000 rows.
Refer to “Working with a Full-time Recording System”
on page 64 and “Working with a Quality Monitoring
System” on page 86 to learn more about previewing.

4 To save your changes, click Save.

Custom Data Migration Mapper Guide 53

Confidential and Proprietary Information of Verint Systems, Inc.

 Chapter 5

Managing Projects

The Custom Data Migration Mapper organizes all migration tasks into projects. You can
use projects to organize your migration tasks. For example, you may need a separate
project for a Full-time Recording system or for a Quality Monitoring system.
Since the Custom Data Migration Mapper functions on a site-by-site basis, you may
organize your migration using one project to contain all sites or store each site in a
separate project. Choose the organizational method that works best for the enterprise.
All projects display in the left pane’s organizational tree view. Under each project, you
will have one or more additional entries. These additional entries are created in the
course of the mapping process. Example entries you may see include connection
settings for source databases, source attribute definitions, and target attribute
definitions.
This chapter contains the following topics:
 Create a Project on page 55
 Open a Project on page 56
 Delete a Project on page 57
 Review Project Status on page 58
 Copy a Project to Another Computer, page 63
Chapter 5 - Managing Projects Create a Project

Create a Project
Create a project when you have a new migration planning project to undertake.
1 Launch the Custom Data Migration Mapper.
2 Click the Migration Mapper tab at the top of the page. .

3 Select Migration Projects in the left pane.

4 Click Create Project.
5 Complete the project settings, as described in “Project Settings” on page 55.
6 Click Save. Your new project is created, and added to the “Migration Projects” node
of the tree view.

Project Settings
The following settings are provided for each user project:

Setting Description

Name Defines the project name used to identify the project

within the Custom Data Migration Mapper. This field is
required.

Customer Name Defines the customer name associated with the

project. This field is required.

Description Provide any text useful for identifying the project’s

purpose and scope.

Custom Data Migration Mapper Guide 55

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 5 - Managing Projects Open a Project

Open a Project
After having created a project, you can easily open it by selecting it in the left pane’s
tree view.
To open a project:
1 Launch the Custom Data Migration Mapper.
2 Click the Migration Mapper tab at the top of the page.

3 Using the left pane’s tree view, select the project you wish to open. Projects display
as primary nodes under the parent Migration Projects.
After selecting the project in the tree view, its properties display in the right pane.

Custom Data Migration Mapper Guide 56

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 5 - Managing Projects Delete a Project

Delete a Project
You can delete a project for which you no longer have a use.

IMPORTANT When you delete a project, you will lose all source and target attribute
definitions.

To delete a project:
1 Open an existing project, as described in “Open a Project” on page 56.
2 Click Delete. A confirmation dialog displays to confirm the deletion of the project,
as well as all child attribute definitions and mappings.
3 If you are sure you want to remove the site permanently, click OK. The project is
removed.

Custom Data Migration Mapper Guide 57

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 5 - Managing Projects Review Project Status

Review Project Status

At any point in the mapping process, you can use the Custom Data Migration Mapper to
check the current status of your mapping projects. The status tabs for the project
provide the following types of information:
 Discovery status by site
 Contact mapping summary by custom data field
 User-defined field mapping summary (applies only to Quality Monitoring systems)
 Evaluation custom data mapping summary (applies only to Quality Monitoring
systems)
 Unmapped attributes summary

View Project Status

To view the status of any project:
1 Open an existing project, as described in “Open a Project” on page 56.
2 Select one of the status tabs provided. Use the topics indicated below to learn more
about each tab’s usage.
For projects containing only Full-time Recording systems, the following status tabs
are available:
 Status Tab on page 58
 Contact Mapping Summary Tab on page 59
 Unmapped Attributes Summary Tab on page 62
For projects containing Quality Monitoring systems, which includes Quality
Monitoring with Full-time Recording systems, the following status tabs are
available:
 Status Tab on page 58
 Contact Mapping Summary Tab on page 59
 User Mapping Summary Tab on page 60
 Evaluation Mapping Summary Tab on page 61
 Unmapped Attributes Summary Tab on page 62

Status Tab
The Status tab provides you with a summary view of the completion status for all
system discovery tasks in a given project.
System discovery refers to the process of connecting to an existing database to examine
the visible custom data fields and to determine how the custom data fields are used.
You can quickly see the start/end dates for the tasks, as well as who initiated the
discovery process.

Custom Data Migration Mapper Guide 58

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 5 - Managing Projects Contact Mapping Summary Tab

The page automatically refreshes at regular intervals. Use the Refresh Rate field to
control the refresh frequency.
The Discovery Task Status tab includes the following details:

Column Description

System Includes each Full-time Recording and Quality Monitoring system

in the project. Click the arrow icon to expand a system to see its
details.

Site/Attribute Definition Provides each attribute definition created for a given system.

Completion Status Displays the completion status for the discovery process for each
attribute definition. Click a displayed status icon to obtain detailed
information about the status. The following icons display:

Discovery process has been completed.

Discovery process has failed or not yet been completed.

Discovery process is in progress.

Task Initiated Date Date and time the discovery process was started.

Task Ended Date Date and time the discovery process was completed.

Initiated User Custom Data Migration Mapper user name who started the
discovery process.

Contact Mapping Summary Tab

The Contact Mapping Summary tab provides you with a summary status of the mapping
progress for contact attributes in a given project. You can quickly see each custom or
standard data attribute, its mapping, lock status, and many other details as described
below.
The Contact Mapping Summary tab includes the following details:

Column Description

Target Contact Attribute Provides the name of the target custom data field to which a
source attribute has been mapped.

Caption The currently defined caption for the target attribute.

In Use Displays in the row for the system that owns the definition of the
custom data field.

Custom Data Migration Mapper Guide 59

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 5 - Managing Projects User Mapping Summary Tab

Column(Continued) Description

System Provides the name of the Full-time Recording or Quality Monitoring

system (as defined in the Custom Data Migration Mapper) which is
using the target attribute.

Attribute Definition Provides the name of the source attribute definition which
contains a mapping to the target attribute.

Mapping Displays the name of the specific mapping which uses the target
attribute.
Click the name to view the mapping details.

Status Displays the current mapping status. Refer to “Field Status” on

page 32 to learn more.

Source Attribute Provides the name of the source attribute which is mapped to the
target attribute.

Source Attribute Data Type Identifies the datatype (string or integer) of the source attribute.

Target Attribute Type Displays the attribute type in the target system.

Source Sample Value If source data are available from previous mapping preview
operations, displays a sample of the mapped data.

User Mapping Summary Tab

The User Mapping Summary tab provides you with a summary status of the mapping
progress for user-defined fields in a given project. You can quickly see each user-defined
field, its mapping, lock status, and many other details as described below.

NOTE The User Mapping Summary tab applies only to Quality Monitoring
systems.

The User Mapping Summary tab includes the following details:

Column Description

Target User Defined Field Provides the name of the target custom data field to which a
attribute has been mapped.

Caption The currently defined caption for the target attribute.

In Use Displays the current lock status for the target attribute. Refer to
“Locked (In Use) Fields” on page 34 to learn more.

System Provides the name of the Quality Monitoring system (as defined in
the Custom Data Migration Mapper) which is using the target
attribute.

Custom Data Migration Mapper Guide 60

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 5 - Managing Projects Evaluation Mapping Summary Tab

Column(Continued) Description

Attribute Definition Provides the name of the source attribute definition which
contains a mapping to the target attribute.

Mapping Displays the name of the specific mapping definition which uses
the target attribute.
Click the name to view the mapping details.

Status Displays the current mapping status. Refer to “Field Status” on

page 32 to learn more.

Source Attribute Provides the name of the source attribute which is mapped to the
target attribute.

Source Attribute Datatype Identifies the datatype (string or integer) of the source attribute.

Source Sample Value If source data are available, displays a sample of the mapped
data.

Evaluation Mapping Summary Tab

The Evaluation Mapping Summary tab provides you with a summary status of the
mapping progress for evaluation fields in a given project. You can quickly see each
evaluation field, its mapping, lock status, and many other details as described below.
NOTE The Evaluation Mapping Summary tab applies only to Quality Monitoring
systems.

The Evaluation Mapping Summary tab includes the following details:

Column Description

Target ECD Field Provides the name of the target evaluation custom data field to
which an evaluation field has been mapped.

Caption The currently defined caption for the target evaluation custom
data field.

In Use Displays the current lock status for the target evaluation custom
data field. Refer to “Locked (In Use) Fields” on page 34 to learn
more.

System Provides the name of the Quality Monitoring system (as defined in
the Custom Data Migration Mapper) which is using the target
evaluation custom data field.

Attribute Definition Provides the name of the source attribute definition which
contains a mapping to the target evaluation custom data field.

Custom Data Migration Mapper Guide 61

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 5 - Managing Projects Unmapped Attributes Summary Tab

Column(Continued) Description

Mapping Displays the name of the specific mapping definition which uses
the target evaluation custom data field.
Click the name to view the mapping details.

Status Displays the current mapping status. Refer to “Field Status” on

page 32 to learn more.

Source Attribute Provides the name of the evaluation source attribute which is
mapped to the target evaluation custom data field.

Source Attribute Datatype Identifies the datatype (string or integer) of the source field.

Source Sample Value If source data are available, displays a sample of the mapped
data.

Unmapped Attributes Summary Tab

The Unmapped Attributes Summary tab provides you with a summary status of any
unmapped source and target attributes for a given project. Unmapped attributes will not
be migrated, and so should be examined closely to ensure that no data loss will occur as
a result of not mapping the attributes.
The Contact Mapping Summary tab includes the following details:

Type Column Description

Unmapped CD/ECD/UDF/ Displays the name of the target custom data field, user data
Target Field field, or evaluation custom data field which has not been
Attributes used by any system in the mapping process.

Data Type Identifies the custom data field data type (string, integer).

Unmapped System Provides the name of the Full-time Recording or Quality

Source Monitoring system (as defined in the Custom Data Migration
Attributes Mapper) which contains the unmapped attribute.

Attribute Provides the name of the source attribute definition which

Definition contains the unmapped attribute.

Type Displays type of user

Field Name Provides the source attribute field name which has not been
mapped.

Type Displays the data type (string, integer) of the unmapped

attribute.

Length Displays the discovered data length for the unmapped

attribute.

Custom Data Migration Mapper Guide 62

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 5 - Managing Projects Copy a Project to Another Computer

Copy a Project to Another Computer

While working on a Custom Data Migration Mapper project, you may find it necessary to
transfer the project to another computer to hand off the project to another party or
simply to work from another location.
To copy a Custom Data Migration Mapper project to another computer:
1 If not already installed on the target computer, install the Custom Data Migration
Mapper. See “Installing the Custom Data Migration Mapper” on page 47.
2 Copy the following file and folder from the source computer to the target computer,
using the locations indicated:
 <Installation Location>\config\projects\<project name>.xml
 <Installation Location>\config\projects\<project name folder>\
NOTE The project name folder may not exist; if it does not exist, copy only the
XML file.

You select the installation location during installation. The default

installation location is:

C:\Verint\CDMM\

3 After you have copied the project, launch the Custom Data Migration Mapper on the
target computer and open the project, as described in “Open a Project” on page 56.

Custom Data Migration Mapper Guide 63

Confidential and Proprietary Information of Verint Systems, Inc.

 Chapter 6

Working with a Full-time

Recording System

After you have created a project, you are ready to begin the discovery and mapping
process for a Full-time Recording system.

NOTE Migration from a Full-time Recording system requires migration-specific

views. You cannot use the default views provided with the Full-time
Recording system. To learn more, refer to “Full-time Recording Systems
and eWare Views” on page 36.

NOTE For Quality Monitoring with Full-time Recording environments, it is

recommended that you complete the mapping process for the Full-time
Recording systems before proceeding with the Quality Monitoring mapping
process. This enables the Full-time Recording system to use the custom
data fields utilizing one of the standard attribute types.

Topics:
 Create a Migration View on page 65
 Discover a Full-time Recording System on page 68
 Attribute Definitions for the Full-time Recording System on page 72
 Initiate Rediscovery of the Full-time Recording Fields on page 77
 Remove a Full-time Recording Attribute Definition on page 78
 Full-time Recording Mapping on page 79
Chapter 6 - Working with a Full-time Recording System Create a Migration View

Create a Migration View

All migration for a Full-time Recording system relies on views.
For migration, create one or more views specifically for the migration. To learn more,
refer to “Full-time Recording Systems and eWare Views” on page 36.
To create a migration view, use the SQL Server Management Studio. Although this
procedure provides you with step-by-step instructions for modifying an existing view
and saving it, it is not intended to provide a full treatment on the use of the SQL Server
Management Studio; for more help with the SQL Server Management studio, consult
your SQL Server product documentation.
To create a migration view:
1 Launch the SQL Server Management Studio.
2 Select your database server, and then open the EWareCalls database.
3 Select the Views entry in the tree view. All views in the database display.

Custom Data Migration Mapper Guide 65

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Create a Migration View

4 Right-click one of the recommended eWare views, as detailed in “Recommended

eWare Views” on page 36, and then select the following shortcut menu options:
Script View As > CREATE To > New Query Editor Window.
For the purpose of illustration in this procedure we are using ViewCSTMCalls,
although you could select any of the recommended eWare views.
The view displays in a new editor window.
Example:

5 Change the view name to a unique name.

NOTE Failure to rename the view will result in loss of the definition of the original
view.

6 Modify the view’s fields to include all required fields, as detailed in “Rules for
Migration Views” on page 36.

Custom Data Migration Mapper Guide 66

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Create a Migration View

7 Optional. You can use a where clause to skip or select the recorders or dates.
Example:
If you want to skip a specific recorder:
-- WHERE (INUM/1000000000)<>600006
If you want to use a date range:
-- WHERE startedat>= '2010-01-01' and startedat<= '2015-01-01'
8 In the toolbar, click the Execute button. The view is compiled and added to the left
pane’s tree view.

Next Step:“Discover a Full-time Recording System” on page 68

Custom Data Migration Mapper Guide 67

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Discover a Full-time Recording System

Discover a Full-time Recording System

Discovery of the Full-time Recording system requires that you configure how the Custom
Data Migration Mapper will connect with the Full-time Recording system. Connection
settings include defining the database server, listening port for the database, database
authentication credentials, etc.
IMPORTANT After discovering the Full-time Recording system, you may find it
necessary to make adjustments to the migration view. If you change the
migration view you must rediscover the Full-time Recording system to pick
up changes to the view. See “About Rediscovery of the Full-time
Recording Fields” on page 72 to learn more about rediscovery.

To discover a Full-time Recording system:

1 Launch the Custom Data Migration Mapper.
2 Open the project where you want the Full-time Recording system to reside in the
Custom Data Migration Mapper, as discussed in “Open a Project” on page 56. The
Project Settings page displays.
3 Click Next.

4 Select Discover Impact 360 FTR System. Complete the Full-time Recorder
Settings, as described in “Full-time Recording Database Settings” on page 69.
5 Click Save. The Custom Data Migration Mapper saves the connection settings.
6 To discover the views used in the system, click Discover Source System. The
Custom Data Migration Mapper attempts to connect to the Full-time Recording
system.

NOTE After successfully connecting, the Custom Data Migration Mapper

automatically completes the following tasks in the Full-time Recording
system:

a. All views in the database are discovered.

b. A new stored procedure is created.

The created stored procedure is used to discover source fields during the
attribute definition phase, as discussed in “Attribute Definitions for the
Full-time Recording System” on page 72.

After a successful connection, a confirmation message displays indicating success.

If you are unable to connect, check your connection settings and the availability of
the Full-time Recording system.
Next Step:“Define Full-time Recording Attributes” on page 72

Custom Data Migration Mapper Guide 68

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Full-time Recording Database Settings

Full-time Recording Database Settings

The following Full-time Recording database settings are provided for each site:

Setting Description

General Settings Name Defines the name within the Custom Data
Migration Mapper that uniquely identifies the
Full-time Recording system. This field is
required.

Description Provide any text to describe the system.

Custom Data Migration Mapper Guide 69

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Full-time Recording Database Settings

Setting(Continued) Description

Eware Calls Database Server* Provide the host name or the IP address for
Database Settings the Full-time Recording database server. This
field is required. Changing this field will require
rediscovery.
IMPORTANT: You must ensure consistency in
the use of host name or IP address across
tools.
 If you provide a host name here, you must
provide a host name in the eWare
Migration Tool during data migration, as
well as when using the User Migration
Tool.
 If you provide an IP address here, you
must provide an IP address in the eWare
Migration Tool during data migration, as
well as when using the User Migration
Tool.

Port* Provide the port on which the Full-time

Recording database server listens for requests.
This field is required. Changing this field will
require rediscovery.

Database Name Displays the instance of the database used on

the database server.
This field is display only.

Database Type Displays the vendor for the database server.

This field is display only.

User Name* Provide the account user name that the

Custom Data Migration Mapper will provide for
authentication when connecting with the
database server.
NOTE: The account used must have
permission in the EwareCalls database to
create new stored procedures.
NOTE: Custom Data Migration Mapper does
not support connecting to SQL Server using
Windows authentication. You must connect
using SQL Server authentication.

Password* Provide the password that the Custom Data

Migration Mapper will provide for
authentication when connecting with the
database server.

Custom Data Migration Mapper Guide 70

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Full-time Recording Database Settings

* Changing the value of these fields for an already discovered Full-time Recording
system will require that you rediscover the Full-time Recording fields. See “About
Rediscovery of the Full-time Recording Fields” on page 72 to learn more about
rediscovery.

Custom Data Migration Mapper Guide 71

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Attribute Definitions for the Full-time Recording System

Attribute Definitions for the Full-time

Recording System
After you have saved your Full-time Recording connection settings, you are ready to
define the Full-time Recording attributes you will be mapping to the target system.
Attribute definition requires that you initiate a field discovery process against the source
system. Discovery will run for the following subset of eWare data:
 The tool will inspect custom data fields.
 A single eWare database view.
During attribute definition the tool will:
 Attempt to the connect with the Full-time Recording system.
 Examine the custom data for the latest calls in the FTR Discovery Period (days)
(default is 30 days).
 Retrieve the attribute definitions for custom data fields.
IMPORTANT After defining attributes for the Full-time Recording system, you may find
it necessary to make adjustments to the migration view. If you change the
migration view you must rediscover the Full-time Recording system to pick
up changes made to the view. See “About Rediscovery of the Full-time
Recording Fields” on page 72 to learn more about rediscovery.

About Rediscovery of the Full-time Recording Fields

You have the option to rediscover the Full-time Recording fields at any time after having
performed the initial discovery. Rediscovery will update your existing attribute
definitions and mappings for the system. If new attributes are discovered, they will be
added. If previously discovered attributes are not found, they will be removed.
In addition, the following actions will require that you rediscover the Full-time Recording
fields:
 Changing the eWareCalls database settings.
 Modifying the migration view being used.

Define Full-time Recording Attributes

Attribute definition for the Full-time Recording fields is required after you have defined
or updated the Full-time Recording database connection settings.
To define attributes for the Full-time Recording system:
1 In the left pane’s tree view, select a previously defined Full-time Recording system
that has not yet undergone attribute definition.
2 Click Next. Click Attribute Definition.

Custom Data Migration Mapper Guide 72

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Full-time Recording Attribute Definition Settings

3 Complete the Attribute Definition Settings, as described in “Full-time Recording

Attribute Definition Settings” on page 73.

4 Click Save. The Custom Data Migration Mapper saves the attribute definition
settings.
Next Step: Return to the “Primary Migration Process Workflow” on page 38 and
continue with the workflow process.

Full-time Recording Attribute Definition Settings

The following Full-time Recording attribute definition settings are provided for each site:

Setting Description

General Settings Name Defines the name within the Custom Data
Migration Mapper that uniquely identifies the
Full-time Recording attribute definitions. This
field is required.

Description Provide any text useful for identifying the Full-

time Recording attribute definitions.

Migration Settings Migration Database View* Select the eWare view you wish to use for
mapping and migration. Refer to “Full-time
Recording Systems and eWare Views” on
page 36 to learn more about migration views
for eWare.

Source Attribute Fields After discovery has been completed, displays

the source attributes retrieved from the Full-
time Recording database. The attributes
displayed are:
 Source Field from View: Name of the
field in the source database.
 Data Type: Type of data stored in the
field, e.g., string, integer, etc.
 Data Length: Field length for the data
sampled by the FTR Discovery Period
(Days). Default is 30 days.
Warning: Actual data length can exceed
this number.
 Target Attribute Type: Type of attribute
to which contact attribute corresponds
within the target system. Refer to “Select
the Full-time Recording Source Field
Attribute Types” on page 75 to learn
more.

Custom Data Migration Mapper Guide 73

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Show Full-time Recording Contacts

* Changing the value of these fields for an already discovered Full-time Recording
system will require that you rediscover the Full-time Recording fields, which will result in
updating of the existing attribute definitions and mappings. See “About Rediscovery of
the Full-time Recording Fields” on page 72 to learn more about rediscovery.

Show Full-time Recording Contacts

After defining your attributes, you have the ability to view the contacts retrieved for the
selected view. Use this feature to see a sample of the contacts retrieved using your
attribute definition settings.
The Custom Data Migration Mapper uses the system-defined number of rows from the
source database for showing contacts. Refer to “Update System Settings” on page 53 to
learn more.
To show Full-time Recording contacts:
1 Access a previously created attribute definition. See “Define Full-time Recording
Attributes” on page 72 to learn more.
2 Click Show Contacts. A pop-up window opens to provide you with a view of the
contacts retrieved from the system.

3 To close the window, click Done.

Custom Data Migration Mapper Guide 74

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Initiate Full-time Recording Field Discovery

Initiate Full-time Recording Field Discovery

After you have created the attribute definition, you are ready to initiate field discovery
for the Full-time Recording system. Field discovery requires that the Custom Data
Migration Mapper connect with the Full-time Recording system to inspect the custom
data fields.

NOTE Field discovery can be a lengthy process, depending on the FTR Discovery
Period (days). The Custom Data Migration Mapper page will update at
regular intervals during the discovery process.

To initiate field discovery:

1 Access a previously created attribute definition. See “Define Full-time Recording
Attributes” on page 72 to learn more.
2 Click Discover Fields. The discovery process begins and the Attribute Definition
Settings page displays a dialog message indicating that discovery is in progress.
3 To close the dialog, click Close.
4 To change the refresh interval of the page, use the Refresh Rate drop-down list.
Click the refresh icon to update the page immediately.
When the discovery completes, the page will populate with the discovered fields.

Select the Full-time Recording Source Field Attribute

Types
After you have completed the source field discovery process, you should assign the
source fields discovered in the selected view and planned for migration to standard
target attribute types or mark the mapping as “Custom.”
Any source attribute not designated as a target attribute type will not be available to
you when performing the mapping process, as described in “Full-time Recording
Mapping” on page 79.
To map the Full-time Recording source fields:
1 Access a previously created attribute definition on which discovery has been
completed. See “Define Full-time Recording Attributes” on page 72 to learn more.
The Attribute Definition Settings page displays.
2 In the Source Attributes Fields section, use the Target Attribute Type drop-
down list to assign the attribute type for each discovered field. Select one of the
following types of entries in the drop-down list box:

IMPORTANT Within a single source attribute definition, you may only use each
standard target Attribute Type once. The Custom type can be used
multiple times.

 Custom: Designates the field as being a new custom field.

Custom Data Migration Mapper Guide 75

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Select the Full-time Recording Source Field Attribute Types

 CTI:<CTI Attribute>: Designates the field for one of the standard CTI
attributes, where <CTI Attribute> is a specific CTI attribute.
 Contact:<Contact Attribute>: Designates the field for one of the standard
contact attributes, where <Contact Attribute> is a specific contact attribute.
 Agent:<Agent Attribute>: Designates the field for one of the standard agent
attributes, where <Agent Attribute> is a specific agent attribute.
 Custom:<Custom Attribute>: Designates the field for one of the custom
attributes, where <Custom Attribute> is a specific custom attribute.
3 After you have assigned the attribute type to each source field required from the
Full-time Recording view, click Save.

Custom Data Migration Mapper Guide 76

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Initiate Rediscovery of the Full-time Recording Fields

Initiate Rediscovery of the Full-time

Recording Fields
NOTE Rediscovery is an optional step.

Before attempting to rediscover the Full-time Recording fields, it’s important that you
understand the impact of rediscovery, as discussed in “About Rediscovery of the Full-
time Recording Fields” on page 72.
You will need to rediscover the Full-time Recording fields if you change the eWare view
being used in the attribute definition.
Rediscovery is required if the Custom Data Migration Mapper detects that the mapping
definition has become stale. Refer to “Stale Mappings” on page 35 to learn more.
To rediscover the fields from a Full-time Recording system:
1 Open the previously defined attribute definition. See “Define Full-time Recording
Attributes” on page 72 to learn more. The Attribute Definition Settings page
displays.
2 Click Discover Fields. Two warning messages appear.
NOTE If the view definition utilized for migration has changed, the first message
indicates that a source system rediscovery is essential for migration to
work correctly, and that you should click Cancel and rediscover the source
system before rediscovering the attribute fields.
The second message informs you that source field discovery can be a long
operation and warns that previously discovered fields are overwritten. You
can click Cancel if you want to end the operation.

3 If you wish to proceed with rediscovery, click OK after each warning message.
The Custom Data Migration Mapper deletes existing fields and mappings and then
attempts to connect with the Full-time Recording system for field rediscovery.
4 To change the refresh interval of the page, use the Refresh Rate drop-down list.
Click the refresh icon to update the page immediately.
When the rediscovery completes, the page populates with the rediscovered fields.

Custom Data Migration Mapper Guide 77

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Remove a Full-time Recording Attribute Definition

Remove a Full-time Recording Attribute

Definition
Removing the attribute definition discards any previously discovered Full-time Recording
fields as well as all mappings associated with them. Ensure you are not actively using
the attribute definition before removing it.
To remove a Full-time Recording attribute definition:
1 Open the previously defined attribute definition settings. See “Define Full-time
Recording Attributes” on page 72 to learn more. The Attribute Definition Settings
page displays.
2 Click Delete. A confirmation dialog displays.
3 If you are certain you wish to remove the attribute definition, as well as all
associated mappings, click OK. The Custom Data Migration Mapper removes the
attribute definition from the system.

Custom Data Migration Mapper Guide 78

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Full-time Recording Mapping

Full-time Recording Mapping

After you have discovered the Full-time Recording fields and assigned the attribute
types, you are ready to begin the mapping process. Mapping requires that you select the
target field to which each source field will be migrated by the upgrade. In addition, you
have the ability to define the target caption you wish to use for each custom data field.
The Custom Data Migration Mapper will validate the mapping assignment to determine if
the mapping is valid and whether data loss may or may not potentially occur.
Depending on when the target system is installed, you can discover the target system
before or after you perform the mapping process. If the target system is not yet
installed, you will complete mapping manually and later synchronize your mapping with
the target system. This process was outlined in “Custom Data Migration Mapper
Workflows” on page 37.
If the target system has already been installed and configured, you can map to the
results of the target system discovery.
Before proceeding, you may find it useful to review the following overview topics:
 Field Status on page 32
 Field Captions on page 33
 Locked (In Use) Fields on page 34
If you are in an IP recording environment using default call tagging, ensure you review
“Default IP Mapping When Default Tagging Is Used” on page 84.

Default Full-time Recording Mapping Logic

The Custom Data Migration Mapper attempts to identify a default mapping for each field.
The default mapping is a suggestion and can be overridden. The identification of a
default mapping is based on the information provided in the Source Attribute Definition.
The default mapping uses the following logic in the given scenarios:
 Source identified as standard target system attribute: the source attribute is
identified as a standard target system attribute and there is a fixed attribute
available in the target system: the system suggests mapping the attribute to the
corresponding target system standard attribute.
NOTE It is possible that the source attribute is not valid for the target system
attribute. When this occurs, the default mapping to the target system
attribute is suggested but the status will indicate an issue exists (either an
invalid mapping or a warning). You then have the following options:
- Leave the mapping as is.
- Change the target mapping to a custom data field.

 Source identified as standard target system attribute: the source attribute is

identified as a standard target system attribute, but no fixed attribute exists in the
target system.

Custom Data Migration Mapper Guide 79

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Default Full-time Recording Mapping Logic

- If other contact mappings have source fields assigned to the same standard
target system type, then the same custom data field is suggested for the source
attribute.
- If other contact mappings do not have source fields assigned to the same
standard target system type, the target system custom attribute logic (see
below) applies.
 Source identified as existing EM custom attribute: the source attribute is
identified as an EM custom attribute.
- If other contact mappings have source fields assigned to the same EM custom
attribute, then the same custom data field is suggested for the source attribute.
- In all other cases, the suggested mapping follows the target system custom data
mapping logic (see below).
 Source identified as target system "custom" attribute type: the source
attribute is assigned to a custom data field using the following logic:
- If the source attribute is already mapped to a custom data field in other mapping
definitions, the system suggests mapping the source attribute to the same
custom data field. Note that the mapping will not be owned by current mapping
definition.
- If the source attribute is not already mapped to a custom data field other
mapping definitions, the system searches for a custom data field with a
corresponding data type and data length.
- If a custom data field is found, the smallest custom data field available is
suggested. The caption of the custom data field is set as described in “Full-
time Recording Default Custom Data Captions” on page 81.
- If a suitable custom data field is not found, no suggested mapping will be
provided for the source attribute. You can override the default and define a
mapping if required. However, the system never suggests a mapping that is
potentially invalid due to a data type mismatch, a potential truncation of
data, or due to a custom data field that is already is use elsewhere.
 Source attribute is not identified as a target system type: no suggestion is
provided and the source attribute will not be available to map to a target attribute.
To determine if a mapping is suggested by the Custom Data Migration Mapper or has
been user-defined, the following icons will be displayed:

Icon Description

Mapping has been suggested by the Custom Data

Migration Mapper.

Mapping has been defined by a user.

Custom Data Migration Mapper Guide 80

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Full-time Recording Default Custom Data Captions

Full-time Recording Default Custom Data Captions

The logic for the default data captions for custom data fields is based on the source
attribute’s type.
 EM custom type: caption is the EM custom attribute's name. If this caption is
already in use by any other custom data field in the project, the caption is the
mapped custom data field’s default caption; for example, "Custom Data 1".
 Target system standard type: caption is the target system standard type name.
If this caption is already in use by any custom data field in the project, the caption
is the mapped custom data field’s caption; for example, "Custom Data 1".
 Target system custom type: Caption is the source field’s name.

Potential Truncation of Source Data

If a source field’s length exceeds the target custom data field’s length, the migration
process will truncate the source data.
If this situation exists and data truncation is a concern, perform additional
investigation in the eWare database to determine
 if the reported maximum length is typical for the source field values, or
 if the extended data length is an anomaly where certain records have longer
values due to incorrect data tagging on the call.
After completing your investigation, you can choose one of the following paths:
 If the long values are an anomaly, then leave the mapping as is; data
truncation will apply only to the incorrectly tagged records.
 If the long values are normal, and the customer does not wish to truncate
the data, modify the migration view to split the single field into multiple
source fields. Then map each source field from the view individually to a
custom data field.
NOTE Any changes to the migration view require a rediscovery of the Full-time
Recording system.

Map Full-time Recording Fields to the Target System

To map source Full-time Recording fields to the target system:
1 Access a previously created attribute definition. See “Define Full-time Recording
Attributes” on page 72 to learn more. The Attribute Definition Settings page
displays.
2 Click Next. The Select Navigation dialog displays.
3 Click Contact Mapping. The Mapping Settings page displays.

Custom Data Migration Mapper Guide 81

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Unlock Full-time Recording Contact Attributes In Use

TIP Depending on your screen resolution, you may find it helpful to minimize
the left pane’s tree view, as shown above. You can minimize, maximize
and restore either pane by clicking the arrow buttons located between the
left and right panes.

4 Enter a unique Name for the mapping you are about to create. This field is
required.
5 To map a source field to a target field, use the Target Contact Attribute drop-
down list to select an available field.
 When you select a Target Contact Attribute field, the Custom Data Migration
Mapper immediately validates your selection and updates the status icon. Refer
to “Field Status” on page 32 to learn about the icon symbols.
 Refer to “Migration Attributes” on page 26 to learn about the fields available to
you.
 To identify a mapping as system-defined or user-defined, use the icon displayed
in the Target Contact Attribute column. See “Default Full-time Recording
Mapping Logic” on page 79 to learn about icon definitions.
6 To change the caption for a Contact Attribute field, update the Caption field. Note
that captions must be unique.
7 To exempt the source field from mapping altogether, select None in the Target
Contact Attribute drop-down list.
8 When you are satisfied with the mapping you have created, click Save. Any
changes to captions that make the current mapping the owner of a custom data
field will lock the custom data field.

The system validates the current mapping. The status column indicates warns you if
any of the following issues exist:
 Mappings to custom data fields that are already in use, either in the target
system or in another mapping for the current mapping project.
 Duplicate captions owned by the current mapping project. Captions must be
unique.
Next Step: Return to the “Primary Migration Process Workflow” on page 38 and
continue with the workflow process.

Unlock Full-time Recording Contact Attributes In Use

As discussed in “Locked (In Use) Fields” on page 34, you can unlock a target field that is
already in use in order to edit its caption.
When you unlock a field, the current mapping then “owns” the mapping to that field and
you are can edit its caption.
CAUTION Unlocking a mapped field may invalidate another mapping by overriding
the meaning of the data stored in the field by the other mapping. Ensure
you fully understand the migration consequences of unlocking a field.

Custom Data Migration Mapper Guide 82

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Preview Full-time Recording Mapping

To unlock a contact attribute:

1 Open a previously created contact attribute mapping. See “Map Full-time Recording
Fields to the Target System” on page 81 to learn more. The Contact Mapping
Settings page displays.
2 Identify a locked field you wish to unlock, and then click its lock icon. The Custom
Data Migration Mapper displays a confirmation dialog to ensure that you understand
the effects of unlocking a field.
3 If you are sure you wish to unlock the field, click OK. The field is unlocked, its lock
icon disappears, and the current mapping becomes the owner of the caption
definition.
4 Edit the Caption as required.
5 To save your changes, click Save.

Preview Full-time Recording Mapping

At any point during the process of Full-time Recording mapping, you have the ability to
preview the current mapping configuration using a subset of the source data. Previewing
provides you with the ability to check the current mapping against actual data to see the
results of the mapping during migration.

IMPORTANT For the initial Full-time Recording mapping preview, you must have the
ability to connect with the Full-time Recording system. The preview is not
available initially when you are working offline. After having performed an
online preview, you can make subsequent previews while working offline.

The Custom Data Migration Mapper uses the system-defined number of rows from the
source database for mapping previews. Refer to “Update System Settings” on page 53
to learn more.
To preview Full-time Recording mapping:
1 Open a previously created contact mapping. Refer to “Map Full-time Recording
Fields to the Target System” on page 81 to learn more.
2 Click Preview Contacts. If this is the first preview you have requested for this
mapping, the system displays the requested number of rows from the database.
If this is not the first attempt to preview contacts, a dialog displays that enables you
to select the type of contact preview you wish to see.
 Select Live Data if you have the ability to connect with the Full-time Recording
system and wish to view contacts retrieved from the live system.
 Select Stored Data if you cannot connect to the Full-time Recording system or if
you wish to view a previously retrieved set of contacts.
After making your selection, the Custom Data Migration Mapper displays the
system-defined number of rows from the source database and displays the mapping
results in a pop-up window.
Next Step: Return to the “Primary Migration Process Workflow” on page 38 and
continue with the workflow process.

Custom Data Migration Mapper Guide 83

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Remove a Full-time Recording Mapping

Remove a Full-time Recording Mapping

Removing the mapping will discard any previously defined mappings. Ensure you are not
actively using the mapping before removing it.
To remove a Full-time Recording mapping:
1 Open the previously defined contact mapping. See “Map Full-time Recording Fields
to the Target System” on page 81 to learn more. The Contact Mapping Settings
page displays.
2 Click Delete. A confirmation dialog displays.
3 If you are certain you wish to remove the mapping, click OK. The Custom Data
Migration Mapper removes the mapping from the system.

Default IP Mapping When Default Tagging Is Used

This topic provides you with a default mapping you can use in an IP recording
environment when default call tagging is used.
Note carefully that the default mapping described below is a basic recommendation.
Prior to mapping, it is essential that you analyze and review the data in the eWare
database. You must understand the way the data is being used before attempting to
map it.

Sample Mapping
For example, if using the migration view CSIPCiscoStitchCallsView_Migration (or
one similar to it), you could map the data as shown below:

Source Attribute Attribute Type Contact Database Field

CalledParty CTI: DNIS Session: DNIS Code

CallingParty CTI: ANI Session: ANI

CalledPartyName CTI: CalledPartyName CD Field

CallingPartyName CTI: CallingPartyName CD Field

CallType CTI: Call Direction CD Field

CallRef CTI: Call Id Sessions: Switch Call ID

Custom Data Migration Mapper Guide 84

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 6 - Working with a Full-time Recording System Modifications to Sample Mapping

Modifications to Sample Mapping

If you need to present a consistent Extension value regardless of whether a call is
inbound or outbound, you could modify the migration view. If you modify the view as
shown below, you can also use the following mapping:

Source Attribute Attribute Type Contact Database Field

Extension CTI: Extension Sessions: Extension

To use the mapping modification shown above, you will need to modify the migration
view as shown below:
NOTE The bold text represents modifications to the view. All other text is
provided for context only.

...
Calls.UserField7 as CallType,
CASE Calls.UserField7
WHEN 'in' THEN Calls.UserField3
WHEN 'INBOUND' THEN Calls.UserField3
WHEN 'out' THEN Calls.UserField2
ELSE NULL
END AS Extension,
Calls.UserField8 as Spare1,
...
The actual values stored in the CallType field indicate the direction of the call. Values can
vary from site to site.
To determine the actual text values to use in the WHEN statements above, use the
following query to obtain sample data values (substituting appropriate date values):
select distinct userfield7, count (*) from tblcalls
Where startedat between '2011-01-01 00:00:00.000' and '2011-12-31 23:59:59.999'
And channel = 0
group by userfield7

Custom Data Migration Mapper Guide 85

Confidential and Proprietary Information of Verint Systems, Inc.

 Chapter 7

Working with a Quality

Monitoring System

After you have created a project and discovered the new target system, you are ready
to begin the discovery and mapping process for a Quality Monitoring system.

NOTE For Quality Monitoring with Full-time Recording environments, it is

recommended that you complete the mapping process for the Full-time
Recording systems before proceeding with the Quality Monitoring mapping
process. This enables the Full-time Recording system to use the custom
data fields utilizing one of the standard attribute types.

This chapter contains the following topics:

 Discover a Quality Monitoring System on page 87
 Attribute Definitions for the Quality Monitoring System on page 89
 Initiate Rediscovery of the Quality Monitoring Fields on page 94
 Remove a Quality Monitoring Attribute Definition on page 95
 Quality Monitoring Contact Mapping on page 96
 Quality Monitoring User-Defined Field Mapping on page 100
 Quality Monitoring Evaluation Attribute Mapping on page 103
Chapter 7 - Working with a Quality Monitoring System Discover a Quality Monitoring System

Discover a Quality Monitoring System

Discovery of the Verint QM 7.x or Avaya QM 10.x/11.x system requires that you
configure how the Custom Data Migration Mapper will connect with the Quality
Monitoring system. Connection settings include defining the database server, listening
port for the database, database authentication credentials, etc.
To discover a Quality Monitoring system:
1 Launch the Custom Data Migration Mapper.
2 Open the project where you want the Quality Monitoring system to reside in the
Custom Data Migration Mapper, as discussed in “Open a Project” on page 56. The
Project Settings page displays.
3 Click Next. The Select Navigation dialog displays.

4 Select Discover Verint QM 7.x System or Discover Avaya QM 10.x/11.x

System. The Source System Settings page displays.
5 Complete the Source Database Settings, as described in “Source System Settings”
on page 87.
6 Click Save. The Custom Data Migration Mapper saves the connection settings and
attempts to connect to the Quality Monitoring system.
After a successful connection, a confirmation message displays indicating success.
If you are unable to connect, check your connection settings and the availability of
the Quality Monitoring system.

Next Step: “Define Quality Monitoring Attributes” on page 89

Source System Settings

The following Quality Monitoring database settings are provided for each site:

Setting Description

General Settings Name Defines the name within the Custom Data
Migration Mapper that uniquely identifies the
Quality Monitoring system. This field is
required.

Description Provide any text useful for identifying the

Quality Monitoring system.

Time Zone Select the time zone where the BDR server
resides.

Custom Data Migration Mapper Guide 87

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Source System Settings

Setting(Continued) Description

Source Database Database Server* Provide the host name or the IP address for
Settings the Quality Monitoring database server. This
field is required. Changing this field will require
rediscovery.

Port* Provide the port on which the Quality

Monitoring database server listens for
requests. This field is required. Changing this
field will require rediscovery.

Database Name* Provide the instance on the database server of

the database you wish to use. This should be
the database containing the Quality Monitoring
custom data. The default database name for a
Quality Monitoring system is “witness”. This
field is required. Changing this field will require
rediscovery.

Database Type Displays the vendor for the database server.

This field is display only.

User Name* Provide the user name that the Custom Data
Migration Mapper will provide for
authentication when connecting with the
database server.
NOTE: Custom Data Migration Mapper does
not support connecting to SQL Server using
Windows authentication. You must connect
using SQL Server authentication.
NOTE: The account used must have
permission in the Quality Monitoring database
to create new functions.

Password* Provide the password that the Custom Data

Migration Mapper will provide for
authentication when connecting with the
database server.

* Changing the value of these fields for an already discovered Quality Monitoring system
will require that you rediscover the Quality Monitoring fields, which will result in
updating of the existing attribute definitions and mappings. See “Rediscovery of the
Quality Monitoring Fields” on page 89 to learn more about rediscovery.

Custom Data Migration Mapper Guide 88

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Attribute Definitions for the Quality Monitoring System

Attribute Definitions for the Quality

Monitoring System
After you have saved your Quality Monitoring connection settings, you are ready to
define the Quality Monitoring attributes you will be mapping to the target system.
Attribute definition requires that you initiate a field discovery process against the source
system for a range of dates. The tool will inspect custom data fields inclusive of the
dates specified. During attribute definition the tool will:
 Attempt to the connect with the Quality Monitoring system.
 Examine the custom data for the specified date range.
 Retrieve the attribute definitions for custom data fields, evaluation custom data
fields, and user-defined data fields.

NOTE Only custom data fields within the specified date range that have a value
will be retrieved by the discovery process. Fields with an empty, i.e., null
value, will not be displayed by the Custom Data Migration Mapper.

Rediscovery of the Quality Monitoring Fields

You have the option to rediscover the Quality Monitoring fields at any time after having
performed the initial discovery. Rediscovery will update your existing attribute
definitions and mappings for the system. If new attributes are discovered, they will be
added. If previously discovered attributes are not found, they will be removed.
In addition, changing any of the Source Database Settings will require field rediscovery.

Define Quality Monitoring Attributes

Attribute definition for the Quality Monitoring fields is required after you have defined or
updated the Quality Monitoring database connection settings.
To define attributes for the Quality Monitoring system:
1 In the left pane’s tree view, select a previously defined Quality Monitoring system
that has not yet undergone attribute definition.
2 Click Next. The Select Navigation dialog displays.
3 Click Attribute Definition. The Attribute Definition Settings page displays.
4 Complete the Attribute Definition Settings, as described in “Quality Monitoring
Attribute Definition Settings” on page 90.

IMPORTANT It is strongly suggested that you leave the ending date of the date range
empty. Use of an empty ending date ensures you migrate all data after the
beginning date.

Custom Data Migration Mapper Guide 89

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Quality Monitoring Attribute Definition Settings

5 Click Save. The Custom Data Migration Mapper saves the attribute definition
settings.
Next Step: “Initiate Quality Monitoring Field Discovery” on page 93

Quality Monitoring Attribute Definition Settings

The following Quality Monitoring attribute definition settings are provided for each site:

Setting Description

General Settings Name Defines the name within the Custom Data
Migration Mapper that uniquely identifies the
Quality Monitoring attribute definitions. This
field is required.

Description Provide any text useful for identifying the

Quality Monitoring attribute definitions.

Migration Settings Migration Date Range Provide the beginning and ending date range
that determines the scope of the custom data
examined in the Quality Monitoring system and
the data to be migrated. A date range is
required.
The date range applies to contact custom data
fields and evaluation custom data (not user-
defined fields). All user data fields will be
migrated.
Date range applies to the GMT date for data.
TIP: To include all data after a date, provide
only a beginning date and leave the ending
date empty.

Custom Data Migration Mapper Guide 90

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Quality Monitoring Attribute Definition Settings

Setting(Continued) Description

Custom Contact Attributes After discovery has been completed, displays

the custom attribute types retrieved from
Enterprise Manager.
NOTE: The target system standard types are
not supported.
The attributes displayed are:
 Source Field: Name of the field in the
source database.
 Data Type: Type of data stored in the
field, e.g., string, integer, etc.
 Data Length: Field length for the data
sampled by the migration date range.
 Usage: Frequency of usage within the
data sampled by the migration date range.
 Target Attribute Type: Type of attribute
to which contact attribute corresponds
within the target system. For Quality
Monitoring, this field is always “Custom”.

Custom Data Migration Mapper Guide 91

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Show Quality Monitoring Contacts, Users or Evaluations

Setting(Continued) Description

User Defined Fields After discovery has been completed, displays

the user defined fields retrieved from the
source system.
The fields displayed are:
 Source Field: Name of the field in the
source database.
 Data Type: Type of data stored in the
field, e.g., string, integer, etc.
 Data Length: Field length for the data
sampled by the migration date range.
 Usage: Frequency of usage within the
data sampled by the migration date range.

Evaluation Attributes After discovery has been completed, displays

the evaluation attributes retrieved from the
source system.
The fields displayed are:
 Source Field: Name of the field in the
source database.
 Data Type: Type of data stored in the
field, e.g., string, integer, etc.
 Data Length: Field length for the data
sampled by the migration date range.
 Usage: Frequency of usage within the
data sampled by the migration date range.
 Target Attribute Type: Type of attribute
to which evaluation attribute corresponds
within the target system.

Show Quality Monitoring Contacts, Users or Evaluations

After defining your attributes, you have the ability to view the contacts, users, or
evaluations retrieved for the selected date range. Use this feature to see a sample of the
data retrieved using your attribute definition settings.
The Custom Data Migration Mapper uses the system-defined number of rows from the
source database for showing contacts, users, and evaluations. Refer to “Update System
Settings” on page 53 to learn more.
To show Quality Monitoring contacts, users, or evaluations:
1 Access a previously created attribute definition. See “Define Quality Monitoring
Attributes” on page 89 to learn more.
2 Click one of the following, depending on the type of data you wish to see:
 Show Contacts

Custom Data Migration Mapper Guide 92

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Initiate Quality Monitoring Field Discovery

 Show Users
 Show Evaluations
A pop-up window opens to provide you with a view of the contacts, users, or
evaluations retrieved from the system.
3 To close the window, click Done.

Initiate Quality Monitoring Field Discovery

After you have created the attribute definition, you are ready to initiate field discovery
for the Quality Monitoring system. Field discovery requires that the Custom Data
Migration Mapper connect with the Quality Monitoring system to inspect the custom data
fields for the date range specified by the attribute definition.

NOTE Field discovery can be a lengthy process, depending on the range of dates
requested. The Custom Data Migration Mapper page will update at regular
intervals during the discovery process.

To initiate field discovery:

1 Access a previously created attribute definition. See “Define Quality Monitoring
Attributes” on page 89 to learn more.
2 Click Discover Fields. The discovery process begins and the Attribute Definition
Settings page displays a dialog message indicating that discovery is in progress.
3 To close the dialog, click Close.
4 To change the refresh interval of the page, use the Refresh Rate drop-down list.
Click the refresh icon to update the page immediately.
When the discovery completes, the page will populate with the discovered fields.
Next Step: Map Quality Monitoring Contacts to the Target System, page 97, and
continue with the workflow process.

Custom Data Migration Mapper Guide 93

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Initiate Rediscovery of the Quality Monitoring Fields

Initiate Rediscovery of the Quality Monitoring

Fields
NOTE Rediscovery is an optional step.

Before attempting to rediscover the Quality Monitoring fields, it’s important that you
understand the impact of rediscovery, as discussed in “Rediscovery of the Quality
Monitoring Fields” on page 89.
You will typically need to rediscover the Quality Monitoring fields if you need to change
the Migration Date Range defined for the attribute definition.
Rediscovery is required if the Custom Data Migration Mapper detects that the mapping
has become stale. Refer to “Stale Mappings” on page 35 to learn more.
To rediscover the fields from a Quality Monitoring system:
1 Open the previously defined attribute definition. See “Define Quality Monitoring
Attributes” on page 89 to learn more. The Attribute Definition Settings page
displays.
2 Click Rediscover Fields. A warning dialog displays to notify you that rediscovery
will result in updates to the existing discovered fields as well as any associated
mappings.
3 If you wish to proceed with rediscovery, click OK. The Custom Data Migration
Mapper attempts to connect with the Quality Monitoring system for field
rediscovery.
4 To close the dialog, click Close.
5 To change the refresh interval of the page, use the Refresh Rate drop-down list.
Click the refresh icon to update the page immediately.
When the rediscovery completes, the page will populate with the rediscovered
fields.

Custom Data Migration Mapper Guide 94

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Remove a Quality Monitoring Attribute Definition

Remove a Quality Monitoring Attribute

Definition
Removing the attribute definition will discard any previously discovered Quality
Monitoring fields as well as all mappings associated with them. Ensure you are not
actively using the attribute definition before removing it.
To remove a Quality Monitoring attribute definition:
1 Open the previously defined attribute definition settings. See “Define Quality
Monitoring Attributes” on page 89 to learn more. The Attribute Definition Settings
page displays.
2 Click Delete. A confirmation dialog displays.
3 If you are certain you wish to remove the attribute definition, as well as all
associated mappings, click OK. The Custom Data Migration Mapper removes the
attribute definition from the system.

Custom Data Migration Mapper Guide 95

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Quality Monitoring Contact Mapping

Quality Monitoring Contact Mapping

After you have discovered the Quality Monitoring fields, you are ready to begin the
mapping process. Mapping requires that you select the target custom data field to which
each contact attribute will be migrated by the upgrade. In addition, you have the ability
to define the target caption you wish to use for each custom data field. The Custom Data
Migration Mapper will validate the mapping assignment to determine if the mapping is
valid and whether data loss may or may not potentially occur.
Depending on when the target system is installed, you can discover the target system
before or after you perform the mapping process. If the target system is not yet
installed, you will complete mapping manually and later synchronize your mapping with
the target system. This process was outlined in “Custom Data Migration Mapper
Workflows” on page 37.
If the target system has already been installed and configured, you can map to the
results of the target system discovery.
Before proceeding, you may find it useful to review the following overview topics:
 Field Status on page 32
 Field Captions on page 33

Default Contact Attribute Mapping Logic

When the Custom Data Migration Mapper suggests a default mapping for a contact
attribute, it uses the information available in the Source Attribute Definition to
determine the default mapping.
 Any source attribute not designated as a target type will not be available in the
target attribute mapping.
 Any source attribute designated as a custom target type will be assigned to a CD
field as follows:
a. The order of source fields is based on usage frequency. Source fields with the
highest frequency of use are mapped first.
b. The system attempts to use an available CD field with a corresponding data type
and data length. The smallest CD field that matches the source data will be
used.
c. If an available CD field is found, the source attribute will be mapped to the
matching CD field, and the caption of the CD field will be set to the name of the
source attribute field.
d. If a matching CD field is not found, the source attribute will not be mapped by
default. You can override the mapping definition to designate a mapping;
however, the system will never suggest a mapping that is potentially invalid due
to a data type mismatch, potential data truncation, or a CD field that is already
in use elsewhere.

Custom Data Migration Mapper Guide 96

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Map Quality Monitoring Contacts to the Target System

Map Quality Monitoring Contacts to the Target System

To map source contact attributes to the target system:
1 Access a previously created attribute definition. See “Define Quality Monitoring
Attributes” on page 89 to learn more. The Attribute Definition Settings page
displays.
2 Select a Target Attribute Type from the drop-down list for one of the source
attributes and then click Save.
3 Click Next. The Select Navigation dialog displays.
4 Click Contact Mapping. The Contact Mapping Settings page displays.

TIP Depending on your screen resolution, you may find it helpful to minimize
the left pane’s tree view, as shown above. You can minimize, maximize
and restore either pane by clicking the arrow buttons located between the
left and right panes.

5 Enter a unique Name for the contact mapping you are about to create. This field is
required.
6 To map a contact source field to a target CD Field, use the Target CD Field drop-
down list to select an available field.

IMPORTANT Mapping the source attribute Contact Name is optional. However, for
future audio replay capability from the source system, the Contact Name
must be mapped.
If you do map it to a custom data field, then users in the target system
will be able to search and replay the contact in the source system by
contact name from within an evaluation.
If contact name is not mapped, then the contact search will have to be
initiated in the target system using other attributes, such as Start Time,
End Time, etc.

 You can only map a source field to a target field once within a single mapping.
 When you select a target CD Field, the Custom Data Migration Mapper
immediately validates your selection and updates the status icon. Refer to “Field
Status” on page 32 to learn about the icon symbols.
 Refer to “Migration Attributes” on page 26 to learn about the fields available to
you.
7 To change the caption for a target CD Field, update the Caption field. Note that
captions must be unique.
8 To exempt the source field from mapping altogether, select None in the Target
ECD Field drop-down list.
9 When you are satisfied with the contact mapping you have created, click Save. The
contact mapping is saved. Any changes to captions that make the current mapping
the owner of a custom data field will lock the custom data field.

Custom Data Migration Mapper Guide 97

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Unlock Quality Monitoring Contact Attributes In Use

Validation is performed on the current mapping. You will be warned in the status
column if any of the following issues exist:
 Mappings to custom data fields that are already in use, either in the target
system or in another mapping for the current mapping project.
 Duplicate captions owned by the current mapping project. Captions must be
unique.
Next Step: “Map Quality Monitoring User-Defined Fields to the Target System” on
page 100

Unlock Quality Monitoring Contact Attributes In Use

As discussed in “Locked (In Use) Fields” on page 34, you have the ability to unlock a
target field that is already in use in order to edit its caption. When you unlock a field, the
current mapping will then “own” the mapping to that field and you are free to edit its
caption.
Exercise caution when unlocking a mapped field. Doing so may invalidate another
mapping by overriding the meaning of the data stored in the field by the other mapping.
Ensure you fully understand the migration consequences of unlocking a field.
To unlock a contact attribute:
1 Open a previously created contact attribute mapping. See “Map Quality Monitoring
Contacts to the Target System” on page 97 to learn more. The Contact Mapping
Settings page displays.
2 Identify a locked field you wish to unlock, and then click its lock icon. The Custom
Data Migration Mapper displays a confirmation dialog to ensure that you understand
the effects of unlocking a field.
3 If you are sure you wish to unlock the field, click OK. The field is unlocked, its lock
icon disappears, and the current mapping becomes the owner of the caption
definition.
4 Edit the Caption as required.
5 To save your changes, click Save.

Preview Quality Monitoring Contact Mapping

At any point during the process of mapping contacts to the target system, you have the
ability to preview the current mapping configuration using a subset of the source data.
Previewing provides you with the ability to check the current mapping against actual
data to see the results of the mapping during migration.

IMPORTANT For the initial Quality Monitoring mapping preview, you must have the
ability to connect with the Quality Monitoring system. The preview is not
available initially when you are working offline. After having performed an
online preview, you can make subsequent previews while working offline.

Custom Data Migration Mapper Guide 98

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Remove a Quality Monitoring Contact Mapping

Contact mapping uses the system-defined number of rows from the source database for
mapping previews. Refer to “Update System Settings” on page 53 to learn more.
To preview contact mapping:
1 Open a previously created contact mapping. Refer to “Map Quality Monitoring
Contacts to the Target System” on page 97 to learn more.
2 Click Preview Contacts. If this is the first preview you have requested for this
mapping, the system displays the requested number of rows from the database.
If this is not the first attempt to preview contacts, a dialog displays that enables you
to select the type of contact preview you wish to see.
 Select Live Data if you have the ability to connect with the Quality Monitoring
system and wish to view contacts retrieved from the live system.
 Select Stored Data if you cannot connect to the Quality Monitoring system or if
you wish to view a previously retrieved set of contacts.
Next Step: “Preview Quality Monitoring User-Defined Field Mapping” on page 101

Remove a Quality Monitoring Contact Mapping

Removing the contact mapping will discard any previously defined mappings. Ensure
you are not actively using the mapping before removing it.
When you remove a mapping, the system will revert ownership of any custom data
fields currently owned by the mapping to the previous owner, if it exists.
To remove a Quality Monitoring contact mapping:
1 Open the previously defined contact mapping. See “Map Quality Monitoring
Contacts to the Target System” on page 97 to learn more. The Contact Mapping
Settings page displays.
2 Click Delete. A confirmation dialog displays.
3 If you are certain you wish to remove the mapping, click OK. The Custom Data
Migration Mapper removes the mapping from the system.

Custom Data Migration Mapper Guide 99

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Quality Monitoring User-Defined Field Mapping

Quality Monitoring User-Defined Field

Mapping
After you have mapped the Quality Monitoring contact fields, you are ready to begin the
mapping process for user-defined fields. Mapping requires that you select the target
user data field to which each source user-defined field will be migrated by the upgrade.
In addition, you have the ability to define the target caption you wish to use for each
user data field. The Custom Data Migration Mapper will validate the mapping assignment
to determine if the mapping is valid and whether data loss may or may not potentially
occur.
Depending on when the target system is installed, you can discover the target system
before or after you perform the mapping process. If the target system is not yet
installed, you will complete mapping manually and later synchronize your mapping with
the target system. This process was outlined in “Custom Data Migration Mapper
Overview” on page 10.
If the target system has already been installed and configured, you can map to the
results of the target system discovery.
Before proceeding, you may find it useful to review the following overview topics:
 Field Status on page 32
 Field Captions on page 33
 Locked (In Use) Fields on page 34

Map Quality Monitoring User-Defined Fields to the

Target System
To map source user-defined fields to the target system:
1 Access a previously created contact mapping. See “Map Quality Monitoring Contacts
to the Target System” on page 97 to learn more. The Contact Mapping Settings
page displays.
2 Click Next. The Select Navigation dialog displays.
3 Click User Mappings. The User Mapping Settings page displays.

TIP Depending on your screen resolution, you may find it helpful to minimize
the left pane’s tree view, as shown above. You can minimize, maximize
and restore either pane by clicking the arrow buttons located between the
left and right panes.

4 Enter a unique Name for the user-defined field mapping you are about to create.
This field is required.
5 To map a user-defined source field to a target user defined field, use the Target
User Defined Field drop-down list to select an available field.

Custom Data Migration Mapper Guide 100

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Unlock User-Defined Fields in Use

 When you select a target User Defined Field, the Custom Data Migration Mapper
immediately validates your selection and updates the status icon. Refer to “Field
Status” on page 32 to learn about the icon symbols.
 Refer to “Migration Attributes” on page 26 to learn about the fields available to
you.
6 To change the caption for a target User Defined Field, update the Caption field.
7 To exempt the source field from mapping altogether, select None in the Target
User Defined Field drop-down list.
8 When you are satisfied with the user-defined mapping you have created, click Save.
The user-defined mapping is saved.
Next Step: “Map Quality Monitoring Evaluation Attributes to the Target System” on
page 104

Unlock User-Defined Fields in Use

As discussed in “Locked (In Use) Fields” on page 34, you have the ability to unlock a
target field that is already in use in order to edit its caption. When you unlock a field, the
current mapping will then “own” the mapping to that field and you are free to edit its
caption.
Exercise caution when unlocking a mapped field. Doing so may invalidate another
mapping by overriding the meaning of the data stored in the field by the other mapping.
Ensure you fully understand the migration consequences of unlocking a field.
To unlock a user-defined field:
1 Open a previously created user-defined mapping. See “Map Quality Monitoring
User-Defined Fields to the Target System” on page 100 to learn more. The User
Defined Field Mapping Settings page displays.
2 Identify a locked field you wish to unlock, and then click its lock icon. The Custom
Data Migration Mapper displays a confirmation dialog to ensure that you understand
the effects of unlocking a field.
3 If you are sure you wish to unlock the field, click OK. The field is unlocked, its lock
icon disappears, and the current mapping becomes the owner of the caption
definition.
4 Edit the Caption as required.
5 To save your changes, click Save.

Preview Quality Monitoring User-Defined Field Mapping

At any point during the process of mapping user defined fields to the target system, you
have the ability to preview the current mapping configuration using a subset of the
source data. Previewing provides you with the ability to check the current mapping
against actual data to see the results of the mapping during migration.

Custom Data Migration Mapper Guide 101

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Remove a Quality Monitoring User-Defined Field Mapping

IMPORTANT For the initial Quality Monitoring mapping preview, you must have the
ability to connect with the Quality Monitoring system. The preview is not
available initially when you are working offline. After having performed an
online preview, you can make subsequent previews while working offline.

User defined field mapping uses the system-defined number of rows from the source
database for mapping previews. Refer to “Update System Settings” on page 53 to learn
more.
To preview user defined field mapping:
1 Open a previously created user defined mapping. Refer to “Map Quality Monitoring
User-Defined Fields to the Target System” on page 100 to learn more. The User
Defined Field Mapping Settings page displays.
2 Click Preview Users. If this is the first preview you have requested for this
mapping, the system displays the requested number of rows from the database.
If this is not the first attempt to preview users, a dialog displays that enables you to
select the type of user preview you wish to see.
 Select Live Data if you have the ability to connect with the Quality Monitoring
system and wish to view users retrieved from the live system.
 Select Stored Data if you cannot connect to the Quality Monitoring system or if
you wish to view a previously retrieved set of users.
Next Step: “Preview Quality Monitoring Evaluation Attribute Mapping” on page 106

Remove a Quality Monitoring User-Defined Field

Mapping
Removing the user-defined field mapping will discard any previously defined mappings.
Ensure you are not actively using the mapping before removing it.
To remove a Quality Monitoring user-defined field mapping:
1 Open a previously created user defined mapping. Refer to “Map Quality Monitoring
User-Defined Fields to the Target System” on page 100 to learn more. The User
Defined Field Mapping Settings page displays.
2 Click Delete. A confirmation dialog displays.
3 If you are certain you wish to remove the mapping, click OK. The Custom Data
Migration Mapper removes the mapping from the system.

Custom Data Migration Mapper Guide 102

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Quality Monitoring Evaluation Attribute Mapping

Quality Monitoring Evaluation Attribute

Mapping
After you have mapped the Quality Monitoring user-defined fields, you are ready to
begin the mapping process for evaluation custom data. Mapping requires that you select
the target evaluation custom data field to which each source evaluation attribute will be
migrated by the upgrade. In addition, you have the ability to define the target caption
you wish to use for each evaluation custom data field. The Custom Data Migration
Mapper will validate the mapping assignment to determine if the mapping is valid and
whether data loss may or may not potentially occur.
Depending on when the target system is installed, you can discover the target system
before or after you perform the mapping process. If the target system is not yet
installed, you will complete mapping manually and later synchronize your mapping with
the target system. This process was outlined in “Custom Data Migration Mapper
Overview” on page 10.
If the target system has already been installed and configured, you can map to the
results of the target system discovery.
Before proceeding, you may find it useful to review the following overview topics:
 Field Status on page 32
 Field Captions on page 33
 Locked (In Use) Fields on page 34

Default Evaluation Attribute Mapping

When the Custom Data Migration Mapper suggests a default mapping for an evaluation
attribute, it uses the information available in the Source Attribute Definition, Contact
Attribute Mapping, and UDF Mapping result to calculate the default mapping as follows:
 Mapping is prioritized based on:
- Classification
- Agent/user attribute

Custom Data Migration Mapper Guide 103

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Default Captions

- Contact attribute

Source Suggested Mapping

Evaluation attribute If a source field is designated as an Attribute Type, and

type (not Custom) the Attribute Type is not Custom, it will be mapped to
the same ECD if that ECD has been used in other
mappings for a source of the same Attribute Type.
NOTE:
 If a source field is Contact Custom Attribute, then
its Attribute Type is the target system CD that the
source field is mapped to in Contract Attribute
Mapping.
 If a source field is UDF, then its Attribute Type is
the target system UDF that the source field is
mapped to in UDF mapping.
 If a source field is Contact Custom Attribute or
UDF, but it is not mapped to target system CD or
target system UDF, then its Attribute Type is blank.

Other source To the next available ECD.

attributes

Default Captions
 Source field of UDF: caption of the ECD will be the caption of the target system
UDF.
 Source field of Contact Custom Attribute: caption of the ECD will be the caption
of the target system CD.
 Other ECDs: caption of the source attribute.

Map Quality Monitoring Evaluation Attributes to the

Target System
To map source evaluation attributes to the target system:
1 Access a previously created user-defined field mapping. See “Map Quality
Monitoring User-Defined Fields to the Target System” on page 100 to learn more.
The User Defined Field Mapping Settings page displays.
2 Click Next. The Select Navigation dialog displays.
3 Click Evaluation Mappings. The Evaluation Mapping Settings page displays.

Custom Data Migration Mapper Guide 104

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Unlock Evaluation Custom Data Fields In Use

TIP Depending on your screen resolution, you may find it helpful to minimize
the left pane’s tree view, as shown above. You can minimize, maximize
and restore either pane by clicking the arrow buttons located between the
left and right panes.

4 Enter a unique Name for the evaluation attribute mapping you are about to create.
This field is required.
5 To map a source evaluation attribute to a target evaluation custom data field, use
the Target ECD Field drop-down list to select an available field.
 When you select a target ECD Field, the Custom Data Migration Mapper
immediately validates your selection and updates the status icon. Refer to “Field
Status” on page 32 to learn about the icon symbols.
 Refer to “Migration Attributes” on page 26 to learn about the fields available to
you.
6 To change the caption for a target ECD Field, update the Caption field.
7 To exempt the source field from mapping altogether, select None in the Target
ECD Field drop-down list.
8 When you are satisfied with the Evaluation mapping you have created, click Save.
The Evaluation mapping is saved.
Next Step: Return to the “Primary Migration Process Workflow” on page 38 and
continue with the workflow process.

Unlock Evaluation Custom Data Fields In Use

As discussed in “Locked (In Use) Fields” on page 34, you have the ability to unlock a
target field that is already in use in order to edit its caption. When you unlock a field, the
current mapping will then “own” the mapping to that field and you are free to edit its
caption.
Exercise caution when unlocking a mapped field. Doing so may invalidate another
mapping by overriding the meaning of the data stored in the field by the other mapping.
Ensure you fully understand the migration consequences of unlocking a field.
To unlock an evaluation custom data field:
1 Open a previously created evaluation attribute mapping. See “Map Quality
Monitoring Evaluation Attributes to the Target System” on page 104 to learn more.
The evaluation Attribute Mapping Settings page displays.
2 Identify a locked field you wish to unlock, and then click its lock icon. The Custom
Data Migration Mapper displays a confirmation dialog to ensure that you understand
the effects of unlocking a field.
3 If you are sure you wish to unlock the field, click OK. The field is unlocked, its lock
icon disappears, and the current mapping becomes the owner of the caption
definition.
4 Edit the Caption as required.
5 To save your changes, click Save.

Custom Data Migration Mapper Guide 105

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Preview Quality Monitoring Evaluation Attribute Mapping

Preview Quality Monitoring Evaluation Attribute

Mapping
At any point during the process of mapping evaluation attributes to the target system,
you have the ability to preview the current mapping configuration using a subset of the
source data. Previewing provides you with the ability to check the current mapping
against actual data to see the results of the mapping during migration.

IMPORTANT For the initial Quality Monitoring mapping preview, you must have the
ability to connect with the Quality Monitoring system. The preview is not
available initially when you are working offline. After having performed an
online preview, you can make subsequent previews while working offline.

Evaluation attribute mapping uses the system-defined number of rows from the source
database for mapping previews. Refer to “Update System Settings” on page 53 to learn
more.
To preview evaluation attribute mapping:
1 Open a previously created evaluation attribute mapping. Refer to “Map Quality
Monitoring Evaluation Attributes to the Target System” on page 104 to learn more.
The Evaluation Attribute Mapping Settings page displays.
2 Click Preview Evaluations. If this is the first preview you have requested for this
mapping, the system displays the requested number of rows from the database.
If this is not the first attempt to preview evaluations, a dialog displays that enables
you to select the type of evaluation preview you wish to see.
 Select Live Data if you have the ability to connect with the Quality Monitoring
system and wish to view evaluations retrieved from the live system.
 Select Stored Data if you cannot connect to the Quality Monitoring system or if
you wish to view a previously retrieved set of evaluations.
Next Step: Return to the “Primary Migration Process Workflow” on page 38 and
continue with the workflow process.

Remove a Quality Monitoring Evaluation Attribute

Mapping
Removing the evaluation attribute mapping will discard any previously defined
mappings. Ensure you are not actively using the mapping before removing it.
To remove a Quality Monitoring evaluation attribute mapping:
1 Open a previously created evaluation attribute mapping. Refer to “Map Quality
Monitoring Evaluation Attributes to the Target System” on page 104 to learn more.
The Evaluation Attribute Mapping Settings page displays.
2 Click Delete. A confirmation dialog displays.

Custom Data Migration Mapper Guide 106

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 7 - Working with a Quality Monitoring System Remove a Quality Monitoring Evaluation Attribute Mapping

3 If you are certain you wish to remove the mapping, click OK. The Custom Data
Migration Mapper removes the mapping from the system.

Custom Data Migration Mapper Guide 107

Confidential and Proprietary Information of Verint Systems, Inc.

 Chapter 8

Discovering a Target System

System discovery refers to the process of connecting to an existing system to examine

the visible custom data fields and to determine how the custom data fields are used.
Note that:
 Since the target system may not have been installed yet, system discovery of the
target system is not required before mapping source systems.
 System discovery of the target system is required when you have already allocated
the usage of one or more custom data fields in the target system or you have
previously migrated data from a source system.
At some point in the workflow for the Custom Data Migration Mapper, you must discover
the target system. Refer to “Custom Data Migration Mapper Workflows” on page 37 to
learn more.

IMPORTANT Before attempting to discover a target system, your target system Data
Center server must be installed, configured, and running. Refer to the
Enterprise Suite Installation Guide to learn about performing the
installation.

Topics:
 Configure Target System Connection Settings on page 109
 Field Discovery for the Target System on page 113
 Discovery Rules for Existing Mappings on page 114
 Initiate Rediscovery of the Target System on page 118
 Remove a Discovered Target System on page 119
 Configure SSL Communication with the Target System on page 120
Chapter 8 - Discovering a Target System Configure Target System Connection Settings

Configure Target System Connection

Settings
The target system connection settings define how the Custom Data Migration Mapper
will connect with the target system. Connection settings include definition of SSL
protocol, host name for the web service, communication ports on the target system, etc.
To configure the target system connection settings:
1 Launch the Custom Data Migration Mapper.
2 Open the project where you want the target system to reside in the Custom Data
Migration Mapper, as discussed in “Open a Project” on page 56. The Project Settings
page displays.
3 Click Next. The Select Navigation dialog displays.

4 Select Discover Target System. The Target System Settings page displays.
5 Complete the Target System Settings, as described in “Target System Settings” on
page 110.
6 Click Save. The Custom Data Migration Mapper saves the connection settings and
attempts to connect to the target system for field discovery.

NOTE If multiple languages are configured, the Custom Data Migration Mapper
will present to you the available languages. You must select a language to
use for the custom data field captions. You cannot use multiple languages
for the field captions. This is the same language that will be used during
data migration.

After a successful connection, a confirmation message displays indicating success.

If you are unable to connect, check your connection settings and the availability of
the target system.

Next Step: Return to the “Primary Migration Process Workflow” on page 38 and
continue with the workflow process.

Custom Data Migration Mapper Guide 109

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Target System Settings

Target System Settings

The following Target System Settings are provided for each target system:

Setting Description

General Settings Name Defines the name within the Custom Data
Migration Mapper that uniquely identifies the
target system. This field is required.

Description Provide any text useful for identifying the

target system.

SSL Configuration Enabled Select if Secure Sockets Layer (SSL)

encryption is used to communicate with the
target system.
NOTE: To use SSL, you must import the root
certificate from the target system server as a
trusted certificate in the Java Virtual Machine
(JVM) hosting the Custom Data Migration
Mapper. See “Configure SSL Communication
with the Target System” on page 120 to
complete this procedure.

Target Custom CD Caption Language* Displays the selected language for the custom
Data Settings data captions. If only one language is in use in
the target system, this field is display only.

Web Service Host* Provide the host name or the IP address for
the target web service. This field is required.
Changing this field will require rediscovery.

CD Web Service Port* Provide the port on which the web service
listens for HTTP requests. This field is required.
Changing this field will require rediscovery.

CD Web Service SSL Port* Provide the port on which the web service
listens for HTTPS requests. This field is
required. Changing this field will require
rediscovery.

Security Token Pass Phrase Provide the pass phrase configured in the
target Enterprise Manager.
If set, the Custom Data Migration Mapper will
generate an advanced security token used
when communicating with the target web
services.

Custom Data Migration Mapper Guide 110

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Target System Settings

Setting(Continued) Description

Target Enterprise EM Web Service Port* Provide the port on which the Enterprise
Manager Settings Manager listens for HTTP requests. This field is
required. Changing this field will require
rediscovery.
Default: 80
Note: For 11.2.0 HF1 and earlier, use port
7001.

EM Web Service SSL Port* Provide the port on which the Enterprise
Manager listens for HTTPS requests. This field
is required. Changing this field will require
rediscovery.
Default: 443
Note: For 11.2.0 HF1 and earlier, use port
7002.

Discovered Custom Data Fields Displays the set of custom data fields
discovered in the target system. For each field,
the page displays:
 Field.
 Data Type (string, integer).
 Caption.
 Status. See “Locked (In Use) Fields” on
page 34 to learn more.
 Owner. Identifies the mapping that
currently controls the field.

Discovered Evaluation Data Fields Displays the set of evaluation data fields
discovered in the target system. For each field,
the page displays:
 Field.
 Control Type.
 Data type (string, integer).
 Caption.
 Status. See “Locked (In Use) Fields” on
page 34 to learn more.
 Owner. Identifies the mapping that
currently controls the field.

Custom Data Migration Mapper Guide 111

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Target System Settings

Setting(Continued) Description

Discovered User Data Fields Displays the set of user data fields discovered
in the target system. For each field, the page
displays:
 Field.
 Data Type (string, integer).
 Caption.
 Status. See “Locked (In Use) Fields” on
page 34 to learn more.
 Owner. Identifies the mapping that
currently controls the field.

* Changing the value of these fields for an already discovered target system will require
that you rediscover the target system custom data fields. See “Field Discovery for the
Target System” on page 113 to learn more about rediscovery.

Custom Data Migration Mapper Guide 112

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Field Discovery for the Target System

Field Discovery for the Target System

When you save your target system connection settings for the first time, the Custom
Data Migration Mapper will automatically initiate system discovery. During system
discovery the tool will:
 Attempt to connect with the target system.
 Determine the languages used for field captions.
 Retrieve the metadata for custom data fields, evaluation data fields, and user data
fields.

CAUTION During discovery of the target system, the Custom Data Migration Mapper
does not access captions for custom data fields and evaluation custom
data fields modified by the Form Designer application. Refer to “Edited
Captions for Custom Data Fields and Evaluation Custom Data Fields” on
page 24 to learn more.

WARNING When performing discovery on a target system for a project where

mappings already exist in the Custom Data Migration Mapper, existing
mappings may be changed to an invalid state. For example, if a custom
data caption in the target system does not match the caption in the
Custom Data Migration Mapper, the mapping may be considered invalid.
When this happens, the mapping is replaced with “None” and the mapping
will be marked as stale; you must then visit each stale mapping and make
corrections as needed. Refer to “Discovery Rules for Custom Data Fields”
on page 114 to learn more.

About Rediscovery of the Target System

You have the option to rediscover the target system at any time after having performed
the initial discovery. However, rediscovery requires that target attribute mappings based
on the target system be removed, requiring that you start the mapping process over
again. Use caution when initiating rediscovery of the target system.
In addition, changing any of the following target connection settings will require that the
system automatically initiate rediscovery after you change a value and click the Save
button:
 CD Caption Language
 Target system Web Service Host
 CD Web Service Port
 CD Web Service SSL Port
 EM Web Service Port
 EM Web Service SSL Port

Custom Data Migration Mapper Guide 113

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Discovery Rules for Existing Mappings

Discovery Rules for Existing Mappings

Whether you are performing discovery of the target system for the first time or initiating
rediscovery of the target system, during discovery the Custom Data Migration Mapper
considers any existing mappings that exist in the project and updates the mappings, if
necessary.
The updates to the mappings may result in the mapping being considered stale. Refer to
“Stale Mappings” on page 35 to learn more.
If a mapping is stale and your action is required, a notification message will display
identifying which mappings require your attention. In addition, the message will always
display when you select a project in the tree view. You will not be able to generate
migration files until all stale mappings have been resolved.
Depending on the updates made to the mappings by the Custom Data Migration Mapper,
you may be required to make adjustments to your mappings. If your action is required
to rectify the mappings, you will be notified.
Refer to the following topics to learn about how updates are applied:
 Discovery Rules for Custom Data Fields on page 114
 Discovery Rules for Evaluation Custom Data and User-Defined Fields on page 116

Discovery Rules for Custom Data Fields

For custom data fields, three conditions considered together determine what updates
the Custom Data Migration Mapper may make to the mapping. It’s important to
understand that these conditions must be considered as a whole and not in isolation.
The three conditions are:
 Does the caption defined in the Custom Data Migration Mapper match the caption
from the target system?
 Is the custom data attribute type set to Custom in Custom Data Migration Mapper?
 Does an attribute exist in the Enterprise Manager with the same name as the
caption?
The union of these conditions determines how the Custom Data Migration Mapper will
update the mapping for a particular field.
In the event that the field discovered from the target system is in an unlocked state, no
action will be taken by the Custom Data Migration Mapper on the field in the mapping.
The field ownership and the caption will remain unchanged.

Custom Data Migration Mapper Guide 114

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Discovery Rules for Custom Data Fields

For each custom data field locked by the target system in an existing mapping, the
following rules will applied:

Discovered Attribute Discovered Action taken by Custom Data

Caption type is attribute Migration Mapper
matches Custom? has same
Caption? name as
Caption?

Yes Yes Yes  Target system is set as the owner of

the custom data field, if not already
 Attribute type is updated with
Enterprise Manager attribute type
 Mapping is unchanged

Scenario: Target system has been

configured correctly according to what was
previously planned in Custom Data
Migration Mapper

Yes Yes No  Target system is set as the owner of

the custom data field, if not already
 Attribute type is left unchanged
 Existing mapping for field is
considered invalid and set to “None”.
 Mapping is considered stale
 You must update the mapping

Scenario: Target system has not been

configured correctly according to what was
planned in Custom Data Migration Mapper
Reason: Custom data field does not have
corresponding attribute in Enterprise
Manager

Yes No No  Target system is set as the owner of

the custom data field, if not already

Scenario: Custom data field is not of type

Custom, therefore no change is required.

Custom Data Migration Mapper Guide 115

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Discovery Rules for Evaluation Custom Data and User-Defined Fields

Discovered Attribute Discovered Action taken by Custom Data

Caption type is attribute Migration Mapper
matches Custom? has same
Caption?(C name as
ontinued) Caption?

No No No  Target system is set as the owner of

the custom data field, if not already
 Attribute type is left unchanged
 Existing mapping for field is
considered invalid and set to “None”.
 Mapping is considered stale
 You must update the mapping

Scenario: Target system has not been

configured correctly according to what was
planned in Custom Data Migration Mapper
Reason:
 Caption does not match
 Custom data field does not have
corresponding attribute in Enterprise
Manager

Discovery Rules for Evaluation Custom Data and User-

Defined Fields
In the event that the field discovered from the target system is in an unlocked state, no
action will be taken by the Custom Data Migration Mapper on the field in the mapping.
The field ownership and the caption will remain unchanged.
For each evaluation custom data field and user-defined field locked by the target system
in an existing mapping, the following rules will applied:

Discovered Action taken by Custom Data Migration Mapper

Caption
matches
Caption?

Yes  Target system is set as the owner of the custom data field, if not
already
 Mapping is unchanged

Scenario: Target system has been configured correctly according to

what was previously planned in Custom Data Migration Mapper

Custom Data Migration Mapper Guide 116

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Discovery Rules for Evaluation Custom Data and User-Defined Fields

Discovered Action taken by Custom Data Migration Mapper

Caption
matches
Caption?

No  Target system is set as the owner of the custom data field, if not
already
 Existing mapping for field is invalid
 Mapping is considered stale
 You must update the mapping

Target system has not been configured correctly according to what was
planned in Custom Data Migration Mapper
Reason:
 Caption does not match

Custom Data Migration Mapper Guide 117

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Initiate Rediscovery of the Target System

Initiate Rediscovery of the Target System

Before attempting to rediscover the target system, it’s important that you understand
the impact of rediscovery, as discussed in “About Rediscovery of the Target System” on
page 113.
Rediscovery is required if the Custom Data Migration Mapper detects that the mapping
with which the target system is associated has become stale. Refer to “Stale Mappings”
on page 35 to learn more.
To rediscover a target system:
1 Launch the Custom Data Migration Mapper.
2 In the left pane’s tree view, select the previously discovered target system. The
System Settings page for the target system displays.

3 Click Rediscover. A confirmation dialog displays that explains the consequences of

performing a rediscovery, as explained in “Field Discovery for the Target System” on
page 113.
4 If you wish to proceed with rediscovery, click OK. The system deletes any current
target attribute mappings and begins the same discovery process explained in
“Configure Target System Connection Settings” on page 109.

Custom Data Migration Mapper Guide 118

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Remove a Discovered Target System

Remove a Discovered Target System

Removing a previously discovered target system will delete all attribute definitions and
mappings associated with it. Ensure you are not actively using the target attributes
before removing a discovered target system.
To remove a discovered target system:
1 Launch the Custom Data Migration Mapper.
2 In the left pane’s tree view, select the previously discovered target system. The
System Settings page for the target system displays.

3 Click Delete. A confirmation dialog displays that explains the consequences of

deleting the target system.
4 If you wish to proceed with the removal, click OK. The system deletes all attribute
definitions and mappings associated with the target system.

Custom Data Migration Mapper Guide 119

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Configure SSL Communication with the Target System

Configure SSL Communication with the

Target System
If you have enabled SSL (Secure Sockets Layer) communications between the target
system and the Custom Data Migration Mapper, you must import the root certificate
from the target system server as a trusted certificate in the Java Virtual Machine (JVM)
hosting the Custom Data Migration Mapper. Use the procedures in this section to fully
configure SSL communications.

Export the Root CA certificate

NOTE Perform this procedure on your target system application server (in other
words, the server for which the certificate was issued).

1 In Windows click Start > Run.

The Run dialog box is displayed.
2 In the Open field, type mmc and click OK.
The Microsoft Management Console is displayed. In the navigation tree on the left
side you should see Certificates under Console Root. If you do not, the certificate
has not been installed on the server. You must run this procedure on a server where
a certificate has been previously installed.
If SSL communication has not been previously configured, you cannot use SSL
communication until you have configured it. Consult the Security Configuration
Guide to learn how to configure SSL.
3 Expand the Trusted Root Certification Authorities node.
4 Expand the Certificates folder.
5 In the list of certificates, locate the root CA certificate that you used to issue and
sign your target system server certificate.
6 Right-click the certificate.
7 Select All Tasks > Export.
The Certificate Export Wizard starts.
8 Click Next.
9 When prompted to select an export file format, select DER encoded binary x.509
(.CER).
10 Click Next.
11 On the next screen select a filename and location for the exported certificate, then
click Next.
12 Verify your settings, then click Finish to export the certificate.
You now have a .CER certificate file.

Custom Data Migration Mapper Guide 120

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 8 - Discovering a Target System Install the Certificate for Custom Data Migration Mapper

13 Copy the .CER file to the location of the Custom Data Migration Mapper installation.

Install the Certificate for Custom Data Migration

Mapper
To install the target system server root certificate as trusted in the JVM:
1 Ensure that the .CER certificate file you exported in “Export the Root CA certificate”
on page 120 has been copied to the location where you have installed the Custom
Data Migration Mapper.
2 Open a command prompt.
3 Navigate to your Custom Data Migration Mapper installation directory.
4 Navigate to the \conf folder of your Custom Data Migration Mapper installation.
5 You must install the certificate by entering the following command:
InstallCertificate.bat <certificate file name>
The certificate is installed.
6 Restart the “Custom Data Migration Mapper” service.

Custom Data Migration Mapper Guide 121

Confidential and Proprietary Information of Verint Systems, Inc.

 Chapter 9

Completing the Mapping

Process

When you have completed the mappings for Full-time Recording sites and Quality
Monitoring sites, you are ready to start the final step in the mapping process. At this
point, you should review and check your mapping projects for any invalid mappings.
After resolving any issues discovered you will be ready to generate the Custom Data
Migration Mapper output files, which will be used by the upgrade and migration process.

IMPORTANT You cannot complete the mapping process until you have first discovered
the target system. Discovery of the target system is a prerequisite to
complete the mapping process. Refer to “Discovering a Target System” on
page 108 to learn more.

Topics:
 Review Mapping Projects on page 123
 Generate Migration Files on page 125
Chapter 9 - Completing the Mapping Process Review Mapping Projects

Review Mapping Projects

You should perform a thorough review of the mapping for all systems within a project
before proceeding. A review should identify and resolve any invalid mappings, as well as
ensuring that all unmapped source attributes and unmapped target attributes are
intended to be omitted.
To assist you with the review process, use the project status tabs. The project status
tabs are fully discussed in “View Project Status” on page 58.

Custom Data Migration Mapper Guide 123

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 9 - Completing the Mapping Process Prerequisites to Completing the Mapping Process

Prerequisites to Completing the Mapping

Process
Before attempting to complete the mapping process, ensure you have met the following
prerequisites:
 You have discovered the target system for the project.
 You have resolved all stale mappings. You cannot proceed with finalization when you
have stale mappings. Refer to “Stale Mappings” on page 35 to learn more.
 You have defined, for each Quality Monitoring and Full-time Recording system in the
project, at least one target attribute mapping.

Custom Data Migration Mapper Guide 124

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 9 - Completing the Mapping Process Generate Migration Files

Generate Migration Files

After you have completed your review of the mappings for all systems within a project,
and you are satisfied that the mapping will result in a successful migration of the source
data, you are ready to generate the output files used by the migration process.
The migration file output consists of a compressed archive file (.zip) which contains the
XML data required for the actual migration. This archive file should be provided to the
upgrade and migration team for use in the upgrade process.
You must generate a separate archive file for each project. A single project may contain
multiple sites.
The archive file contains:
 Connection details to the source system and the target system.
 Mapping details for the target custom data, user-defined data, and evaluation
custom data definitions.
 A separate folder for each Full-time Recording and Quality Monitoring system
containing system-specific mapping details.
To generate the migration archive file:
1 Launch the Custom Data Migration Mapper.
2 Click the Migration Mapper tab at the top of the page. The Migration Projects page
displays.

3 In the left pane’s tree view, select the project for which you need to generate the
migration archive file.
4 Click Generate Files. The Custom Data Migration Mapper examines the project. If
any unmapped source or target attributes exist, they are displayed in a pop-up
window. Refer to “Unmapped Attributes Summary” on page 126 to learn more.
.

5 If you are satisfied with the unmapped attributes, click Generate Files. A file
download dialog opens.
6 Click Save, and then select the location on your file system where you wish to save
the generated archive file. The archive is saved.
Now that you have created the mapping file for the migration, you will use the
mapping file during the actual data migration process in conjunction with the Server
Readiness tool.
Refer to the following guides to learn more about using the mapping file with the
migration:
 Full-time Recording 7.x Upgrade and Migration
 Quality Monitoring 7.x Upgrade and Migration
Next Step: Return to the “Primary Migration Process Workflow” on page 38 and
continue with the workflow process.

Custom Data Migration Mapper Guide 125

Confidential and Proprietary Information of Verint Systems, Inc.

Chapter 9 - Completing the Mapping Process Unmapped Attributes Summary

Unmapped Attributes Summary

The following details are provided in the Unmapped Attributes Summary window. The
window displays when generating the mapping output files for a Custom Data Migration
Mapper project. The contents of the window provide you with a final chance to review all
unmapped attributes, both source and target, before output file creation.
NOTE Unmapped attributes will not be part of the migration.

Setting Description

Unmapped CD CD Field Name of the custom data field in the target

Attributes system to which nothing is mapped in your
project.

Data Type The data type for the target custom data field.

Unmapped ECD ECD Field Name of the evaluation custom data field in
Attributes the target system to which nothing is mapped
in your project.

Data Type The data type for the target evaluation custom
data field.

Unmapped UDF UDF Field Name of the user data field in the target
Attributes system to which nothing is mapped in your
project.

Data Type The data type for the target user-data field.

Unmapped Source System The source system from which the unmapped
Attributes attribute originates.

Attribute Definition The attribute definition in which the unmapped

attribute resides in the Custom Data Migration
Mapper project.

Type The type of data to which the attribute

corresponds. For example, User, Contact,
Evaluation, and so on.

Field Name The name of the source attribute field which is

not mapped.

Type The data type for the unmapped attribute. For

example, string, integer, and so on.

Length The longest data value found for the

unmapped field in the source system for the
migration date range.

Custom Data Migration Mapper Guide 126

Confidential and Proprietary Information of Verint Systems, Inc.

 Appendix A

Troubleshooting

This troubleshooting section provides you with tips and suggestions for commonly
encountered issues and solutions you might encounter when using the Custom Data
Migration Mapper application.
Appendix A - Troubleshooting Print from Your Project

Print from Your Project

In the course of create mappings for one or more projects, you will find it useful to print
out the current state of your mappings and attribute definitions.
Printing provides you with both a record of your project state as well as a visual aid for
planning additional mappings. You will find that printing is particularly useful for:
 Configuring attributes and custom data fields in Enterprise Manager
 Dealing with enterprise migrations, due to the complexity of the mapping decisions
you will be making.
To print your mappings or attribute definitions, you should use the print feature of the
Custom Data Migration Mapper. You will find the print icon in the top-most toolbar.

To print from the Custom Data Migration Mapper:

1 In the left navigational tree, select the entity that you need to print, such as an
attribute definition or a mapping.
2 Expand all items in the definition by using the arrow icons located in the section
headers. Any items that you cannot see when you start printing will not display on
the printed page.
3 When you are satisfied with the appearance of the items on the screen, click the
Print icon. The page content is sent to the printer.

Next Step: Return to the “Primary Migration Process Workflow” on page 38 and
continue with the workflow process.

Custom Data Migration Mapper Guide 128

Confidential and Proprietary Information of Verint Systems, Inc.

Verint Global Headquarters
330 South Service Road
Melville, NY 11747 USA

[email protected]
1-800-4VERINT

www.verint.com

© 2015 Verint Systems Inc.

All Rights Reserved Worldwide.
Confidential and Proprietary Information of Verint Systems Inc.

The contents of this material are confidential and proprietary to Verint Systems Inc.
and may not be reproduced, published, or disclosed to others without express
authorization of Verint Systems Inc.