Migrate clusters to Mission Control

For Mission Control, there are two types of cluster migrations:

  • Infrastructure migrations: Move an existing cluster to Mission Control without changing the database platform or version.

  • Platform migrations and upgrades: Move your data from one database platform to another, or upgrade your database software version. This type of migration can use your existing infrastructure or deploy new infrastructure, depending on the approach you choose.

Infrastructure migrations

An infrastructure migration moves an existing DataStax Enterprise (DSE), Hyper-Converged Database (HCD), or Apache Cassandra® cluster from one infrastructure to another, including its data.

The following guides are for infrastructure migrations only. You cannot change database platforms or versions during a Mission Control cluster migration.

Platform migrations and upgrades

This type of migration moves your data from one database platform to another, such as DSE to HCD. This can also be used for version upgrades that can’t be performed with the usual upgrade process.

There are several ways to perform a platform migration or upgrade:

  • Migrate or upgrade by restoring a backup: If your cluster is already on Mission Control, certain platform migrations and version upgrades are possible when restoring from a backup.

  • Use the Zero Downtime Migration (ZDM) tools: With this option, your new cluster is independent from your existing cluster. Deploy your new cluster with Mission Control, use data migration tools to copy your data to the new cluster, and then decommission the existing cluster. ZDM Proxy synchronizes new writes on both clusters, so you can keep using your existing cluster as long as you need.

  • In-place upgrades for DSE to HCD migrations: Perform an in-place platform upgrade on your existing cluster, with or without Mission Control.

For more information and options, see the following:

Combined infrastructure and platform migrations

If you want to migrate your infrastructure to Mission Control and upgrade/migrate your database platform, do one of the following:

  • Perform each migration separately. For example, migrate your existing cluster to Mission Control, and then migrate/upgrade your database platform.

  • Use ZDM Proxy to support two independent clusters, deploying your new cluster to Mission Control with the new database platform, and then decommission your existing cluster copying your data to the new cluster.

Was this helpful?

Give Feedback

How can we improve the documentation?

© Copyright IBM Corporation 2026 | Privacy policy | Terms of use Manage Privacy Choices

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: Contact IBM