# US 2025/0156381 A1 · Systems and methods for converting data types in data migration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0156381 A1
- Document ID: US20250156381A1
- Status: Published application
- Kind: A1
- Application number: 18/506,614
- Filed: 2023-11-10
- Published: 2025-05-15
- Earliest claimed: 2023-11-10
- Assignees: The Toronto-Dominion Bank
- Applicants: The Toronto-Dominion Bank
- Inventors: Avinash Ban; Margot Shepherd-Spurgeon
- Web page: https://patentgrep.com/patent/US20250156381A1

## CPC

- G06F 16/214: {Database migration support}
- G06F 16/258: {Data format conversion from or to a database}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for migrating data are provided. A migration application communicates with a source database and a target database, and receives a command to migrate data therebetween. It automatically detects that, for a source data field in the source database that is to be migrated to a target data field in the target database, the source data field is of a first data type and the target data field is of a second data type that is different from the first data type. The migration application automatically searches a rules database for a conversion rule in relation to the first data type and the second data type. The migration application automatically executes the conversion rule to convert data in the source data field to converted data that is of the second data type. The migration application automatically migrates the converted data to the target database.

## Claims

### Claim 1

A system for migrating data, the system comprising:
a memory, a network interface, and a processor, the processor operably coupled to the memory and the network interface, the processor configured to:
receive a command to migrate data from a source database to a target database;
automatically determine if a first data type of a source data field in the source database, which is to be migrated to a target data field in the target database, is different or the same as a second data type of the target data field;
responsive to automatically detecting the first data type is different from the second data type, automatically search a rules database in the memory for a conversion rule in relation to the first data type and the second data type;
after obtaining the conversion rule, automatically execute the conversion rule to convert data in the source data field to converted data that is of the second data type; and,
automatically migrate the data from the source database, including the converted data, to the target database.

### Claim 2 (depends on 1)

The system of claim 1, wherein the system is part of a public cloud computing system, the target database resides on the public cloud computing system, and the source database resides on an on-premise computing system.

### Claim 3 (depends on 2)

The system of claim 2, wherein the system comprises a virtual machine operating on the memory, the network interface and the processor of the public cloud computing system, and the virtual machine is configured to run a Java batch program for migrating the data.

### Claim 4 (depends on 3)

The system of claim 3, wherein the system communicates with the source database using a Java Database Connectivity connection.

### Claim 5 (depends on 1)

The system of claim 1, wherein the processor is further configured to:
detect a plurality of source tables in the source database;
create a plurality of data migration threads respectively corresponding to the plurality of source tables for transferring the data to a plurality of target tables in the target database; and,
prior to executing each of the plurality of data migration threads, automatically determine for each of the plurality of source tables if there is at least a given source data field in a given source table that has a different data type compared to a corresponding given target data field in a corresponding given target table.

### Claim 6 (depends on 5)

The system of claim 5, wherein the plurality of data migration threads are executed in parallel to simultaneously transfer the data from the plurality of source tables to the plurality of target tables.

### Claim 7 (depends on 1)

The system of claim 1, wherein the memory stores therein an encrypted database vault, the encrypted database vault storing in an encrypted format at least a source user ID and a source password for accessing the source database, and a target user ID and a target password for accessing the target database; and, after receiving the command, the processor is further configured to access the encrypted database to use the source user ID and the source password to access the source database, and to use the target user ID and the target password to access the target database.

### Claim 8 (depends on 1)

The system of claim 1, wherein the system is part of an on-premise computing system, the target database resides on the on-premise computing system, and the source database resides on the on-premise computing system.

### Claim 9 (depends on 1)

The system of claim 1, wherein the memory stores thereon a scheduled date, and the processor is further configured to automatically migrate the data from the source database, including the converted data, to the target database on the scheduled date.

### Claim 10 (depends on 1)

The system of claim 1, wherein the first data type is a first data format, and the second data type is a second data format; and wherein the processor is further configured to:
automatically detect that the first data format is not supported by the second target database; and
automatically convert the first data format to the second data format according to according to the conversion rule.

### Claim 11

A method for migrating data, the method executed in a computing environment comprising one or more processors and memory, the method comprising:
receiving a command to migrate data from a source database to a target database;
automatically determining if a first data type of a source data field in the source database, which is to be migrated to a target data field in the target database, is different or the same as a second data type of the target data field;
responsive to automatically detecting the first data type is different from the second data type, automatically searching a rules database in the memory for a conversion rule in relation to the first data type and the second data type;
after obtaining the conversion rule, automatically executing the conversion rule to convert data in the source data field to converted data that is of the second data type; and,
automatically migrating the data from the source database, including the converted data, to the target database.

### Claim 12 (depends on 11)

The method of claim 11, wherein the computing environment is a public cloud computing system, the target database resides on the public cloud computing system, and the source database resides on an on-premise computing system.

### Claim 13 (depends on 12)

The method of claim 12, wherein the computing environment comprises a virtual machine operating on the memory, a network interface and the one or more processors of the public cloud computing system, and the virtual machine is configured to run a Java batch program for executing the method.

### Claim 14 (depends on 11)

The method of claim 11, further comprising:
detecting a plurality of source tables in the source database;
creating a plurality of data migration threads respectively corresponding to the plurality of source tables for transferring the data to a plurality of target tables in the target database; and,
prior to executing each of the plurality of data migration threads, automatically determining for each of the plurality of source tables if there is at least a given source data field in a given source table that has a different data type compared to a corresponding given target data field in a corresponding given target table.

### Claim 15 (depends on 14)

The method of claim 14, wherein the plurality of data migration threads are executed in parallel to simultaneously transfer the data from the plurality of source tables to the plurality of target tables.

### Claim 16 (depends on 11)

The method of claim 11, wherein the memory stores therein an encrypted database vault, the encrypted database vault storing in an encrypted format at least a source user ID and a source password for accessing the source database, and a target user ID and a target password for accessing the target database; and, after receiving the command, the method further comprising accessing the encrypted database to use the source user ID and the source password to access the source database, and to use the target user ID and the target password to access the target database.

### Claim 17 (depends on 11)

The method of claim 11, wherein the computing environment is part of an on-premise computing system, the target database resides on the on-premise computing system, and the source database resides on the on-premise computing system.

### Claim 18 (depends on 11)

The method of claim 11, wherein the memory stores thereon a scheduled date, and the method further comprising automatically migrating the data from the source database, including the converted data, to the target database on the scheduled date.

### Claim 19 (depends on 11)

The method of claim 11, wherein the first data type is a first data format, and the second data type is a second data format; and wherein the method further comprising:
automatically detecting that the first data format is not supported by the second target database; and
automatically converting the first data format to the second data format according to according to the conversion rule.

### Claim 20

A non-transitory computer readable medium storing computer executable instructions which, when executed by at least one computer processor, cause the at least one computer processor to carry out a method migrating data, the method comprising:
receiving a command to migrate data from a source database to a target database;
automatically determining if a first data type of a source data field in the source database, which is to be migrated to a target data field in the target database, is different or the same as a second data type of the target data field;
responsive to automatically detecting the first data type is different from the second data type, automatically searching a rules database in the memory for a conversion rule in relation to the first data type and the second data type;
after obtaining the conversion rule, automatically executing the conversion rule to convert data in the source data field to converted data that is of the second data type; and,
automatically migrating the data from the source database, including the converted data, to the target database.
