Skip to content

A raw copy of the custom migration used for the FCS Drupal 7 to Drupal 8 project.

Notifications You must be signed in to change notification settings

CornellCustomDev/cwd_migrate_fcs

Repository files navigation

cwd_migrate_fcs

A raw copy of the custom migration used for the FCS Drupal 7 to Drupal 8 project; by Alison McCauley and Eric Woods.

Please note! -- Migration functionality included in Drupal core and the key contrib modules is changing and growing alllll the time, so just remember that this migration was built in summer 2019. One example, from Drupal core 8.9.0-beta1 release notes:

A new complete node migration, d7_node_complete.yml (for Drupal 7) and d6_node_complete.yml (for Drupal 6) is now available. This migration will migrate all nodes and node revisions, including translated nodes and translated node revisions. The complete node migration will eventually replace the existing trio of node migrations. See change record on the new 'complete node migration' for more information on the new migrations.

Links

Just, dumping some links in here until if/when we do additional documentation/organization!

Notes from running on Pantheon envs

Pantheon documentation

...including recs for connecting to source/D7 database: Running Drupal 8 Data Migrations on Pantheon Through Drush

REMINDER: may need to wake up source site, if it's a multidev (i.e. especially during development):
terminus env:wake cu-dfa.poli-migr

Misc

...thoughts or whatever...

  • Key contrib modules: migrate_upgrade, migrate_tools, migrate_plus
    • Explanation of "what's what" (from @heddn on Drupal slack, 2019-12-23):

      upgrade is generating config entities from the core migrate templates.
      tools is the toolbox to execute migrations
      plus is all the process and source plugins that didn't make it into core, including config entity support

  • The URL alias handling in this migration is SUPER COOL. "Also," as of Drupal 8.8.x, aliases are different, so, FYI (from @mikelutz on Drupal slack, 2019-12-23):

    Prior to 8.8 there was a custom destination for url alias, but starting with 8.8.0, aliases are entities, so you can migrate them in like any entity.

  • From John Locke (@freelock) on Drupal slack (2020-02-15), talking about how they do migrations without a custom migrate module, in response to my question about an online resource for doing migrations in the UI and/or without a custom migrate module (since my migration experience is 6-8 months old):

    what I do is use drush migrate-update to create the migrate configs
    e.g. drush migrate-upgrade --configure-only --legacy-root=/home/john/git/drupal6
    then drush migrate-import --tag=Configuration
    and then when you drush cex you've got a ton of migrate configs to work with
    oh but you do want to enable all the modules that might be included in your migration before starting -- e.g. media migrations, flag, addressfield, etc -- many of these have migrations that will auto configure themselves with that first command
    and you also need to set up a database connection to the old db. Haven't looked for a good online resource recently -- we've done 20 - 30 of these, so I'm mostly copying from existing settings files, and my shell history 😉

  • Get list of available migrate plugins -- this example will output a list of source plugin keys:
    lando drush ev "print_r(array_keys(\Drupal::service('plugin.manager.migrate.source')->getDefinitions()));"

About

A raw copy of the custom migration used for the FCS Drupal 7 to Drupal 8 project.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages