Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.If I create my own migrate_plus.migration yaml, I try to list migration_dependencies and name ones from the core d7 migrate_drupal module (d7_note_type, d7_field). The dependencies get ignored.
If I copy a yaml from it and put it in my module (ex. d7_user_role) and give it a migration_group, the dependency is then respected and used.
Is this the advised direction for migrations? Copy core yml out into your own migrations and tweak as necessary? What I am trying to do is leverage the parts that work (create roles, filter formats, node types, fields, users) so I can script the parts that don't work well (content, files, taxonomy).
The source is Drupal 7, and I am running into problems because some of the field types in use (Address, Entity Reference, Geofield, Weight) have no migration path nor is there way to hook in and describe the migration path to the migrate_drupal module (see #2569805: For Drupal migration, identify the source module).
Comments
Comment #2
mikeryanmigrate_plus/migrate_tools right now only deal with migrations defined as configuration entities, not with core migration plugins. In #2752335: Properly integrate configuration-entity-based migrations with the core plugin manager, I'm hoping to find a way to integrate the two forms of migration plugins so the tools can handle both seamlessly. In the meantime, yes, the expectation is that you will export all the migrations to you need to configuration entities to do custom Drupal-to-Drupal migrations.
Comment #3
mikeryan