Skip to content
Percona Software for MongoDB Documentation

For help, click the link below to get free database assistance or contact our experts for personalized support.

Get help from Percona

FAQ

Percona Link for MongoDB is a data migration tool that you can use for various use cases. Among them are:

  • Migration from MongoDB Atlas or MongoDB Enterprise to Percona Server for MongoDB.
  • Cluster synchronization across environments, such as staging to production.
  • Setup of live replication for backup, testing, or audit environments.
  • Downtime minimization during a migration by using continuous sync until cutover.

Which MongoDB versions are supported?

  • Source clusters: MongoDB 6.0.17 and later, including Atlas and MongoDB Enterprise editions.
  • Target clusters: Percona Server for MongoDB 6.0.17 and later.

Check Supported deployments to learn more.

Can I sync from Atlas to a self-hosted Percona Server for MongoDB?

Yes. Percona Link for MongoDB is explicitly built to support Atlas to Percona Software migrations with minimal effort.

Yes. Both the source and target must be replica sets. Sharded clusters are not yet supported, but planned.

No. Percona Link for MongoDB currently supports one-way synchronization only (source → target). However, you can re-run Percona Percona Link for MongoDB with a reversed connection strings to do the other direction sync.

Is there a way to monitor sync progress?

Yes. Percona Link for MongoDB provides Prometheus metrics exposed at the /metrics endpoint and provides detailed logging for sync status, lag, and errors. See how you can configure monitoring with PMM. You can also use a monitoring tool of your choice.

Can I filter which databases or collections to sync?

Yes. Percona Link for MongoDB allows you to include/exclude filters for specific databases or collections. This option is currently available via HTTP API. The command-line support will be added in future releases.

Percona Link for MongoDB is designed with resilience in mind:

  • It supports automatic retries on transient errors.
  • It uses checkpointing to resume from the last known sync point after restart.
  • Logs include detailed error reporting for troubleshooting.

What features are planned for future releases?

Sharded cluster support and high availability are the next features we are working on.

Last update: June 5, 2025
Created: June 5, 2025