Case Study: How Princeton University upgraded from Drupal 7 to Drupal 9
summary
Princeton upgrades roughly a thousand Drupal 7 sites into Drupal 8 then 9 (now 9.5), consolidating three bundles—Site Builder v1, Open Scholar, and custom sites—into Site Builder version two while eliminating many dead shells (63 sites surprisingly upgraded, hundreds pruned). ffw writes custom migration scripts and handles upgrade tooling; internal team (15 people, seven developers, a dedicated PM) builds platform features, a tiger theme, a sites database app and uses a project inbox (drupalupgrade@princeton.edu). The team injects fun with paper tigers and phases work to keep momentum.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 2:56History of Drupal at Princeton
- 5:40Project goals and leadership
- 9:03Scope and site assessment
- 14:17Consolidation strategy
- 19:44Estimating and finding partners
- 23:23Project kickoff and execution
- 27:45Communication and management
- 33:44Lessons learned and closing
- 37:24Q&A session
related talks
47mUpgrading to Drupal 10: A real case
45mWhat path forward? The future for non-profit organizations still on Drupal 7
42mSo You Want To Rewrite That...
53mDeconstructing the monolith
40mModernizing the Legacy
30mTackling Technical Debt at Adobe: A Story
13mMigrations - an Upgrade Story
35mRow, Row, Row Your Rows Surviving Multi Agency Government Drupal Migrations