Yandex Cloud
Search
Discuss with expertTry 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
      • PostgreSQL cluster
      • Migrating a Managed Service for PostgreSQL cluster to another version
      • Data in MySQL®
      • Third-party MySQL® cluster
      • MongoDB cluster
      • Migrating a Yandex StoreDoc (Managed Service for MongoDB) cluster from 4.4 to 6.0
      • ClickHouse® cluster
      • Greenplum® cluster
      • Migrating data from AWS RDS for PostgreSQL
      • OpenSearch cluster
  • Troubleshooting
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials

In this article:

  • Required paid resources
  • Getting started
  • Transferring data
  1. Tutorials
  2. Migration
  3. Greenplum® cluster

Migrating Greenplum® clusters

Written by
Yandex Cloud
Updated at May 14, 2026
  • Required paid resources
  • Getting started
  • Transferring data

You can migrate your database from a third-party Greenplum® or PostgreSQL cluster to Yandex MPP Analytics for PostgreSQL using Yandex Data Transfer. This method enables you to:

  • Migrate your database with zero downtime.
  • Migrate from older to newer versions of Greenplum®.
  • Eliminate the need for an intermediate VM or for exposing your Managed Service for PostgreSQL target cluster to the internet.

For more information, see Problems addressed by Yandex Data Transfer.

Note

Data Transfer enables you to transfer the state of the source database to the Yandex MPP Analytics for PostgreSQL target without keeping it up-to-date (the Snapshot transfer type). Changes occurring on the source after the transfer is completed will not be transferred.

To migrate your database, you need to directly transfer the data, acquire a write lock for the old database, and switch over the load to the database cluster in Yandex Cloud.

Required paid resourcesRequired paid resources

  • Yandex MPP Analytics for PostgreSQL cluster, which includes the use of computing resources allocated to hosts, storage and backup size (see Yandex MPP Analytics for PostgreSQL pricing).
  • Each transfer: use of computing resources and the number of transferred data rows (see Data Transfer pricing).
  • Public IP addresses if public access is enabled for cluster hosts (see Yandex Virtual Private Cloud pricing).

Getting startedGetting started

Create a Greenplum® target cluster with computing capacity and storage size matching the source database’s environment.

The source and target database names must be the same.

Transferring dataTransferring data

  1. Prepare the source cluster:

    • Greenplum®
    • PostgreSQL
  2. Prepare the target cluster.

  3. Create a source endpoint with the following settings:

    • Database type: Greenplum or PostgreSQL.

    • Endpoint parameters → Connection settings: Custom installation.

      Configure the source cluster connection settings.

  4. Create a target endpoint with the following settings:

    • Database type: Greenplum.

    • Endpoint parameters → Connection settings: Managed Service for Greenplum cluster.

      Specify the target cluster ID.

  5. Create a transfer of the Snapshot-type that will use the new endpoints.

  6. Activate the transfer.

  7. Wait for the transfer status to change to Completed.

    For more information about transfer statuses, see Transfer lifecycle.

  8. Switch the source cluster to read-only mode and transfer the workload over to the target cluster.

  9. To minimize resource consumption, delete the resources you no longer need:

    1. Delete the completed transfer.
    2. Delete the source and target endpoints.

Greenplum® and Greenplum Database® are registered trademarks or trademarks of Broadcom Inc. in the United States and/or other countries.

Was the article helpful?

Previous
ClickHouse® cluster
Next
Migrating data from AWS RDS for PostgreSQL
© 2026 Direct Cursus Technology L.L.C.