Website Migration Case Study

A large university website cannot be moved with guesswork.

Masoud GolchinFebruary 22, 2024Updated September 25, 2026
A browser’s Network panel shows a PPHS newsroom request returning a 301 redirect before the Keck USC newsroom loads.

USC and the Scale of the Challenge

USC is the oldest private research university in California. It serves almost 50,000 students across 23 schools and runs a wide network of websites, subsites, and digital assets. The Keck School of Medicine alone had major content and operational needs, which made the move far more complex than a standard redesign launch.

Before the rebuild, Refact supported USC’s older site through maintenance work. That gave us a close view of the content structure, technical limits, and publishing needs already in place. When USC moved to a new web experience designed with Digital Pulp, our role shifted from support to execution.

More Than a Redesign

This was not just a visual refresh. USC’s web presence included microsites, subdomains, article archives, and assets spread across different areas of the organization. The real job was to move that content cleanly, preserve working paths for users, and reduce the risk that comes with a large institutional launch.

That kind of move needs a clear website migration process, not just development hours. It also needs careful coordination between design, engineering, hosting, and content teams.

How Refact Approached the Migration

The migration worked like a phased move, not a single cutover. We mapped old URLs, reviewed content types, handled transfers, and cleaned up content so it fit the structure of the new site.

  • Content migration: We moved pages, posts, and articles from multiple USC subdomains into the new environment. That included checking formatting, assets, and content relationships so key information did not break in transit.
  • Content cleanup: We organized pages, assets, and metadata to match the standards of the new platform. This helped the new site stay easier to manage after launch.
  • Redirect planning: We set up redirect rules to protect search traffic and send users to the right destination after old URLs changed.

Large moves succeed when teams do the prep work early. That includes the kind of inventory and structure review covered in prepare content for a CMS migration.

Planning a move of your own? Our Migration Blueprint maps the content, redirects, and risks before anything is touched. Get the blueprint.

Phase 1.5 and the PPHS Migration

One key milestone came with the migration of the PPHS website from its own subdomain into the new Keck School of Medicine site. We called this phase 1.5 because it sat between the first migration work and the larger remaining rollout.

This phase included three core tasks:

  • Newsroom migration: We cleaned and moved articles and related assets from the PPHS newsroom into the new Keck USC newsroom. We also added user profiles and access for authors and editors.
  • 301 redirects at scale: We created and automated redirect rules so old links would continue working and search performance would be protected.
  • Hosting transition support: We handled technical migration work tied to the new hosting setup so the move stayed stable.

That phase created a strong base for the rest of the project. It also showed why phased migration is often the safer path for large organizations with complex content systems.

From Migration Support to Long-Term Partnership

After phase 1.5, Refact began work on the remaining sections of the older USC web presence. Our role also expanded. Beyond migration, we now help maintain the new site and support future improvements as USC’s main digital partner.

The result is bigger than a cleaner website. USC now has a stronger foundation for content management, a better experience for visitors, and a partner that can continue improving the platform over time.

If you are planning a high-stakes migration and want a team that brings clarity before code, talk with Refact.

Migrating off a legacy CMS? Let’s talk. Free 30-minute call, no pitch.

Share
Written by
Masoud Golchin
Masoud Golchin

Masoud Golchin is a backend developer at Refact, working on server-side systems, internal tooling, and infrastructure. He builds and maintains the services that support both client projects and the team’s day-to-day development workflow. His work includes backend logic, developer tools, system reliability, and the technical foundations that allow products to scale and operate consistently. At Refact, Masoud focuses on creating practical engineering solutions that help the team move faster while keeping systems organized, maintainable, and dependable.

More from Masoud Golchin
Related Insights

More on Migration

See all Migration articles

Shopify to WooCommerce Migration: A Founder’s Guide

Shopify to WooCommerce migrations typically have no major issues on launch day, but problems usually crop up three weeks later when the marketing lead notices the top blog post now returns a soft 404, finance can’t reconcile last month’s orders due to uncommunicated changes in tax rules, or when a customer messages to say they […]

Migrate WooCommerce to Shopify: 2026 Playbook

A WooCommerce store wouldn’t normally fail on a Tuesday. Most of the time, it calcifies. A plugin update can quietly break checkout an hour before a campaign. Variant pricing can get out of whack from concurrent edits to products. The marketing team doesn’t touch the theme because there is no developer to assist. Eventually, the […]

Webflow to WordPress Migration: A Practical Guide

A Webflow site rarely crashes on a Tuesday. It starts to break down slowly instead. Each new step in the publishing process starts to get slower, new content types will not fit inside a CMS collection, the marketing team is forced to file support tickets for changes that once took five minutes, and the monthly […]

Your next step

Let's build something that lasts.

Tell us what you are trying to build, improve, or migrate. We will help you identify the right next step and what it will take to move forward.