A better idea would be to detect a new migration and take the steps necessary to make sure the user doesn’t lose any data. Leaving it in users’ hands is going to generate endless misunderstandings, support tickets and more lost data in the long run.
Few users will take the time to understandd andd take proper care of data management settings.
I see your metadata editing team is working very hard on these features. You should rush out a knowledge base article with the right settings and why.
Writing metadata changes immediately to the .xmp and storing all metadata in the .xmp and making the .xmp king is the only route to safely preserve metadata in a multi-application workflow. It’s not that it’s not possible to lose metadata to badly behaved apps with the .xmp king structure but without this structure, one is sure suffer metadata inconsistency and over time to lose metadata.
Windows world is way cheaper
I like my Mac Pros and I like Mojave. Sadly I don’t like DxO very much any more as I’ve made a huge investment of both money and time in your applications. Forcing users to go through the OS upgrade annually is extremely customer hostile. With OS -2 or better yet OS -3 like CaptureOne users can skip OS versions and change OS every two or three years.
I can’t imagine wasting time on a full OS update every year.