Transferring website (part 2)

Transferring website (part 1) ?

Once you've selected the most appropriate management system for your site and saved and tested the backup in the old version, we'll take the active steps to move it.

The path to the new platform consists of the following steps:

Choosing a new CMS for the site

It's a strange thought, but it's the most critical step in moving a site. It is often forgotten or ignored. The right choice must be clearly defined:

• Deficiencies of the existing platform that require CMS replacement;
• Features and capabilities of the new CMS (both built-in and optional, as well as paid plug-ins);
• The requirements for your website and the goals you want to achieve with the migration;
• The absence of these features does not allow you to maximize the use of your resources.

By consciously comparing and evaluating this data, you will understand whether choosing a new CMS is a reasonable choice and will meet your needs and expectations.

Evaluate the performance of the resource before migrating it to a new CMS

We mentioned that avoiding losses in the site migration process is challenging. But first, you need to capture the information that will monitor when evaluating these losses. Comparing old and new metrics will help you make timely adjustments and achieve better results.

When selecting evaluation criteria, use the information you are interested in to analyze site performance. Then, use long-form (annual) and recent (one month) Google Analytics reports for benchmark data.

You can also use data from analysis systems such as Serpstat and Ahrefs to compare data.

Material for programmers

Clients may not always be able to provide this information because they may not have sufficient knowledge in this area. However, you can use this item to check the quality of the programmer's work, for example, by requesting a report in the form of a screenshot.

The main points in the source terms should be as follows:

• site structure rules;
• template for generating a URL;
• An example of using Title, Description, and H1 meta tags;
• Basic parameters:

- Robots.txt and Sitemap.xml configuration requirements

- Setting up server response codes

- micro markup configuration

- Image settings, etc.

• A detailed list of corrective SEO actions

 

Checking the test version of the site

Before you accept the work of a programmer who has prepared a test version of the site according to the terms of reference, you need to analyze the work done and ensure that everything is done as you would like it done. So, first, you should be check:

• Compliance with the stated design requirements, using a design layout or selecting a quality replacement template;
• Verification of exact compliance with all of the above items. To speed up the process and minimize possible errors and misunderstandings, we recommend that you conduct such checks during each technical operation;
• Review the site's usability. If possible, involve third-party helpers or do it yourself and try to assess the convenience of the resource from the visitor's point of view;
• Check the operation and performance of the test version resources.

Creating terms of reference for the transfer of the site to a new CMS

• If the preliminary version of the site is correct for you, prepare terms of reference for each stage of the handover and implementation control. Focus on generating a 301 server response code, in other words, managing redirects;
• File transfer audits. Save your Google dashboard data to avoid data loss;
• Keep the data on the site up to date: Date, contacts and other information should be realistic;
• Migration of content to a new engine with data saved;
• Transfer of information about the transfer of the site and related changes to specialists working on the optimization and promotion of the resource;
• The order of approval of the test version of the site and the data of the authorized person confirm the initiation of the process of migrating the site to the new platform.

Configuring analytics

When migrating the site to another CMS, you will need to change all the settings in Google Analytics. At the same stage, it is necessary to set up the e-commerce functionality for the site.

Checking the new version

In addition to checking that the forms, buttons, and links on the site work, you should check the following

• Robots.txt file;
• Redirects on the site;
• Meta tags for each page;
• Correct transmission of statistical data.

Fix the data from Google Analytics and start tracking statistics. Initially, it is advisable to check the site's position every day and compare the statistics with the benchmark. There may be some decrease (usually 10-20%). After 3-5 weeks, if all works of website transfer do without errors, the resource should return to its previous position or positions will grow.

Conclusion

Now you know how to transfer sites from one CMS to another without significant loss of position. However, the process is very time-consuming and burdensome. Consequently, decide to transfer only if the benefits are significant.

Remember the right choice of platform, a clear understanding and compliance with all necessary actions - the key to success. It will avoid serious problems and the need to fix something global in the next few years.