Read a sample: 1. The Content Side of a Website Migration
A website migration can look like a technical project from the outside. A new platform is selected, a design is approved, and someone announces a launch date. The marketing team may be asked to provide updated copy or review a few pages near the end.
By then, many of the most consequential content decisions may already have been made—or missed.
What happens to an old service page that customers still use? Where should a bookmarked resource lead if its topic is absorbed into another page? Who confirms that the new contact information is correct? If the new site has less room in its navigation, which sections should remain easy to find?
These are not merely copyediting questions. They affect how people find information, complete tasks, and understand the organization. They also require coordination with the colleagues who build, configure, and launch the site.
The content side of migration is the work of making those decisions deliberately. It includes understanding what exists, deciding what belongs on the new site, preparing it for its new home, and checking that people can still reach and use it. The content team does not need to perform every technical task. It does need to make its requirements visible early enough for the right people to act on them.
This book will help you do that without turning you into a developer or asking you to create an elaborate process your team cannot maintain. The goal is a workable plan: clear decisions, named owners, useful records, and checks proportionate to the risk.
A website migration is a meaningful change to the location, platform, structure, or presentation of a site. Your organization might move to a different content management system, change its domain, redesign its pages, merge several sites, or reorganize its navigation. Some projects involve several of these changes at once.
Not every migration changes every page. A platform move might preserve much of the existing structure. A reorganization might leave the platform in place but change where important information lives. In either case, the content team should look beyond whether text has been copied successfully.
A page is more than its paragraphs. It may include a title, headings, images, links, downloadable files, contact details, forms, and information that appears in search results. It also has a relationship to other pages. Visitors may arrive through a search engine, a saved link, an email, a partner’s website, or the site’s own navigation. They may never see the homepage.
A migration can interrupt any of those paths. It can also improve them. Outdated instructions can be corrected, overlapping pages can be combined, and important information can become easier to find. The challenge is to make improvements without losing useful material or leaving visitors stranded.
That is why “move everything” and “start fresh” are both risky as automatic strategies. Moving everything can preserve clutter, contradictions, and obsolete information. Starting fresh can discard pages, files, and paths that still serve a purpose. The better approach is to examine what you have and make decisions based on audience needs, business priorities, available evidence, and the constraints of the project.
To make the work concrete, consider a hypothetical organization called Harbor House Learning. It offers workshops and practical resources for community groups. Its small marketing team manages the website alongside email, events, and other communications.
Harbor House is moving to a new website platform. The organization also wants a simpler navigation menu and a clearer distinction between its workshops, resources, and organizational information. An external development partner will configure the new site, while internal staff will supply and approve the content.
The current site has grown over time. Some pages describe active workshops; others refer to events that have passed. A resource section contains useful guides, but several pages overlap. Staff members have linked to particular pages in emails and shared downloadable files with community partners. No one person knows the purpose and history of every page.
The marketing manager, Lena, is responsible for coordinating the content work. She does not need to know how to configure the new platform. She does need to know which decisions the development partner is waiting for, which colleagues can verify the information, and which pages deserve attention before launch.
For example, Harbor House has an older page about planning a community meeting. Lena proposes combining its most useful advice with a newer facilitation guide. That sounds straightforward until the team asks a few questions. Are organizations still linking to the older page? Does it contain a download that is absent from the newer guide? Can visitors arriving at the old address be sent to a relevant destination? Who will check that the combined guide is accurate?
The answers involve content judgment, organizational knowledge, and technical implementation. No single role owns the entire problem. A successful migration depends on connecting those roles before assumptions become defects.
Harbor House is an illustration, not a model your organization must copy. Your site may sell products, explain services, support members, or publish public information. Your team may be internal, external, or a mixture. The same underlying questions still apply: What exists? Who needs it? What should happen to it? Who will make that happen, and how will the result be checked?
Content responsibility begins with decisions, not just writing. Depending on the size of your organization, one person may perform several of the following responsibilities, or each may be…