Job email-move-cpanel-mailboxes-to-microsoft-365 · revised 9 October 2026
Move up to five cPanel mailboxes to Microsoft 365
Copy up to five hosted business mailboxes and their old messages into Microsoft 365, switch incoming mail safely, and prove new and old mail are present.
You might be seeing
- Staff search old email on the web host while new email goes to Microsoft 365
- The host has a mailbox cut-off date
- Customers get bounces after the MX records change
No passwords, keys, card details or admin invites needed to start.
What usually happened
The old host holds the only copy of years of business conversations. Changing MX records moves new incoming mail but does not copy the old mailbox contents; changing them before accounts and senders are ready can bounce or misroute enquiries. Sent folders, aliases and calendars need separate checking.
Who it’s for: Owner or office manager of a small business using mailboxes bundled with web hosting and wanting reliable Microsoft 365 email.
Usually starts when: The web host is closing, mailbox storage fills up, or a move to Microsoft 365 is approved but nobody knows how to keep the old messages and avoid an email gap.
The result: Up to five agreed mailboxes receive new mail in Microsoft 365 and contain their old messages through an agreed cut-off date, with no missing sample folders or messages.
Check whether this job fits
Five short questions. Your answers stay on this page unless you choose to email them.
Checks you can run yourself
Check each mailbox’s size
In cPanel, open Email Accounts; the list shows each mailbox and its disk usage.
Look for: How many mailboxes there are and whether any is over 10 GB.
See where your mail is delivered now
Run this read-only lookup with your own domain, or use any public DNS lookup website.
dig +short MX yourbusiness.co.ukLook for: The server names that receive your mail today. After the move they should point to Microsoft 365.
What you get
- Mailbox and alias inventory with counts and cut-off time
- Copy log and sample checks per inbox, sent folder and one named historic folder
- MX and sender-authentication switch steps and old-host rollback plan
- A short user guide for signing in and finding old messages
Included
- Up to five IMAP mailboxes, each up to 10 GB, from one host to tenant accounts you own
- An inventory of mailbox sizes, aliases, forwarding rules and DNS mail records
- An initial IMAP copy, a delta copy and MX switch by the domain holder
- Tests of incoming, outgoing and old-folder access for each mailbox
- Recreating the agreed aliases and forwarding rules in Microsoft 365 before MX changes
Not included
- Microsoft 365 licences or creating the tenant on your behalf
- Calendar, contacts and task migration unless the old host exports them in a separately agreed format
- More than five mailboxes or 10 GB per mailbox
- Archiving or legal discovery guarantees
- Moving the website or its DNS hosting to a new provider
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
For each mailbox, the destination has the same agreed folder names and a sample of old and recent messages in Inbox and Sent
Evidence: Folder counts and dated sample message IDs before/after
After the MX switch, a message from outside reaches each destination mailbox and a reply returns without a bounce
Evidence: Two-way test messages and headers per mailbox
Each agreed alias and forwarder is present in Microsoft 365 and a test message sent to it reaches the named destination account
Evidence: Test message and destination per alias
The old provider remains available for a defined catch-up window and the final delta copy includes messages received during the switch
Evidence: Delta-copy log and time-stamped sample
Source and destination folder-level message counts reconcile after the final delta, with every skipped or failed item resolved before acceptance; samples alone do not establish complete migration.
Evidence: Per-folder migration report, error/retry log and client-confirmed reconciliation, excluding only items explicitly outside the agreed scope.
Sign-off. You sign off after each mailbox, folder sample, alias and two-way message test passes, and after the final delta copy. Keep old mailboxes accessible for the agreed overlap window.
If it fails. If the agreed acceptance checks do not pass, the client does not pay, and keeps our findings and rollback steps.
When it fits, and when we stop
It fits when
- You own the domain and can change its MX and related records
- You have Microsoft 365 licences and can create the destination mailboxes
- The old host permits IMAP access and can keep the old mailboxes active during the move
- Each source mailbox is at most 10 GB
We stop and tell you if
- The old mailboxes are unavailable or the provider will not allow an export
- A legal hold, regulated records or jurisdiction rule requires a specialist migration plan
- Microsoft 365 tenancy or domain verification has not been set up and nobody can approve it
- The business cannot allow a staged change and the old host shuts off immediately
What could go wrong
Keep both sets of mailboxes active throughout the overlap. If MX is restored to the old host, reconcile messages delivered or sent at Microsoft 365 back to the continuing mailbox before closing either side. Cached DNS can keep delivering to both. A simple MX switch-back does not restore a single complete mailbox; if safe reconciliation is unavailable, stop the switch and agree a recovery plan.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| Messages arrive at the old host while DNS changes spread | Leave both active, run a delta copy, and test with outside senders before closing the old host. |
| Old Sent or custom folders are skipped by the copy | Inventory every folder and check message IDs from Inbox, Sent and a custom folder per account. |
| Outlook shows duplicated or missing messages | Compare unique message IDs and sample dates; stop before deleting old mailboxes. |
A second reviewer compares mailbox counts and samples before the switch, and checks the MX, SPF and autodiscover changes before your domain holder applies them.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Inventory all old mailboxes, aliases and forwarders; verify target Microsoft 365 accounts and domain ownership
- Under a client-approved scoped migration account, copy the IMAP folders and messages to Microsoft 365; the client may instead run the import from our instructions
- Recreate each agreed alias or forwarder in Microsoft 365, then compare folder counts and historic messages
- Have a separate reviewer compare the counts, alias map and MX switch plan
- The domain holder switches MX and sender records; run a final delta copy from the still-active old mailboxes
- Test incoming and outgoing mail for every mailbox and delivery to every agreed alias and forwarder
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access, any licences and necessary permissions are in place. Hosting, platform and supplier charges are excluded unless the written quote includes them. No charge or booking is created by an enquiry.
Need to keep it working?
For a changing team, discuss a bounded mailbox onboarding and offboarding service. Licence costs and account authority remain yours.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Microsoft publishes an IMAP migration method that your IT person can follow. It can save the labour fee if someone at the business knows how to check folders and DNS.
- If the only problem is mailbox storage, ask the current host for a larger plan before moving providers.
Questions
Will the old emails be in Outlook after the move?
We copy and sample-check agreed folders, including Sent. We do not delete the old mailboxes until your team confirms what it needs.
Will email stop during the switch?
We keep both sides active while MX answers spread and test incoming mail from outside. A provider or DNS fault can still delay mail; the old host stays available for catch-up.
Start with an email
Send us
- The domain, old mail provider and how many mailboxes you have
- Approximate mailbox sizes and the date the old host closes
- Whether Microsoft 365 accounts and licences already exist
- Who controls the domain’s DNS
Later, once you agree
- Client-controlled IMAP access to the old mailboxes and scoped migration permissions at Microsoft 365, through an authorised handoff rather than passwords in email
- A list of every mailbox, alias and forwarding rule, plus one dated historic message per mailbox to sample
- An authorised domain holder for the MX change and staff to sign in and check their own folders
- A company-controlled secure handoff agreed before access: no live passwords, keys, private code or customer records by ordinary email.
You own the old and new mail accounts, domain and DNS. After agreement, you authorise a narrowly scoped migration account or client-operated Microsoft import; SI agents may run only the approved copy and comparison work, never receive passwords in ordinary email. A separate reviewer checks counts and routing; your domain holder approves the live MX switch. Synthetic Industry is owned by a person and remains accountable for the agreed work.
Or write to hello@syntheticindustry.ai with “email-move-cpanel-mailboxes-to-microsoft-365” as the subject.