I have been trolling the web and think I have the safest procedure for this but wanted to double check the process when moving a client to paid email hosting. I assume there are people here who have done this many times. This is my first time transferring a client's emails so want to ensure everything will go without a hitch.
Create paid email hosting service for client.
Check DNS records have been created and add A record(s) for the clients current website.
Create all email addresses in the new hosting service. I am assuming we will have full access to create the addresses at this time.
Forward current email addresses to a "safe" email address so emails won't get lost during the service transfer.
Change the nameservers at the client's domain registrar to mine.
Wait for propagation of the DNS and ensure new email accounts are working.
Initiate transfer of the client's domain to my account via the usual method
Have I missed anything or should I change the order of any of the steps.
These steps are correct and you will have a seemless migration without loosing any mails.
However, point 4 is not clear for me and does not make sense:
While you setup the new email hosting plan, mails are still delivered to the actual mail server. You just need to change the DNS servers when ready as you mention in point 5 and setup in your mail client the same email accounts using the new mail server (pop/smtp). In that way you will have during 24-48 hours mails incoming from both servers, the old and the new one. Past 48-72 hours most probably no incoming mails will be arrive from the old mail server and you can delete the old mail client setup.
Concerning point 3: Yes, this was recently changed at RC and we can create Mail accounts and Mail forwarder accounts even if the ownership is not verified.
Thanks Marco. I hadn't thought about having the email address twice in the mail client using the both the old and new mail servers to avoid missing emails. What I meant in Point 4 was to forward the current email address to a gmail address (or something like that) so emails wouldn't be missed in the transition. Your suggestion gets around that problem.
The administrator has disabled public write access.