This page helps you decide whether and when to upgrade, what changes in your environment to expect, and what happens if you roll back the upgrade. If you have multiple environments, you can decide separately for each environment whether to upgrade it to Latest Dynatrace. For more information on upgrading a specific Dynatrace capability, see Upgrade to Latest Dynatrace.
Upgrading an environment moves it from Dynatrace Classic capabilities to Latest Dynatrace. Before you plan the work, it helps to know what changes in your environment and what you gain from the upgrade.
Use this page to:
The following sections explain how to accomplish these goals.
Latest Dynatrace replaces Dynatrace Classic capabilities with structurally different ones. For example, a Dynatrace Classic management zone's role might be split across segments, IAM policies, and Grail buckets. That's why upgrading is migration work rather than a switch.
To get oriented with the new concepts, see:
Upgrading takes planning and migration work, but it moves your environment to a platform that scales better, gives you access to recent product advancements, and delivers a significantly improved user experience.
Latest Dynatrace gives you:
For step-by-step guidance on upgrading your environment, including how to find your upgrade group, choose between manual and AI-assisted approaches, and plan the work in the right order, see How to upgrade your environment to Latest Dynatrace.
Upgrading an environment is a deliberate decision that you can reverse during the grace period.
The rollback makes Dynatrace Classic apps and APIs available again.
The rollback doesn't restore Dynatrace Classic configuration objects that you deleted or replaced during migration. If you delete Dynatrace Classic objects and then roll back, the Dynatrace Classic apps are available again, but without that configuration.
Use this guide when you need to: