Drupal Migration

End-of-life notices, accessibility failures, hosting renewals and redesigns can all trigger major Drupal platform decisions. This webinar focuses on working out how much complexity a project actually requires before committing to an approach. ...more

A 2020 request for volunteers to test a non-production Drupal 9 build provides an early benchmark for the platform work that followed across Australian government agencies. ...more

A replatforming project can move the visible content and still leave important structure behind. References between Drupal entities need their own migration plan. ...more

Field mapping was only part of this council migration. The source API also required Drupal to account for throttled requests, unusual pagination, incomplete records, and cached downloads during development. ...more

Eight additional Drupal GovCon respondents focus on the controls, human decisions, and content structures that keep digital systems usable when automation and changing discovery meet production reality. ...more

A separate conversion copy lowers the risk to the live site, but it does not settle whether every module, theme, layout, and custom feature will work after the move. ...more

Security patches do not deploy themselves, maintain custom integrations, or decide what content moves to a replacement platform. University transition plans show where those responsibilities remain. ...more

Modern headless tools can move faster in clean greenfield builds. Talish Khan argues that the comparison changes when content structures, migrations, permissions, and long-term ownership become harder. ...more

When Paragraphs-based content models grow deep, Drupal teams can inherit slower rendering, heavier databases, and harder migrations. Custom Field maintainer Andy Marquis explains where field-based structured data offers a leaner alternative, and where Paragraphs still belongs. ...more