Migrate configuration

Dynatrace offers several tools to help you successfully migrate your configuration from a Dynatrace Managed environment to the SaaS environment. The table below will help you select the appropriate tool for your environment, your configuration experience, and the upgrade approach you intend to follow.

To avoid configuration compatibility issues, update your Dynatrace Managed deployment to the latest version. The best practice is to update Dynatrace Managed to the same version as your SaaS environment.

Select a tool

Tool name	Should I use it?
SaaS Upgrade Assistant recommended	The SaaS Upgrade Assistant lets you easily import your Dynatrace Managed configuration to your SaaS environment and edit it in simple UI. Use the SaaS Upgrade Assistant if You have little to no experience with configuration You want to migrate without installing and learning additional software You are migrating one Dynatrace Managed environment into exactly one new SaaS environment using the Big Bang approach You monitor fewer than 500 hosts You are migrating to an AWS or Azure region that is Grail-enabled
Dynatrace Config Manager	The Dynatrace Config Manager is an open source, community-developed standalone application that enables you to import and adjust configuration automatically while migrating to SaaS. Convenient when configurations and monitoring scope are dynamic in Managed and SaaS environments. Works equally well with the Big Bang and Phased approaches when migrating to any existing SaaS environment with some configuration and workloads. Automatically resolves entity ID differences caused by OneAgent reinstallation. This helps when migrating big environments (monitoring more than 500 hosts).
Dynatrace Configuration as Code	If you already use Dynatrace Configuration as Code via Monaco or Dynatrace Configuration as Code via Terraform, you can repoint the target to your SaaS environment.

Tool name

Should I use it?

SaaS Upgrade Assistant

recommended

The SaaS Upgrade Assistant lets you easily import your Dynatrace Managed configuration to your SaaS environment and edit it in simple UI.

Use the SaaS Upgrade Assistant if

You have little to no experience with configuration
You want to migrate without installing and learning additional software
You are migrating one Dynatrace Managed environment into exactly one new SaaS environment using the Big Bang approach
You monitor fewer than 500 hosts
You are migrating to an AWS or Azure region that is Grail-enabled

Dynatrace Config Manager

The Dynatrace Config Manager is an open source, community-developed standalone application that enables you to import and adjust configuration automatically while migrating to SaaS.

Convenient when configurations and monitoring scope are dynamic in Managed and SaaS environments.
Works equally well with the Big Bang and Phased approaches when migrating to any existing SaaS environment with some configuration and workloads.
Automatically resolves entity ID differences caused by OneAgent reinstallation. This helps when migrating big environments (monitoring more than 500 hosts).

Dynatrace Configuration as Code

If you already use Dynatrace Configuration as Code via Monaco or Dynatrace Configuration as Code via Terraform, you can repoint the target to your SaaS environment.

Get started

Use one of the following migration procedures, depending on your selected tool.

Migrate using SaaS Upgrade Assistant

recommended

To migrate your configuration using the SaaS Upgrade Assistant, see SaaS Upgrade Assistant.

With this approach, you export the Dynatrace Managed environment's configuration in the Cluster Management Console and upload it to the app.

Migrate using Monaco

To migrate your configuration using Monaco

Install Dynatrace Configuration as Code via Monaco on a host with network access to your Dynatrace Managed cluster (for example, to the cluster node itself).
Create a deployment manifest: manifest.yaml
For each environment that you want to migrate, add a configuration:
- In the environment’s web UI, go to Access tokens and select Generate new token.
- Type a token name and set a feasible expiration date.
- Select the scopes below:
  - Read configuration
  - Read settings
  - Read SLO
  - Access problem and event feed, metrics, and topology
  - Create and read synthetic monitors, locations, and nodes
- Store the token in a secret place. For example, use a password manager.
- Create an operating system environment variable with the token value. For example, on Linux systems:
```
export ENV_TOKEN_PRODUCTION_FIN= dt0c01.abc123.abcdefjhij1234567890
```
- Add the environment data to the manifest.yaml:
  - Add the name to the projects field
  - In the managed environmentGroup, input the URL with a token
  Example manifest.yaml:
```
manifestVersion: 1.0

projects:
- name: production-fin
- name: production-logistics

environmentGroups:
- name: managed
  environments:
  - name: production-fin
    url:
        value: https://foo123.dynatrace-managed.com/e/1231aaa1-1111-434e-8111-11abcd1234a1
    token:
        name: MIGRATION_TOKEN_PROD_FIN
  - name: production-logistics
    url:
        value: https://foo123.dynatrace-managed.com/e/2345bbb3-3333-456b-1566622abcd3456a1
    token:
        name: MIGRATION_TOKEN_PROD_LOGISTICS
```
Run Monaco using the download command:
monaco download manifest manifest.yaml

Create your SaaS environment configuration. Apply the steps described in step 3 above, but set the token scope as follows:
- Read Configuration
- Write Configuration
- Read settings
- Write settings
- Read SLO
- Write SLO
- Access problem and event feed, metrics, and topology
- Create and read synthetic monitors, locations, and nodes Store the token in a secure place (for example, use a password manager).

Change data privacy settings.

Example:

environmentGroups:
    - name: saas
      environments:
      - name: abc1234456
        url:
            value: https://abc1234456.live.dynatrace.com
        token:
            name: ENV_TOKEN_SAAS

Run Monaco using the deploy command: monaco deploy -e saas
Resolve problems and conflicts as stated in the output log. Use skipDeployment: "true" for unsupported or duplicated configurations and recreate them manually.

Now your configuration should be replicated in your new SaaS environment.

Migrate using Terraform

To migrate your configuration using Configuration as Code via Terraform, follow the migration guide.

Migrate using Config Manager

Start by installing Terraform on your system as described in the Terraform documentation.

Download the binary according to your operating system.
Set the PATH to ensure the Terraform binary is accessible system-wide.
Verify the setup by opening a new terminal session and running the following command:
```
terraform version
```

Download the latest version of Dynatrace Config Manager from GitHub.
Learn more by watching the quickstart video:

Questions?

Visit the Upgrade to SaaS forum to ask questions, get answers, and share what you've learned with others.

Settings that require manual migration

Dynatrace Configuration as Code implementations don't support all settings that you use. To ensure a complete configuration migration, you need to check and manually migrate the additional settings listed below.

Extensions 1.0 and Extensions 2.0 configuration, including endpoint credentials
AWS credentials
Azure credentials
GCP monitoring
Cloud Foundry credentials
Kubernetes/Openshift credentials
Heroku monitoring
VMware platform monitoring
Credential vault for synthetic monitors
Access tokens and personal access tokens
Problem notifications integration, such as Jira, OpsGenie, PagerDuty, Trello, VictorOps, and xMatters
Push notifications via the Dynatrace mobile app
Metrics not linked to instances
Dashboard sharing settings
RUM web and mobile key user actions
RUM user action and session properties
Web application usability analytics - rage clicks
JavaScript errors
Mobile symbolication
Request naming order
Merged services
Process group custom names and descriptions
Server-side service deep monitoring settings: Real-time updates to Java and PHP services
Server-side service deep monitoring settings: Exclude noisy exceptions
Server-side service deep monitoring settings: Exclude incoming web request URLs
Server-side service deep monitoring settings: Capture SQL bind variables
Network zones
Multi-dimensional analysis saved views
Data Explorer saved queries
Custom service rules order
Remote environments
Account management - users, groups, permissions, and IAM policies

Questions?

Visit the Upgrade to SaaS forum to ask questions, get answers, and share what you've learned with others.