Case Studies
Wadsworth Center
Wadsworth Center

Government

Wadsworth Center: Drupal 7 to 10, No Disruption to Users or Content

Drupal 7–10 Migration Content Architecture Accessibility Custom Features
Banner-image-wadsworth.png
Drupal 7→10
Full platform migration
Simplified
Content architecture, redundant types merged
Zero
User login disruption during migration
Improved
Accessibility and responsiveness

THE CHALLENGE

A government research hub carrying a decade of content architecture debt

Wadsworth Center is part of the NY State Department of Health and supports research programs in public health. The Drupal 7 platform it ran on was showing its age.

  • Numerous overlapping content types made management complex and error-prone
  • Drupal 7 had reached end-of-life, creating maintenance overhead
  • Content architecture had accumulated redundant, overlapping content types with no clear governance
  • Responsiveness and accessibility needed improvement
  • Search functionality needed refinement for a better user experience
  • Custom Drupal 7 features and a complex data structure required custom code to migrate without functionality loss

THE SOLUTION

Moving from a legacy government site to a modern research hub

01

Content architecture simplification

Content architecture simplification

Specbee's team consolidated content types with similar structures, reducing overlap and allowing for more diverse categories within each, grouped logically.

  • Content type consolidation
  • Reduction of redundant, overlapping content types
  • Content architecture simplification
  • Custom code, YAML files, and custom processors to preserve data integrity through the consolidation
02

Custom migration modules and Drupal 10 transition

Custom migration modules and Drupal 10 transition

The migration required custom code to handle Wadsworth's specific content structure. The transition preserved user logins and the site's existing look.

  • Custom migration code and processors developed for Wadsworth's content structure
  • Drupal 7 to Drupal 10 migration
  • User logins unaffected by the migration
  • Overall site look preserved through the transition
03

Performance, accessibility, and search improvements

Performance, accessibility, and search improvements

The migration also addressed responsiveness, accessibility, and search usability.

  • Responsiveness improvements
  • Accessibility standards compliance
  • Search function refined for better relevance and filtering
  • Performance improvements
04

Test catalog and content usability improvements

Test catalog and content usability improvements

Beyond the core migration, the team improved the test catalog feature so records could be updated via CSV upload instead of manual entry. This cut down repetitive editorial work and made keeping the catalog current less of a chore for the Wadsworth team.

  • Test catalog feature enhanced to support CSV file uploads for updated records
  • Usability improvements aimed at reducing manual content-update effort
05

Ongoing post-launch support

Ongoing post-launch support

Specbee stayed involved after go-live to help resolve any issues that came up, rather than handing off the platform and disappearing. That ongoing collaboration helped keep the migration's outcome stable in the weeks following launch.

  • Ongoing support provided to address issues after launch
  • Continued collaboration with the Wadsworth team to ensure a smooth, stable outcome

BACKGROUND

For a state agency, a Drupal 7 end-of-life situation isn't just a technical inconvenience — it adds maintenance overhead and risk. Wadsworth Center's website had accumulated years of content architecture decisions that made good sense at the time but had become overhead.

Government site migrations carry high stakes for disruption. User logins, existing URLs, and the visual continuity of a public-facing government website aren't things you experiment with. Specbee's approach kept those stable while the underlying platform changed.

KEY INSIGHT

The architecture simplification was the long-term payoff.

Government site migrations carry high stakes for disruption. User logins, existing URLs, and the visual continuity of a public-facing government website aren't things you experiment with. Specbee's approach kept those stable while the underlying platform changed.

The Results

A government research hub on a secure, maintainable platform

Migration complete, with a simplified architecture and improved usability.

MetricBeforeAfter
Platform Drupal 7 (EOL) Drupal 10
Content types Redundant, overlapping Consolidated and simplified
User logins At risk during transition Fully preserved
Accessibility Below standard Compliance addressed
Search Needed refinement Refined and improved

Complete

Drupal 7→10 migration

End-of-life software replaced with a current, maintained platform.

Simplified

Content architecture

Redundant content types consolidated for ongoing management.

Zero

User disruption

Logins and visual design remained intact through the transition.

Improved

Accessibility & search

Standards addressed, search refined. 

Work With Us

Talk to the team that delivered this

Most conversations start with a 30-minute call and a look at where you are today. No pitch deck. No pressure. Just clarity on what the right path forward looks like for your platform.

Typically respond within 1 business day · 100% Drupal-focused team · No generalists