# Moving Dynatrace configuration between installations **URL:** \ **Category:** Open Q&A\ **Tags:** installation, settings\ **Created:** [March 15, 2020, 8:14pm UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783 "2020-03-15T20:14:40Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![josedamianruizl](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@josedamianruizl](https://community.dynatrace.com/u/josedamianruizl)\ **Post date:** [March 15, 2020, 8:14pm UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/1 "2020-03-15T20:14:40Z")
Hello all! I have a Dynatrace installation (PoC - Proof of Concept installation), and in next dates we will have a new Dynatrace Installation (we can say Production Installation)… So how we can move with less effort current monitoring configuration (dashboards, alarms, tags, etc.) from PoC installation to the new and final Production installation ? Please we really appreciate guidelines, best practices and automation tools for moving from PoC Dynatrace cluster nodes to Final Production Dynatraace cluster nodes. Target is recreate configuration with less effort and risks. Many Thanks Damián ---
**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\ **Post date:** [March 16, 2020, 7:48am UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/2 "2020-03-16T07:48:39Z")
I’m working on such tool right now, it will still take some time because of lacks of time for that project. But in general, the only you can use right now i Configuration API: > **[Configuration API](https://docs.dynatrace.com/docs/dynatrace-api/configuration-api)** > > Find out what you need to use the configuration section of the Dynatrace API. When we are doing POC’s in most cases we are creating server that will handle production after presales. In such case we just change license into production one and we are ready to go. Sebastian ---
**Author:** ![josedamianruizl](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@josedamianruizl](https://community.dynatrace.com/u/josedamianruizl)\ **Post date:** [March 16, 2020, 7:55am UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/3 "2020-03-16T07:55:24Z")
Thank you very much Sebastian. Is anfeasible option to add new cluster nodes to the current cluster PoC, and then properly switch off the PoC nodes ? Or is not a supported option ? Many Thanks. Damian ---
**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\ **Post date:** [March 16, 2020, 8:00am UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/4 "2020-03-16T08:00:28Z")
Ok I’ve frogotten about backup and restore option: > **[Backup and restore a cluster](https://docs.dynatrace.com/managed/managed-cluster/operation/back-up-and-restore-a-cluster)** > > Understand the steps and commands required to restore a Dynatrace Managed cluster. Use this and should be fine. But in general you can alway add new cluster to current one, they will replicate and then you can disable old one. Sebastian ---
**Author:** ![josedamianruizl](https://avatars.discourse-cdn.com/v4/letter/j/f04885/32.png) [@josedamianruizl](https://community.dynatrace.com/u/josedamianruizl)\ **Post date:** [March 16, 2020, 8:15am UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/5 "2020-03-16T08:15:27Z")
Hello Sebastian. Could be possible to backup a specific environment a restore this specific environment to the new cluster ? In our current PoC we have 2 environments: Preproduction and Production. Many Thanks. Damián. ---
**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\ **Post date:** [March 16, 2020, 8:40am UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/6 "2020-03-16T08:40:20Z")
I think you will have to backup whole thing and than delete one of environments from new cluster. This should be fine for you as well. Sebastian ---
**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\ **Post date:** [March 16, 2020, 12:12pm UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/7 "2020-03-16T12:12:27Z")
We had the same scenario going for our POC to purchased instance. You can fiddle around with the API if you’d like and saving the json payload for each dashboard and the settings ETC. my Professional recommendation would be to create a cluster backup. You will need to get a hold of a support rep to assist you with restoring from the backup. But since you just completed the POC the sales rep should be able to get you in contact with the right person. **It is important to note,** that the back up is for settings and configuration only, your user data and such will not be carried over. ---
**Author:** ![pahofmann](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pahofmann/32/17076_2.png) [@pahofmann](https://community.dynatrace.com/u/pahofmann)\ **Post date:** [March 16, 2020, 3:03pm UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/8 "2020-03-16T15:03:55Z")
Hello, we ([amasol](https://amasol.de/english/)) are currently working on a solution that will cover your use case. Currently we plan to cover three main use cases with the solution: - Config Backups - Easy Configuration Management - Continuous Configuration Management **Config Backups** The dynatrace managed backup mechanism is intended for disaster recovery. There is no way to do fine grained restoration of specific configuration. We solve that issue by doing continuous backups of the dynatrace configuration to a git repository. **Easy Configuration Management** We want to make it easy to copy configuration between different tenants, environments or even inside them. This will make it possible for example, to copy config over from PoC environment or to copy configuration between the different stages of your applications. Via a web UI it will be possible to copy configuration or restore it from a backup. **Continuous Configuration Management** For the last iteration we plan to enable customers to integrate dynatrace configuration updates into der CI/CD pipelines. With this you can deploy new dynatrace configuration directly with your application over different stages, simply with an API call. Use case one ( **Backups** ) is already implemented and currently being tested by different customers. The **Easy Configuration Management** is the next step on our roadmap. Once the second use case is finished, we plan to offer the solution on the dynatrace [marketplace](https://www.dynatrace.com/marketplace/). If you want more information or have feedback please let me know! ---
**Author:** ![pahofmann](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pahofmann/32/17076_2.png) [@pahofmann](https://community.dynatrace.com/u/pahofmann)\ **Post date:** [March 16, 2020, 3:19pm UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/9 "2020-03-16T15:19:35Z")
Currently the simplest way is to import the dynatrace configuration API spec.json into [Postman](https://www.postman.com/) as a collection, and then create different postman environments for the dynatrace environments. It’s still a lot of manual work, but it makes it a lot shorter then manual copy/paste 🙂 ---
**Author:** ![pahofmann](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pahofmann/32/17076_2.png) [@pahofmann](https://community.dynatrace.com/u/pahofmann)\ **Post date:** [March 16, 2020, 4:01pm UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/10 "2020-03-16T16:01:05Z")
We plan to offer this as a SaaS Service for customer of our [aMC Plattform](https://amasol.de/english/vendors-und-products/amasol-managed-cloud.html), Dynatrace SaaS, and Dynatrace Managed customers where the cluster is available from the outside. We will also offer a self hosted version that can be run on a VM or deployd as a container. This will then also work for closed off Managed or Offline installation.s ---
**Author:** ![dave\_mauney](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dave_mauney/32/27784_2.png) [@dave\_mauney](https://community.dynatrace.com/u/dave_mauney)\ **Post date:** [March 16, 2020, 5:12pm UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/11 "2020-03-16T17:12:07Z")
Here are some already existing solutions that might work for you. I have not personally tried them out, but have gathered the various links only. **Dynatrace Sync** > **[GitHub - AlonsoDeCosio/dynatrace-sync-environments: Sync multiple Dynatrace environments](https://github.com/AlonsoDeCosio/dynatrace-sync-environments)** > > Sync multiple Dynatrace environments [https://gitlab.com/eduardvdbent/dtconf](https://gitlab.com/eduardvdbent/dtconf) Hope this helps, dave ---
**Author:** ![dave\_mauney](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dave_mauney/32/27784_2.png) [@dave\_mauney](https://community.dynatrace.com/u/dave_mauney)\ **Post date:** [March 16, 2020, 7:36pm UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/12 "2020-03-16T19:36:59Z")
If the latency is less than about 10 ms between the old nodes and new nodes you can add a node to migrate. See the links below for more details: Migrating a Cluster > **[Migrate a cluster](https://docs.dynatrace.com/managed/managed-cluster/operation/migrate-a-cluster)** > > Learn how to migrate a cluster from one data center to another. Adding A Node > **[Add a Managed Cluster node](https://docs.dynatrace.com/managed/managed-cluster/installation/add-cluster-node)** > > Add a node to your Managed Cluster by downloading the installer, running it on the target host, and monitoring synchronization progress. Enable/Disable a cluster node > **[Configure Cluster capabilities](https://docs.dynatrace.com/managed/managed-cluster/configuration/configure-cluster-capabilities)** > > Configure OneAgent data processing and web UI traffic on individual Managed Cluster nodes using the Cluster Management Console or REST API. Removing A Node > **[Remove a cluster node](https://docs.dynatrace.com/managed/managed-cluster/operation/remove-a-cluster-node)** > > Learn how to remove a new cluster node using either the command prompt or the Cluster Management Console. ---
**Author:** ![Josef](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@Josef](https://community.dynatrace.com/u/Josef)\ **Post date:** [May 24, 2021, 11:16pm UTC](https://community.dynatrace.com/t/moving-dynatrace-configuration-between-installations/18783/13 "2021-05-24T23:16:53Z")
Hi Damian, we have such a Dynatrace configuration backup solution in place. Contact me or follow this link to get started [https://www.dynatrace.com/hub/?query=composer](https://www.dynatrace.com/hub/?query=composer) Our solution is very easy to use. You can install it within a few minutes, backup the Dynatrace configuration and use it for the restore on the new environment. Best regards Josef