Hi SB-26050706-0,
1) Issue
Need to migrate 500+ Mixed Reality (MR) training modules created in Dynamics 365 Guides to Unity or Unreal Engine, including extracting content, assets, and instructional logic.
2) Reason
This challenge arises due to platform and architecture differences:
- Probably no native Export to Unity/Unreal: Dynamics 365 Guides is designed as a managed MR training solution for HoloLens and does not provide a direct export pipeline to game engines like Unity or Unreal.
- Proprietary Data Storage
Guide steps, holograms, anchors, and workflows are stored in Dataverse and Azure (via Guides services), not as easily portable scene files.
- Mixed Content Types
Guides consist of: 3D models (often originally imported assets), Spatial anchors, Instructional steps, Media (images/videos), UI-driven workflow logic, ...
--> These components are not packaged in a unified format compatible with Unity/Unreal.
- Spatial Anchoring Dependencies
Placement of holograms relies on MR anchoring systems (Azure Spatial Anchors or local anchors), which differ from Unity/Unreal implementations.
3) Resolution
There is probably no out-of-the-box migration tool. Microsoft currently does not provide a native export or migration utility from D365 Guides to Unity/Unreal.
Recommended Migration Approach (Phased Extraction Strategy):
Phase 1: Asset Extraction
- Retrieve original 3D models from Source repositories (preferred), or
- Export from Guides/Dataverse if available
- Extract: Images, Videos and Reference documents
--> Tip: Maintaining a mapping of Guide: Assets is critical for scale (500+ modules).
Phase 2: Data Extraction (Guide Structure)
- Use Dataverse APIs / Power Platform tools to extract: Step sequences, Instructions (text), Media references, Metadata, ...
- Tools: Power Platform CLI, Dataverse Web API, Data Export Service / Synapse Link
--> Output this into a structured format (e.g., JSON).
Phase 3: Rebuild Logic in Unity/Unreal
- Recreate: Step-by-step workflows, Navigation logic, Instruction overlays, ...
- Implement using: Unity MRTK (Mixed Reality Toolkit) or Unreal MR frameworks
--> This step is typically manual/semi-automated, not a direct conversion.
Phase 4: Spatial Anchoring Replacement
- Replace Guides anchoring with: Azure Spatial Anchors (Unity/Unreal SDKs), or Native engine anchoring systems
--> Expect rework: anchor positions often need recalibration.
---
Best Practice Architecture for Migration at Scale
- Build a transformation pipeline: Dataverse → JSON → Unity ingestion scripts
- Create template-based scenes:
- Standardize step UI, navigation, and layout
- Automate repetitive imports:
- Script asset ingestion into Unity/Unreal
---
Automation Opportunities
- Generate Unity prefabs or Unreal blueprints from: Guide step metadata
- Script: Step creation, UI population, Media linking
--> Full automation is difficult, but partial automation can significantly reduce effort.
---
Alternative Strategy (If full migration not mandatory)
- Consider whether all 500 modules must be migrated: Archive low-value Guides, Rebuild only high-impact scenarios
- Evaluate Power Platform + MR alternatives: Dynamics 365 Guides replacement with custom MR apps or maintain hybrid coexistence temporarily
---
Common Pitfalls
- Expecting a “one-click migration” (does not exist)
- Underestimating effort to rebuild spatial experiences
- Loss of contextual anchoring when moving platforms
- Poor asset governance (missing source 3D models)
- Not standardizing before migration
---
Overall Recommendation
The most effective approach is: Treat migration as a re-engineering project, not a data export exercise
- Extract reusable assets and metadata
- Rebuild experiences using Unity/Unreal best practices
- Automate wherever possible (templates + scripts)
- Prioritize high-value training modules first
This ensures scalability, maintainability, and alignment with modern MR development platforms.
Rg,
Alexander
*Due to the complex and different possibilities of deploying Dynamics 365 I highly recommend not to setup the application without some expert/partner or support. (For more information contact me under anassl@inno-solutions.info or visit www.inno-solutions.de)
*The Information comes directly from the manufacturer or provider and are validated (not guaranteed) up to date of creation of the posting.
References:
- Microsoft Licensing Guide
- Microsoft Doc`s/Learn
2
Share
Report
All responses (
Answers (
