r/webhosting • u/purcelljd • 8d ago
Advice Needed General sequence of operations
Thanks for the best hosting recommendation! This will save me a lot of time.
I'm moving my hosting (from think of a color) to a new one. 3 domains and a few email accounts.
What is the best sequence of operations? ex.
step 1. Transfer Registrar
step 2. Transfer Domain to new provider
step 3. Backup existing sites
step 4. Restore sites on new provider
step 5. Change DNS
step x: no idea on how to deal with transferring the emails
And any recommendations on timeframe between each (e.x. "T minus 2 days")
1
u/Lard_Denning 8d ago
the domain's actual registration, the DNS host, email host, and website host, are all different services. what exactly are you actually trying to change? "all of them" is a valid answer, but you don't have to do them all at the same time, or to the same company. so it's important to figure out what it is that you actually want first, before getting into what you need to do.
1
u/purcelljd 7d ago
Everything.
1
u/Lard_Denning 7d ago
i would do DNS first, once that's propagated, transfer your registration and maintain the same nameservers you just switched to. this shouldn't affect web availability. then you do the content migration for web / mail hosting, finally update the DNS records for those to point to the new server. after you verify that's switched over and working you can pull down the old hosting.
1
u/kemalios 7d ago
I do these for clients and it's the mail leg that bites. Create the mailboxes on the new host first, send and receive a test from each, and only then change MX. Flip MX before the mailboxes exist and mail bounces, and bounced mail does not come back.
Copy SPF, DKIM and DMARC out of the old zone before you touch nameservers. They are DNS records, so they do not follow you when you recreate the zone, and a missing DKIM shows up as mail quietly landing in spam a week later.
Three domains: do one at a time, and don't start the second until the first has had a week of clean mail.
1
u/purcelljd 7d ago
While its 3 domains, 1 is parked (directed to another one). As for email, thank you...adding to my list of To Do's
1
u/joabda__ 8d ago
Some providers allow you to create a temporary domain, I would use that to check the site before changing DNS entried.
If not, you can use a subdomain, staging.yourdomain.com to verify the restore
1
u/StealthyPHL 8d ago
For transferring mail I recommend imapsync - there’s a free version online for 3GB and less. For more there’s a free download command line that is great too. I’ve used both.
1
1
u/Nearby-Listen-664 7d ago
Steps 1 and 2 are kinda the same thing, and you don’t even need to move the domains to change host
1
u/Important_Rockey 7d ago
I’d split this into two separate projects. Move hosting and email first, then transfer the registrar a week or two later once everything is stable. Doing both at once means if something breaks, you won’t know which change caused it. Registrar transfers can also take up to a week to complete.
1
u/Soggy-Slops 7d ago
One trick that makes everything easier is moving DNS to a neutral provider like Cloudflare first. Copy all your current records there, point the domains’ nameservers at it, and wait a day. From then on, switching hosting or email is just editing records, and your registrar transfer later won’t touch your DNS at all.
5
u/kai-zaphosting 8d ago
Actually, you can skip the registrar steps for now. Moving hosting doesn't mean moving the domains, you just point DNS at the new host. Switching registrars at the same time gives you a second thing that can break, and a freshly transferred domain usually can't be moved again for 60 days anyway. If you want a new registrar, do it as its own project a few weeks later.
The order I'd use: build the sites on the new host and check them first (the staging subdomain idea someone mentioned works well for that), create the mailboxes there, then drop the TTL on your DNS records to something like 300 seconds a day or two ahead. Then cut over by changing the A/CNAME and MX records in one go.
If your DNS is managed by the old host (common with registrar-plus-host bundles), the zone disappears when you cancel. Either keep editing the records there until cutover, or recreate the full zone at the new DNS host (extra subdomains, verification TXT and mail records included) and switch the nameservers at the registrar before cancelling. Lowering TTLs doesn't speed up a nameserver change, that's governed by the NS TTL at the registry (often up to 24-48 hours), so the old-hosting overlap I mention below matters even more in that case.
Swap the SPF include and DKIM key for the new host's values when you switch MX, otherwise outbound mail from the new host can land in spam.
Email is the part I see go wrong most often. Mail doesn't move on its own, so copy the old mailboxes over with the new host's IMAP migration tool or
imapsync, then run it once more right after cutover to catch whatever landed in between. Keep the old hosting paid for a week or so afterwards so nothing gets lost while DNS caches expire.Happy to go deeper on the email side if that's the scary bit.