- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Access Management
- Preparations
- Data Migration
- Databases Supported by Data Migration
- Cross-Account TencentDB Instance Migration
- Migrating to MySQL
- Migrating to MariaDB
- Migrating to TDSQL-C for MySQL
- Migrating to TDSQL MySQL
- Migrating to PostgreSQL
- Migrating to MongoDB
- Migrating to SQL Server
- Migrating to TencentDB for Redis
- Offline Migration of MySQL Data
- Advanced Migration Operations
- Task Management
- Data Sync
- Databases Supported by Data Sync
- Cross-Account TencentDB Instance Sync
- Synchronize to PostgreSQL
- Sync into Tencent Cloud
- Sync from Tencent Cloud
- Advanced Sync Operations
- Task Management
- Task Status Description
- Viewing Task
- Starting Task
- Retrying Task (MySQL)
- Verifying Task
- Stopping Task
- Pausing Task
- Resuming Task
- Resetting Task
- Deleting Task
- Changing Configuration
- Transition from Pay-as-You-Go to Monthly Subscription
- Terminating/Returning Instance
- Renewing Task
- Deisolating Task
- Deleting Instance
- Viewing Log
- Deleting Task
- Data Subscription (Kafka Edition)
- Databases Supported by Data Subscription
- Creating Data Subscription Task
- Data Consumption
- Creating Consumer Group
- Managing Consumer Group
- Consuming MySQL Data
- Consuming MongoDB Data
- Consuming TDSQL for PostgreSQL Data
- Consuming Subscribed Data with Kafka Client (Protobuf)
- Consuming Subscribed Data with Kafka Client (Avro)
- Consuming Subscribed Data with Kafka Client (JSON)
- Consuming Subscribed Data with Flink Client (Avro)
- Consuming Data with Flink
- Advanced Subscription Operations
- Task Management
- Data Migration (OldDTS)
- Data Subscription (OldDTS)
- Fix for Verification Failure
- Check Item Overview
- Check Items of MySQL/MariaDB/Percona/TDSQL-C for MySQL/TDSQL for MySQL
- MongoDB Check Items
- PostgreSQL Check Items
- TDSQL for PostgreSQL
- Redis/Tendis
- SQL Server
- Database Connection Check
- Source Database Existence Check
- Target Database Existence Check
- Peripheral Check
- Migration Network Check
- Version Check
- Source Instance Permission Check
- Account Conflict Check
- Partial Database Parameter Check
- Source Instance Parameter Check
- Source Instance Type (Master or Replica)
- Parameter Configuration Conflict Check
- Target Database Content Conflict Check
- Target Database Space Check
- Target Database Load Check
- Local Disk Space Check
- Binlog Parameter Check
- Oplog Check
- Foreign Key Dependency Check
- View Check
- Advanced Object Check
- Incremental Migration Precondition Check
- Extension/Plugin Compatibility Check
- Source Database Balancer Check
- Source Database Node Role Check
- ShardKey Check
- Warning Item Check
- DLL Ring Sync Check for Single Database/Table Object
- DLL Sync Conflict Check for Single Database/Table Object in the Same Target
- Level-2 Subpartitioned Table Check
- Primary Key Check
- DDL Check for Tables to Be Migrated
- System Database Conflict Check
- Table Structure Check for Source and Target Instances
- InnoDB Table Check
- Migration Object Dependency Check
- Constraint Check
- Cutover Description
- Monitoring and Alarms
- Ops Management
- DTS-DBbridge
- Best Practices
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- (NewDTS) Data Migration APIs
- DescribeMigrationJobs
- DescribeMigrationDetail
- CreateMigrationService
- ModifyMigrationJob
- CreateMigrateCheckJob
- DescribeMigrationCheckJob
- SkipCheckItem
- StartMigrateJob
- StopMigrateJob
- ResumeMigrateJob
- RecoverMigrateJob
- ModifyMigrateName
- ModifyMigrateJobSpec
- IsolateMigrateJob
- DestroyMigrateJob
- DescribeMigrateDBInstances
- CompleteMigrateJob
- PauseMigrateJob
- ContinueMigrateJob
- Data Sync APIs
- ModifySyncJobConfig
- CreateModifyCheckSyncJob
- DescribeModifyCheckSyncJobResult
- StartModifySyncJob
- DescribeSyncJobs
- CreateSyncJob
- ConfigureSyncJob
- CreateCheckSyncJob
- SkipSyncCheckItem
- DescribeCheckSyncJobResult
- StartSyncJob
- StopSyncJob
- ResumeSyncJob
- ResizeSyncJob
- RecoverSyncJob
- IsolateSyncJob
- DestroySyncJob
- PauseSyncJob
- ContinueSyncJob
- Data Consistency Check APIs
- Data Types
- Error Codes
- DTS API 2018-03-30
- SDK Documentation
- FAQs
- Error Handling (NewDTS)
- Error Handling (OldDTS)
- Service Agreement
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Access Management
- Preparations
- Data Migration
- Databases Supported by Data Migration
- Cross-Account TencentDB Instance Migration
- Migrating to MySQL
- Migrating to MariaDB
- Migrating to TDSQL-C for MySQL
- Migrating to TDSQL MySQL
- Migrating to PostgreSQL
- Migrating to MongoDB
- Migrating to SQL Server
- Migrating to TencentDB for Redis
- Offline Migration of MySQL Data
- Advanced Migration Operations
- Task Management
- Data Sync
- Databases Supported by Data Sync
- Cross-Account TencentDB Instance Sync
- Synchronize to PostgreSQL
- Sync into Tencent Cloud
- Sync from Tencent Cloud
- Advanced Sync Operations
- Task Management
- Task Status Description
- Viewing Task
- Starting Task
- Retrying Task (MySQL)
- Verifying Task
- Stopping Task
- Pausing Task
- Resuming Task
- Resetting Task
- Deleting Task
- Changing Configuration
- Transition from Pay-as-You-Go to Monthly Subscription
- Terminating/Returning Instance
- Renewing Task
- Deisolating Task
- Deleting Instance
- Viewing Log
- Deleting Task
- Data Subscription (Kafka Edition)
- Databases Supported by Data Subscription
- Creating Data Subscription Task
- Data Consumption
- Creating Consumer Group
- Managing Consumer Group
- Consuming MySQL Data
- Consuming MongoDB Data
- Consuming TDSQL for PostgreSQL Data
- Consuming Subscribed Data with Kafka Client (Protobuf)
- Consuming Subscribed Data with Kafka Client (Avro)
- Consuming Subscribed Data with Kafka Client (JSON)
- Consuming Subscribed Data with Flink Client (Avro)
- Consuming Data with Flink
- Advanced Subscription Operations
- Task Management
- Data Migration (OldDTS)
- Data Subscription (OldDTS)
- Fix for Verification Failure
- Check Item Overview
- Check Items of MySQL/MariaDB/Percona/TDSQL-C for MySQL/TDSQL for MySQL
- MongoDB Check Items
- PostgreSQL Check Items
- TDSQL for PostgreSQL
- Redis/Tendis
- SQL Server
- Database Connection Check
- Source Database Existence Check
- Target Database Existence Check
- Peripheral Check
- Migration Network Check
- Version Check
- Source Instance Permission Check
- Account Conflict Check
- Partial Database Parameter Check
- Source Instance Parameter Check
- Source Instance Type (Master or Replica)
- Parameter Configuration Conflict Check
- Target Database Content Conflict Check
- Target Database Space Check
- Target Database Load Check
- Local Disk Space Check
- Binlog Parameter Check
- Oplog Check
- Foreign Key Dependency Check
- View Check
- Advanced Object Check
- Incremental Migration Precondition Check
- Extension/Plugin Compatibility Check
- Source Database Balancer Check
- Source Database Node Role Check
- ShardKey Check
- Warning Item Check
- DLL Ring Sync Check for Single Database/Table Object
- DLL Sync Conflict Check for Single Database/Table Object in the Same Target
- Level-2 Subpartitioned Table Check
- Primary Key Check
- DDL Check for Tables to Be Migrated
- System Database Conflict Check
- Table Structure Check for Source and Target Instances
- InnoDB Table Check
- Migration Object Dependency Check
- Constraint Check
- Cutover Description
- Monitoring and Alarms
- Ops Management
- DTS-DBbridge
- Best Practices
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- (NewDTS) Data Migration APIs
- DescribeMigrationJobs
- DescribeMigrationDetail
- CreateMigrationService
- ModifyMigrationJob
- CreateMigrateCheckJob
- DescribeMigrationCheckJob
- SkipCheckItem
- StartMigrateJob
- StopMigrateJob
- ResumeMigrateJob
- RecoverMigrateJob
- ModifyMigrateName
- ModifyMigrateJobSpec
- IsolateMigrateJob
- DestroyMigrateJob
- DescribeMigrateDBInstances
- CompleteMigrateJob
- PauseMigrateJob
- ContinueMigrateJob
- Data Sync APIs
- ModifySyncJobConfig
- CreateModifyCheckSyncJob
- DescribeModifyCheckSyncJobResult
- StartModifySyncJob
- DescribeSyncJobs
- CreateSyncJob
- ConfigureSyncJob
- CreateCheckSyncJob
- SkipSyncCheckItem
- DescribeCheckSyncJobResult
- StartSyncJob
- StopSyncJob
- ResumeSyncJob
- ResizeSyncJob
- RecoverSyncJob
- IsolateSyncJob
- DestroySyncJob
- PauseSyncJob
- ContinueSyncJob
- Data Consistency Check APIs
- Data Types
- Error Codes
- DTS API 2018-03-30
- SDK Documentation
- FAQs
- Error Handling (NewDTS)
- Error Handling (OldDTS)
- Service Agreement
Data migration is a one-time task of replicating data from the source database to the target database at the database level. After the migration is completed, the business will be cut over to the new database.
DTS supports data migration from self-built databases, TencentDB databases, and third-party cloud databases.
- Migration from a self-built database to the cloud: Migrating a self-built database in the local IDC or on CVM, or a Lighthouse database on the Lighthouse instance to a TencentDB database.
- Migration between TencentDB instances: Such as database version upgrade, cross-region migration (including migration between regions inside China or outside China, or cross-border migration), and the migration between database instances under different Tencent Cloud accounts.
- Migration from a third-party cloud database to TencentDB: Such as migration from an Alibaba Cloud or AWS database to TencentDB.
You can select different access types based on the deployment modes of the source databases. DTS supports the following access types: Public Network, Self-Build on CVM, Direct Connect, VPN Access, Database, and CCN, each requiring different network conditions. For more information, see Preparations Overview.
Databases that can be migrated with DTS are as detailed below:
| Data Flow Direction | Migration Direction | Source Database Type & Version | Target Database Type & Version | Migration Type | Cross-Account Migration | Source Database Access Type |
|---|---|---|---|---|---|---|
| MySQL > MySQL | To Tencent Cloud |
|
TencentDB for MySQL 5.5/5.6/5.7/8.0 | Supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | |
| MariaDB > MySQL | To Tencent Cloud | TencentDB for MySQL 5.5/5.6/5.7/8.0 | Not supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | ||
| Percona > MySQL | To Tencent Cloud | Self-built Percona 5.5/5.6/5.7/8.0 | TencentDB for MySQL 5.5/5.6/5.7/8.0 | - | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | |
| TDSQL for MySQL > MySQL | To Tencent Cloud | TDSQL for MySQL 5.7/8.0 | TencentDB for MySQL 5.7/8.0 | Not supported | Database | |
| MySQL > MariaDB | To Tencent Cloud | TencentDB for MariaDB 5.7/8.0/10.0/10.1 | Supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | ||
| MariaDB > MariaDB | To Tencent Cloud | TencentDB for MariaDB 5.7/8.0/10.0/10.1 | Not supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | ||
| Percona > MariaDB | To Tencent Cloud | Self-built Percona 5.5/5.6/5.7/8.0 | TencentDB for MariaDB 5.7/8.0/10.0/10.1 | - | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | |
| TDSQL for MySQL > MariaDB | To Tencent Cloud | TDSQL for MySQL 5.7/8.0/10.0/10.1 | TencentDB for MariaDB 5.7/8.0/10.0/10.1 | Not supported | Database | |
| MySQL > TDSQL-C for MySQL | To Tencent Cloud |
|
TDSQL-C for MySQL 5.7/8.0 | Supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | |
| MariaDB > TDSQL-C for MySQL | To Tencent Cloud | TDSQL-C for MySQL 5.7/8.0 | Not supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | ||
| Percona > TDSQL-C for MySQL | To Tencent Cloud | Self-built Percona 5.5/5.6/5.7/8.0 | TDSQL-C for MySQL 5.7/8.0 | - | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | |
| MySQL > TDSQL for MySQL | To Tencent Cloud | TDSQL for MySQL 5.7/8.0 | Supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | ||
| MariaDB > TDSQL for MySQL | To Tencent Cloud |
|
TDSQL for MySQL 5.7/8.0/10.0/10.1 | Not supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | |
| Percona > TDSQL for MySQL | To Tencent Cloud | Self-built Percona 5.5/5.6/5.7/8.0 | TDSQL for MySQL 5.7/8.0 | - | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | |
| TDSQL for MySQL > TDSQL for MySQL | To Tencent Cloud | TDSQL for MySQL 5.7/8.0/10.0/10.1 | TDSQL for MySQL 5.7/8.0/10.0/10.1 | Not supported | Database | |
| PostgreSQL > PostgreSQL | To Tencent Cloud |
|
TencentDB for PostgreSQL 10/11/12/13 | Supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | |
| MongoDB > MongoDB | To Tencent Cloud | TencentDB for MongoDB 3.0/3.2/3.4/3.6/4.0/4.2 | Supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN | ||
| SQL Server > SQL Server | To Tencent Cloud | TencentDB for SQL Server 2008 R2/2012/2014/2016/2017/2019 | Not supported | Public Network/Self-Build on CVM/Direct Connect/VPN Access/Database/CCN |
Note：
- In the above table, the migration direction “To Tencent Cloud” indicates that the target database is a TencentDB instance, just as shown in the Target Database Type & Version column.
- Cross-account migration only makes sense when both the source and target databases are TencentDB instances under different Tencent Cloud root accounts.
- Requirements for database versions:
- MySQL/TDSQL for MySQL/MariaDB/TDSQL-C: The target database version must be later than or the same as the source database version. The versions are differentiated by the major version number; for example, v5.6.x can be migrated to v5.6.x, v5.7.x, or later.
- PostgreSQL: For full migration, the target database version must be later than or the same as the source database version; for incremental migration, migration between versions above v10.x is supported.
- MongoDB: Migration between all versions is supported.
- SQL Server: Only migration from Basic Edition to High Availability Edition (including Dual-Server High Availability Edition and Cluster Edition) is supported, and the version number of the target database must be above that of the source database.
- The above table lists the features supported by NewDTS. For Redis data migration, see Migration with DTS.
Yes
No
Was this page helpful?