Short answer. Changing host means copying the site elsewhere, testing it, then changing one address in the DNS. In order: the inventory of the seven things to move, including the mailboxes; the DNS cache time lowered two days before; the copy and the tests on the new server, under a temporary address; a freeze of a few hours and one last copy; the switch; then the old server kept on for seven days, so you can go back by pointing the DNS back. The page addresses do not change, which protects links and search ranking. The domain name transfer is another operation, optional: never in the same week.
This guide is for the manager whose site is slow or badly hosted, for the one whose contractor has disappeared, and for the founder based in France who wants to move their company's site in Algeria. The definitions and facts quoted come from public sources: the web hosting service, the domain name system and its cache time, the MX record, the domain name transfer, the IMAP protocol, the hosts file, the 301 redirect, the certificate. The site, its seven items and its switch hours are a constructed example. This guide does not compare hosts and gives no prices.
Moving a site, in six steps
The first step is accented: take inventory.
What is moved. A web hosting service provides the infrastructure required to host websites and make them accessible on the World Wide Web. Changing host means making the same site work on another infrastructure, then sending visitors there. Access first. The inventory starts with one question: who has the access to the current hosting, the DNS zone and the domain name? If it is with a former contractor, the first step is described in the guide to the domain name and hosting.
Why this order. Everything before the switch is done without visitors seeing anything: the old site keeps serving. The switch itself is a single change, and everything after it is checking. Where to go. The choice of the new location, in Algeria, in Europe or both, has its own criteria, covered in the guide to hosting in Algeria or in Europe.
Seven things to move, not one
The figure moves seven items from the old host to the new one.
The site and its database. Files are copied; the database is exported then imported. On a site that takes orders or enrolments, the database changes every minute: it is for the database that the old site is frozen before the last copy. The mailboxes. If they are at the same host, they move too: the MX record specifies the mail server responsible for accepting email messages on behalf of a domain name, and it will have to point to the new one. The content of the mailboxes is copied with IMAP, the standard protocol used by email clients to retrieve messages from a mail server. The full configuration is in the guide to professional email.
What is not seen. Scheduled tasks, launched by a time-based job scheduler: sending reminders, a nightly export, a backup. The messages the site sends by itself, order confirmation or contact form, which depend on a sending setting specific to each host. And the DNS zone, to be recreated line by line, including the lines nobody remembers. One method and one test per line. The inventory is finished when each item has both.
«The home page is the first thing people check; mail is the one they forget.»
Before switching: five layers to test
The accented layer is mail.
Testing with no visitors. The new site is tested before the DNS changes: through a temporary address supplied by the host, or by editing on one computer the hosts file, the operating system file that maps hostnames to IP addresses. That computer then sees the new server under the real name, while everyone else still sees the old one. The same addresses. Each page keeps its address. If an address must change, a 301 redirect, the status code used for permanent redirecting, leads the old one to the new one: that is what protects links already shared and search ranking.
The certificate. A certificate is an electronic document used to prove that a public key belongs to its holder; it is issued on the new server, for the name with and without “www”. Without it, the browser shows a warning to the first visitor, as in the outages described in the guide to the site that no longer works. One test per journey. Not just the home page: a form sent, an account opened, an order placed, a message received. And afterwards. The new server's backup is in place before the switch, not after: see the guide to backups.
The switch, hour by hour
The figure follows four lanes, from 72 hours before to 48 hours after.
The cache time. When a DNS resolver receives an answer, it caches that record for the time, in seconds, specified by the TTL. TTLs are often lowered by the DNS administrator prior to a service being moved, in order to reduce possible disruptions: a 300-second TTL helps records expire in five minutes. So it is lowered two days before, long enough for the old long value to fade everywhere. One caveat: some caching nameservers set their own TTLs regardless of the one configured.
The freeze. A few hours before, the old site goes read-only or shows a maintenance message; the last copy of the database is made, checked, then the address is changed in the DNS. Going back. The old server stays on and intact: if a problem appears, the DNS is pointed back, and a few minutes later visitors return to it. Afterwards. A probe checks the site every few minutes during the first week, as in the guide to monitoring; the TTL goes back to its long value after a day.
«As long as the old server stays on, the decision can be undone in a few minutes.»
Changing host, transferring the name: two operations
The figure compares the two operations on six points.
Two different things. A domain name transfer is the process of changing the designated registrar of a domain name. It moves neither the site nor the mail: the name can stay registered where it is, and point to any host. All you need is control of its DNS zone. How it is done. The new registrar asks for an authentication code, supplied by the old one; the process may take about five days, and a transferred name cannot be transferred again for a period, long set at 60 days, which a 2025 decision plans to bring down to 30 days. Check the rule in force with your registrar.
Names in .dz. They are administered by the DZ Network Internet Center, a subdivision of CERIST, and follow their own procedures: ask the office that registered yours. The order. Move first, check for a week, and only then transfer the name if you want everything in one place. Doing both at once means losing the way back at the moment you need it.
Three weeks, from the inventory to cancellation, in 2027
Three weeks in the example, the first one for the inventory.
- What the manager receives: the inventory of the seven items, the access in their own name, the site tested on the new server, a dated switch with its way back, the old server kept for seven days, and a verification report before cancellation.
- What the company no longer does: change host on a Friday evening, find out on Monday that mail no longer arrives, cancel the old server the same day, transfer the name in the middle of the move.
- What is measured: minutes of unavailability during the switch, messages received and sent afterwards, pages answering at the same address as before, scheduled tasks that ran.
- What Symloop does: the inventory, recovering the access, the copy and the tests, the switch and its way back, monitoring during the first week, then, if you wish, the name transfer.
Week 1, the inventory: the seven items, the access, the current cache time, the switch date chosen on a quiet day. Weeks 1 and 2, the copy and the tests: the site, the database, the mailboxes, then the five layers tested one by one.
Week 2, the switch, on a morning of low activity, never on a Friday evening. Week 3, the old server kept, then cancellation: cancel only after checking mail, forms, scheduled tasks and a backup restored on the new server. The name transfer, if wanted, comes afterwards.
- How do you change a website's host?
- In six steps: take inventory of what has to move, lower the DNS cache time, copy the site and test it on the new server, freeze the old one and make a last copy, change the address in the DNS, then keep the old server on for a week before cancelling.
- Must the domain name be transferred to change host?
- No. The name can stay registered where it is: you only need to edit its DNS zone so that it points to the new host. Transferring the name is another operation, optional, to be done later.
- How do you transfer a domain name?
- Ask the old registrar for an authentication code, give it to the new one, and the process takes about five days. Beforehand, check that the DNS zone will be taken over identically. For a name in .dz, the procedure is the Algerian registry's: ask your office.
- Will we lose our mail?
- Not if the mailboxes are part of the inventory: each mailbox is copied, the forwards recreated, and the record that directs mail changes at the same time as the site or separately. Sending and receiving are tested before and after the switch.
- Will the site be down during the change?
- With a lowered cache time and a new server already tested, the switch shows within a few minutes. On a site that records orders, there is a freeze of a few hours during which it can be consulted but not modified.
- Will we lose our search ranking?
- The risk comes from addresses that change, not from the host. Keep the same page addresses, set a permanent redirect for those that change, and check the certificate and the speed on the new server.
- How long does DNS propagation take?
- It depends on the cache time set in your zone: if it is 24 hours, allow up to a day; if you lowered it to five minutes two days before, a few minutes. Some caching servers keep the old address a little longer.
- What if the old host or the contractor no longer answers?
- Start by regaining control of the domain name and its DNS zone: that is what lets you point elsewhere. Then recover a copy of the site and the database, from the hosting if you have access, otherwise from a backup.
- When should the old hosting be cancelled?
- Not before seven days, and only after checking mail, forms, scheduled tasks and a backup restored on the new server. As long as it is on, going back takes only a few minutes.
- How long does it take, and where do we start?
- Three weeks in this guide's example, including one morning for the switch itself. Start with the inventory and with the question of access: who can sign in to the current hosting, the DNS zone and the domain name?