Migration Strategy for Dynamics 365 Guides (Deprecated) – Any Official or Recommended Approach?

There is no official or automated migration path from Dynamics 365 Guides to Unity, Unreal, or other XR training platforms in the provided information. The available Microsoft guidance focuses on:

1. Planning for end of support
   • Dynamics 365 Guides and Dynamics 365 Remote Assist reach end of support on December 31, 2026 and will no longer receive security updates, bug fixes, or technical support after that date.
   • Recommended actions are:
     • Identify users and scenarios that rely on Guides/Remote Assist.
     • Plan a transition before December 31, 2026.
     • Explore alternative mixed reality solutions from Microsoft partners via the Microsoft Marketplace.
     • For some Remote Assist scenarios, consider the spatial annotation feature in Microsoft Teams Mobile.
2. Moving Guides content between Dataverse environments (not out of Guides)
   • A Content Migration Tool (Public Preview) exists specifically for Dynamics 365 Guides to move content between Microsoft Dataverse environments (including across tenants and between commercial and GCC):
     • It is a Windows PowerShell script that copies content from a source environment to a destination environment; the source is unchanged.
     • Supported migration types include:
       • All content in an environment (excluding telemetry events).
       • Guides and associated 3D objects, images, and videos.
       • All or subsets of 3D objects, images, videos, and object anchors.
     • It does not export content into a format directly consumable by Unity, Unreal, or other non-Dataverse platforms.
   • Folder structures can be exported/imported between Dataverse environments using Power Platform export/import, then re-linked to content by running the Content Migration Tool afterward.
3. Constraints and prerequisites for the Content Migration Tool
   • Both source and destination environments must:
     • Use Dynamics 365 Guides solution version 700.0.0.x or later.
     • Have the same major and minor version numbers.
   • Required roles:
     • Source: System Admin (preferred) or Operator/Author.
     • Destination: System Admin (preferred) or Author.
   • The tool does not support migration of guides based on schema v3 or v4; those must be manually upgraded within Guides first.
   • 3D object collections require System Admin role to migrate parent objects.
4. Recommended migration pattern within the Microsoft ecosystem (not to Unity/Unreal)
   • If remaining on Guides until end of support, the recommended pattern for moving content between environments is:
     1. Export/import Guides folders between environments using Power Apps/Power Platform.
     2. Use the Guides Content Migration Tool to migrate guides, 3D content, and media so folder–content relationships are reconstructed.
5. Alternatives and next steps
   • The provided information only points to:
     • Exploring mixed reality solutions on the Microsoft Marketplace as alternatives to Guides.
     • Using Microsoft Teams Mobile spatial annotation for certain remote collaboration scenarios.
   • No official tooling is described for:
     • Exporting Guides content into Unity or Unreal projects.
     • Automatically converting Guides step flows, anchors, or interactions into other XR runtimes or newer headsets.

Within the available information, the only Microsoft-backed migration capability is between Dataverse environments using the Guides Content Migration Tool and Power Platform export/import for folders. Any move to Unity, Unreal, or non-Guides XR platforms would require custom, manual processes outside what is documented here.

References:

• Migrate Dynamics 365 Guides content from one Microsoft Dataverse environment to another using the Content Migration Tool (Public Preview)
• Export and import Dynamics 365 Guides folders between environments
• Dynamics 365 Guides and Remote Assist reaching end of support on December 31, 2026
• Existing Microsoft Power Platform engagement and Guides deployment strategy