Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Tutorials
    • All tutorials
    • Deploying the Apache Kafka® web interface
    • Migrating a database from a third-party Apache Kafka® cluster to Managed Service for Apache Kafka®
    • Moving data between Managed Service for Apache Kafka® clusters using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Debezium
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Debezium
    • Delivering data from Managed Service for YDB to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for ClickHouse® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for Greenplum® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for MongoDB using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for MySQL® using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for OpenSearch using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for PostgreSQL using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Managed Service for YDB using Data Transfer
    • Delivering data from Managed Service for Apache Kafka® to Data Streams using Data Transfer
    • Delivering data from Data Streams to Managed Service for YDB using Data Transfer
    • Delivering data from Data Streams to Managed Service for Apache Kafka® using Data Transfer
    • YDB change data capture and delivery to YDS
    • Configuring Kafka Connect to work with a Managed Service for Apache Kafka® cluster
    • Automating Query tasks with Managed Service for Apache Airflow™
    • Sending requests to the Yandex Cloud API via the Yandex Cloud Python SDK
    • Configuring an SMTP server to send e-mail notifications
    • Adding data to a ClickHouse® DB
    • Migrating data to Managed Service for ClickHouse® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for ClickHouse® using Data Transfer
    • Asynchronously replicating data from PostgreSQL to ClickHouse®
    • Exchanging data between Managed Service for ClickHouse® and Yandex Data Processing
    • Configuring Managed Service for ClickHouse® for Graphite
    • Fetching data from Managed Service for Apache Kafka® to Managed Service for ClickHouse®
    • Fetching data from Managed Service for Apache Kafka® to ksqlDB
    • Fetching data from RabbitMQ to Managed Service for ClickHouse®
    • Saving a Data Streams data stream in Managed Service for ClickHouse®
    • Asynchronous replication of data from Yandex Metrica to ClickHouse® using Data Transfer
    • Using hybrid storage in Managed Service for ClickHouse®
    • Sharding Managed Service for ClickHouse® tables
    • Data resharding in a Managed Service for ClickHouse® cluster
    • Loading data from Yandex Direct to a data mart enabled by Managed Service for ClickHouse® using Cloud Functions, Object Storage, and Data Transfer
    • Loading data from Object Storage to Managed Service for ClickHouse® using Data Transfer
    • Migrating data with change of storage from Managed Service for OpenSearch to Managed Service for ClickHouse® using Data Transfer
    • Loading data from Managed Service for YDB to Managed Service for ClickHouse® using Data Transfer
    • Migrating databases from Google BigQuery to Managed Service for ClickHouse®
    • Configuring Cloud DNS to access a Managed Service for ClickHouse® cluster from other cloud networks
    • Migrating a Yandex Data Processing HDFS cluster to a different availability zone
    • Importing data from Managed Service for MySQL® to Yandex Data Processing using Sqoop
    • Importing data from Managed Service for PostgreSQL to Yandex Data Processing using Sqoop
    • Mounting Object Storage buckets to the file system of Yandex Data Processing hosts
    • Working with Apache Kafka® topics using Yandex Data Processing
    • Automating operations with Yandex Data Processing using Managed Service for Apache Airflow™
    • Shared use of Yandex Data Processing tables through Metastore
    • Transferring metadata between Yandex Data Processing clusters using Metastore
    • Importing data from Object Storage, processing and exporting to Managed Service for ClickHouse®
    • Migrating to Managed Service for Elasticsearch using snapshots
    • Migrating collections from a third-party MongoDB cluster to Managed Service for MongoDB
    • Migrating data to Managed Service for MongoDB
    • Migrating Managed Service for MongoDB cluster from 4.4 to 6.0
    • Sharding MongoDB collections
    • MongoDB performance analysis and tuning
    • Migrating a database from a third-party MySQL® cluster to a Managed Service for MySQL® cluster
    • Managed Service for MySQL® performance analysis and tuning
    • Syncing data from a third-party MySQL® cluster to Managed Service for MySQL® using Data Transfer
    • Migrating a database from Managed Service for MySQL® to a third-party MySQL® cluster
    • Migrating a database from Managed Service for MySQL® to Object Storage using Data Transfer
    • Migrating data from Object Storage to Managed Service for MySQL® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for MySQL® to Managed Service for Apache Kafka® using Debezium
    • Migrating a database from Managed Service for MySQL® to Managed Service for YDB using Data Transfer
    • MySQL® change data capture and delivery to YDS
    • Migrating data from Managed Service for MySQL® to Managed Service for PostgreSQL using Data Transfer
    • Migrating data from AWS RDS for PostgreSQL to Managed Service for PostgreSQL using Data Transfer
    • Migrating data from Managed Service for MySQL® to Managed Service for Greenplum® using Data Transfer
    • Configuring an index policy in Managed Service for OpenSearch
    • Migrating data from Elasticsearch to Managed Service for OpenSearch
    • Migrating data from a third-party OpenSearch cluster to Managed Service for OpenSearch using Data Transfer
    • Loading data from Managed Service for OpenSearch to Object Storage using Data Transfer
    • Migrating data from Managed Service for OpenSearch to Managed Service for YDB using Data Transfer
    • Copying data from Managed Service for OpenSearch to Managed Service for Greenplum® using Yandex Data Transfer
    • Migrating data from Managed Service for PostgreSQL to Managed Service for OpenSearch using Data Transfer
    • Authenticating a Managed Service for OpenSearch cluster in OpenSearch Dashboards using Keycloak
    • Using the yandex-lemmer plugin in Managed Service for OpenSearch
    • Creating a PostgreSQL cluster for 1C:Enterprise
    • Searching for the Managed Service for PostgreSQL cluster performance issues
    • Managed Service for PostgreSQL performance analysis and tuning
    • Logical replication PostgreSQL
    • Migrating a database from a third-party PostgreSQL cluster to Managed Service for PostgreSQL
    • Migrating a database from Managed Service for PostgreSQL
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Data Transfer
    • Delivering data from Managed Service for PostgreSQL to Managed Service for Apache Kafka® using Debezium
    • Delivering data from Managed Service for PostgreSQL to Managed Service for YDB using Data Transfer
    • Migrating a database from Managed Service for PostgreSQL to Object Storage
    • Migrating data from Object Storage to Managed Service for PostgreSQL using Data Transfer
    • PostgreSQL change data capture and delivery to YDS
    • Migrating data from Managed Service for PostgreSQL to Managed Service for MySQL® using Data Transfer
    • Migrating data from Managed Service for PostgreSQL to Managed Service for OpenSearch using Data Transfer
    • Troubleshooting string sorting issues in PostgreSQL after upgrading glibc
    • Migrating a database from Greenplum® to ClickHouse®
    • Migrating a database from Greenplum® to PostgreSQL
    • Exporting Greenplum® data to a cold storage in Object Storage
    • Loading data from Object Storage to Managed Service for Greenplum® using Data Transfer
    • Copying data from Managed Service for OpenSearch to Managed Service for Greenplum® using Yandex Data Transfer
    • Creating an external table from a Object Storage bucket table using a configuration file
    • Migrating a database from a third-party Valkey™ cluster to Yandex Managed Service for Valkey™
    • Using a Yandex Managed Service for Valkey™ cluster as a PHP session storage
    • Loading data from Object Storage to Managed Service for YDB using Data Transfer
    • Loading data from Managed Service for YDB to Object Storage using Data Transfer
    • Processing Audit Trails events
    • Processing Cloud Logging logs
    • Processing CDC Debezium streams
    • Analyzing data with Jupyter
    • Processing files with usage details in Yandex Cloud Billing
    • Entering data into storage systems
    • Smart log processing
    • Transferring data within microservice architectures
    • Migrating data to Object Storage using Data Transfer
    • Migrating data from a third-party Greenplum® or PostgreSQL cluster to Managed Service for Greenplum® using Data Transfer
    • Migrating Managed Service for MongoDB clusters
    • Migrating MySQL® clusters
    • Migrating to a third-party MySQL® cluster
    • Migrating PostgreSQL clusters
    • Creating a schema registry to deliver data in Debezium CDC format from Apache Kafka®

In this article:

  • Required paid resources
  • Getting started
  • Migrating data using Yandex Data Transfer
  • Example of migrating a collection
  • Set up the source cluster
  • Create and configure a target cluster
  • Set up endpoints and a transfer
  • Transfer the data
  • Delete the resources you created
  1. Building a data platform
  2. Migrating collections from a third-party MongoDB cluster to Managed Service for MongoDB

Migrating collections from MongoDB to Managed Service for MongoDB

Written by
Yandex Cloud
Updated at April 25, 2025
  • Required paid resources
  • Getting started
  • Migrating data using Yandex Data Transfer
  • Example of migrating a collection
    • Set up the source cluster
    • Create and configure a target cluster
    • Set up endpoints and a transfer
    • Transfer the data
    • Delete the resources you created

To migrate collections stored in a third-party MongoDB cluster to a Managed Service for MongoDB cluster, you need to transfer the data, write-lock the old database, and transfer the load to a Yandex Cloud cluster.

Required paid resourcesRequired paid resources

The support cost includes:

  • Managed Service for MongoDB target cluster fee: Using computing resources allocated to hosts, and its disk space (see MongoDB pricing).
  • Per-transfer fee: Using computing resources and the number of transferred data rows (see Data Transfer pricing).
  • Fee for using public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).

Getting startedGetting started

Make sure that you can connect to the source cluster hosts from the internet.

Migrating data using Yandex Data TransferMigrating data using Yandex Data Transfer

  1. Prepare the source cluster.

  2. Prepare the target cluster.

  3. Create a source endpoint with the following parameters:

    • Database type: MongoDB

    • Endpoint parameters → Connection settings: Custom installation

      Specify the parameters for connecting to the source cluster.

    Note

    The service does not support transferring Time Series collections, so you should exclude these collections in the endpoint settings.

  4. Create a target endpoint with the following parameters:

    • Database type: MongoDB

    • Endpoint parameters → Connection settings: Managed Service for MongoDB cluster

      Specify the ID of the target cluster.

  5. Create a transfer of the Snapshot and increment type that will use the created endpoints.

    To make large collections (over 1 GB) copy more quickly, enable parallel copy in the transfer settings. Specify two or more workers. The collection will split into the specified number of parts that will be copied concurrently.

    For parallel copy to work, the data type in the _id field should be the same for all documents in a collection. If a transfer discovers a type mismatch, the collection will not be partitioned but transferred in a single thread instead. If needed, remove documents with mismatched data types from the collection before starting a transfer.

    Note

    If a document with a different data type is added to a collection after a transfer starts, the transfer will move it at the replication stage after the parallel copy operation is completed. However, when re-enabled, the transfer will not be able to partition a collection because the _id field's type requirement will not be met for some of the documents in the collection.

  6. Activate the transfer.

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

  8. Switch the source cluster to read-only and transfer the load to the target cluster.

  9. On the transfer monitoring page, wait for the Maximum data transfer delay metric to decrease to zero. This means that all changes that occurred in the source cluster after data copying was completed are transferred to the target cluster.

  10. Deactivate the transfer and wait for its status to change to Stopped.

    For more information about transfer statuses, see Transfer lifecycle.

  11. Delete the stopped transfer.

  12. Delete endpoints for both the source and target.

Example of migrating a collectionExample of migrating a collection

  1. Set up the source cluster.
  2. Create and configure a target cluster.
  3. Set up endpoints and a transfer.
  4. Transfer data.
  5. Delete the resources you created.

Set up the source clusterSet up the source cluster

  1. Connect to the mongos host of the MongoDB source cluster using mongosh.

  2. Create a db1 database.

  3. Create a user with the db1 owner permissions and log in with that user's credentials:

    use admin
    db.createUser({
      user: "user1",
      pwd: passwordPrompt(),
      roles: [
          {
              role: "dbOwner",
              db: "db1"
          }
      ]
    })
    
    db.auth("user1")
    
  4. Fill in collection1 in db1 with random values. 200,000 entries will be added to the collection:

    use db1
    function randomName() {
      // Base 36 uses letters and digits to represent a number:
      return (Math.random()+1).toString(36).substring(2);
    }
    
    var day = 1000 * 60 * 60 * 24;
    function randomDate () {
      return new Date(Date.now() - (Math.floor(Math.random() * day)));
    }
    
    for (var i = 1; i <= 200000; ++i) {
      db.collection1.insertOne({
       name: randomName(),
       creationDate: randomDate(),
       uid: i
      });
    }
    

Create and configure a target clusterCreate and configure a target cluster

Non-sharded target cluster
Sharded target cluster
  1. Create a Managed Service for MongoDB cluster with any suitable configuration.
  2. Create a database named db1.
  3. Create a user named user_transfer with the readWrite role for the new database.
  1. Create a Managed Service for MongoDB cluster with any suitable configuration. There must be at least two hosts in the cluster.
  2. Enable sharding.
  3. Create a database named db1.
  4. Create a user named user_transfer with the readWrite role for the created database and the mdbShardingManager role for the admin service base.
  5. Following these steps, create an empty sharded collection named collection1 in db1 and configure it.

Set up endpoints and a transferSet up endpoints and a transfer

Non-sharded target cluster
Sharded target cluster
  1. Create an endpoint for the source cluster:
    • Database type: MongoDB
    • Connection settings: Custom installation
      • CA certificate: Upload the certificate file if a connection to the source cluster requires encryption.
      • Host list: Specify the FQDN of the source cluster hosts.
      • Port: Specify the port for connecting to the hosts.
      • Authentication source: db1
      • User: user1
      • Password: Enter the user1 password.
  2. Create an endpoint for the target cluster:
    • Database type: MongoDB
    • Connection settings: MDB cluster.
      • Specify the ID of the target cluster.
      • User: user_transfer
      • Password: Enter the user_transfer password.
      • Cleanup policy: Drop
  3. Create a transfer:
    • Transfer type: Snapshot and increment
    • Source: Select the created endpoint for the source cluster.
    • Target: Select the created endpoint for the target cluster.
  1. Create an endpoint for the source cluster:
    • Database type: MongoDB
    • Connection settings: Custom installation
      • CA certificate: Upload the certificate file if a connection to the source cluster requires encryption.
      • Host list: Specify the FQDN of the source cluster hosts.
      • Port: Specify the port for connecting to the hosts.
      • Authentication source: db1
      • User: user1
      • Password: Enter the user1 password.
  2. Create an endpoint for the target cluster:
    • Database type: MongoDB
    • Connection settings: MDB cluster.
      • Specify the ID of the target cluster.
      • User: user_transfer
      • Password: Enter the user_transfer password.
      • Cleanup policy: Don't cleanup or Truncate.
  3. Create a transfer:
    • Transfer type: Snapshot and increment
    • Source: Select the created endpoint for the source cluster.
    • Target: Select the created endpoint for the target cluster.

Transfer the dataTransfer the data

Non-sharded target cluster
Sharded target cluster
  1. Activate the created transfer.

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

  3. Switch the source cluster to read-only mode and transfer the load to the target cluster.

  4. On the transfer monitoring page, wait for the Maximum data transfer delay metric to decrease to zero. This means that all changes that occurred in the source cluster after data copying was completed are transferred to the target cluster.

  5. Connect to the target cluster.

  6. Make sure collection1 has been transferred and contains 200,000 documents as in the source cluster:

    use db1
    db.collection1.countDocuments()
    
    200000
    
  1. Activate the created transfer.

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

  3. Switch the source cluster to read-only and transfer the load to the target cluster.

  4. On the transfer monitoring page, wait for the Maximum data transfer delay metric to decrease to zero. This means that all changes that occurred in the source cluster after data copying was completed are transferred to the target cluster.

  5. Connect to the target cluster.

  6. Make sure collection1 has been transferred, contains 200,000 documents as in the source cluster, and the documents are distributed across shards:

    use db1
    db.collection1.countDocuments()
    
    200000
    
    db.collection1.getShardDistribution()
    
    Shard rs01 at rs01/<host_1>
    {
      data: '7.05MiB',
      docs: 99752,
      chunks: 2,
      'estimated data per chunk': '3.52MiB',
      'estimated docs per chunk': 49876
    }
    ---
    Shard rs02 at rs02/<host_2>
    {
      data: '7.08MiB',
      docs: 100248,
      chunks: 2,
      'estimated data per chunk': '3.54MiB',
      'estimated docs per chunk': 50124
    }
    ---
    ...
    

Delete the resources you createdDelete the resources you created

Some resources are not free of charge. To avoid paying for them, delete the resources you no longer need:

  1. Deactivate the transfer and wait for its status to change to Stopped.

    To learn more about the transfer lifecycle, see the Yandex Data Transfer documentation.

  2. Delete the stopped transfer.

  3. Delete endpoints for both the source and target.

  4. Delete the created Managed Service for MongoDB cluster.

Was the article helpful?

Previous
Migrating to Managed Service for Elasticsearch using snapshots
Next
Migrating data to Managed Service for MongoDB
Yandex project
© 2025 Yandex.Cloud LLC