Development
Your Redesign Is a Migration Wearing a New Coat
The mockup never showed the archive.
Every institutional redesign begins the same way: leadership approves a beautiful set of comps, the contract is signed, and everyone exhales. What the comps showed was a homepage, a news feed, an interior page template. What the comps did not show was years of PDF-linked program guides, a faculty directory with hundreds of inbound links from Google Scholar, or a few legacy microsites that still send traffic. The look was the meeting; the content is the project.
Redesign as a category misleads buyers into thinking the work is visual. It is not. Visual work is the surface that gets approved in a conference room. The actual labor is a migration: moving content, reassigning addresses, auditing what is alive versus what is merely indexed, and deciding what gets cut versus what gets carried. Institutions that understand this before the contract is signed finish on time. Institutions that discover it at launch extend the contract.
The look was the meeting; the content is the project.
What crawlers find that nobody remembered.
When we crawl an institutional site before a redesign, the number that surprises clients is never the homepage count. It is the PDFs: annual reports, program sheets, accreditation documents, grant attachments, files uploaded and forgotten across a decade of staff turnover. Each one may have inbound links. Each one is a decision waiting to be made. Redirect it, retire it, or rehost it — but those are three different answers, and they cannot all be made on launch week. A site migration that starts without an inventory is not a migration; it is a gamble.
The same audit surfaces URL structure problems that the new design would inherit if nobody caught them: campaign-tracking slugs baked into static pages, department names that changed two reorgs ago, subdomain arrangements that predate the current CMS. None of this appears in a mockup. All of it determines whether the new site launches clean or launches carrying the old site's debt in a new container.
Structure before surface, always.
A migration-first redesign begins with a content inventory and a redirect strategy, not a mood board. The content model — what types of pages exist, how they relate, what fields each one requires — is designed before a single template is sketched. This is not slower. It is faster, because the expensive late-stage rework of a design that assumed the wrong content shape never happens. The content architecture is the foundation; the visual system sits on top of it, not underneath it.
Redirect maps get built in parallel with design, not after. Every URL in the current site is assigned a destination or a retirement decision before launch day arrives. Search equity built over years stays intact. Staff who embedded links in email newsletters, grant applications, and printed materials are not handed a list of broken addresses the week the site goes live. If you are preparing a redesign scope and none of this is in the plan yet, talk to us before the mockup phase begins.
The sites that hold up two years after a launch are not the ones with the sharpest visual system. They are the ones where someone mapped the content, made the hard retirement decisions, and built the redirect layer before any code went live. The look fades into the background. The structure either works or it doesn't. That is the project your institution is actually buying — and the earlier you know it, the better.