| title | summary |
|---|---|
Migration Overview |
Learn an overview of data migration scenarios and the solutions for TiDB Cloud. |
You can migrate data from a wide variety of data sources to TiDB Cloud. This document gives an overview of the data migration scenarios.
If your source data is stored in Amazon S3 or Google Cloud Storage (GCS) buckets, before importing or migrating the data to TiDB Cloud, you need to configure access to the buckets. For more information, see Configure Amazon S3 access and GCS access.
TiDB is highly compatible with MySQL. You can migrate data from any MySQL-compatible databases to TiDB Cloud smoothly, whether the data is from a self-hosted MySQL instance or RDS service provided by the public cloud. For more information, see Migrate Data from MySQL-Compatible Databases.
After full data migration, you can also perform incremental data migration from MySQL-compatible databases to TiDB Cloud. For more information, see Migrate Incremental Data from MySQL-Compatible Databases.
If your application uses MySQL shards for data storage, you can migrate these shards into TiDB Cloud as one table. For more information, see Migrate and Merge MySQL Shards of Large Datasets to TiDB Cloud.
You can migrate data from Amazon Aurora MySQL to TiDB Cloud in bulk using the import tools on TiDB Cloud console.
For more information, see Migrate from Amazon Aurora MySQL to TiDB Cloud in Bulk.
You can use Amazon Simple Storage Service (Amazon S3) or Google Cloud Storage (GCS) as a staging area for importing or migrating data into TiDB Cloud.
For more information, see Import or Migrate from Amazon S3 or GCS to TiDB Cloud.
- Import CSV Files from Amazon S3 or GCS into TiDB Cloud
- Import Apache Parquet Files from Amazon S3 or GCS into TiDB Cloud
You can troubleshoot access denied errors that might occur when you import data from Amazon S3 into TiDB Cloud. For more information, see Troubleshoot Access Denied Errors during Data Import from Amazon S3.