Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

The migration screen lacks important information for a user to decide wether she should migrate her vault or not.

Motivation

A new version of Cryptomator can introduce a new vault format, which is up to now always enforced to be used to keep implementation and support low. Unfortunately, also with a version some legacy OS or configuration might not be supported anymore. An unmindful user could migrate its vault and just notice on such an unsupported OS, that he cannot rollback the migration.

Therefore, we should update the migration screen with additional reminders or warnings.

The current migration looks like this:

I think, the vault health check intro screen can be used as a good template:

Considered Alternatives

Block installations on unsupported systems - The user might still use the raw jar, and it might migrate on supported systems.

Add a rollback rountine for the migration - Depending on the migration, this would require effort.

Anything else?

Ideas of warnings can be taken from #1877 and our blog post about 1.6.0.