<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Tenant consolidation in Dynatrace SaaS – Is there any way to preserve historical data (metrics/traces)? in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Tenant-consolidation-in-Dynatrace-SaaS-Is-there-any-way-to/m-p/297605#M38896</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;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.&lt;BR /&gt;From what I understand, tools like Monaco and&amp;nbsp;SaaS Upgrade Assistant&amp;nbsp;can help migrate configurations (dashboards, alerting profiles, management zones, etc.), but they do not cover historical observability data.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;My main concern is around:&lt;BR /&gt;- Metrics history&lt;BR /&gt;- Distributed traces&lt;BR /&gt;- Problem history / Davis AI data&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;As far as I know, this data cannot be migrated between SaaS tenants due to architectural isolation.&lt;BR /&gt;However, I wanted to ask the community (and Dynatrace team, if possible):&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Is there any internal or supported mechanism (even via Dynatrace support) to transfer or preserve historical data between SaaS tenants?&lt;BR /&gt;Are there any recommended best practices for handling this type of consolidation beyond keeping the old tenant in read-only mode?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;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.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Any insights or real-world experiences would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks in advance!&lt;/P&gt;</description>
    <pubDate>Mon, 13 Apr 2026 11:24:55 GMT</pubDate>
    <dc:creator>arobayo17</dc:creator>
    <dc:date>2026-04-13T11:24:55Z</dc:date>
    <item>
      <title>Tenant consolidation in Dynatrace SaaS – Is there any way to preserve historical data (metrics/traces)?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Tenant-consolidation-in-Dynatrace-SaaS-Is-there-any-way-to/m-p/297605#M38896</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;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.&lt;BR /&gt;From what I understand, tools like Monaco and&amp;nbsp;SaaS Upgrade Assistant&amp;nbsp;can help migrate configurations (dashboards, alerting profiles, management zones, etc.), but they do not cover historical observability data.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;My main concern is around:&lt;BR /&gt;- Metrics history&lt;BR /&gt;- Distributed traces&lt;BR /&gt;- Problem history / Davis AI data&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;As far as I know, this data cannot be migrated between SaaS tenants due to architectural isolation.&lt;BR /&gt;However, I wanted to ask the community (and Dynatrace team, if possible):&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Is there any internal or supported mechanism (even via Dynatrace support) to transfer or preserve historical data between SaaS tenants?&lt;BR /&gt;Are there any recommended best practices for handling this type of consolidation beyond keeping the old tenant in read-only mode?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;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.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Any insights or real-world experiences would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Mon, 13 Apr 2026 11:24:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Tenant-consolidation-in-Dynatrace-SaaS-Is-there-any-way-to/m-p/297605#M38896</guid>
      <dc:creator>arobayo17</dc:creator>
      <dc:date>2026-04-13T11:24:55Z</dc:date>
    </item>
    <item>
      <title>Re: Tenant consolidation in Dynatrace SaaS – Is there any way to preserve historical data (metrics/traces)?</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Tenant-consolidation-in-Dynatrace-SaaS-Is-there-any-way-to/m-p/297608#M38897</link>
      <description>&lt;P&gt;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.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;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.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Apr 2026 12:59:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Tenant-consolidation-in-Dynatrace-SaaS-Is-there-any-way-to/m-p/297608#M38897</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2026-04-13T12:59:38Z</dc:date>
    </item>
  </channel>
</rss>

