Securities Prototype 1

After completing this unit, you will be able to

Have an overview of Data migration Activities

Understand the various phases in Data Migration

Know the DM life cycle

Securities Prototype 2
Securities Prototype 3
 The DM activity is a target system based approach which means it is the T24
system and not the client system(CS).

The migration of the data from the Client system to T24 application and NOT
from Client System database to T24’s database.

There is a dedicated migration support team based at Chennai in Temenos

Application Management Services – TOFF DM team.

Standard migration guidelines based on the experience and know-how out of

repeated execution of the best practices.

The approach includes periodic need based onshore presence.

Support data migration from Client System to T24 and T24 to T24 (where
upgrade is not feasible)

Securities Prototype 4
The above picture shows the overall activities performed in Data Migration. It
depicts the activities in a phased manner.
 The initiation phase is the first phase which takes about 5% of the DM process.

Here the client needs to define the requirement for data migration.

The requirement analysis and effort estimate has to be calculated to arrive at a

DM approach and process.

The presentation on the migration approach, process , utilities & deliverables

would be delivered by TOFF DM team and would be explained in detail. Once
the approach and process are finalised, the process for data extraction and
cutover strategy needs to be designed.

Cutover Strategy document would be delivered initially and discussed further

in the workshops that involves the interaction with the client‘s business and IT
team to propose and get sign off of an approach for data migration, so that
transition from legacy system to T24 is achieved in a smooth and accurate
manner with minimal upheaval to the business

Securities Prototype 6
 After the extraction and cutover strategy design is over, the data migration
strategy involving business and technical has to be designed.

The DM cutover needs to be planned for migration area preparation, the data
for upload and reconciliation.

Initial workshops to be conducted to explain approach, process and agree on

the business, technical & cutover strategy to suit the client requirement

The sign off is called for the Approach, process and strategy plan which leads
to the next phase(Mapping Phase).

Securities Prototype 7
 The mapping phase is the second phase where in 30% of the data migration
work is involved.

The business unit mapping with t24 modules has to prepared with the module-
wise strategy document and the client. It should cover the Upload table list,
data comparison scope and the migration upload strategies for the client T24
release.

Based on the Upload table list and the upload and cutover strategy, the data
mapping sheet (DMS) is prepared. The DMS consists of sample data, helptext,
mandatory and conditional fields, post update tables, input able fields and their
field type and properties. The Data Mapping Definition(DMD) in T24 needs to
be configured with the help of the DMS.

The Data Extract Specification(DES) in T24 consists of Data Extract List and
strategy, T24 file and field names, Client system file and field names. This
helps in creating a mapped DES and a Data Extract Definition(DED) is
configured in T24. The DED worksheet is the base file used to get the
information on the fields to be extracted after the upload of data for checking
the correctness of the data uploaded / comparison between the client system
and T24 extract.

Securities Prototype 8
 A document is prepared and delivered to client known as DUT (T24 Data
Upload Test ) documentation. This is prepared in offshore with the clinical
data that reflects the strategy and fields in the Mapped DMS to verify the T24
DM upload tool component configuration.

Similarly a DET (T24 Data Extract Test) documentation is to explain the

process of T24 Data extract from T24 and the required output format based on
mapped DES.

The process of mapping is conducted based on workshops where in, the CS

Business Unit is mapped to T24 Module, the CS Source Tables is mapped to
T24 Target Tables and the Cs Source Table Fields is mapped to T24 Target
Table Fields.

Securities Prototype 9
 The process for data mapping of data extract and T24 upload from CS to T24
is decided.

The process for data comparison between legacy system and T24 using the
DES is decided.

Once the mapped DMS and DES worksheets are updated, the Mapping phase
is signed off.

Securities Prototype 10
 After the sign off of the mapping phase, the preparation phase is brought in to effect. It takes about 20% of the DM
process.

A client base environment is created where in the DM upload tool is configured and integrated as per the mapped
DMS.

Next the T24 extract tool is configured and integrated in to the environment based on the mapped DES.

The client need to validate client system data based on the definition given in the DMS and prepare for data
conversion & cleansing.

Converting CS data to suit T24 like Account number according to new T24 account number structure ,Product classifications
according to T24 categories based on TAABS.
Cleansing the CS data to suit T24 like 70 character address line into 35 * n number of lines in T24 ,Remove /
replace characters that are not acceptable in T24 based on the validation rule.

The Client has to prepare the extraction programs based on the DMS’s for extracting the data file.TOFF DM will handle this part if it
is T24 to T24 Migration.

Staging area to collate data from different client systems and prepare data file in the T24 acceptable format and
should contain the data structure as in T24. Data Cleansing and Data Conversion of the client system can also be done
in staging area. Build the T24 reference data within the data files (e.g. accounts to portfolios) which is a prerequisite.
Staging area is the base for creating final data file for T24 upload.

A sign off to the preparation phase is called after the DM tool and CS extract program are executed.

Securities Prototype 11
 The Testing phase is the fourth phase and takes 30% of process time in DM.

Test Upload consists of Dummy migrations where in the process is executed in

offshore with sample / clinical data and is re-run till error free execution of approach
& process. The milestone is reached when there is a Confirmation of defined
approach, process & strategy, Correctness of data file format, Successful test run leads
to Trial Migration.

The process in Trial Migration is Testing with limited scope with production data,
Review and rectification of errors, Re-run till error free extraction, loading and
reconciliation by Client,Trail migration is taken from offshore through remote
connectivity. The milestone is reached when there is a Confirmation of mapping
between the T24 and Legacy systems, Extraction and upload process crystallised,
documented and signed off, Reconciliation Specification signed off,T24 data
deliverable to SIT,Successful test run leads to Dress Rehearsal.

Securities Prototype 12
 Training & Hand over of T24 DM Upload & Extract Tool if required:
• This activity is carried on if the client would like to get trained in the T24 DM
Upload & T24 DM Extract tools to handle further migrations.
• This is customized training program. Prepared based on the requirement and target
audience need with the separate effort estimate for offshore & onshore work

Dress Rehearsals:
• Process
o Production infrastructure
o Full scope of data upload into T24
o Reports built and available for reconciliation of data by the Client
o Financial reconciliation with the General Ledger of the client system
o Runs to be repeated until fully reconciled
o Timed and improved at each run to fit within final cutover window
• Milestone
o T24 Data deliverable to UAT
o Successful test run leads to prepared Go Live status

Securities Prototype 13
 The Reporting process consists of Administrative and Technical reports.

The administrative reports includes Daily/weekly publishing of the offshore and

onshore work plan with resources, Separate Daily Activity Log for each Migration
Consultant, Weekly work execution report to the Project team and Client.

The Technical reports includes T24 Migration Tool’ s upload and extract reports,
Timing Log, Issue and Risk Log,
Execution report consisting of statistics, issues, solution, lesson learned and action
plan for corrective measures etc for each migration exercise.

The sign off from the Testing phase leads to the Cutover phase.

Securities Prototype 14
The Cutover phase is the final phase takes about 15% of the Data Migration
process.

The cutover / migration date has to be decided and communicated.Based on

the run book / plan the cutover and data migration activities has to be
executed.

Extraction of data file based on the properties of the Mapped DMS and
provided for upload.

The data file will be uploaded to T24 using DM upload tool.

Extraction of T24 data based on signed off T24 Data Extract specifications
and provide output for comparison.
 Handling defects on defined process, follow up, impact analysis, workaround and
solutions.

First Migration COB will be done after post migration activities for cycling the date
for the next business day that is Go Live date.

The client has to execute reconciliation plan & run comparison programs to check the
T24 extract with client system extract, manual verification of business reconciliations
& get sign off from relevant business team for Go / No Go decision.

Securities Prototype 15
Securities Prototype 16
 After completing this unit, you will be able to

Have an overview of Data migration Activities

Understand the various phases in Data Migration

Know the DM life cycle

Securities Prototype 17
18