Website hosting migration

Website hosting migration is moving a site to a different server while keeping the same CMS and the same site. We move all the files and the database, set up the server, switch the domain (DNS), install the SSL certificate (HTTPS) and check that everything works. Unlike migration from one CMS to another (see the “CMS migration” service), where the platform itself changes and the templates are rebuilt, here the site stays exactly the same — only the “house” it lives in changes. The page addresses do not change, so the move has almost no effect on SEO. Hosting providers often offer a free transfer, but that is usually a generic automatic copy of the files — without setting up email and SSL, without checking that forms and payments actually work, and without responsibility for the result. We do the move turnkey. This is done when the current hosting is slow, expensive, unreliable, or you need to move to a server in a specific country (for example, in Russia under the personal data law). Picture this: the site barely loads on the old hosting — we move it to a fast server, and it opens noticeably faster while staying the same. The base price starts from 15,000 ₽ for a typical site; large sites, online stores and heavy email cost more.

• The current hosting is slow or often goes down — the site is slow or unavailable, and clients leave.
• The hosting is expensive or inconvenient — you overpay or lack the capabilities you need.
• You need a server in a specific country (for example, in Russia under the personal data law) — the current one does not fit.
• Moving is scary — you are afraid of losing data, email, or taking the site down for a long time.

• Moving all the files and the database to the new server
• Setting up the server for your CMS (PHP, permissions, environment)
• Moving the email and installing the SSL certificate (HTTPS)
• Switching the domain (DNS) with minimal downtime
• A post-move check: forms, payments, speed, everything works
• A full backup before the move — nothing is lost
• Keeping the same page addresses — SEO does not suffer
• We keep the old hosting running until the new one is confirmed working

• The site runs on new, fast and reliable hosting
• The data, database and email are fully moved — nothing is lost
• The site stays available throughout the move — there is almost no real downtime
• The addresses are the same — search rankings do not suffer

• You leave a request and give access to the current hosting and the domain
• We move the files and database to the new server, set it up and test a copy
• We switch the DNS at a quiet time, keep both servers running and verify that everything works

• How is a hosting move different from a CMS migration?

  A CMS migration (see the “CMS migration” service) is a change of platform: the site is rebuilt on a new system, priced from 80,000 ₽. A hosting move is a change of the server only: the site and the CMS stay the same, what changes is the “house” it runs in, so it is simpler and cheaper. Hosting — moving to a different apartment with the same furniture; migration — changing the system itself.

• Why not use the free transfer offered by the hosting?

  A free transfer from a host is usually an automatic copy of the files: for a simple site it may be enough. But it often does not set up email, SSL and the environment, and does not check that forms, payments and integrations actually work after the move. We do the move turnkey: a full backup, moving the files, database and email, setting up the server and SSL, checking everything, and responsibility for the result — and we do not turn off the old hosting until the new one works. If the site is very simple, we will honestly say that the free option is enough.

• Will the site be unavailable during the move?

  Almost not. We move and set up the site on the new server in advance, test a copy, and only then switch the domain — at a quiet time. During the DNS update, some users reach the old server for a while and some reach the new one, but both work, so the site stays available. To keep the versions from diverging, we ask you not to make changes during the switch.