Website relaunch – a defined task
Website Relaunch: Content Migration Without Blindly Copying
This page deals exclusively with the transfer of existing content. It helps decide what can remain unchanged, what needs to be revised, and which legacy content no longer serves a purpose in the new website.
The focus is on the content inventory: texts, media, downloads, page roles, and responsible approvals. Navigation and redirects are only addressed where they support a specific content decision.
Classify the relaunchDedicated workspace for this URL
Inventory Instead of Copy List
Each existing page is initially assigned a transparent status. Whether to retain, merge, revise, or not transfer are distinct decisions; a blanket export does not answer any of them.
Target Role Before Transfer
Content is only transferred to the new website once the target page, user query, and responsible person have been determined. This prevents old material from becoming unchecked clutter in the new system.
Acceptance at the Content Level
Before going live, it's not just a matter of checking if text exists. Completeness, correct media, functioning downloads, clear topic assignment, and documented approval are crucial.
Test sequence for this relaunch component
Inventory Management All relevant content is recorded in a worklist with URL, format, topic, recency, and responsible party. This makes gaps and duplicated topics visible.
Separate Value and Task – High previous effort is not a reason for migration. The decisive factor is whether the content in the new site answers a clearly identifiable user question or supports a necessary decision.
Connect Source and Target Pages – The future page is defined for each element to be migrated. Several weak legacy pages can be merged into a robust target page, provided their functions are truly aligned.
Check Media and Downloads – Images, documents, and embedded content are part of the migration. Therefore, file status, description, integration, and permissions are checked together with the page text.
Documenting Release and Remaining List – Open content is assigned an owner and a deadline. Items that are intentionally not migrated remain visible in the decision list to prevent them from reappearing unexpectedly just before publication.
Questions from Project Preparation
Which content should be included in the migration inventory first?
Business-critical service, product, and contact information, as well as frequently used downloads, are captured first. Supplementary content follows. The order is determined by the function in the new website, not by the old menu position.
Does every existing page need to be migrated?
No. An old page is only retained if it continues to fulfill a specific user question or necessary function. Content without a clear role can be revised, merged, or deliberately not migrated.
When are texts revised during migration?
The decision is made before the transfer. Minor corrections can be part of the migration; however, a fundamental repositioning requires its own editorial scope and should not be hidden as a secondary task.
How are duplicate topics in the old content handled?
First, the strongest common target role is determined. Then, useful statements are grouped together, and repetitions are removed. Separate target pages only remain relevant if different search or user questions exist.
At what point is the content migration complete? : ...
The process is complete when all planned content has been assigned to its target page, approved by the relevant experts, and checked for completeness, and when any deliberately excluded content remains documented.
Suitable basis for the request
For an initial assessment, the existing page inventory, the goal of the relaunch, and which content is particularly critical are sufficient.