VulCode

Moving your website to new hosting

VulCode, a software house from Kraków, moves websites to new hosting. We move sites, WordPress included, together with the database, email and DNS records, and plan the switch so there is no downtime or only a few minutes of it, at the quietest time. The page addresses stay the same, so the site does not have to earn its Google rankings again.

from PLN 299

The figure for your scope comes in a free quote.

Migration checklist
A report after moving a store to a new server: the answers of old addresses, daily 404 errors, redirect chains and Google clicks week by week

A move without downtime: the order of steps

Downtime usually comes from the wrong order: DNS changed before the new server is ready, or the old hosting switched off before it stopped receiving traffic. That is why the steps always go in the same order.

  • The same addresses

    With a hosting change alone the page addresses stay, so no redirects and no change of address in Search Console are needed.

  • A way back

    The old server runs until the move is over, so if anything goes wrong it is enough to point the DNS records back to it.

Site
Your domain, WordPress
From
your current hosting
To
the new server
Window
the quietest time
  1. A lower TTL in DNS
    at least a week before the move
    The records get a short lifetime, so after the change visitors reach the new server quickly.
  2. A copy and the new server
    We copy the files and database and run the site on the new server before anything changes in DNS.
  3. A test under the real domain
    We point a test computer to the new server through its hosts file, so we check the site, forms and certificate at the real address.
  4. The switch
    the A record, and with email also MX, SPF and DKIM
    Database changes made since the copy are moved right before the records change.
  5. The old server until traffic stops
    We shut it down only when its logs show no more traffic, as Google advises.

What we move and how we check it

Every part of the site has its own test before DNS changes, and once more after the switch.

  1. Site files

    Current hosting
    the theme, plugins, images and downloads
    New server
    the same files with the right permissions
    We compare file counts and sizes and open images and downloads at their addresses.
  2. Database

    Current hosting
    content, settings, users, form entries
    New server
    the same database on the new server
    Record counts before and after, with changes since the copy moved right before the switch.
  3. Server configuration

    Current hosting
    the PHP version, redirects, caching, wp-config.php
    New server
    a server set up for the site
    The same redirects as on the old server, checked by a script under the real domain.
  4. Email

    Current hosting
    mailboxes and MX, SPF and DKIM records
    New server
    the same email addresses
    We send and receive test messages, including from the site's forms.
  5. SSL certificate

    Current hosting
    the certificate on the old server
    New server
    a certificate for the domain on the new server
    The site answers over HTTPS only, with no browser warnings.
  6. Background jobs

    Current hosting
    cron, backups, scheduled emails
    New server
    running on the new server
    We check that jobs start on time and that backups are written.
Current hosting: Runs until the move is over and serves as the way back.
New server: First checked under the real domain, live from the switch.

Email and DNS: what happens to the records

DNS does not broadcast changes across the internet. A server that asked about your domain remembers the answer for the time set in the TTL, so some visitors see the new server at once and some only after it runs out. That is why both servers run side by side in the meantime.

RecordWhat it is forWhat we do in the move
A and AAAAThe address of the server the site runs on.We change it to the new server's address in the switch window, after the test under the real domain.
CNAME wwwThe www version of the address, leading to the same site.We check that it leads to the new server and that one version of the address redirects to the other.
MXThe server that receives email for the domain.It stays as it is when email stays with the current provider. When email moves, we change it together with the mailboxes.
SPF (TXT)The list of servers allowed to send email from the domain.We add the new server when it sends email from forms, so the messages do not land in spam.
DKIM (TXT)The key the mail server signs messages with.We move it together with the email, so the signature still matches.
TTLHow long other servers remember a DNS answer.We lower it to a few hours at least a week before the move.

How much a website move costs

Moving a website costs from PLN 299. We give the figure for your site in a free quote: it goes up mainly with the number of mailboxes, the size of the files and database, and a change of domain or system along the way.

ServicePriceService page
The move and care after it
Website and store migrationMoving a website to new hosting, or a store migration with products, customers and orders.Moving a website from PLN 299 Store migration from PLN 999
Maintenance and supportHosting with monitoring, backups, updates and small changes after the move.from PLN 99/month
Website speed optimizationA PageSpeed Insights diagnosis and fixes in the code when the site is still slow on the new server.from PLN 399

Questions about moving a website

About Google rankings, downtime, email, WordPress and the cost.

Changing hosting?

Tell us where your site and email are now and where they should go. We reply within an hour with questions and a free quote.