[Meta] Support for D7 -> D9 contrib migrate

I'ved added #2897021: [META] Migrate support for importing field collections as paragraphs to help us plan a better migration path for field collections.

For the remaining items on the list... to help us create a plan for all things important to you, please pick things off and create contrib tasks for them as well. Similar to those I created for field collections. Drupal is a do-ocracy, so let's do this thing.

Thanks for starting this effort, rivimey. I haven't looked at Migrate much before, but I'm starting to migrate three small sites (inc my personal blog) so am finally taking interest in this and will do what I can.

Added the top D8 downloaded modules to the IS.

I realize this is targeted for contrib modules, but here are a couple annoyances I've encountered that could tangentially be related to contrib modules, that I'm not sure where else to mention:

* core "Shortcuts" module, shortcut set migrations are wonky and links are broken in various cases when contrib module edit screens have changed URLs. Not sure a lot can actually be done to fix this automatically, but maybe a message would be nice to go review the links.

* Permissions from contrib modules are migrated "as is" from Drupal 7 even if there is no Drupal 8 module providing the given permission. These permissions appear in the yaml file exports for each role, but do not appear in the UI, and there's no way to clean these up except by scanning through the file to manually remove them from each role, then run configuration import to delete from the database.

@jwilson3: Did you check if there are core issues about those?

I did, and couldn't find anything relevant (probably, for reasons mentioned, that this is a bit of a gray area between core and contrib space). At the very least though, one would think core should be trimming out "non-existent" permissions -- so maybe its worth filing as a core bug -- but on the other hand maybe core folks consider this a feature, so you can manually review, replicate as necessary and clean these up yourself?

Edit: only one way to find out, I've created #2953111: Only migrate role permissions that exist on the destination.

re #12: please open a core issue on the shortcuts issue. We can discuss possible fixes there.

Adding workflow / wbm upgrade links.

it needs suggestions to site builders, indicating which modules are supported migrate targets for the old D7 ones. E.g. when the jplayer module is seen in the source DB, it could suggest that installing the audiofile module + jplayer plugin before migrate would enable migrate to properly migrate the fields.

This is worth its own issue in the core ideas queue, sounds like a 'migrate suggestions' module.

There is already https://www.drupal.org/project/upgrade_status which does things from the other direction - you can install it on a Drupal 7 site and it will show your options for Drupal 8 modules.

Changing this into the [meta] it seems to be.

Reordering the summary, in preparation to add a new contrib migration issue.

Adding feeds

Moving closed issues to a subsection

Add pargraphs meta

Added a note about #2936365: Migrate UI - allow modules to declare the state of their migrations.

Might it be useful to also collect links to articles / docs pages that describe how to handle migration scenarios? There are lots of common config scenarios that arise, I think many of them could be simplified.

Common scenarios:

• D7 module used a number of variables, in D8 it uses configuration objects, but ultimately stores the same or similar values.
• D7 module used variables, in D8 it uses config entities.
• D7 module used a custom table for configuration, in D8 it uses config entities.
• D7 module used a custom table for configuration, in D8 it uses a field on specific entities.

I'm sure there are lots more scenarios.

Noted that Pathauto's patch is in the 8.x-1.4 release.

Added items for Easy Meta and Metatags Quick, both of which will get migrations to Metatag.

Curious if anyone thinks #3062331: Automate generation of D7 -> D8 migration paths? would be helpful here... a tool to auto-generate Migration paths for modules being converted from D7 to D8. Or wishful thinking that this could be done?

@webchick: Yes, I think that would help a bit.

Oh, shit yeah! I just found out via https://www.lullabot.com/articles/overview-migrating-drupal-sites-8 that https://www.drupal.org/project/migrate_upgrade is a thing, so apparently that problem is solved. :)

Thanks for sharing the An Overview for Migrating Drupal Sites to 8 article @webchick. I wonder why it's not included on Planet Drupal, even though it's included in their feed https://www.lullabot.com/planet/feed?

Clarified that some of Metatag's upgrade path hasn't been done yet.

Added Fieldable Panels Panes' upgrade plan.

Page Title, and extra Metatag migrations.

There is now a patch for #2953036: Upgrade (migrate) data from Drupal 7 => Drupal 8

#2953036: Upgrade (migrate) data from Drupal 7 => Drupal 8 fixed!

I am willing to help get these issues committed. If tests are needed, I can write them if a test fixture (a source db dump) is provided. Ping me in #migration to ask your questions.

Eck fixed.

#2638406: Poll migrate support is ready for review again and any help to push it over the line will be appreciated as this was a core module in Drupal 7 so a migration path is pretty important.

Activity has certainly died down here since about 2019 and activity has been happening in the contrib project themselves or in the #migration Drupal slack channel. And with Migrate Drupal and Migrate Drupal UI being approved for removal I don't this issue is needed any more. It served it purpose well.

Not sure how to close this but working as designed seems right.