Review the analysis and conversion verdict

Beta. Read the analysis as a comparison between the source behavior and the proposed OwlMeans application. The verdict helps you decide whether to continue and what to address first.

1. Open the conversion’s current status and analysis.
2. Check the detected source family and the parts of the app it has identified.
3. Compare the extracted stories with the workflows you listed during preparation.
4. Read blockers, uncertain areas and suggested changes.
5. Correct the product description or answer outstanding questions.
6. Continue only when the proposed scope covers the behavior you need.

Review these areas

Area	What to compare
Screens and workflows	Can a user still complete the important actions?
Records and relationships	Are the required fields and links represented?
Users and access	Are the original roles and restrictions understood?
Integrations	Which external services require replacement or configuration?
Data migration	What records need a separate migration plan?

A positive verdict is a basis for proceeding, not a substitute for trying the converted result. If the verdict identifies an unsupported feature, decide whether to simplify it, replace it or keep the original application for now.

See stages and costs before approving the next step.

Names and marks

GitHub and GitHub Copilot are brands of GitHub, Inc. Usage policy. OwlMeans documentation does not imply sponsorship or endorsement by those owners.