Baseline solution (A)
Load your earlier version here. If you are just exploring, you only need this ZIP.
No file selectedOpen a solution ZIP. Understand its components. Map its architecture. Compare releases. All without uploading your solution anywhere.
Explore fictional teaching packages, download a sample ZIP or compare two project tracker releases. No Microsoft environment or account is required.
These are original mock Dataverse export structures for testing the explorer, not genuine Microsoft exports and not suitable for import into Dataverse. For Microsoft-authored examples, visit Copilot Studio Samples ↗. The complete gallery works offline.
Choose an exported solution ZIP, or load the synthetic demo to see how the explorer works.
Load your earlier version here. If you are just exploring, you only need this ZIP.
No file selectedLoad another exported ZIP to compare components and properties against A.
No comparison loadedYour architecture, one clear picture.
Load a ZIP to reveal its composition.
Search your solution by component name, type or property.
| COMPONENT | TYPE | DETAILS | Explore |
|---|---|---|---|
| No solution loaded yet. Try the sample to start exploring. | |||
Generate diagrams directly from the solution metadata — without cloud rendering.
Load a solution to visualise tables, relationships and integrations.
Understand what changed between two solution exports — component by component.
| COMPONENT | TYPE | CHANGE | DETAILS |
|---|---|---|---|
| Add a second solution ZIP, or load the comparison demo. | |||
Understand what's possible before modifying a managed solution export.
Dataverse does not provide a supported file-only way to convert managed packages into unmanaged packages. Altering managed flags in XML is not a valid conversion.
Official Microsoft documentation: SolutionPackager limitations ↗ · Export unmanaged source ↗
Inventory and architecture exports can help with an authorised reconstruction, but cannot restore missing unmanaged source, editability, licences or dependencies.
Your solution files stay with you. Inspect what this page does, not just what it promises.
ZIP extraction, XML/JSON parsing, diagrams, comparisons and downloads execute in your browser. Files aren't uploaded to Mightora. The tool doesn't ask for Dataverse credentials or connections.
Environment variable values are deliberately excluded from reports. Potentially sensitive solution metadata remains in memory until you clear the workspace or close this tab.
The online edition loads the shared Mightora UI from jsDelivr and its branding assets from GitHub. The offline edition has no external dependencies and blocks network connections.
See resource domains observed by the browser's Performance API. This is a partial view, not an audit or guarantee that all requests have been captured.
To independently verify: press F12 → Network → enable Preserve log → reload → inspect requests. On mobile, use desktop browser developer tools or a network inspection tool.
Same explorer. No installation, server, CDN or internet connection required.
No. The application processes files in your browser memory. The online edition loads interface resources from CDNs; the offline edition does not make external requests.
Yes. Standard exported Dataverse solution ZIPs can be analysed regardless of managed state. Some metadata may be absent in managed exports, and the explorer surfaces warnings where appropriate.
It matches discovered components by type and logical name, and compares extracted metadata properties. It does not perform a semantic analysis of JavaScript, formulas or all flow actions.
No. Microsoft does not support direct conversion via SolutionPackager or changing an archive flag. The recovery assessment provides a checklist for obtaining the original unmanaged source or documenting an authorised rebuild.
Not fully yet. The current parser targets XML-based exported solution ZIPs. A ZIP of YAML source-control files will show a coverage warning and may provide an incomplete inventory.