Safe migration
Website migration to new hosting
Website migration is the move of a site's files, database and settings to another hosting service, server or platform. We prepare a backup and a migration plan, and check the files, database, domain settings, HTTPS and page addresses. We test the key features before and after the switchover.
On this page 10 sections
- 01What do we check when moving a website?
- 02When is it worth moving a website?
- 03What do we record before the move?
- 04How do we plan the DNS switchover?
- 05What should you prepare before we start?
- 06How do we reduce the risk of downtime?
- 07Keeping your search visibility
- 08Email is not automatically part of a website migration
- 09What do we check before the DNS switchover?
- 10What do we check after the switchover?
What do we check when moving a website?
First, we list the files, data and connected services that need to move. We also plan how to return to the previous environment if needed.
- 01
Files, databases and scheduled tasks
- 02
DNS, SSL and email records
- 03
Staging environment and feature testing
- 04
Switchover, monitoring and rollback plan
When is it worth moving a website?
Moving a website usually makes sense when the current hosting no longer fits its needs. Pages load slowly even after optimization, the hosting fee keeps rising, or the provider no longer updates the PHP or database versions the site's system requires. Another common case is a platform change, for example when a site moves to a different content management system or online store solution.
Before deciding, check whether a new environment will really solve the problem. If oversized images or outdated plugins slow the site down, moving it will not make it faster on its own. In that case we first discuss what can be fixed in the current environment, and we plan a move only when it has a clear benefit.
- 01
Slow or unstable hosting
The site is often unavailable or responds slowly because of limited server resources.
- 02
Rising hosting costs
Elsewhere you would pay less for similar features, or get more for the same price.
- 03
Unsupported environment
The hosting provider no longer allows the software versions the site needs.
- 04
Platform change
The website or online store moves to a different system, so the data structure changes and the addresses may change too.
What do we record before the move?
Before we start, we document the current website. We note everything that must keep working after the move. This list later becomes the test plan: we check each item in the new environment before changing the DNS records.
- 01
Pages and their addresses
We collect the list of existing URLs so that after the move we can check that each one opens or is redirected.
- 02
Forms and their recipients
We note where enquiry, registration and order form data is sent and who receives the notifications.
- 03
Email and other DNS records
We record the MX, SPF, DKIM, DMARC and other domain records so they are not lost when settings change.
- 04
Scheduled tasks
We check which cron jobs run automatically, such as backups, synchronization or email sending.
- 05
SSL certificate
We plan how the certificate will be issued and renewed in the new environment so the site works over HTTPS.
- 06
Third-party integrations
We list the payment, delivery, analytics and other systems that may depend on the server address or settings.
How do we plan the DNS switchover?
A few days before the switchover, we lower the TTL value of the domain's DNS records, if the domain management allows it. The change then reaches visitors faster, and a return to the previous environment is quicker if needed. We agree the switchover time with you and choose a period with the fewest visitors or orders.
While the DNS changes propagate, some visitors may still reach the old server. During that time we restrict content changes and order taking in the old environment, or agree in advance how data created in that period will be moved. After the switchover we submit the sitemap to Google Search Console, if we have access, and monitor indexing errors and 404 pages.
What should you prepare before we start?
Before the work, we will ask for access to the current hosting, the domain management and the website admin. Share these through a secure method we agree separately. Do not send passwords through the contact form or in a plain email.
It also helps to list the website features that matter most to your business: order taking, payments, enquiry forms, customer login or integrations with other systems. We test these features first, and after the switchover we review how they work together with you.
How do we reduce the risk of downtime?
We assess the current environment and make a backup. We test the new environment before changing the domain's DNS records. If the key features do not work, we must be ready to return to the previous version.
Keeping your search visibility
We keep existing page addresses, and for any that change we set up permanent 301 redirects. We check canonical links, robots.txt, the sitemap, metadata and internal links. Specific Google rankings cannot be guaranteed.
Email is not automatically part of a website migration
MX, SPF, DKIM and DMARC records are checked separately. Mailbox migration is included only when the scope and access are clearly agreed.
What do we check before the DNS switchover?
In the new environment we check the main pages, forms, login, the database connection, HTTPS, file uploads and scheduled tasks. Domain records are changed only once we have a copy of the current version and a rollback plan. If the site's URL structure changes, we prepare a map of old and new addresses before the switchover.
- 01
Key visitor and administrator journeys
- 02
Files, database and environment settings
- 03
HTTPS, DNS and dependencies on connected services
- 04
301 redirects and indexing signals
What do we check after the switchover?
We check that visitors reach the new server, the security certificate is valid, the key pages and forms work, and the logs show no new critical errors. We also review robots.txt, the sitemap, canonical links and redirects. We shut down the previous environment only after the agreed checks are done and we are sure the option to return to it is no longer needed.
Frequently asked questions
How much does website migration cost?
Moving a standard website or a WordPress site to new hosting costs from €200. The price includes a backup, a migration plan, checks of the files, database, domain and HTTPS, and feature testing after the switchover. Platform or domain changes and large online store databases are charged at €45/hour.
Will the website be down during the migration?
There may be a short outage, but we plan the work to keep it brief. Its length depends on the system, the amount of data and the DNS changes. We first prepare the site in the new environment, test the key features before and after the switchover, and plan in advance how to roll back if needed.
Will you move our email?
Only if email migration is clearly included in the scope of work and we have the access we need. Email depends on the domain's DNS records, so even when we move only the website, we check the MX and other mail records so that messages keep arriving. Moving mailbox contents is agreed separately.
What do you need for an estimate?
Tell us your current and future hosting, the website platform, who manages the domain and which connected services you use, such as email or third-party integrations. Based on this, we assess the risks and prepare a migration plan. Do not send passwords or access details through the contact form; we agree a secure way to share them separately.
Tell us where your website runs now and where you want to move it.
We reply with a proposed first stage and a clear price. You can also write to us directly:
info@techprojects.ltDiscuss your website migration