There was a question in slack about the plan for migrations, I couldn't find an issue in the queue so I am opening one.
There are two parts to migrations, for Drupal CMS it will probably need to work on both:
1. Having the equivalent content model and features to migrate into.
2. The actual data migration itself.
For the data migration, Drupal core is going to remove the Drupal 6 and 7 source plugins from Drupal 12, see 📌 Tasks to deprecate Migrate Drupal Postponed . However there are no plans to remove the migration framework or modern Drupal destinations from core, and if Drupal CMS starts to have migration recipes available that would be a good use case for it now that Drupal 6 and 7 are both end-of-life.
For WordPress migrations specifically, there is already some contrib support:
https://www.drupal.org/project/wordpress_migrate →
https://www.drupal.org/project/wordpress_migrate_sql →
Active
General
I have two recipes that leverage the Migrate API. The second one is pretty minimal for now (and it has only a dev release).
Add reference to parent issue: 📌 [META] Starshot work tracks Active
Don't want to mix this up with the 1.0 tracks, we'll have to figure out how to group these in the context of the new and ongoing work. Not sure what that is yet!