tencent cloud

Data Transfer Service

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Data Migration
Data Sync
Data Subscription (Kafka Edition)
Strengths
Supported Regions
Specification Description
Purchase Guide
Billing Overview
Configuration Change Description
Payment Overdue
Refund
Getting Started
Data Migration Guide
Data Sync Guide
Data Subscription Guide (Kafka Edition)
Preparations
Business Evaluation
Network Preparation
Adding DTS IP Addresses to the Allowlist of the Corresponding Databases
DTS Service Permission Preparation
Database and Permission Preparation
Configuring Binlog in Self-Built MySQL
Data Migration
Databases Supported by Data Migration
Cross-Account TencentDB Instance Migration
Migration to MySQL Series
Migrating to PostgreSQL
Migrating to MongoDB
Migrating to SQL Server
Migrating to Tencent Cloud Distributed Cache
Task Management
Data Sync
Databases Supported by Data Sync
Cross-Account TencentDB Instance Sync
Sync to MySQL series
Synchronize to PostgreSQL
Synchronization to MongoDB
Synchronize to Kafka
Task Management
Data Subscription (Kafka Edition)
Databases Supported by Data Subscription
MySQL series Data Subscription
Data Subscription for TDSQL PostgreSQL
MongoDB Data Subscription
Task Management
Consumption Management
Fix for Verification Failure
Check Item Overview
Cutover Description
Monitoring and Alarms
Supported Monitoring Indicators
Supported Events
Configuring Metric Alarms and Event Alarms via the Console
Configuring Indicator Monitoring and Event Alarm by APIs
Ops Management
Configuring Maintenance Time
Task Status Change Description
Practical Tutorial
Synchronizing Local Database to the Cloud
Creating Two-Way Sync Data Structure
Creating Many-to-One Sync Data Structure
Creating Multi-Site Active-Active IDC Architecture
Selecting Data Sync Conflict Resolution Policy
Using CLB as Proxy for Cross-Account Database Migration
Migrating Self-Built Databases to Tencent Cloud Databases via CCN
Best Practices for DTS Performance Tuning
FAQs
Data Migration
Data Sync
FAQs for Data Subscription Kafka Edition
Regular Expressions for Subscription
Error Handling
Common Errors
Failed Connectivity Test
Failed or Alarmed Check Item
Inability to Select Subnet During CCN Access
Slow or Stuck Migration
Data Sync Delay
High Data Subscription Delay
Data Consumption Exception
API Documentation
History
Introduction
API Category
Making API Requests
(NewDTS) Data Migration APIs
Data Sync APIs
Data Consistency Check APIs
(NewDTS) Data Subscription APIs
Data Types
Error Codes
DTS API 2018-03-30
Service Agreement
Service Level Agreements
DocumentationData Transfer ServicePurchase GuideBilling Overview

Billing Overview

PDF
Focus Mode
Font Size
Last updated: 2026-03-02 10:45:22

Billing Mode

Billing Mode
Payment Mode
Use Case and Description
Yearly/monthly subscription
Prepaid Billing. You pay when you create an instance.
It is more cost-effective in the long term for businesses with stable needs than pay-as-you-go billing.
Pay-as-you-go
Postpaid Billing. A bill is generated every hour, and fees are deducted from your Tencent Cloud account based on the bill.
It is suitable for instantaneously fluctuating businesses. In this mode, instances can be released immediately after the use to save costs.
Only pay-as-you-go data sync tasks can be changed to the monthly subscription billing mode.

Billable Items and Rules

Note:
You will be charged for using MySQL/TDSQL-C MySQL/MariaDB/Percona links in data migration and data sync tasks through DTS from June 15, 2023. The existing data migration and data sync tasks created before the official billing will be charged. For more information, see Existing DTS Task Billing Rules.
Billing for all supported links in data subscription started on 2020.
Feature Instance
Billable Item
Billing Mode
Description
Data Migration
Link configuration fees
Pay-as-you-go
Full migration is free of charge. Fees are incurred only during normal incremental migration (including data consistency check). When the task ends or is paused, billing will also stop.
If you select Structural migration or Full migration for Migration Type, no fees will be incurred.
If you select Full + incremental migration for Migration Type, during source database export and data import, full migration is performed free of charge. During subsequent incremental sync, incremental migration is performed and billing starts. When you click Complete, the task ends and billing stops.
Note:
Because DTS continues to pull the data and binlog of the source database during the task pause, billable links will still be billed when the migration task is paused.
Public network traffic fees
Pay-as-you-go
Currently, the public network traffic is free of charge.
Data Sync
Link configuration fees
Monthly subscription and pay-as-you-go
A monthly subscribed task is billed upon purchase.
A pay-as-you-go task is free of charge during configuration and will incur fees only when it starts running. Fees will incur only when it runs normally, and billing will stop when it is paused.
Note:
Because DTS continues to pull the data of the source database during the task pause, billable links will still be billed when the sync task is paused.
Public network traffic fees
Pay-as-you-go
Currently, the public network traffic is free of charge.
Data Subscription
Link configuration fees
Pay-as-you-go
Billing will start after the configuration is completed and the instance starts successfully.
Data storage fees
Free
Currently, data storage is free of charge.
In pay-as-you-go billing mode, the fees for one hour's usage will be frozen during task creation and will be unfrozen when you terminate the instance or the instance is isolated and terminated due to overdue payments. This is the case even in scenarios where no fees are incurred, for example, incremental migration is not selected in a migration task, or a pay-as-you-go sync task is purchased but not started. We recommend that you terminate completed or unwanted tasks promptly to unfreeze fees in time.

Billable DTS Links

Only the following commercial links for data migration and sync are billed, and you will be notified if billing starts for other free links. All supported links for data subscription are billed.
Data Migration
Data Sync
MySQL/MariaDB/Percona > MySQL
MySQL/MariaDB/Percona > MariaDB
MySQL/MariaDB/Percona > TDSQL-C MySQL
MySQL/MariaDB/Percona/TDSQL-C for MySQL > MySQL
MySQL/MariaDB/Percona/TDSQL-C for MySQL > MariaDB
MySQL/MariaDB/TDSQL-C for MySQL > TDSQL-C for MySQL
MySQL/MariaDB/Percona/TDSQL-C for MySQL > Kafka

Data Migration Billing Details

Link configuration fees (pay-as-you-go)
Note:
For DTS link configuration billing, three key factors are specifications, cross-region selection, and target region. Prices vary depending on the combo. For more information, see the purchase page in the [DTS console](https://buy.cloud.tencent. com/migration!85f6590a97448e3282d761536d270586).
Specifications are increased from small to medium to large, xlarge, and 2xlarge. Higher specifications incur higher fees and deliver better transmission performance.
The cost of links across regions is higher than that of links in the same region. For example, "Beijing-to-Beijing" means the same region, "Beijing-to-Shanghai" means cross-region, "Beijing-to-Beijing Finance" means cross-region, and each finance region is counted as an independent region.
The billing will differ depending on whether the target region is Chinese Mainland, the finance region in Chinese Mainland, Hong Kong (China), or other countries and regions. See the table below for details. In a cross-region link, the billing outcome is always the same for the same target region regardless of the region choice made on the source side.
RPS indicates the number of incremental data rows migrated to the target table per second by DTS RPS is subject to various factors such as operational load of the source database, network bandwidth, and network latency. Therefore, the following figure data is for reference only.
Specifications
Target Region - Chinese Mainland (USD/Hour)
Target Region - Finance Regions in Chinese Mainland (USD/Hour)
Target Region - Hong Kong (China) and Other Countries/Regions (USD/Hour)
Maximum RPS
Same region
Across region
Same region
Across region
Same region
Across region
small
0.14571429
0.20428571
0.27714286
0.38857143
0.21857143
0.30571429
2000
medium
0.25714286
0.36
0.48857143
0.68428571
0.38571429
0.54
5000
large
0.43
0.60142857
0.81714286
1.14428571
0.64571429
0.90428571
6000
xlarge
0.77428571
1.08428571
1.47142857
2.06
1.16142857
1.62571429
7000
2xlarge
1.37428571
1.92428571
2.61142857
3.65571429
2.06142857
2.88571429
11000

Data Sync Billing Details

Note:
For DTS link configuration billing, three key factors are specifications, cross-region selection, and target region. Prices vary depending on the combo. For more information, see the purchase page in the DTS console.
Specifications are increased from micro to small to medium and large. Higher specifications incur higher fees and deliver better transmission performance.
The cost of links across regions is higher than that of links in the same region. For example, "Beijing-to-Beijing" means the same region, "Beijing-to-Shanghai" means cross-region, "Beijing-to-Beijing Finance" means cross-region, and each finance region is counted as an independent region.
The billing will differ depending on whether the target region is Chinese Mainland, the finance region in Chinese Mainland, Hong Kong (China), or other countries and regions. See the table below for details. In a cross-region link, the billing outcome is always the same for the same target region regardless of the region choice made on the source side.
RPS indicates the number of incremental data rows synced to the target table per second by DTS. RPS is subject to various factors such as operational load of the source database, network bandwidth, and network latency. Therefore, the following figure data is for reference only.
Link configuration fees (monthly subscription)
Specifications
Target Region - Chinese Mainland (USD/Month)
Target Region - Finance Regions in Chinese Mainland (USD/Month)
Target Region - Hong Kong (China) and Other Countries/Regions (USD/Month)
Maximum RPS
Same region
Across region
Same region
Across region
Same region
Across region
micro
56.85714286
79.6
108.0285714
151.24
85.28571429
119.4
1000
small
120.2857143
168.4
228.5428571
319.96
180.4285714
252.6
2000
medium
168.5714286
236
320.2857143
448.4
252.8571429
354
5000
large
250
350
475
665
375
525
11000
Link configuration fees (pay-as-you-go)
Specifications
Target Region - Chinese Mainland (USD/Hour)
Target Region - Finance Regions in Chinese Mainland (USD/Hour)
Target Region - Hong Kong (China) and Other Countries/Regions (USD/Hour)
Maximum RPS
Same region
Across region
Same region
Across region
Same region
Across region
micro
0.12
0.16857143
0.22857143
0.32
0.18
0.25142857
1000
small
0.25428571
0.35571429
0.48285714
0.67571429
0.38142857
0.53428571
2000
medium
0.35428571
0.49571429
0.67285714
0.94142857
0.53142857
0.74428571
5000
large
0.53
0.74142857
1.00714286
1.41
0.79571429
1.11428571
11000

Data Subscription Billing Details

Source database region
Link Configuration Fees - Pay-as-You-Go (USD/Hour)
Chinese mainland
0.35714286
Chinese mainland finance zones
0.43714286
Hong Kong (China) and other countries/regions
0.43714286

Existing DTS Task Billing Rules

1. The billing rules for existing data migration tasks are as follows:
After billing started officially, the specifications of existing tasks were switched to xlarge by default, which can be modified for NewDTS but not OldDTS.
The pay-as-you-go billing mode was adopted.
As incremental migration tasks are billed, we recommend that you cut over promptly after migration is completed to avoid incurring unnecessary fees.
2. The billing rules for existing data sync tasks are as follows:
After billing started officially, the specifications of existing tasks were switched to medium by default and can be modified.
The monthly subscription billing mode was adopted, and the uniform expiration date was set to June 15, 2023.
After billing started officially, sync tasks entered the overdue payment status first (and could still be used normally for 24 hours). You needed to renew them in the console; otherwise, they would be suspended after 24 hours and deleted automatically seven days after suspension.
Note:
After billing started and the specifications were switched to the default value, the RPS limits took effect gradually.
Previous Topic: Data Synchronization SpecificationNext Topic: Configuration Change Description

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback