Yandex Cloud
Search
Contact UsTry it for free
  • 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
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 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®
    • Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Delivering data to Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Delivering 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 the test data
  • Create a database in the target cluster
  • 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. Migrating data from Managed Service for MySQL® to Yandex MPP Analytics for PostgreSQL using Yandex Data Transfer

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

Written by
Yandex Cloud
Updated at December 5, 2025
  • Required paid resources
  • Getting started
  • Prepare the test data
  • Create a database in the target cluster
  • 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 a data transfer from Managed Service for MySQL® to Greenplum® databases in Yandex MPP Analytics for PostgreSQL using Data Transfer. To do this:

  1. Prepare the test data.
  2. Create a database in the target cluster.
  3. Prepare and activate your transfer.
  4. 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).
  • Greenplum® cluster: computing resources allocated to hosts, size of storage and backups (see Yandex MPP Analytics for PostgreSQL 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
Using Terraform
  1. Create a Managed Service for MySQL® source cluster in any availability zone with publicly available hosts in any suitable configuration and 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 Greenplum® target cluster in any suitable configuration with publicly available hosts and the following settings:

    • Username: mgp_user.
    • Password: <target_password>.
    • Access from Data Transfer: Enabled.
  4. Make sure that the cluster security groups are set up correctly and allow connecting to them:

    • Managed Service for MySQL®.
    • Yandex MPP Analytics 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 mmy-to-mgp.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.
    • Greenplum® target cluster in Yandex MPP Analytics for PostgreSQL.
    • Source endpoint.
    • Transfer.
  6. Specify the following in mmy-to-mgp.tf:

    • MySQL® and Greenplum® versions
    • MySQL® and Greenplum® 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 mmy_db database in the Managed Service for MySQL® source cluster.

  2. Create a simple table named table1:

    CREATE TABLE table1 (
    id int NOT NULL,
    name varchar (10),
    PRIMARY KEY (id)
    );
    
  3. Populate the table with data:

    INSERT INTO table1 VALUES
    (1, 'Name1'),
    (2, 'Name2'),
    (3, 'Name3');
    

Create a database in the target clusterCreate a database in the target cluster

  1. Connect to the auxiliary postgres database in the Greenplum® target cluster as mgp_user.

  2. Create a database named mgp_db:

    CREATE DATABASE mgp_db;
    

Set up and activate the transferSet up and activate the transfer

  1. Create a Greenplum®-type target endpoint and specify its cluster connection settings:

    • Connection type: Managed Service for Greenplum cluster.
    • Managed Service for Greenplum cluster: <name_of_Greenplum®_target_cluster> from the drop-down list.
    • Database: mgp_db.
    • User: mgp_user.
    • Password: <user_password>.
  2. Create a source endpoint and transfer:

    Manually
    Using 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: <name_of_MySQL®_source_cluster> from the drop-down list.
      • Database: mmy_db.
      • User: mmy_user.
      • Password: <user_password>.
    2. Create a transfer of the Snapshot and replication type that will use the new endpoints.

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

    1. In the mmy-to-mgp.tf file, specify the following settings:

      • target_endpoint_id: Target endpoint ID.
      • transfer_enabled: 1 (create a transfer).
    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 mgp_db in your target Greenplum® cluster.

  2. Run this query:

    SELECT * FROM mmy_db.table1;
    

Test the replication processTest the replication process

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

  2. Populate the table1 table with data:

    INSERT INTO table1 VALUES
    (4, 'Name4');
    
  3. Make sure the new row has been added to the target database:

    1. Connect to mgp_db in your target Greenplum® cluster.

    2. Run this query:

      SELECT * FROM mmy_db.table1;
      

Delete the resources you createdDelete the resources you created

Note

Before deleting the resources, deactivate the transfer.

Some resources are not free of charge. Delete the resources you no longer need to avoid paying for them:

Manually
Using Terraform
  • Transfer
  • Endpoints
  • Managed Service for MySQL® cluster
  • Greenplum® 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
Migrating data from Managed Service for MySQL® to Yandex Managed Service for PostgreSQL using Yandex Data Transfer
Next
Syncing data from a third-party MySQL® cluster to Yandex Managed Service for MySQL® using Yandex Data Transfer
© 2025 Direct Cursus Technology L.L.C.