I like the old saying, "don't tell people your plans; show them your results." Our world is full of dreamers, which is a good thing per se, but if the dreams are left alone without execution, our world can never get better.
Everyone in the banking industry feels pressure from digitized banking customers because they expect first calls user experience on all channels and the availability of all finance products with a few fingertips. Unfortunately, if you still sit on an outdated core banking product, you won't keep up with these expectations.
What to remember when you migrate from T24 Core Banking to another CBS?
Find your best T24 business and technical experts because you will need their advice during your migration journey. Get a good understanding of your new product and follow up with your T24 experts o learn how to fetch these records. Furthermore, it would help if you had dues and accrual amounts for some applications, such as loans and deposits. Finally, advanced tooling is a must, given the massive amount of data to be transmitted.
We had a good experience with the following data extraction tools:
Custom data extract routines in T24
For your migration to T24, the steps below should take into consideration.
A. Pre Migration activities
T24 system should be available with all the functionality defined by business
Multi-app servers are preferred to load data quickly
Pre-migration environment checks and changes in applications such as Holiday, SPF, CURRENCY, COUNTRY, etc
Browser setup and TSA service checks
B. Loading static data into T24
The data migration will usually start with loading DAO and then CUSTOMER and its related tables
C. Loading Financial Data into T24
The financial data include Accounts, loans, deposits, payments, etc.
For loans and deposits in AA, the below activities need to be run depending on the type of loans/deposits
D. Reconciliation and frequent backup of loaded data
Once the data is loaded to any application, the data should be extracted and compared with the CBS files. If there is any mismatch, the data should be corrected before loading the subsequent application data.
There should be breakpoints where the data backup should be taken. It will help in the restoration of data in subsequent levels of migration.
E. Post-migration activities
After the migration, the pre-migration changes should be reverted to the original state.
F. Pre-COB and post-COB reports
COB should be run after the migration activity is completed
GL-report should be run before and after COB for reconciliation purposes
What tools to use for your data migration to T24 Core Banking?
The DM Tool, part of T24, is a great choice. Once the initial configuration is completed, you can use this excellent utility.
This application allows the user to define the data format in the incoming tape. The following provides the list of fields, positions, and the associated description. Local routines can be written to manipulate the data at the field level and load.
This table is used to create folders, copy data files to the respective folders, and generate the DM.SERVICE.CONTROL (DSC) that is necessary for a data load to T24. Using the application DM.PREREQUISITE we can make required folders and moves the data files to their respective paths. We will also be able to create folders for placing reconciliation extracts from T24
Extracting the data from T24 uses applications called DME, local routines can also be written to manipulate the data and export it.
Extraction of Data from T24 is necessary when a Migration is to take place between older releases of T24 to a newer release or for reconciliation extracts. The application DM.EXTRACTOR is used for the extraction of data from T24.
All the best for your data migration project!