Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Managed Service for MySQL®
  • Getting started
    • All tutorials
    • Managed Service for MySQL® performance analysis and tuning
    • Exporting a database to Yandex Data Processing
    • Migrating a database from Managed Service for MySQL® to MySQL®
    • Transferring data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Transferring data to Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Transferring data to Yandex Managed Service for Apache Kafka® using Debezium
    • Migrating a database to Yandex Managed Service for YDB using Yandex Data Transfer
    • Migrating a database from Managed Service for MySQL® to Yandex Object Storage
    • Migrating data from Yandex Object Storage to Managed Service for MySQL®
    • MySQL® change data capture and delivery to YDS
    • Migrating data from Yandex Managed Service for PostgreSQL to Managed Service for MySQL® using Yandex Data Transfer
    • Migrating data from Managed Service for MySQL® to Yandex Managed Service for PostgreSQL using Yandex Data Transfer
    • Migrating data from Managed Service for MySQL® to Yandex MPP Analytics for PostgreSQL using Yandex Data Transfer
    • Syncing data from a third-party MySQL® cluster to Yandex Managed Service for MySQL® using Yandex Data Transfer
    • Migrating a database from MySQL® to ClickHouse® using Yandex Data Transfer
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Required paid resources
  • Getting started
  • Prepare your test data
  • Set up and activate the transfer
  • Test your transfer
  • Test copying
  • Test replication
  • Delete the resources you created
  1. Tutorials
  2. Migrating data from Yandex Managed Service for PostgreSQL to Managed Service for MySQL® using Yandex Data Transfer

Migrating data from Yandex Managed Service for PostgreSQL to Managed Service for MySQL® using Yandex Data Transfer

Written by
Yandex Cloud
Updated at January 15, 2026
  • Required paid resources
  • Getting started
  • Prepare your test data
  • Set up and activate the transfer
  • Test your transfer
    • Test copying
    • Test replication
  • Delete the resources you created

You can set up a data transfer from a Managed Service for PostgreSQL database to a Managed Service for MySQL® database using Data Transfer. Proceed as follows:

  1. Prepare the test data.
  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 PostgreSQL cluster: Computing resources allocated to hosts, storage and backup size (see Managed Service for PostgreSQL pricing).
  • Managed Service for MySQL® cluster: Computing resources allocated to hosts, storage and backup size (see Managed Service for MySQL® pricing).
  • Public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).

Getting startedGetting started

Set up the infrastructure:

Manually
Terraform
  1. Create a Managed Service for PostgreSQL source cluster in any availability zone with publicly accessible hosts (of any suitable configuration) and the following settings:

    • DB name: mpg_db
    • Username: mpg_user
    • Password: <source_password>
  2. Grant the mdb_replication role to mpg_user.

  3. In the same availability zone, create a Managed Service for MySQL® target cluster with publicly accessible hosts (of any suitable configuration) and the following settings:

    • DB name: mmy_db
    • Username: mmy_user
    • Password: <target_password>
  4. Make sure the cluster security groups are properly configured and allow inbound cluster connections:

    • Managed Service for PostgreSQL
    • Managed Service for MySQL®
  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 postgresql-mysql.tf configuration file to your current working directory.

    This file describes:

    • Networks and subnets where your clusters will be hosted.
    • Security groups for cluster access.
    • Managed Service for PostgreSQL source cluster.
    • Managed Service for MySQL® target cluster.
    • Source and target endpoints.
    • Transfer.
  6. In the postgresql-mysql.tf file, specify the following:

    • MySQL® and PostgreSQL versions
    • MySQL® and PostgreSQL user passwords
  7. Validate your Terraform configuration files using this command:

    terraform validate
    

    Terraform will display any configuration errors detected in your 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 your test dataPrepare your test data

  1. Connect to the database in the Managed Service for PostgreSQL source cluster.

  2. Populate the database with test data. In this example, we will use a simple table with car sensor information.

    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

Manually
Terraform
  1. Create a PostgreSQL-type source endpoint and configure it using the following settings:

    • Installation type: Managed Service for PostgreSQL cluster.
    • Managed Service for PostgreSQL cluster: <PostgreSQL_source_cluster_name> from the drop-down list.
    • Database: mpg_db.
    • User: mpg_user.
    • Password: <user_password>.
  2. Create a MySQL®-type target endpoint and specify its cluster connection settings:

    • Connection type: Managed Service for MySQL cluster.
    • Managed Service for MySQL cluster: <MySQL®_target_cluster_name> from the drop-down list.
    • Database: mmy_db.
    • User: mmy_user.
    • Password: <user_password>.
  3. Create a Snapshot and replication-type transfer configured to use the new endpoints.

  4. Activate the transfer and wait for its status to change to Replicating.

  1. In the postgresql-mysql.tf file, set transfer_enabled to 1.

  2. Validate your Terraform configuration files using this command:

    terraform validate
    

    Terraform will display any configuration errors detected in your 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.

  4. The transfer will activate automatically upon creation. Wait for its status to change to Replicating.

Note

If the transfer activation fails with the Unable to push DDL error:

  1. Connect to the target database and create an empty table measurements with the same schema as the source table.
  2. Restart the transfer.

Test your transferTest your transfer

Make sure the transfer works correctly by testing copying and replication.

Test copyingTest copying

  1. Connect to the database in the Managed Service for MySQL® target cluster.

  2. Verify that the source table has been transferred to the target database by running this query:

    SELECT * FROM measurements;
    

Test replicationTest replication

  1. Connect to the database in the Managed Service for PostgreSQL source cluster.

  2. 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);
    
  3. Check that the added row appears in the target database:

    1. Connect to the database in the Managed Service for MySQL® target cluster.

    2. Run this query:

      SELECT * FROM measurements;
      

Delete the resources you createdDelete the resources you created

Note

Before deleting the resources, deactivate the transfer.

To reduce the consumption of resources you do not need, delete them:

Manually
Terraform
  1. Delete the transfer.
  2. Delete the endpoints.
  3. Delete the Managed Service for MySQL® cluster.
  4. Delete the Managed Service for PostgreSQL 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
MySQL® change data capture and delivery to YDS
Next
Migrating data from Managed Service for MySQL® to Yandex Managed Service for PostgreSQL using Yandex Data Transfer
© 2026 Direct Cursus Technology L.L.C.