Content with Approved versions, older than the latest current version (meaning, a draft or more have been stored after the approved version) will always be dropped in migration.
If Portlets using identical xslt-file uses same params, but differs only on DataSource-tab in CMS, these changes needs to be migrated manually. Making CMS2XP do this good is not easy, and it will not come without downsides on other things, like "too many part-folders in the app" etc.
Headsup: Name of each Part will be the filename of the xslt-file used for that Portlet in CMS, but Fragments will use the Portlet's name.´
Then I guess we've summarized all the quirks we've stumbled upon today.
Document these in the tool's documentation:
Then I guess we've summarized all the quirks we've stumbled upon today.