> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/changelog/migration-report.md).

# Check Duaer upgrade readiness with the migration report

In Duaer, the migration report scans every digital organization and the instance configuration, and lists what to fix before you upgrade to the next major version.
## Open the migration report

The owner or an admin of the Duaer instance opens Settings › Migration report. The top line says how many digital organizations are already compatible with the target version, for example "36 of your 40 Duaer Organizations are already compatible with version 3.0.0". The goal is to leave no problems in the rest or in the instance configuration.

For each change, refer to [Duaer v3 breaking changes](/changelog/v30-breaking-changes.md).

## Read Duaer migration report issues

Issues sit on two tabs: Duaer Organization issues affect specific digital organizations, and Instance issues affect the whole instance. Each issue has a title, a description, a documentation link, and a severity:

- Critical: breaks after the upgrade. Update or replace the affected nodes; an instance issue may stop the instance from starting.
- Medium: may still run but could produce wrong results. Review and test before upgrading.
- Low: behavior changes slightly in specific cases. Most digital organizations keep working.

## Fix digital organization issues

1. Start with Critical. Select the Duaer Organizations count under an issue to open the affected list.
2. The list shows the name, whether it is published, the nodes affected, the number of executions, and when it last ran and was last updated. Select an affected node to open it directly.
3. Update the digital organization as the issue documentation describes, and test it in a development environment first.
4. Some issues have a Migrate button that fixes the digital organization for you. Migrate saves the change as a new version while the published version keeps running; when it looks right, select Publish, or Skip publishing to publish later.

## Fix instance issues and check again

Instance issues need environment variable or deployment changes; follow each issue's documentation link. When you are done, select Refresh to scan again. Once both tabs show no issues, upgrade as described in [updating Duaer](/hosting/installation/updating.md).
## Questions

### Who can see the Duaer migration report?

The owner and admins of the Duaer instance. Members do not see it in Settings.

### Does Migrate in the Duaer migration report change the live version?

No. In Duaer, Migrate saves the change as a new version and the published version keeps running until you select Publish.