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 Data Transfer
  • Available transfers
  • Getting started
    • All tutorials
      • MySQL® to YDB
      • PostgreSQL to YDB
      • MySQL® to PostgreSQL
      • PostgreSQL to MySQL®
      • MySQL® to Greenplum®
      • OpenSearch in YDB
      • OpenSearch in Greenplum®
      • PostgreSQL in OpenSearch
      • Elasticsearch in OpenSearch
  • Troubleshooting
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials

In this article:

  • Required paid resources
  • Getting started
  • Prepare the test data
  • Set up and activate the transfer
  • Test the transfer
  • Test the copy operation
  • Test the replication process
  • Delete the resources you created
  1. Tutorials
  2. Migration with data storage type changed
  3. MySQL® to PostgreSQL

Migrating data from Yandex Managed Service for MySQL® to Yandex Managed Service for PostgreSQL

Written by
Yandex Cloud
Updated at November 26, 2025
  • Required paid resources
  • Getting started
  • Prepare the test data
  • Set up and activate the transfer
  • Test the transfer
    • Test the copy operation
    • Test the replication process
  • Delete the resources you created

You can set up data transfer from Managed Service for MySQL® to Managed Service for PostgreSQL databases using Data Transfer. To do this:

  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, size of storage and backups (see Managed Service for PostgreSQL pricing).
  • 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).

Getting startedGetting started

Set up the infrastructure:

Manually
Terraform
  1. Create a Managed Service for MySQL® source cluster in any availability zone with publicly available hosts in any suitable configuration with the following settings:

    • DB name: mmy_db
    • Username: mmy_user
    • Password: <source_password>
  2. Grant the REPLICATION CLIENT and REPLICATION SLAVE administrative privileges to mmy_user.

    For more information about administrative privileges, see the settings description.

  3. In the same availability zone, create a Managed Service for PostgreSQL target cluster in any suitable configuration with publicly available hosts and the following settings:

    • DB name: mpg_db
    • Username: mpg_user
    • Password: <target_password>
  4. Make sure that the cluster security groups are set up correctly and allow connecting to them:

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

    This file describes:

    • Networks and subnets where your clusters will be hosted.
    • Security groups for making cluster connections.
    • Managed Service for MySQL® source cluster.
    • Managed Service for PostgreSQL target cluster.
    • Source and target endpoints.
    • Transfer.
  6. Specify the following in mysql-postgresql.tf:

    • MySQL® and PostgreSQL versions
    • MySQL® and PostgreSQL user passwords
  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 test dataPrepare the test data

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

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

Manually
Terraform
  1. Create a source endpoint of the MySQL® type and specify these cluster connection settings in it:

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

    • Installation type: Managed Service for PostgreSQL cluster.
    • Managed Service for PostgreSQL cluster: <PostgreSQL_target_cluster_name> from the drop-down list.
    • Database: mpg_db.
    • User: mpg_user.
    • Password: <user_password>.
  3. Create a transfer of the Snapshot and replication type that will use the endpoints you created.

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

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

  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.

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

Test the transferTest the transfer

To verify that the transfer is operational, test the copy and replication processes.

Test the copy operationTest the copy operation

  1. Connect to the Managed Service for PostgreSQL target cluster database.

  2. Run this query:

    SELECT * FROM mmy_db.measurements;
    

Test the replication processTest the replication process

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

  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. Make sure the new row has been added to the target database:

    1. Connect to the Managed Service for PostgreSQL target cluster database.

    2. Run this query:

      SELECT * FROM mmy_db.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:

Manually
Terraform
  • Transfer
  • Endpoints
  • Managed Service for MySQL® cluster
  • 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
PostgreSQL to YDB
Next
PostgreSQL to MySQL®
© 2025 Direct Cursus Technology L.L.C.