Symptoms
I’m upgrading a project from Unity 2022.3 / 6000.0 / 6000.1 to Unity 6000.2 LTS or later and I want to enable the new Diagnostics service.
I’m worried that enabling the new Diagnostics service will cause existing live builds to stop sending data to legacy Cloud Diagnostics (including User Reporting).
I want to migrate smoothly without losing visibility into crash/exception trends during the transition.
I need a clearer understanding of when legacy Cloud Diagnostics will stop working during a staged rollout.
Cause
Crash and exception reporting behavior is defined at compile time, not runtime.
Changing Project Settings in the Editor only affects future builds you create from that project.
Already-released builds keep using whichever Diagnostics/Reporting implementation they were built with until you replace them with updated builds.
As a result, legacy Cloud Diagnostics does not stop for existing live builds just because you enable the new Diagnostics service in the Editor.
Resolution
What happens in your scenario
If you follow this flow:
Upgrade the project to Unity 6000.2 LTS or later
Enable new Diagnostics in Project Settings > Services
Build, test, and release new builds per platform
Then:
Existing live builds (already released):
Continue reporting to legacy Cloud Diagnostics for as long as those builds remain installed and active in the wild, or until the legacy Cloud Diagnostics service is officially sunset.New builds you release after enabling new Diagnostics:
Report to the new Diagnostics service (for crash/exception reporting), because those builds are compiled with the new configuration.
In other words, there is no immediate cutover moment triggered by step (2). The “cutover” is gradual and happens as players adopt the new builds you ship.
Recommended migration steps (smooth rollout)
Plan a staged release
Roll out new builds on one platform (or a smaller percentage of users) first if you can, so you can validate reporting continuity before full rollout.
2. Enable both systems if needed:
There is no interference between legacy Cloud Diagnostics and the new Diagnostics service. If you prefer, you can have both enabled at the same time for new builds to ensure a seamless transition.
3. Handling User Reporting.
User Reporting has always been its own distinct package, though it was previously bundled alongside legacy Cloud Diagnostics. It is no longer bundled with the new Diagnostics service. To continue using this feature, simply ensure the Unity User Reporting package is installed in your project.
4. Validate end-to-end before release
In a test build, generate a forced exception/crash (for Diagnostics). I recommend following the steps in this article: How can I validate that Cloud Diagnostics Crash and Exception Reporting is working?
Confirm the events appear in the expected dashboards for the correct project/environment.
5. Run both systems in parallel (temporarily)
Expect a period where:
Legacy dashboards still show data from older builds in the field.
New dashboards show data from updated builds.
Note: This overlap is completely normal during a staged rollout.