Data Migration Overall Approach

Agenda

 1. Objectives
2. Scope
3. Approach
1. Project Initiation
2. Data Analysis & Design
3. Staging
4. Reconciliation
5. Migration Trial

4. Discontinuing of existing systems

5. Backup & Audit trail
6. Roles & Responsibilities
Simple objectives

This document will highlight the general strategy for

identifying, capturing and transferring data from existing
systems to Temenos T24.

The goal is to propose an approach for data migration so

that:
 the transition to T24 is achieved in a smooth and
accurate manner
 with minimal upheaval to the business
Agenda

1. Objectives

 2. Scope
3. Approach
1. Project Initiation
2. Data Analysis & Design
3. Staging
4. Reconciliation
5. Migration Trial

4. Discontinuing of existing systems

5. Backup & Audit trail
6. Roles & Responsibilities
A vast potential perimeter…

Data to be migrated can be categorized as following:

Static data – This is defined as reference data that rarely
changes once it is set up in the T24; typically Customer and
Account data falls into this category
Dynamic data – This is data that changes regularly (typically
everyday) mainly as a result of the processing of
transactions. (E.g. contract, account balance, …)
Historical data – The business requires access to historical
data for legal investigations and need to be able to back-
value accounting entries.

And impact potentially every Temenos T24

module
…that needs to be reduced

However historical data presents a major migration problem

and Temenos has consistently advised against taking on
historic accounting entries.
Likewise the following areas are considered out of scope
even if there are inter-dependencies with data migration:
– Parameterization
– Interfaces
– Go-live implementation plan
– Accounting reconciliation
– Discontinuing of existing systems
Agenda

1. Objectives
2. Scope

 3. Approach
1.
2.
Project Initiation
Data Analysis & Design
3. Staging
4. Reconciliation
5. Migration Trial

4. Discontinuing of existing systems

5. Backup & Audit trail
6. Roles & Responsibilities
 Data Migration in context

Sales

Initiation

Training

Analysis/Review

Build / Configuration
Procedures & System
Documentation

Core Development

Local Development

Functional Testing
User
Training
Data Migration
Conversion Conversion

UAT
Temenos Business

Client Technical

Joint Combined
Post live
 Data Migration – Detail (I)

Kick Off
Sub-Project Initiation
Meeting
Migration
Agreement (I)
Data Mapping Data Analysis and Design
Review
Migration
Agreement (II)

Build Staging

Cleansing
Extract Pre-Process
Functional Test
Cycle
Reconciliation Reconciliation
Approach
Plan

Migration

Temenos Business Freeze Agreement (III)

Client Technical Milestone

Joint Combined
 Data Migration – Detail (II)

Environment Migration Trial

Preparation
(untimed)
Execution
Analysis &
Anomalies
Environment Migration Dry Run
Preparation
Execution
Analysis &
Anomalies
Environment Go-Live Weekend
Preparation
Execution

Go-Live
Temenos Business

Client Technical

Joint Combined
Project Initiation

Planning and organizing, deals with the activities that set

the stage for successful delivery:

 Kick-off – an initial meeting with key client

personnel is held to introduce the key members of
the data migration team and their client
counterparts, present TEMENOS data migration
methodology;
 Migration Project Agreement (Part I) – Data
migration planning and organization is the process
of identifying what should be done, by whom and
when.
Data analysis and design

Discusses data migration delivery activities in the context of

a “traditional” data migration phase; the study of client’s
specific data migration issues, which are the prelude to a
successful Build stage:
 Data Mapping Tables (DMT) review – Once the product list
defined (in the previous task), a list of applications required
in the migration process can be completed. Based on the
dependencies of each application in T24 one or more DMT’s
will be completed;
 Migration Project Agreement (Part II) – during the Project
Initiation a first version of the “Migration Project Agreement”
has been delivered. It contains a work plan and schedule
that is to a level of detail sufficient to proceed with work. But
this work plan and schedule may not be useful as a project
planning and control tool when the times come to conduct
the data migration.
 Staging - Overview

Source 1

Upload Staging OFS T24

Database
Source 2

Staging Database goals

Source 3 1. Consolidate data 4. Generate records
Several sources can be used to fill one T24 table New records are automatically
2. Check data generated
Data are checked before upload in T24 (i.e. DE.PRODUCT for all customers)
(i.e. database integrity, presence of mandatory 5. Extract OFS file
Excel fields) One unique file generated, already
3. Update data cleaned and correct
Files Data can be updated with information provided in
Excel files
Staging 1/2

Implements and tests data migration tools:

 Build – The majority of the development in the Staging /

Working database will be the creation of relationships and
links between the various data tables provided by the bank
and T24. Other developments will relate to the changing of
field formats, e.g. currency amounts and date fields;

 Cleansing – Cleansing data is a Client activity, which

consists of two main parts: purging of old or inaccurate data;
adding of additional information to meet T24 mandatory
fields for take-on (enrichment);
Staging 2/2

Implements and tests data migration tools:

 Extract pre-processes – In the extraction sub-task the

client needs to identify the output method used to extract the
data from the existing system into a format that can be used
by the migration team to load into the Staging Database;

 Functional test cycle – In this section the T24 consultant

will use the data output from the Staging Database and the
tools available in T24 to load the data into the various
applications. Encountered errors are documented, analyzed
and decisions are to be made in conjunction with the client
as to how these errors are to be resolved.
Reconciliation 1/2

Aims to present the procedures necessary to ensure that

the integrity of the data is maintained when transferring it to
T24:
 Reconciliation approach – each product / business area is
examined individually to determine the most suitable
reconciliation method
– The data reconciliation strategy is based on some fundamental
principles concerning data ownership and data sign-off;
– Whilst a reconciliation team will be developed to employ the
procedures necessary to verify data, it will be a requirement of
each data owner to recommend the reconciliation methodology
and to sign off the converted data;
– These processes, roles and responsibilities will be documented
in the “Migration Project Agreement”.
Reconciliation 2/2

Aims to present the procedures necessary to ensure that

the integrity of the data is maintained when transferring it to
T24:

 Reconciliation plan – once the approach agreed,

a detailed reconciliation plan is build which will be
tested during the migration trials;

 Migration Project Agreement (Part III) – this

approach and reconciliation methods are built into
the Migration Project Agreement.
Migration Trial and Dry runs

Plans and conducts unit test of migration software and

reconciliation methods:

 Preparation – prepares the environment used to

perform a complete data upload;

 Execution – conducts the data migration system

test of dummy uploads;

 Post-execution analysis & anomalies report –

conducts Migration & Reconciliation / Audit
Agenda

1. Objectives
2. Scope
3. Approach
1. Project Initiation
2. Data Analysis & Design
3. Staging
4. Reconciliation
5. Migration Trial

 4. Discontinuing of existing systems

5. Backup & Audit trail
6. Roles & Responsibilities
Discontinuing of existing systems

Several tasks related to the legacy systems need to be

performed:
 Extract pre-processes – extract the data from the
existing system into a format that can be used by
the migration;
 Discontinuing – once T24 in production legacy
systems are partially or completely replaced:
 Partial reversal – data transferred to T24 need to be
reversed from the source system;
 Complete discontinuing – if the legacy system is
completely replaced then a discontinuing plan need to be
build (including backup for audit purposes).
Agenda

1. Objectives
2. Scope
3. Approach
1. Project Initiation
2. Data Analysis & Design
3. Staging
4. Reconciliation
5. Migration Trial

4. Discontinuing of existing systems

 5. Backup & Audit trail

6. Roles & Responsibilities
Backup & Audit trail 1/2 - Document processes

Audit department requires to be able to rebuild the

migration process and track every single steps. For this
purpose a backup strategy need to be set up including
the following topics:

 Document processes
– Data mapping & conversion algorithm – covered by
Data Mapping Tables (DMT) & Migration Project
Agreement;
– Reconciliation Strategy – covered by Migration Project
Agreement (Part III);
– Reconciliation reports – reports used during the
reconciliation process.
Backup & Audit trail 2/2 - Backup data

Data backup – conversion tools & source data need to be

backup:

 Staging database – contains data mapping and

automatic conversion routines;

 Manual input forms & reports – cover forms

used to document manual input and cleansing;

 Source systems – a complete backup need to be

taken before partial or complete discontinuing.
Agenda

1. Objectives
2. Scope
3. Approach
1. Project Initiation
2. Data Analysis & Design
3. Staging
4. Reconciliation
5. Migration Trial

4. Discontinuing of existing systems

5. Backup & Audit trail

 6. Roles & Responsibilities

 Roles and Responsibilities

Deliverables Temenos Client

Data Mapping Tables (DMT) Coordinator, provide T24 Provide Legacy Systems
knowledge knowledge

Build Develop Staging Database, Acceptance test of staging

data upload into T24, testing database and upload procedures

Legacy Systems Data Cleanup Provide Support Cleanse legacy systems

Manual Collection and input Provide Support Collect and enter data

Legacy Systems extraction Provide cleansing guidelines Develop extraction routines

System discontinuing Provide Support Discontinue systems

T24 reports Develop reports

Legacy Systems reports Develop reports

Reconciliation Provide Support Approve data upload