# Dynatrace Managed Cluster Migration

**URL:** <https://community.dynatrace.com/t/dynatrace-managed-cluster-migration/9610>\
**Category:** Dynatrace Managed\
**Tags:** installation, dynatrace-managed\
**Created:** [December 5, 2017, 8:45pm UTC](https://community.dynatrace.com/t/dynatrace-managed-cluster-migration/9610 "2017-12-05T20:45:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![hayden\_miedema](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/hayden_miedema/32/29357_2.png) [@hayden\_miedema](https://community.dynatrace.com/u/hayden_miedema)\
**Post date:** [December 5, 2017, 9:05pm UTC](https://community.dynatrace.com/t/dynatrace-managed-cluster-migration/9610/2 "2017-12-05T21:05:00Z")

</div>

Hey Patrick,

I am actually in the process of this with a customer with a bit different requirements/considerations. But, as you said, there would be some issues if you go about with your approach. The main one that comes to mind is that agents are currently reporting to that cluster (old one node) and an environment within that cluster. If you move to new hardware, you would have to procure a new environment, which would lead to having to redeploy all agents.

The best way to do this would actually be to add your newly provisioned node to the existing cluster. At that point, there will be metric replication done from the Cassandra database. Timeseries metrics do not replicate in this process actually. So, depending on what is configured as the transaction storage period, you would want to run this two node cluster for as many days as you have selected there (default is 10 days). This would just be to ensure that you do not have a gap in transaction (code-level) data for any amount of time.

Once this period is done, you could decommission and remove the old node from the cluster.

Let me know if you have questions,

Hayden

---

_[View the full topic](https://community.dynatrace.com/t/dynatrace-managed-cluster-migration/9610)._
