Transferring Business Email to SmarterMail Without Breaking Outlook, iPhones, Shared Calendars, or DMARC
Business owners often stay on overpriced or unreliable email hosts simply because they are afraid moving 15 or 50 mailboxes will break everyone’s phone and Outlook on Monday morning. Here is the exact sequence we use to migrate business email cleanly.
After switching email providers, employees cannot connect on iPhones or Outlook, historical Sent/Archive folders are missing, or third-party invoicing/CRM emails start failing DMARC.
Switching MX records before pre-staging mailboxes and initial IMAP sync, missing the _autodiscover._tcp SRV record, or flipping DMARC to p=reject before auditing third-party senders.
Pre-create all mailboxes, aliases, and lists; run a 2-pass IMAP sync (bulk pre-sync + post-MX delta sync); publish both CNAME and SRV Autodiscover records; and audit every sender before tightening DMARC.
Interactive Business Email Migration Checklist
Follow these 6 steps to move a company domain to SmarterMail without disrupting staff:
1. Why You Should Never Migrate 50 GB Mailboxes After Flipping the MX Record
If a company has twenty employees with 15 to 50 GB of email history each, copying all of that data over IMAP after you flip the MX record means employees spend Monday morning staring at empty folders while hundreds of gigabytes trickle across the network.
Instead, we always use a two-pass migration: we provision every mailbox, alias, and mailing list on east.greentreemail.com days ahead of time and run Pass #1 while your team is still working normally on the old mail host. Pass #1 copies 99% of the historical messages and folder structures in the background.
Then, at the scheduled cutover time, we point your domain’s MX record to mx.greentreemail.com so new incoming mail flows immediately into SmarterMail, and we trigger Pass #2—which only has to copy the handful of emails that arrived or were sent since Pass #1. That delta pass finishes in minutes.
| Migration Element | Single-Pass "Flip & Copy" Cutover | GreenTree Two-Pass SmarterMail Cutover |
|---|---|---|
| Historical Folder Availability | Empty folders for hours while gigabytes copy after cutover | 99% pre-synced 24–48h early; final delta finishes in minutes |
| Role Accounts & Scanner Relays | Often forgotten until office printers or billing alerts fail | Inventoried upfront (aliases, group lists, copier/web app SMTP) |
| SPF Transition Window | Hard-swapped on cutover day (causes softfails on cached nodes) | Dual-authorized 24h prior, then pruned cleanly 48h post-cutover |
| Device Setup (Outlook / iPhone) | Manual server/port typing on every device | Zero-touch Autodiscover via CNAME + _autodiscover._tcp SRV |
2. Two Details People Forget: _autodiscover._tcp SRV Records and Office Copiers
Two small details separate a smooth email cutover from a noisy Monday morning:
• 1. Publishing Both Autodiscover Records: Many DNS admins add an autodiscover CNAME record and stop there. Modern versions of Outlook, Apple Mail, and mobile clients also query _autodiscover._tcp.yourdomain.com (SRV record on port 443). Publishing both the CNAME and the SRV record ensures that when a user types their email address and password, the client finds east.greentreemail.com automatically without asking for port numbers.
• 2. Office Multifunction Printers & Website Forms: Almost every commercial office has a Ricoh, Canon, Xerox, or Brother scanner that emails PDFs to staff (scan@yourdomain.com), plus a website or accounting package sending automated receipts. Before flipping MX records, we check every device and web app so none of them are left trying to authenticate against the retired mail server.
# 1. Verify Inbound MX points to Proxmox Mail Gateway nslookup -type=mx yourdomain.com # 2. Verify Autodiscover SRV record resolves to east.greentreemail.com:443 nslookup -type=srv _autodiscover._tcp.yourdomain.com # 3. Verify SPF & DMARC TXT records nslookup -type=txt yourdomain.com nslookup -type=txt _dmarc.yourdomain.com
Common Questions on SmarterMail Mailbox & Autodiscover Cutovers
How does the two-pass IMAP sync prevent missing emails during the switch to SmarterMail?
We pre-create your mailboxes on SmarterMail before changing your MX records and run a two-pass IMAP sync: Pass #1 copies bulk historical mail 24–48 hours before cutover, and Pass #2 runs after the MX change to copy any messages that arrived on the old server during DNS propagation.
Do you support domain mailing lists and shared calendars in SmarterMail?
Yes. Our SmarterMail Enterprise Business & Lists tier ($10/mo per 50 GB mailbox—with 1 account included free on $99+ hosting plans) includes full support for domain mailing lists, shared calendars, contacts, tasks, CalDAV/CardDAV, and ActiveSync/Webmail.
What happens to existing GreenTree mailbox customers when new rates are published?
Existing GreenTree hosting and mailbox customers keep their grandfathered monthly rates on active accounts, as documented on our /email page and in Clause 4 of our Master Terms of Service.
Inside Our 3-Tier Enterprise Email Architecture: Inbound PMG, SmarterMail Enterprise & Multi-Gateway Outbound
See how our decoupled Proxmox Mail Gateway + SmarterMail Enterprise stack saves 25-person teams $5,400–$18,000+ over 3 years compared to per-seat hyperscale mail.
Ready to Move Off Per-Seat Mail Bills or an Aging Mail Host?
We handle the entire SmarterMail + Proxmox Mail Gateway migration for you. Plans are $6/mo (25 GB Core), $10/mo (50 GB Business & Lists), and $18/mo (100 GB Executive Vault), with 1 Enterprise mailbox included on every $99+ hosting plan.
Related Notes From the Sysadmin Desk
Running SmarterMail in Production: Why Your Mailbox Server Should Never Accept Direct Internet Mail or Send Directly to the Outside World
Decouple mail into three isolated tiers: (1) Inbound Proxmox Mail Gateway (mx.greentreemail.com) for edge threat scrubbing, (2) Isolated SmarterMail Vault (east.greentreemail.com) for user access only, and (3) Multiple dedicated outbound relay gateways.
The Zero-Downtime Server Transfer Runbook: How We Move Live Websites, Databases, and Mailboxes Without Losing a Single Order or Email
Execute a 5-stage cutover: lower DNS TTLs to 60 seconds 48 hours early, stage and test via local hosts-file override, pre-issue TLS certificates, run a final sub-second rsync + database delta sync, and enforce a 5-source 301 redirect map.
Authoritative BIND DNS in the Real World: Why Secondary Nameservers Serve Stale TTLs (And How to Catch Zone Drift in 60 Seconds)
Always increment the YYYYMMDDnn SOA serial before rndc reload, strip stale per-record TTL overrides, align registrar glue/NS records with the zone, and query every delegated nameserver directly.