Compare the structures of the old and new stations

How to migrate the old website to maintain content and business access

Updated on 2026-11-21

1 / 6Compare the structures of the old and new stations

Revision is not just about changing pages. Only by first taking inventory of the old URLs and data, and then arranging corresponding relationships, switching and rollback, can the loss of entries and form interruptions be reduced.

Let’s talk about the conclusion first

Back up the old URL first and try to keep the valid address; map the pages that need to be changed one by one, test the redirection, and continue to check the access and business process after going online.

Take inventory of the old site and first find the assets that need to be retained

Existing page addresses, images, download files, content categories and form destinations should be sorted out before revision. When you have statistics permission, check which pages bring visits, consultations or external references; if you don’t have statistics, you should also check the navigation, in-site links and known promotion entrances. If you only copy the text on the home page, it is easy to miss product pages or documents that are still collected by customers.

The backup should cover the files, databases and necessary configurations actually used by the website, and record the operating environment and recovery methods. Domain name resolution, certificates, emails, and websites may be managed by different accounts, and the person responsible must also be identified. Do not overwrite the production directory when the old site has not been completely saved, otherwise there may be no recoverable version after an error occurs in the new site.

  • Form a list of old URLs and mark them as retained, merged, redirected, or deleted instead of just counting the number of pages.
Organize old pages and retain content
Organize old pages and retain content

Arrange clear destinations for old addresses one by one

For pages whose content themes are still the same, the original address will be retained first; when the path needs to be adjusted, a correspondence table between the old URL and the new URL will be established. Permanent migration usually uses a permanent server redirect, such as 301 or 308. It should point directly to the corresponding new content, avoid multiple jumps, loops, or redirect all old pages to the homepage.

Pages that are truly deleted and have no suitable replacement content should return the correct Not Found or Removed status. If you change the address of pictures and download files, you also need to check the references. When retaining old product information, the version and current applicability must be clearly marked, and services that have been discontinued cannot be continued to maintain access.

  • Randomly check the actual occurrence of deep addresses, addresses with Chinese characters, capitalization, and trailing slashes.

Go through the entire business process in the test environment first

The test site will check content, mobile layout, images, navigation, search and downloads, as well as form fields, receiving locations and confirmation prompts. Test data should be clearly labeled to avoid being mistaken for real business opportunities. When using the old site to export data, clean up unnecessary personal information first, and control access permissions in the test environment.

Search-related settings are reviewed separately: official domain names, canonical addresses, site maps, internal links, and prohibited indexing settings during the development phase. The configurations of the test station and the official station cannot be copied directly. The web page returns a successful status, the browser displays correctly, the form is saved successfully, and the notification reaches the person in charge, which are results that need to be verified separately.

  • Select the three most important customer paths and have them confirmed by content, technology and business leaders.

The switching time, freezing range and rollback are agreed upon in advance

Choose a time period when there is relatively little business to switch, and agree on a content freezing time in advance. Before switching, make a final backup to record the old and new versions, deployment location, and parsing settings. If the old site is still generating orders or inquiries, it is necessary to clarify how to supplement the incremental data to avoid the data newly added after backup being lost during the switch.

Write down issues that must be rolled back, such as main pages being inaccessible, core forms continuing to fail, or data being incomplete. Specify who judges, who performs, and what to do with new data during the cutover after recovery. Try to distinguish the impact of domain name changes, content system changes, and large-scale content changes. Otherwise, it will be difficult to determine where the problem comes from when a failure occurs.

  • The rollback must consider the new data, and cannot simply overwrite the old backup and call it a day.

Continue to check after going online instead of just looking at the homepage

After going online, visit the old address and new address according to the list, check the status, jump destination, page content and file download, and then complete a consultation test. Then observe the error logs, access statistics, and search tools for visible problems. Keep migration records. If you find that the old promotion link is invalid, you can locate the specific page and correct it.

Search crawling, indexing, and sorting may fluctuate after migration, and recovery time cannot be guaranteed as a fixed number of days. Just because the page is online does not mean it has been included in the search, nor can a search screenshot be used to prove that the migration is lossless. If visits or inquiries decrease, investigation should be combined with entrance changes, content adjustments and seasonal factors, rather than just looking at total traffic.

  • Migration acceptance should include content, technology, consultation process and follow-up monitoring records, and identify matters that remain to be seen.

Take this list with you

  • The old website, files, business portals and account responsibilities have been inventoried.
  • File and database backups are complete and know how to restore them.
  • There is a corresponding table for changing the URL, and the jump destination has been randomly checked.
  • Official domain name, index settings, and core forms verified.
  • Responsibilities for handover, incremental data processing and rollback have been agreed upon.
  • Continue to check the old entrance and business data after going online.

Black and white cat content editor. The specific scope should be checked against the current status of the site; search rankings or AI citations are not promised.

Discuss my site↗
← All website building guides

Start with a clear need

Give the business one
Better online entrance.

Let’s talk about your website ↗Submit requirements online ↗