Row, Row, Row Your Rows Surviving Multi Agency Government Drupal Migrations
summary
Practical migration recipe that actually works: export legacy databases to CSVs, keep the SQL queries and CSVs versioned in Git, and drive Drupal imports with migrate_source_csv plus migrate_plus/migrate_tools. A Drush-backed helper (shared as migrate CSV keeper on GitHub) automates fresh exports; files are fetched over HTTP and the process preserve file URLs to avoid broken hotlinks. Use Tugboat previews to run migrations per PR; reuse a “junk drawer” repo; real projects hit 50–70k rows and combine multiple sites into one.
AI-written summary · about
chapters (19)
- 0:00Introduction and best outcome
- 1:24Speaker introduction and background
- 3:13Why Drupal migrations are complex
- 4:17Pre-migration team alignment
- 5:41Drupal migration tools and setup
- 7:06Exporting data to CSV for migration
- 9:20Cleaning data with SQL queries
- 12:11Starting with user and taxonomy migrations
- 13:34Files and media migration strategies
- 15:17Understanding migration YAML files
- 17:28Using process plugins for complex tasks
- 19:58Testing and running migrations locally
- 21:22Automated QA with Tugboat
- 22:45Launching migrations and minimizing downtime
- 23:30Scaling migrations across multiple sites
- 24:35Reusing code with a junk drawer
- 26:02AI assistance for migrations
- 27:08Key takeaways and summary
- 28:33Q&A session
related talks
29mYour database migrations are bad and you should feel bad
47mUpgrading to Drupal 10: A real case
48mThe Great Migration
50mMigrating Your Most Critical Feature Without Regressions or Downtime
18mFrom Today to 10X: Why Groww chose
35mMigration without Migraines: Automatic Migration at Scale
20mLegacy Migration... Differently
36m5 Hard-Learned Lessons from Successful Database Migration and Modernization