Future of migrate in core in a post Drupal 7 world

Problem/Motivation

There has been some discussion about what the future of migrate is once Drupal 7 marketshare is sufficiently reduced and it no longer makes sense to maintain the Drupal 6/7 migrations in core.

I don’t actually believe that d7 marketshare will be low enough by Drupal 10 to remove the migrate_drupal module, but it will happen eventually. One of the thresholds we’ve used as to whether a feature goes in contrib or in core is whether it directly supports the core mission of providing Drupal 6/7 migrations into drupal 8, so what happens once that system is no longer needed?

Proposed resolution

Discuss the future of migrate in Drupal Core in a post Drupal 7 world

Summary of discussion

Migrate API

• Move back to contrib

OR

• Make the API robust (whether that is soong or not)
  • Proved useful for pulling data into core. lowers the barriers to entiry to Drupal when coming from other systsm.
  • Keep destination plugins, base process and migration plugins. source plugins can be deprecated
  • Bring more migrate plus and tools into core
  • Define a new threshold for what’s allowed in core, otherwise we risk a bloat of very specialized process plugins, among other things. The new criterion could be to support migrations from JSON:API (the actual API, not the module that implements it in Drupal).

migrate_drupal, migrate_drupal_ui

• Move to contrib when D7 market share drops 'enough'