Data Migration Type Conversion for Secure Cloud Database Transfer

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Migrating data between databases with different data types, especially from an on-premise to a public cloud environment, is challenging due to the lack of security-focused tools and the need for manual intervention to correct data types, which is inefficient and prone to errors.

Innovation Solution

A system and method that automatically detects data type differences, applies conversion rules, and executes them to convert data types before migration, using a Java batch program and parallel data migration threads, with encryption for security, and scheduled data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual data pre-processing is used to correct data type differences, then data migration can be completed, but the process becomes inefficient and error-prone

Engineering Contradiction:

Improvedata migration accuracyVSAvoiddata migration efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system performs preliminary detection of data type differences between source and target databases before migration begins. Conversion rules are pre-configured and stored in a rules database, enabling automatic type conversion during migration without manual intervention, thus improving both accuracy and efficiency

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The migration system automatically detects data type mismatches and applies appropriate conversion rules from the rules database without requiring manual operator intervention. The system self-corrects data type issues that would otherwise require manual pre-processing, eliminating human error while maintaining high migration speed

Inventive Principle:

Principle #25Self-service

2Reliability

If existing data migration tools are used for on-premise to cloud migration, then migration can proceed, but security requirements are not adequately addressed

Engineering Contradiction:

ImprovesecurityVSAvoidmigration tool compatibility

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system introduces an encrypted database vault as an intermediary security layer between the migration process and sensitive data. Credentials are stored in encrypted form and only decrypted during authorized migration operations, providing security-focused functionality that existing tools lack while maintaining compatibility with various database types

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The migration system is designed to handle multiple database types (on-premise and cloud) with unified security protocols. The encrypted vault and conversion rules framework provide universal security and adaptability across different migration scenarios, making the tool versatile while meeting security requirements

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If additional devices and software are installed to facilitate data migration, then migration capability is enhanced, but system complexity increases

Engineering Contradiction:

Improvemigration capabilityVSAvoidsystem configuration

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system combines multiple migration functionalities (data type detection, conversion rule application, encrypted credential storage, and parallel migration execution) into a single integrated platform. This consolidation provides enhanced migration capability without requiring operators to install and configure multiple separate devices and software components

Inventive Principle:

Principle #5Merging (Combining)

4Adaptability or versatility

If data type conversion is performed manually, then data compatibility is achieved, but the process is time-consuming

Engineering Contradiction:

Improvedata compatibilityVSAvoidmigration time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

Conversion rules for different data type combinations are pre-configured and stored in a rules database before migration begins. The system detects data type differences and automatically applies the appropriate pre-defined conversion rules, achieving data compatibility instantly without time-consuming manual conversion processes

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system executes multiple parallel data migration threads simultaneously, each handling different data tables or datasets. This parallel execution maintains continuous migration flow while automatically performing type conversions, significantly reducing total migration time compared to sequential manual processing

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS20260111399A1Systems and methods for converting data types in data migration

Publication Date: 2026.04.23 THE TORONTO DOMINION BANK

AI summary

Systems and methods for migrating data are provided. A migration application communicates with a source database and a target database, and is configured 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 obtains 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.