Skip links
Lets Talk
Published in: email migration

How to Set Up SPF, DKIM & DMARC — The Complete Guide

Author
Published on:
Table of Contents

Migrating your business email is one of the most high-stakes infrastructure tasks you will ever perform. Done right, your team barely notices the change. Done wrong, emails go missing, clients cannot reach you, and critical data disappears.

This guide gives you a complete, phase-by-phase email migration checklist — covering everything from pre-migration planning and DNS changes to post-migration verification and staff training. Whether you are moving from shared hosting email to Google Workspace, switching from one cPanel server to another, or consolidating multiple accounts into Microsoft 365, this checklist has you covered.

Quick Answer: An email migration is the process of moving email accounts, messages, contacts, and calendar data from one provider or server to another -- while keeping downtime, data loss, and disruption to an absolute minimum.

What Is an Email Migration and Why Does It Matter for Small Businesses?

Email Migration and Why Does It Matter for Small Businesses

Email migration means transferring your existing email infrastructure — inboxes, archived messages, contacts, calendar events, and configurations — from your current provider to a new one. For small businesses, this is rarely a purely technical event. It touches every person in your organisation who uses email to communicate with clients, suppliers, and partners.

Poor migrations cause real business damage: lost sales leads, missed invoices, broken client trust, and hours of IT firefighting. A structured checklist removes the guesswork and ensures nothing falls through the cracks.

Common migration scenarios include: moving from shared hosting email to Google Workspace, switching from Microsoft 365 to Zoho Mail, upgrading from a self-hosted VPS to a managed cloud provider, or simply changing web hosting providers when your domain moves.

What Are the Most Common Types of Email Migration?

Not all email migrations are the same. The approach depends on the source and destination platforms, the volume of data, and how much downtime you can tolerate.
the Most Common Types of Email Migration
Migration Type Downtime Risk Complexity Data Loss Risk Cost Best For
IMAP-to-IMAP Sync Low Low Medium Free Gmail → Google WS, Zoho
MX Cutover Medium Medium Medium Free Most small businesses
Third-Party Tool Low Low Low $5 – $50 Non-technical teams
Manual PST/MBOX Import Medium Medium Medium Free Outlook → Google WS
Hosting Provider Move Higher High Low Varies cPanel → cPanel
Professional Migration Low Low Minimal $200 – $2,000 Large teams, zero risk

What Is an IMAP-to-IMAP Migration and When Should You Use It?

IMAP-to-IMAP sync is the most common method for small businesses. Tools like Thunderbird, imapsync, or a provider’s built-in import wizard connect to your old server via IMAP and copy every email folder to the new server. It is non-destructive — nothing is deleted from the source until you are ready.

What Is an MX Cutover Migration?

An MX cutover is when you update your domain’s MX records to point to the new mail server while IMAP-syncing historical emails in parallel. New emails start flowing to the new provider immediately after MX propagation. This is the standard method for most business migrations and balances simplicity with speed.

When Should You Use a Professional Migration Tool?

Paid tools like BitTitan MigrationWiz, CloudFuze, and SkyKick handle IMAP sync, calendars, contacts, and collaboration data in one dashboard. They are worth the cost for migrations involving 10 or more users or complex data structures.

Which Email Migration Tool Should You Use for Your Scenario?

Email Migration Tool Should You Use for Your Scenario
The right tool depends entirely on where you are migrating from and to. Here is the definitive provider-to-tool mapping:
From Provider To Provider Recommended Tool IMAP Sync? Difficulty
Gmail (free) Google Workspace Google WS Migration Tool Yes Easy
Outlook / M365 Google Workspace GAMMO / Cloudfuze Yes Medium
cPanel Email Google Workspace imapsync / Thunderbird Yes Medium
Yahoo Mail Zoho Mail IMAP Sync (built-in) Yes Easy
Shared Hosting Microsoft 365 BitTitan MigrationWiz Yes Medium
Self-Hosted VPS Google Workspace imapsync CLI / Thunderbird Yes Advanced
Zoho Mail Microsoft 365 BitTitan MigrationWiz Yes Medium
Any Provider Fastmail IMAP Import (built-in) Yes Easy

Pro Tip:  imapsync is the most powerful open-source migration tool available. It runs from a terminal and supports nearly any IMAP-to-IMAP migration. For non-technical users, Thunderbird offers a free GUI alternative that achieves the same result without the command line.

Anterpreneur CTA

What Is the Complete Email Migration Checklist for Small Businesses?

the Complete Email Migration Checklist for Small Businesses
The checklist below is divided into six phases. Work through each phase in order. Do not skip Phase 1 — the decisions made during planning determine whether everything else succeeds.

PHASE 1 : Pre-Migration Planning -- What Must You Do Before Anything Else?

Audit all existing email accounts list every active mailbox, alias, shared inbox, and forwarder. Include: name, email address, storage used, last active date, and whether the account needs migrating.
Identify all email dependencies list every service or app that sends or receives email from your domain. Examples: CRM (Salesforce, HubSpot), helpdesk (Zendesk, Freshdesk), booking systems, e-commerce platforms.
Check current storage usage per mailbox ensure your new provider has enough storage. Rule of thumb: new provider storage is at least 1.5x your current usage to allow room to grow.
Record all existing DNS records export or screenshot your current MX, SPF, DKIM, DMARC, and TXT records. Use MXToolbox.com or your registrar’s DNS panel to view all current records before making any changes.
Choose your new email provider and plan confirm pricing, user count, storage limits, and setup requirements. See: [Insert internal link here] What Are the Different Types of Email Providers?
Set a migration date and time window schedule the cutover during your lowest-traffic period. Best practice: Friday evening or Saturday morning. Avoid month-end, quarter-end, or peak trading days.
Notify your team inform all staff of the migration plan, expected timeline, and any action required. Send written notice at least 5 to 7 business days in advance with a clear FAQ document.
Create a rollback plan document exactly how you will revert to the old system if something goes wrong. Keep old accounts active for at least 30 days post-migration. Do NOT cancel old hosting immediately.
Set up a migration project inbox a dedicated address for migration-related queries and updates. Example: it-migration@yourdomain.com so all communication is centralised and trackable.

PHASE 2 :Data Backup - What Must You Back Up Before Migration?

Export a full backup of all mailboxes from the current server cPanel: Use Backup Wizard or JetBackup. Google Workspace: Use Google Takeout or Vault. Outlook/M365: Export PST files.
Download a local copy of all emails in MBOX or PST format Thunderbird can export mailboxes to MBOX format from any IMAP account. Store files in at least two locations.
Back up all contacts export as vCard (.vcf) or CSV from your current provider. Google: Contacts → Export. Outlook: People → Export to CSV. Zoho: Contacts → Export.
Back up all calendar events export as .ICS files from every user calendar. Google Calendar: Settings → Import & Export. Outlook: File → Open & Export → Import/Export.
Back up shared drives and email attachments separately if applicable Large attachments are sometimes missed by IMAP sync tools. Confirm attachment migration is included in your tool.
Verify backup file integrity open backup files and spot-check 5 to 10 emails to confirm readability. A backup you cannot restore is not a backup. Test restoration before you begin the live migration.
Store backups in at least two separate locations local and cloud storage. Example: external hard drive plus Google Drive or Dropbox. Label files with date and source provider name.
Document the backup location and credentials for your team If you are unavailable during migration, someone else must be able to access the backup files immediately.

PHASE 3 :New Environment Setup -- How Do You Prepare the New Provider?

Create your account on the new email provider and verify billing details Confirm your plan supports the number of users, storage, and any compliance or security features you need.
Add and verify your domain on the new platform Google Workspace: Admin Console → Domains. Microsoft 365: Admin Center → Domains. Zoho: Mail → Domains.
Create all user accounts on the new provider before migrating any data Use the same email addresses as the old system. Set temporary passwords and record them for handover.
Create all aliases, groups, shared inboxes, and distribution lists Map each alias from the old system to the new system. Do not miss inactive aliases — they may still receive important mail.
Configure SMTP settings for any third-party services that send email through your domain Update SMTP credentials in: CRM, helpdesk, booking system, accounting software, WooCommerce, Shopify, etc.
Set up IMAP and SMTP settings for all users email clients (Outlook, Apple Mail, Thunderbird). Prepare a settings reference sheet with: incoming server, outgoing server, port numbers, and SSL settings.
Configure email forwarding rules and filters if used Recreate existing filters, labels, and folder structures on the new provider to match the old setup.
Set up shared calendars and contacts on the new platform if applicable Google Workspace: shared calendars via Google Calendar. Microsoft 365: shared mailboxes via Outlook.
Test sending and receiving on the new provider using a test domain or internal accounts Send test emails between new accounts before going live. Confirm delivery in both inbound and outbound directions.

PHASE 4 :Email Data Migration -- How Do You Transfer Your Emails Safely?

Choose your migration method IMAP sync tool, provider migration wizard, or PST/MBOX import. For most small businesses: use the provider’s built-in migration wizard first. Fall back to Thunderbird or imapsync if needed.
Begin IMAP sync migration for all user accounts Start with the most important mailboxes. Monitor sync progress. Large inboxes of 10GB or more may take 12 to 48 hours to complete fully.
Monitor sync logs for errors Watch for failed folders, skipped messages, or authentication timeouts. Most tools log errors to a dashboard. Review logs at least once daily during active migration.
Migrate contacts for all users Import vCard or CSV files into the new provider’s contacts section. Verify contact count before and after.
Migrate calendar events for all users Import ICS files into the new calendar. Spot-check recurring events and meetings with external guests.
Run a delta sync after the main migration is complete Capture any new emails that arrived during the process. A delta sync closes the gap between your migration start date and the MX cutover date.
Verify message counts per mailbox Compare old server versus new server. Counts should be within 95 to 100 percent of the original. Minor differences are normal (spam, deleted items).
Confirm folder structure is replicated All custom folders and subfolders must be present on the new server. Pay special attention to nested folders which some IMAP tools skip if not explicitly configured.
Test email access on the new provider for each account Before updating DNS, log in to webmail, mobile app, and desktop client. Confirm read/unread status, drafts, and sent items are intact.

PHASE 5 :DNS Cutover -- How Do You Switch Your Domain's Email Flow?

Lower your DNS TTL to 300 seconds (5 minutes) at least 24 to 48 hours before the cutover. This ensures the MX change propagates globally in minutes rather than hours once you make the switch.
Prepare all DNS record values from your new provider before the cutover window. Have new MX records, SPF record, DKIM TXT record, and DMARC record ready to paste before you begin.
Update MX records to point to the new mail server Delete old MX records. Add new MX records with the correct priority values from your new provider’s documentation.
Update SPF TXT record authorise the new provider’s sending servers. Replace the old SPF include with the new provider’s value. Only ONE SPF TXT record is permitted per domain.
Publish new DKIM public key TXT record at the correct selector subdomain. Obtain the DKIM TXT record from the new provider’s admin panel. Add at selector._domainkey.yourdomain.com.
Update or create DMARC TXT record at _dmarc.yourdomain.com. If starting fresh, begin with p=none and a reporting address. See: [Insert internal link here] SPF DKIM DMARC Guide.
Remove old SPF includes from any decommissioned senders. Old DKIM selectors can remain temporarily (harmless) but remove old SPF includes to stay under the 10-lookup limit.
Verify DNS propagation using DNSChecker.org or MXToolbox. Check that new MX records are visible globally before sending any test emails post-cutover.
Send test emails immediately after propagation confirms both inbound and outbound. Send from external Gmail or Outlook to your domain. Reply back to the external address. Confirm both directions.
Check email headers on first received emails confirm SPF, DKIM, and DMARC pass. In Gmail: open email → three-dot menu → Show Original. Look for spf=pass, dkim=pass, dmarc=pass.
Update all third-party services with new SMTP credentials and MX details. Work through every tool noted in Phase 1. Update SMTP settings and send a test email from each one.

PHASE 6 :Post-Migration Verification -- How Do You Confirm Success?

Monitor new mailboxes actively for 24 to 72 hours post-cutover Have at least one technical person available to respond to email delivery issues during this window.
Set up email clients for all users on the new provider (Outlook, Apple Mail, mobile apps). Provide staff with a written IMAP/SMTP settings guide and run a short team briefing on the new webmail interface.
Remove old server IMAP connections from email clients Do not leave old and new accounts both active. This prevents confusion and avoids emails being sent or read from the old account accidentally.
Verify auto-responders and out-of-office messages Ensure they are correctly configured on the new platform. Recreate any existing auto-replies immediately.
Confirm email deliverability score Use mail-tester.com and ensure a score of 8/10 or higher. Fix any flagged issues promptly.
Check deliverability signals Use Google Postmaster Tools or Microsoft SNDS to monitor spam rate, IP reputation, and authentication results.
Keep the old email server active for at least 30 days Users may need access to old emails. Set forwarding so any remaining emails reach the new system.
Set redirect or auto-forward on the old server Some servers cache old MX records. Forward any delayed emails to the new provider.
Cancel or downgrade old email hosting after 30 days Do NOT cancel earlier. Early cancellation can cause permanent data loss.
Document the new email setup Record account details, DNS records, SMTP credentials, and provider contacts. Store securely for team access.
Collect staff feedback after one week Identify issues with folders, contacts, or calendar events using a short survey before they affect clients.

How Do You Migrate Email to Google Workspace Specifically?

Migrate Email to Google Workspace Specifically
Google Workspace is the most common destination for small business email migrations. Google provides its own free migration tool inside the Admin Console, which handles the process without third-party software.

What Is the Google Workspace Migration Tool?

Google Workspace Data Migration Service built into the Admin Console lets you migrate from Gmail, Microsoft Exchange, Lotus Notes, and any IMAP server — all through a simple guided wizard.

  1. Go to Google Admin Console > Data > Data Migration.
  2. Select your migration source: Gmail, Exchange, IMAP, or other.
  3. Enter your source server IMAP settings and admin credentials.
  4. Choose the date range — migrate all mail or only emails after a specific date.
  5. Select all users or specific accounts to migrate.
  6. Click Start and monitor the migration dashboard for progress and errors.
# Google Workspace IMAP migration settings reference:Source: Any IMAP server (e.g., cPanel, Zoho, Yahoo) IMAP Host: mail.yourdomain.com (or your provider’s IMAP hostname) IMAP Port: 993 (SSL) or 143 (STARTTLS) Authentication: Username (full email address) + Password   What it migrates: All mail folders including Inbox, Sent, Drafts, and custom folders. What it does NOT migrate: Contacts, calendars, tasks — these must be migrated separately.

Pro Tip:  Use the Google Workspace Admin Console migration tool for clean, wizard-driven migrations of up to 100 users. For larger organisations or complex data including shared calendars, use a paid tool like MigrationWiz or CloudFuze.

How Do You Migrate Email to Microsoft 365?

# DKIM TXT Record Example DNS Name: google._domainkey.yourdomain.com Type: TXT Value: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA… # Note: # The p= value is your base64-encoded public key. # It will be several hundred characters long — this is normal.

How Do You Verify Your DKIM Record?

Use MXToolbox DKIM Lookup and enter your domain and selector. A valid result shows “DKIM record found” with the public key details.

Alternatively, send a test email to mail-tester.com which gives you a full deliverability score including DKIM pass/fail status.

How Do You Set Up DMARC — Step by Step?

Set Up DMARC — Step by Step

Microsoft 365 supports several migration paths. The most common for small businesses is the IMAP migration wizard available in the Microsoft 365 Admin Center.

How Does the Microsoft 365 IMAP Migration Work?

  1. Log in to Microsoft 365 Admin Center > Setup > Migration.
  2. Select IMAP as the migration type and enter your source IMAP server details.
  3. Upload a CSV file listing the user accounts to migrate (email address, username, password).
  4. Microsoft syncs all emails from the source IMAP server to the new mailboxes.
  5. Once sync is complete, update MX records to point to Microsoft 365.
  6. Complete a final delta sync to capture any mail received during the cutover window.

Warning:  Microsoft 365 IMAP migration does not include contacts or calendars. Export contacts as CSV and calendar events as ICS files, then import them separately via Outlook desktop app or the Microsoft 365 admin tools.

How Do You Migrate Email Between cPanel Servers?

Migrate Email Between cPanel Servers
Moving between web hosting providers is extremely common for small businesses. If both source and destination run cPanel or WHM, the migration can be nearly fully automated.

What Is the Fastest Way to Migrate Between Two cPanel Servers?

  1. Log in to WHM on the destination server.
  2. Go to WHM > Transfers > Transfer or Restore a cPanel Account.
  3. Enter the source server hostname, root username, and SSH password or key.
  4. WHM copies all email accounts, inboxes, databases, files, and DNS zones automatically.
  5. Update the domain’s nameservers or MX records to point to the new server.
  6. Verify all email accounts are accessible via webmail on the new server.

What If Only One Server Has cPanel?

If migrating from a non-cPanel source to a cPanel destination, you will need to use imapsync or Thunderbird to copy mailboxes account by account. This takes longer but gives you full control over which data transfers.
# imapsync example — copy one mailbox from old server to new cPanel server: imapsync –host1 mail.oldserver.com –user1 [user@yourdomain.com](mailto:user@yourdomain.com) –password1 OldPass123 –host2 mail.newserver.com –user2 [user@yourdomain.com](mailto:user@yourdomain.com) –password2 NewPass456 –ssl1 –ssl2 –syncinternaldates –addheader # Options explained: –ssl1 / –ssl2 Use SSL encryption on both source and destination connections –syncinternaldates Preserve the original received dates on migrated emails –addheader Adds a migration header to avoid re-syncing duplicates on repeat runs

What Are the Most Common Email Migration Mistakes and How Do You Avoid Them?

  • Cancelling old hosting before migration is complete: The single most common catastrophic mistake. Always keep old accounts active for minimum 30 days post-cutover.
  • Not backing up before starting: IMAP sync tools are non-destructive, but connectivity issues mid-sync can corrupt partial mailboxes. Always back up first.
  • Forgetting to migrate contacts and calendars: IMAP tools only migrate email. Contacts and calendars must be exported and imported separately every time.
  • Changing MX records before the new mailboxes are ready: If you update MX records before creating accounts on the new provider, inbound emails bounce immediately.
  • Missing third-party senders in SPF: Every service that sends email from your domain must be added to your new SPF record or those emails land in spam.
  • Not updating staff email clients: After DNS cutover, users with old IMAP settings see their email stop syncing. Prepare a settings guide before cutover day.
  • Migrating during peak business hours: Schedule MX cutover for the lowest-traffic window. Never migrate on a Monday morning, month-end, or before a major client deadline.
  • Skipping post-migration deliverability checks: New IP addresses sometimes trigger spam filters. Check mail-tester.com and Google Postmaster Tools within 48 hours.
Critical: Do NOT cancel your old email hosting on the same day as your migration. Emails continue arriving at the old MX for hours or days due to DNS caching. Premature cancellation causes permanent email loss with no recovery path

How Long Does a Small Business Email Migration Take?

Migration duration depends on the number of user accounts, total data volume, and connection speed between your old and new servers.
Business Size Users Estimated Data Typical Migration Time
Solo / Freelancer 1 – 2 1 – 5 GB 2 – 4 hours
Micro Business 3 – 10 5 – 25 GB 4 – 12 hours
Small Business 10 – 30 25 – 100 GB 1 – 3 days
Growing SME 30 – 100 100 – 500 GB 3 – 7 days
Complex / Multi-Domain 100+ 500+ GB 1 – 4 weeks
These estimates cover the IMAP sync and DNS propagation phases. Phase 1 planning and backup should always be completed at least 5 to 7 days in advance regardless of business size.

What Is the Recommended Email Migration Timeline for Small Businesses?

the Recommended Email Migration Timeline for Small Businesses
Use this phased timeline as a project management framework. Adapt the durations to your team size and complexity.
Phase Timeline Action
Phase 1 Day 1 – 3 Publish SPF. Audit all accounts, map dependencies, choose provider, set timeline and notify team.
Phase 2 Day 3 – 5 Full mailbox backup, export contacts and calendars. Store in two separate locations.
Phase 3 Day 5 – 7 Set up all accounts, aliases, and SMTP configs on the new provider. Test internal sending.
Phase 4 Week 1 – 2 IMAP sync all mailboxes, contacts, and calendars. Monitor for errors. Run delta sync.
Phase 5 Week 2 Lower TTL. Update MX, SPF, DKIM, and DMARC. Verify propagation. Send test emails.
Phase 6 Week 2 – 6 Monitor deliverability. Configure all clients. Keep old server live for 30 days minimum.
Anterpreneur CTA

What Should You Do If Something Goes Wrong During Migration?

Something Goes Wrong During Migration

What If Emails Are Bouncing After the MX Cutover?

  • Check that the new MX records have propagated fully using MXToolbox.
  • Verify the recipient account exists on the new server — check for typos in the email address.
  • Confirm the new server is accepting connections on port 25 (inbound SMTP).
  • Check whether the new server IP is on any spam blocklists using the MXToolbox Blacklist Check.

What If Emails Are Missing After Migration?

  • Run a second IMAP sync using imapsync or Thunderbird to catch any missed messages.
  • Check the IMAP sync log for errors relating to specific folders or date ranges.
  • Confirm the old server is still accessible and the original emails are present.
  • Restore from your MBOX or PST backup as a last resort using your email client’s import function.

What If Staff Cannot Access Email After Migration?

  • Confirm the user account exists and the password is correct on the new provider.
  • Verify IMAP and SMTP settings match the new provider’s documentation exactly — check port numbers and SSL.
  • Clear the email client’s cached account settings and re-add the account from scratch.
  • Test via webmail first — if webmail works but the desktop client does not, the issue is client configuration.
Best Practice: Your rollback plan is your safety net. If migration goes critically wrong, revert your MX records to the old server values. Because you kept the old server active and did not delete any accounts, email will resume flowing to the original system within minutes of DNS propagation.

Ready to Start Your Email Migration? Here Is Your Action Plan.

A successful email migration does not happen by accident. It requires a clear plan, a full backup, a staged cutover, and at least 30 days of running both old and new environments in parallel.

Use this six-phase checklist as your master reference. Print it, share it with your team, and check off each item as you go.

  • Phase 1 – Plan: Audit accounts, map dependencies, choose provider, set timeline.
  • Phase 2 – Back up: Full mailbox export, contacts, calendars stored in two locations.
  • Phase 3 – Set up: Create all accounts, aliases, and SMTP configs on the new provider.
  • Phase 4 – Migrate: IMAP sync all mailboxes, contacts, and calendars. Run delta sync.
  • Phase 5 – Cutover: Update MX, SPF, DKIM, and DMARC records. Verify propagation.
  • Phase 6 – Verify: Monitor deliverability, configure clients, keep old server live for 30 days.

Planning an Email Migration for Your Business?

We handle end-to-end email migrations for small businesses — from shared hosting to Google Workspace, Microsoft 365, Zoho, or self-hosted VPS setups. We manage the planning, backup, IMAP sync, DNS cutover, staff onboarding, and post-migration monitoring so your team stays connected throughout.

Book a Free Email Migration Consultation

Frequently Asked Questions (FAQs)

Will I lose any emails during migration?

If you follow the checklist — especially Phase 2 (full backup) and Phase 4 (IMAP sync before MX cutover) — the risk of email loss is extremely low. IMAP sync tools copy emails without deleting the originals, and a delta sync captures any new messages received during the migration window. The only scenario that causes genuine data loss is cancelling old hosting before migration is complete.

Perform the full IMAP sync first, then run a final delta sync immediately before updating MX records. With a pre-lowered TTL of 300 seconds, MX propagation takes 5 to 15 minutes. During that window some emails may arrive at the old server — which is why you keep it active and forward stragglers to the new provider.

No — if your email address stays the same (you@yourdomain.com), your contacts will not notice any change. The migration only changes the back-end infrastructure. If you are changing your email address as part of the migration, send an address-change notification and set up forwarding from the old address.

For 1 to 10 users, self-service migration using your new provider’s built-in tools is achievable with a structured checklist. For 10+ users, complex data (shared calendars, CRM integrations), or mission-critical environments with zero tolerance for downtime, a professional migration service is worth the investment.

DIY migration using free tools costs nothing beyond your time. Paid tools like BitTitan MigrationWiz cost $10 to $25 per mailbox. Professional migration services typically range from $200 for a 1 to 5 user project to $2,000 or more for a 50-user engagement. The cost is almost always justified by avoiding even a single day of email downtime.

Email aliases and shared inboxes are routing configurations, not mailboxes with stored emails. They do not need to be IMAP-synced. However, you must manually recreate each alias, group, and shared inbox on the new provider before the MX cutover. Failure to do so means emails sent to those addresses will bounce after DNS is updated.

Your historical emails migrate to the new provider via IMAP sync. A complete sync before MX cutover ensures all emails from the old server exist in the new mailboxes. Additionally, keep a local MBOX or PST backup as a permanent archive. Most providers also allow you to import MBOX or PST files directly at any time.

Leave a comment