The fear that stops most host changes: 'what if my site goes down?' Here is why a properly done migration involves zero downtime — and the safety net that makes it stress-free.
Why downtime is optional Your OLD host keeps serving visitors until you tell DNS to stop sending people there. The migration happens on the NEW host in parallel — the two sites coexist. Nothing goes offline at any point.
The sequence (recap, with the safety logic) 1. Copy files + database to the new host 2. Test the copy thoroughly on a subdomain (the new site, under a hidden name) 3. Lower DNS TTL a day ahead (shortens the switch memory) 4. Flip DNS to the new host — the only 'switch' moment 5. Old host stays frozen for a week (the rollback)
During the propagation hours Some visitors hit the old site, some the new — both are working, so nobody notices. Watch orders/forms on both. Mail may split between old and new servers for hours: keep both mailboxes alive and forward stragglers.
The rollback promise Anything wrong post-switch? Flip DNS back. Two minutes, zero data loss. The old site never left. This safety net is why 'my site will die during migration' is a myth — the only way downtime happens is if you DELETE the old site before the new one is proven.
What support does with you Kairalmas support walks the whole sequence on WhatsApp: checks your backup, verifies the test copy, times the DNS switch for a quiet hour, and confirms SSL. The migration guide in this blog has the step-by-step.
Changing hosts is a Tuesday task, not a leap of faith — the architecture of DNS guarantees it.