What the checker reviews
Views and layout
Default views, alternate views, editability hints, show/hide sections, and layout signals from the XSL views.
Fields and controls
Text inputs, dates, checkboxes, dropdowns, people fields, repeating regions, and bound plain-text controls.
Rules and data
View switches, set-field actions, submit behavior, secondary lists, SharePoint connections, and unsupported script flags.
How to read the result
- Supported means the converter has a known first-pass pattern.
- Partial means a scaffold can be generated, but builder review should be expected.
- Manual review means the behavior may need a Power Apps, Power Automate, connector, or custom rebuild pattern.
- Warnings are the first place to look before moving to Required Settings.
Use the checker for portfolio triage
Run several forms through analysis and group them into quick wins, standard migrations, and complex rebuild candidates. This is more reliable than estimating based only on file names or SharePoint library counts.
Common questions
Does free analysis consume an export credit?
No. Export credits are for successful package generation, not for running analysis.
Is the report enough for an estimate?
It is a strong first-pass estimate input. For production commitments, also validate the destination SharePoint schema and any custom integration requirements.
Can I share the report with a builder?
Yes. The report is designed to support builder handoff and identify where Power Apps Studio review is needed.