Tenant consolidation in Dynatrace SaaS – Is there any way to preserve historical data (metrics/traces)?

[arobayo17]

Hi everyone,

I’m currently involved in a scenario where two companies, each with their own Dynatrace SaaS tenant, are merging into a single organization. As part of this process, we are planning to consolidate observability into one target tenant.
From what I understand, tools like Monaco and SaaS Upgrade Assistant can help migrate configurations (dashboards, alerting profiles, management zones, etc.), but they do not cover historical observability data.

My main concern is around:
- Metrics history
- Distributed traces
- Problem history / Davis AI data

As far as I know, this data cannot be migrated between SaaS tenants due to architectural isolation.
However, I wanted to ask the community (and Dynatrace team, if possible):

Is there any internal or supported mechanism (even via Dynatrace support) to transfer or preserve historical data between SaaS tenants?
Are there any recommended best practices for handling this type of consolidation beyond keeping the old tenant in read-only mode?

We are trying to define the best strategy before proceeding, especially to understand whether losing historical data is truly unavoidable or if there are alternatives worth considering.

Any insights or real-world experiences would be greatly appreciated.

Thanks in advance!

[Julius_Loman · Accepted solution]

Data cannot be migrated. The only viable option is to keep the old environment running and access the historical data there. You can use the cross-environment integration (for classic apps) if you want cross-environment tracing (in classic distributed traces) or classic dashboards. 

My recommendation would be to choose one of the environments and migrate the other one. Not directly, but a planned migration adopting practices from the environment you are migrating to, such as tagging strategies, host groups, naming conventions, etc.