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 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 source cluster
  • Set up and activate the transfer
  • Test the transfer
  • Delete the resources you created
  1. Tutorials
  2. Migration with data storage type changed
  3. PostgreSQL to YDB

Migrating data from PostgreSQL to YDB

Written by
Yandex Cloud
Updated at January 15, 2026
  • Required paid resources
  • Getting started
  • Prepare the source cluster
  • Set up and activate the transfer
  • Test the transfer
  • Delete the resources you created

Managed Service for YDB clusters support real-time data ingestion from PostgreSQL databases. The system will automatically insert this data into YDB tables named after the original schemas and tables.

To start data delivery:

  1. Set up 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 PostgreSQL cluster: Computing resources allocated to hosts, storage and backup size (see Managed Service for PostgreSQL pricing).

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

  • Managed Service for YDB database (see Managed Service for YDB pricing). The cost depends 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, storage size, and backups.

Getting startedGetting started

Set up your data delivery infrastructure:

Manually
Terraform
  1. Create a Managed Service for PostgreSQL source cluster using any suitable configuration with publicly accessible hosts.
  2. Create a Managed Service for YDB database with your preferred configuration.
  3. In the source cluster, create a user and assign them the mdb_replication role.
  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-mpg-ydb.tf configuration file to your current working directory.

    This file describes:

    • Network.
    • Subnet.
    • Security group and the rule required for connecting to the Managed Service for PostgreSQL cluster.
    • Managed Service for PostgreSQL source cluster.
    • PostgreSQL database.
    • Managed Service for PostgreSQL user.
    • Managed Service for YDB database.
    • Source endpoint.
    • Transfer.
  6. In the data-transfer-mpg-ydb.tf file, specify the following settings:

    • source_pg_version: PostgreSQL version in the source cluster.
    • source_db_name: Database name in the source cluster.
    • source_user_name: Username for connecting to the source cluster.
    • source_user_password: User password.
    • target_db_name: Managed Service for YDB database name.
    • transfer_enabled: Set to 0 to prevent the automatic creation of a source endpoint and transfer before you manually create a target endpoint.
  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 the source clusterPrepare the source cluster

  1. Connect to the source cluster’s database with your new user account.

  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 public.sensors (
        "device_id" text PRIMARY KEY 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
    );
    

    Populate the table with data:

    INSERT INTO public.sensors VALUES
        ('iv9a94th6rzt********', '2020-06-05 17:27:00', 55.70329032, 37.65472196,  427.5,    0, 23.5, 17, NULL),
        ('rhibbh3y08qm********', '2020-06-06 09:49:54', 55.71294467, 37.66542005, 429.13, 55.5, NULL, 18, 32),
        ('iv9a94th678t********', '2020-06-07 15:00:10', 55.70985913, 37.62141918,  417.0, 15.7, 10.3, 17, NULL);
    
  3. Prepare the source cluster for transfer.

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 your Managed Service for YDB database from the list.

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

  2. Create a source endpoint and transfer:

    Manually
    Terraform
    1. Create an endpoint for the previously created PostgreSQL source with the following settings:

      • Database type: PostgreSQL.
      • Endpoint parameters:
        • Installation type: Managed Service for PostgreSQL cluster.
        • Managed Service for PostgreSQL cluster: Managed Service for PostgreSQL cluster you created earlier.
        • Database: Name of the database you created in the Managed Service for PostgreSQL cluster.
        • User: Name of the user you created in the Managed Service for PostgreSQL cluster.
        • Password: User password.
        • Included tables: <DB_name>.sensors.
    2. Create a Snapshot and replication-type transfer configured to use the new endpoints.

    3. Activate the transfer.

    1. In the data-transfer-mpg-ydb.tf file, specify the following settings:

      • target_endpoint_id: ID of the target endpoint.
      • transfer_enabled: 1 to create a source endpoint and a transfer.
    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.

      The transfer will activate automatically upon creation.

Test the transferTest the transfer

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

  2. Make sure that the data from the source Managed Service for PostgreSQL cluster has been transferred to the Managed Service for YDB database:

    Management console
    1. In the management console, select the folder containing your database.
    2. From the list of services, select Managed Service for YDB.
    3. Select your database from the list.
    4. Navigate to the Navigation tab.
    5. Verify that the Managed Service for YDB database contains the public_sensors table with test data.
  3. Connect to the Managed Service for PostgreSQL source cluster and populate the sensors table with data:

    INSERT INTO public.sensors VALUES
        ('iv7b74th678t********', '2020-06-08 17:45:00', 53.70987913, 36.62549834, 378.0, 20.5, 5.3, 20, NULL);
    
  4. Verify that the added row’s details have appeared in the Managed Service for YDB database:

    Management console
    YDB CLI
    1. In the management console, select the folder containing your database.
    2. From the list of services, select Managed Service for YDB.
    3. Select your database from the list.
    4. Navigate to the Navigation tab.
    5. Verify that the new data has been added to the public_sensors table.
    1. Connect to the Managed Service for YDB database.

    2. Verify that the new data has been added to the public_sensors table.

      ydb table query execute \
        --query "SELECT * \
        FROM public_sensors"
      

Delete the resources you createdDelete the resources you created

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

Manually
Terraform
  1. Deactivate and delete the transfer.

  2. Delete source and target endpoints.

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

  4. Delete the Managed Service for YDB database.

  5. 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® to YDB
Next
MySQL® to PostgreSQL
© 2026 Direct Cursus Technology L.L.C.