> 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/1-0-migration-checklist.md).

# Duaer 1.0 migration checklist

What to check when moving up from before Duaer 1.0.
## Do not start from the commit list

Name the version you are on, then see what the version you are moving to drops. 1.0 is where this product line settled those habits. Later 2.0 checks mark the Start node as removed.

Crossing 2.0 means [2.0 breaking changes](/2-0-breaking-changes.md). Crossing v3 means [v3](/changelog/v30-breaking-changes.md). Keep the encryption key and the database on every upgrade. Refer to [updating](/hosting/installation/updating.md).
## Questions

### Which page do you read first from a very old version in Duaer?

Read this page, then the breaking-change page for the major version you are moving to. Follow what the instance version check names.

