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.The decision has been made to release the Search API D8 version without a migration path. Since then, there has also not really been any interest in getting a migration path working. However, if we do want to implement this at some point, this would be the issue to do it.
So, if you could use a Search API migration for your site, please comment here to show your interest!
Since the structure of our configuration is still pretty similar to the D7 version, writing the migration code should be relatively straight-forward. We'd just have to know whether there is actually any interest.
Comments
Comment #1
drunken monkeyAlready wrote a first one, for updating the used variables. I guess we shouldn't wait with this but always include an update function when the underlying system is changed. That way, we'll also hopefully forget none.
Comment #1.0
drunken monkeyAdded note about new config system.
Comment #2
drunken monkeyComment #3
drunken monkeyUpdates are dead, long live Migration!
Comment #4
drunken monkeyComment #5
drunken monkeyCore proves that it's fine to do a stable release without migration code – but it would probably still be good to get that working soon. I don't think it will be that difficult.
Comment #6
drunken monkeyFrom #2953038: Upgrade (migrate) data from Drupal 7 => Drupal 8:
The config is pretty similar, so writing migration code should be relatively straight-forward – provided the entity types, fields, etc. being indexed are also the same on both sites.
Also, updating the IS to reflect the current state of the discussion.
Comment #7
drunken monkey