Society website replatform
A global engineering professional society, migrated off a legacy CMS after a competitive bid.
NEEDS OWNER INPUT: this client is not named pending written permission. The case study is written so the engineering stands on its own without identifying them. Flip the permission field to Named once consent is in writing.
The migration
Around two thousand articles and fourteen hundred URLs, off a legacy CMS and onto WordPress. Every URL was audited and categorised before anything moved: most migrated directly, several hundred needed their content revisited, and a smaller set was archived behind redirects.
When the source system fights back
The legacy host refused automated requests, returning an error on essentially every media file. The source database was missing its users table entirely, so migrating accounts had to become a separate build rather than part of the import. Neither of these appears in any plan. Both are the actual work.
Who is allowed to edit what
A volunteer organisation has hundreds of people holding roles that turn over annually. We built the system that maps those roles to editing rights: someone arrives through institutional single sign-on, the system works out which committee positions they hold, links them to their public profile, and decides exactly which pages they may edit. Nobody needs admin access to update their own committee page.
The annual turnover of those appointments is automated too, with expiry dates, reminders and a dashboard showing what is about to lapse.