Email migration service in Pakistan from Gmail, Google Workspace, Microsoft 365, GoDaddy email, Yahoo, Zimbra and any IMAP host. Preserves folder structure, read/unread state, attachments and timestamps. Starting at PKR 500 per mailbox or free with annual business email plans. Used by businesses across Karachi, Lahore, Islamabad and Sialkot.
Mailbox transfer from any cPanel or shared-hosting source to a new cPanel destination, keeping the full message history, folder structure, aliases, forwarders, autoresponders and spam rules. Standard is PKR 1,499 for up to 10 mailboxes, then PKR 100 per extra box. Free with annual HostingWalay hosting. Read the scope section before you order: Google Workspace, Microsoft 365 and Zoho are a different job and priced separately, and we would rather tell you that here than after you have paid.
See the specialised page for general website, cPanel or WordPress migrations
This price covers cPanel-to-cPanel transfers, where we take a server-side backup of the mailboxes and restore it. SaaS providers such as Google Workspace, Microsoft 365, Zoho and Outlook.com do not give anyone that kind of backup, so those moves run over IMAP sync with an MX cutover instead. We do them, but they are quoted separately because the effort depends on mailbox count and total volume.
Both tiers include the full message history, folder structure, aliases, forwarders, autoresponders and spam rules. Extra mailboxes are a flat PKR 100 each. Past 100 mailboxes, send us the count and we will quote it properly rather than multiplying.
HostingWalay branded service
Anonymous mailbox migration handoff
You give us access to the source cPanel, we take the mailbox backups and restore them on the destination, with WhatsApp updates from your Karachi engineer as each stage finishes. Our commitment is under 24 hours for up to 10 mailboxes and under 48 for bulk jobs over 50.
Message us and give us access to the source cPanel account. We confirm the mailbox inventory and the clock starts the same business day. If your source is a SaaS provider, that is the separately quoted IMAP route and we will tell you what it needs.
Each mailbox is pulled as an archive from the source server, with a manifest recording what it contains. Message history, folder structure, attachments, aliases, forwarders, autoresponders and filter rules all come with it. Your source mailboxes stay live and unmodified the whole time.
Mailboxes are recreated on the destination with their original addresses, the archives are restored, and aliases, forwarders and autoresponders are re-applied. At this point both sides hold the same mail.
Folder counts and message counts are checked mailbox by mailbox against the source. You log into a few of them yourself on the destination webmail and confirm they look right. We do not touch MX records until you say so.
MX TTL is lowered to 300 seconds a day beforehand. A final sync picks up anything that arrived during your testing, usually in under five minutes, then MX flips to the destination and new mail starts landing there. Your source mailboxes stay accessible throughout propagation, so nothing is stranded.
An IMAP-to-IMAP sync copies messages and folders, and it does that well. What it cannot copy is the things that live in the server configuration rather than the mailbox: filter rules, autoresponder schedules, forwarders and aliases. Those have to be recreated by hand afterwards, which is where they get missed. A server-side backup takes the whole configuration with it, and it is faster on large mailboxes. We still use an IMAP sync at the end, to catch mail that arrives during testing.
We take complete mailbox archives from the source server, not just the IMAP folders. Filter rules, autoresponder schedules and per-folder settings come across with them rather than needing to be rebuilt.
Source mailboxes stay live and unmodified until you verify the destination. Final IMAP delta-sync captures any mail received during testing before MX cutover, so no inbound message is lost.
One named engineer in Karachi handles the whole job rather than a ticket queue passing it around. Urdu, English or Roman Urdu, with WhatsApp updates as each batch restores.
Source MX records stay live during TTL propagation; destination MX records published in parallel. No bounce window, no inbound mail loss during cutover, no IT support tickets from confused users.
Free with any annual HostingWalay hosting plan. As a standalone job, Standard is PKR 1,499 for up to 10 mailboxes with PKR 100 for each additional box. Past 100 mailboxes, send us the count and we will quote it rather than multiplying. White Label, for agencies and IT consultants who need an anonymous handoff with a branded report and an NDA, is PKR 4,499 for up to 10 mailboxes. One-time per job, nothing recurring.
Because none of them give anyone a server-side mailbox backup to extract. That is a limitation on their side, not a policy on ours. The only way to move them is an IMAP-to-IMAP sync followed by an MX cutover, which takes longer and where the effort depends on mailbox count, total volume and how much history you want brought across. We do those migrations, we just quote them separately rather than pretending they fit a flat rate.
For this price, yes. cPanel or WHM on both ends is the fastest and most reliable route. Plesk, DirectAdmin and self-managed mail servers running Postfix, Dovecot, Exim or Cyrus can use the same backup-and-restore approach if they expose a mailbox archive export. If yours does not, we fall back to IMAP sync and quote that separately. Tell us what you are on and we will say which route applies.
Under 10 mailboxes totalling less than about 5 GB is usually done within 24 hours. Ten to fifty mailboxes takes 24 to 48. A hundred or more, or a hundred gigabytes plus, runs over two to three days in batches of twenty to thirty, because pushing harder than that runs into rate limits and slows the whole job down. You get a WhatsApp update as each batch finishes.
Source cPanel admin access, or WHM if it is a multi-account job, plus destination access if the destination is not us. You do not need to collect passwords from your users: a cPanel backup carries the hashed passwords across, so everyone keeps signing in with what they already use. Whatever credentials you give us are stored encrypted and deleted once the migration is signed off, and we would suggest rotating them at your end afterwards anyway.
Yes, and this is the main reason we work from a server-side backup rather than an IMAP sync. Aliases such as info@ and sales@, forwarders to other addresses, autoresponders, spam and filter rules, and mailing list configuration all move with the mailboxes. An IMAP-only migration copies the messages but leaves all of that to be rebuilt by hand, which is where things get missed.
No. We only take copies; the originals stay live and untouched throughout. After the destination is verified and MX has cut over, you decide when to decommission the source, and there is no rush. Keeping the old account open for a couple of weeks after cutover costs little and is a sensible safety net.
The source keeps receiving mail right up until MX propagates, so nothing bounces in the meantime. We lower the MX TTL to 300 seconds a day beforehand so propagation is quick, and once you have signed off on the destination a final sync picks up anything that arrived during your testing. Then MX flips. Every message that comes in during the window ends up in a mailbox on the destination.
Log into two or three mailboxes on the destination webmail yourself, ideally the busiest ones. Check the folder list matches, open something old to confirm history came across, and check any alias or forwarder you rely on actually forwards. Five minutes of that is worth more than any report we could send you, and we do not touch MX until you are satisfied.
That is what the White Label tier is for. The final report and status emails carry your branding, an NDA is available, and your client never sees our name anywhere in the process. It is aimed at agencies, IT consultants and hosting resellers who handle the client relationship themselves. Volume pricing applies from ten migrations a month.