The thing that trips people up most isn't the module compatibility list — it's field data that technically migrates but silently loses formatting or reference integrity. Run a full content audit before you start, not just a module audit. Specifically check: paragraph/field collection nesting, any custom entity reference views, and URL alias patterns if you're on pathauto. Those three are where most "successful" migrations turn into a six-month cleanup project afterward.

I have an old Drupal 7 site that I can't seemingly migrate to drupal 11, Here's where I am at present:

I downloaded all the files from the existing site and created a ddev copy of the site with the same php version etc, the site renders and i can view all the nodes and such

I created a new ddev project running Drupal 11.4.4 and add a secondary db to that via ddev import-db --file=/home//Documents/Sites/sitename/databasename_2013.sql I also created .ddev/docker-compose.volumes.yaml so can mount the files etc from the drupal 7 site for the migration module as well as added the required modules that I used on the drupal 7 site if they existed

After running the migrate step via the extension Migrate Drupal UI I see that the images & users are imported in the new ddev Drupal 11 site, the images are too, but none of the nodes are done, I'm stumped on how to proceed now, I suspect the issue is related to multi languages as that site initially was drupal 6 and multi language enabled but not sure how to check now after all these years