Email us at info@henrytech.org to discuss your Drupal Migration today!
Things you will need:
1) MSSQL (or Sitecore) database file
3) Docker
Steps:
1) Extract MSSQL (or Sitecore) database file (most likely .zip)
Email us at info@henrytech.org to discuss your Drupal Migration today!
Things you will need:
1) MSSQL (or Sitecore) database file
3) Docker
Steps:
1) Extract MSSQL (or Sitecore) database file (most likely .zip)
If you have been tasked with migrating a site from Sitecore to Drupal, you might have run into the same problem I did -- a complete lack of all documentation on the subject. There is one module called "sitecore_migrate" which has a Drupal.org page, and has a promising name, but left us with that drooping feeling of disappointment as it holds literally nothing. And I found out why... to make a module that migrates ANYTHING from Sitecore to Drupal automatically is extremely difficult as I found out firsthand. So I believe the guy had high hopes and then realized how impossible it would be.
D10 Upgrades from Drupal 9 can be tricky! There are usually unforeseen issues. Here are some commonly seen problems and solutions.
The best place to find steps on how to upgrade: https://www.drupal.org/docs/upgrading-drupal/upgrading-from-drupal-8-or-later/upgrading-a-composer-based-site
Sometimes during a migration, we need a process plugin, which alters the value before it gets stored in the new database. This example is useful if the original values have too many characters to fit into the new field.
Create a new file as your_custom_module/src/Plugin/migrate/process/SkipOnTooLong.php:
Sometimes during a migration, fields are not directly migrateable in the .yml file. In this case, or if there is more processing of the data that cannot be handled by a plugin, you can use an event subscriber that fires on the migration of each row.
In your your_custom_migration_module/src/EventSubscriber/CustomMigrateSubscriber.php: