Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Data Transfer
  • Available transfers
  • Getting started
    • All tutorials
      • PostgreSQL cluster
      • Data in MySQL®
      • Third-party MySQL® cluster
      • MongoDB cluster
      • Migrating MongoDB cluster from 4.4 to 6.0
      • ClickHouse® cluster
      • Data resharding in a Managed Service for ClickHouse® cluster
      • Greenplum® cluster
      • Migrating data from AWS RDS for PostgreSQL
      • OpenSearch cluster
  • Troubleshooting
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials

In this article:

  • Required paid resources
  • Start data transfer
  • Finish data transfer
  • Delete the resources you created
  • See also
  1. Tutorials
  2. Migration
  3. Data in MySQL®

Migrating MySQL® clusters

Written by
Yandex Cloud
Updated at May 5, 2025
  • Required paid resources
  • Start data transfer
  • Finish data transfer
  • Delete the resources you created
  • See also

With Data Transfer, you can transfer data from a third-party source cluster to a Managed Service for MySQL® target cluster.

This method allows you to migrate the entire database without interrupting user service. To use it, allow connections to the source cluster from the internet.

To transfer a database from MySQL® to Managed Service for MySQL®:

  1. Start data transfer.
  2. Finish data transfer.

If you no longer need the resources you created, delete them.

Required paid resourcesRequired paid resources

The support cost includes:

  • Managed Service for MySQL® cluster fee: Using computing resources allocated to hosts and disk space (see Managed Service for MySQL® pricing).
  • Fee for using public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
  • Transfer fee: Using computing resources and the number of transferred data rows (see Data Transfer pricing).

Start data transferStart data transfer

  1. Prepare the source cluster.

  2. Prepare the infrastructure and start the data transfer:

    Manually
    Terraform
    1. Create a Managed Service for MySQL® target cluster in any suitable configuration. In this case, the following applies:

      • The MySQL® version must be the same or higher than in the source cluster.

        Transferring data with MySQL® major version upgrade is possible but not guaranteed. For more information, see the MySQL® documentation.

        You cannot perform migration while downgrading MySQL® version.

      • SQL mode must be the same as in the source cluster.

    2. Prepare the target cluster.

    3. Create a source endpoint:

      • Database type: MySQL

      • Endpoint parameters → Connection settings: Custom installation

        Specify the parameters for connecting to the source cluster.

    4. Create a target endpoint:

      • Database type: MySQL

      • Endpoint parameters → Connection settings: Managed Service for MySQL cluster

        Select a target cluster from the list and specify its connection settings.

    5. Create a transfer of the Snapshot and increment type that will use the created endpoints.

    6. Activate your transfer.

      Warning

      Abstain from making any changes to the data schema in the source and target clusters when the data transfer is running. To learn more, see Working with databases during transfer.

    1. Prepare the source cluster.

    2. If you do not have Terraform yet, install it.

    3. Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.

    4. Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it.

    5. Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.

    6. Download the data-transfer-mysql-mmy.tf configuration file to the same working directory.

      This file describes:

      • Network.
      • Subnet.
      • Security group and the rule required to connect to a cluster.
      • Managed Service for MySQL® target cluster.
      • Source endpoint.
      • Target endpoint.
      • Transfer.
    7. Specify the following in the data-transfer-mysql-mmy.tf file:

      • Source endpoint parameters.

      • Target cluster parameters also used as target endpoint parameters:

        • target_mysql_version: MySQL® version. Must be the same or higher than in the source cluster.
        • target_sql_mode: SQL mode. It must be the same as in the source cluster.
        • target_db_name: Database name.
        • target_user and target_password: Name and user password of the database owner.
    8. Make sure the Terraform configuration files are correct using this command:

      terraform validate
      

      If there are any errors in the configuration files, Terraform will point them out.

    9. Create the required infrastructure:

      1. Run this command to view the planned changes:

        terraform plan
        

        If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

      2. If everything looks correct, apply the changes:

        1. Run this command:

          terraform apply
          
        2. Confirm updating the resources.

        3. Wait for the operation to complete.

      All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

      Once created, your transfer will be activated automatically.

Finish data transferFinish data transfer

  1. Wait for the transfer status to change to Replicating.

  2. Switch the source cluster to read-only mode and transfer the load to the target cluster.

  3. On the transfer monitoring page, wait for the Maximum data transfer delay metric to decrease to zero. This means that all changes that occurred in the source cluster after data was copied are transferred to the target cluster.

  4. Deactivate the transfer and wait for its status to change to Stopped.

    For more information about transfer statuses, see Transfer lifecycle.

Delete the resources you createdDelete the resources you created

Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:

Manually
Terraform
  • Delete the Managed Service for MySQL® cluster.
  • Delete the stopped transfer.
  • Delete the endpoints for both the source and target.
  1. In the terminal window, go to the directory containing the infrastructure plan.

    Warning

    Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

  2. Delete resources:

    1. Run this command:

      terraform destroy
      
    2. Confirm deleting the resources and wait for the operation to complete.

    All the resources described in the Terraform manifests will be deleted.

For a real example of MySQL® database migration using Data Transfer, see Syncing MySQL data using Yandex Data Transfer.

See alsoSee also

For other migration methods, see the Yandex Managed Service for MySQL® documentation.

Was the article helpful?

Previous
PostgreSQL cluster
Next
Third-party MySQL® cluster
Yandex project
© 2025 Yandex.Cloud LLC