Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for YDB
  • Getting started
    • All tutorials
    • Deploying a web application
    • Connecting to YDB from a Yandex Cloud Functions function in Python
    • Connecting to a YDB database from a Yandex Cloud Functions function in Node.js
    • Converting a video to a GIF in Python
    • Creating a skill for Alice and a website with authorization
    • Migrating a database from Yandex Managed Service for MySQL® using Yandex Data Transfer
    • Delivering data from YDB to Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Delivering data from YDB to Yandex Data Streams using Yandex Data Transfer
    • Loading data from Yandex Object Storage to YDB using Yandex Data Transfer
    • Loading data from YDB to Yandex Object Storage using Yandex Data Transfer
    • Loading data from YDB to Yandex Managed Service for ClickHouse® using Yandex Data Transfer
    • Migrating data from Yandex Managed Service for OpenSearch to YDB using Yandex Data Transfer
    • Building a CI/CD pipeline in GitLab with serverless products
    • Delivering data from Yandex Managed Service for PostgreSQL to Yandex Managed Service for YDB using Yandex Data Transfer
    • Streaming Yandex Cloud Postbox events to Yandex Data Streams and analyzing them with Yandex DataLens
    • Delivering data from Yandex Managed Service for Apache Kafka® to Data Streams using Yandex Data Transfer
    • Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Saving a data stream from Data Streams to Managed Service for ClickHouse®
    • Delivering data from a Data Streams queue to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from a Data Streams queue to Managed Service for YDB using Data Transfer
    • MySQL® change data capture and delivery to YDS
    • PostgreSQL change data capture and delivery to YDS
    • Interactive debugging of Cloud Functions
    • Locking Terraform states using Managed Service for YDB
    • Developing a custom integration in API Gateway
    • Developing CRUD APIs for movie services
    • Building an interactive serverless application using WebSocket
    • URL shortener
    • Uploading audit logs to MaxPatrol SIEM
    • Yandex Cloud Postbox integration with external systems via webhooks
  • Access management
  • Monitoring metrics
  • Audit Trails events
  • FAQ
  • Public materials

In this article:

  • Required paid resources
  • Set up the infrastructure
  • Prepare the source cluster
  • Set up and activate the transfer
  • Test the transfer
  • Delete the resources you created
  1. Tutorials
  2. Migrating a database from Yandex Managed Service for MySQL® using Yandex Data Transfer

Migrating a database from Yandex Managed Service for MySQL® to YDB using Yandex Data Transfer

Written by
Yandex Cloud
Updated at November 26, 2025
  • Required paid resources
  • Set up the infrastructure
  • Prepare the source cluster
  • Set up and activate the transfer
  • Test the transfer
  • Delete the resources you created

Data Transfer enables you to transfer data from a Managed Service for MySQL® source cluster to Managed Service for YDB.

To transfer data:

  1. Prepare the source cluster.
  2. Set up and activate the transfer.
  3. Test your transfer.

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

Required paid resourcesRequired paid resources

  • Managed Service for MySQL® cluster: computing resources allocated to hosts, size of storage and backups (see Managed Service for MySQL® pricing).

  • Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).

  • Each transfer: use of computing resources and number of transferred data rows (see Data Transfer pricing).

  • Managed Service for YDB database. Its pricing is based on deployment mode:

    • In serverless mode, you pay for data operations and storage volume, including stored backups.
    • In dedicated instance mode, you pay for the use of computing resources allocated to the database, size of storage and backups.

    See Managed Service for YDB pricing.

Set up the infrastructureSet up the infrastructure

Manually
Terraform
  1. Create a Managed Service for MySQL® source cluster in any suitable configuration.

  2. Create a Managed Service for YDB database with your preferred configuration.

  3. If using security groups, configure them to allow internet access to your cluster.

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

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

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

  4. 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.

  5. Download the data-transfer-mmy-ydb.tf configuration file to the same working directory.

    This file describes:

    • Network.
    • Subnet.
    • Security group and the rule permitting access to the Managed Service for MySQL® cluster.
    • Managed Service for MySQL® source cluster.
    • Managed Service for YDB database.
    • Source endpoint.
    • Transfer.
  6. In the data-transfer-mmy-ydb.tf file, specify the following:

    • The Managed Service for MySQL® source cluster parameters that will be used as the source endpoint parameters:

      • source_mysql_version: MySQL® version.
      • source_db_name: Database name.
      • source_user and source_password: Database owner username and password.
    • target_db_name: Managed Service for YDB database name.

  7. Make sure the Terraform configuration files are correct using this command:

    terraform validate
    

    Terraform will show any errors found in your configuration files.

  8. 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.

Prepare the source clusterPrepare the source cluster

  1. If you created the infrastructure manually, prepare the source cluster.

  2. Connect to the Managed Service for MySQL® source cluster.

  3. Add test data to the database. As an example, we will use a simple table with information transmitted by car sensors.

    Create a table:

    CREATE TABLE measurements (
        device_id varchar(200) NOT NULL,
        datetime timestamp NOT NULL,
        latitude real NOT NULL,
        longitude real NOT NULL,
        altitude real NOT NULL,
        speed real NOT NULL,
        battery_voltage real,
        cabin_temperature real NOT NULL,
        fuel_level real,
        PRIMARY KEY (device_id)
    );
    

    Populate the table with data:

    INSERT INTO measurements VALUES
        ('iv9a94th6rzt********', '2022-06-05 17:27:00', 55.70329032, 37.65472196,  427.5,    0, 23.5, 17, NULL),
        ('rhibbh3y08qm********', '2022-06-06 09:49:54', 55.71294467, 37.66542005, 429.13, 55.5, NULL, 18, 32);
    

Set up and activate the transferSet up and activate the transfer

  1. Create a target endpoint:

    • Database type: YDB.

    • Endpoint parameters:

      • Connection settings → Database: Select the Managed Service for YDB database from the list.

      • Service account ID: Select or create a new service account with the ydb.editor role.

  2. Create a source endpoint and transfer:

    Manually
    Terraform
    1. Create a source endpoint:

      • Database type: MySQL®

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

        Select your source cluster from the list and specify its connection settings.

    2. Create a transfer of the Snapshot and replication type that will use the new endpoints.

    3. Activate the transfer.

    1. In the data-transfer-mmy-ydb.tf file, uncomment the following:

      • target_endpoint_id variable. Also, set it to the value of the endpoint ID for the target created in the previous step.
      • yandex_datatransfer_endpoint and yandex_datatransfer_transfer resources.
    2. Make sure the Terraform configuration files are correct using this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

    3. 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.

      The transfer will activate automatically upon creation.

Test the transferTest the transfer

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

  2. Verify that the data has been transferred from the source Managed Service for MySQL® cluster to the Managed Service for YDB database:

    Management console
    CLI
    1. In the management console, select the folder with the DB you need.
    2. From the list of services, select Managed Service for YDB.
    3. Select the database from the list.
    4. Navigate to the Navigation tab.
    5. Check that the Managed Service for YDB database contains the <source_cluster_DB_name>_measurements table with test data.
    1. Connect to the Managed Service for YDB database.

    2. Check that the database contains the <source_cluster_DB_name>_measurements table with test data:

      SELECT *
      FROM <source_cluster_DB_name>_measurements;
      
  3. Connect to the Managed Service for MySQL® source cluster and populate the measurements table with data:

    INSERT INTO measurements VALUES
        ('iv7b74th678t********', '2020-06-08 17:45:00', 53.70987913, 36.62549834, 378.0, 20.5, 5.3, 20, NULL);
    
  4. Check that the Managed Service for YDB database shows information about the added row:

    Management console
    CLI
    1. In the management console, select the folder with the DB you need.
    2. From the list of services, select Managed Service for YDB.
    3. Select the database from the list.
    4. Navigate to the Navigation tab.
    5. Check that new data has been added to the <source_cluster_DB_name>_measurements table.
    1. Connect to the Managed Service for YDB database.

    2. Check that new data has been added to the <source_cluster_DB_name>_measurements table:

      SELECT *
      FROM <source_cluster_DB_name>_measurements;
      

Delete the resources you createdDelete the resources you created

Note

Before deleting the resources, deactivate the transfer.

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

  1. Delete the transfer.

  2. Delete the target endpoint.

  3. If you created a service account when creating the target endpoint, delete it.

Delete the other resources depending on how you created them:

Manually
Terraform
  • Delete the source endpoint.
  • Delete the Managed Service for YDB database.
  • Delete the Managed Service for MySQL® cluster.
  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.

Was the article helpful?

Previous
Creating a skill for Alice and a website with authorization
Next
Delivering data from YDB to Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
© 2025 Direct Cursus Technology L.L.C.