When migrating to a new system, there are challenges that must be taken into account.
Something that you'll undoubtedly encounter early on if you’re used to earlier versions is the shift from Classic UI to the new Touch UI, which should be used in order to leverage new features. Right clicks and hovering aren’t possible as the UI is optimised for touch devices. This may affect you if, for example, Tab Containers are set up so that an author navigates to each tab by selecting it, just as an end user would. In these cases, the recommendation is to rebuild the components as overlays. Re-enabling the functionality (building an overlay) may potentially cause problems when upgrading to a new version.
Some existing features have been enhanced, which may require some training for authors to make the transition easier. The reference overview, for example, which previously showed all incoming references aggregated on page level, now shows every incoming and outgoing reference (lent and borrowed content) on component level. This is more precise but will fail a one-to-one comparison. This does require some configuration during the migration but it helps authors to see how the pages are connected and to know that they might be breaking links when they delete or unpublish a page.
Last but not least, there are smaller new features like the Timeline, which allows users to see the change history of a page and compare versions side by side. While changes such as this one may be more subtle, they are very useful and will increase user satisfaction.