MedhaCloud
IceWarp → M365IceWarp All VersionsCalDAV/CardDAV ExportGroupWare MappedZero Downtime CutoverDelta Sync IncludedDNS Handled30-Day Hypercare$15/User FlatIceWarp → M365IceWarp All VersionsCalDAV/CardDAV ExportGroupWare MappedZero Downtime CutoverDelta Sync IncludedDNS Handled30-Day Hypercare$15/User Flat

IceWarp to Office 365 Migration

IceWarp Server (self-hosted or cloud) → Microsoft 365. Mail over IMAP, calendars and contacts via CalDAV/CardDAV export, TeamChat wind-down plan. From $15/user, zero downtime cutover.

$0
Per-user starting
0wk
Typical timeline
0
Data loss
Pricing Engine · LiveIceWarp → M365
From
IceWarp
25remaining
To
0migrated
Microsoft 365
Microsoft 365
$0
M365 live by
JUL 21, 2026
25

BitTitan Certified · Zero Data Loss Record · DNS Handled

$0
Per-user starting
0wk
Typical timeline
2-4hr
MX Cutover Window
0
Data Loss Incidents
Apps + data we migrate

Every mailbox. Every folder. Verified.

Outlook
Outlook
Mail · calendar · contacts
Exchange
Exchange
Mailboxes · aliases · lists
OneDrive
OneDrive
Files · folders · shares
SharePoint
SharePoint
Sites · document libraries
Teams
Teams
Channels · chats · files
Microsoft 365
Microsoft 365
Full admin · direct tenant
Why leave IceWarp

What staying actually costs.

01 / 04 · Ecosystem ceiling
ECO

IceWarp’s all-in-one pitch ends where Teams meetings, Intune device management, and Copilot begin. Standardizing on Microsoft means leaving.

02 / 04 · DAV-based groupware
DAV

IceWarp calendars/contacts live on CalDAV/CardDAV — no EWS. Fidelity depends on doing the export path right, which is exactly what we script.

03 / 04 · Self-hosted burden
SELF

Patch cycles, TLS renewals, storage growth — a mail server is a full-time tenant in your infrastructure. M365 evicts it.

04 / 04 · Cutover window
2-4hr

Standard off-hours MX flip after delta sync — a 30-user IceWarp server completes within a week.

What's included

Everything handled. Nothing assumed.

01

Server-side IMAP mail sync

Mail and folder structure migrate over IMAP with delta passes, paced to your server’s capacity.

02

CalDAV/CardDAV export path

Calendars and contacts export via DAV/ICS/VCF server-side and import into Exchange Online — verified per user, recurring events checked.

03

GroupWare mapping

IceWarp shared folders and group calendars map to Microsoft 365 shared mailboxes and group calendars by agreed policy.

04

TeamChat wind-down

IceWarp TeamChat history can’t migrate to Teams — we plan the export/archive and the Teams rollout so collaboration doesn’t skip a beat.

05

DNS + deliverability

MX, SPF, DKIM, DMARC configured on Microsoft 365; the old server’s IP reputation stops being your problem.

06

Decommission runbook

After verification: mail routing off, DAV endpoints closed, server retired — documented so nothing keeps listening on port 25.

Delivery methodology

Assess. Plan. Migrate. Cutover.

01

Assess

1-2 days · Source audit, mailbox inventory, domain list. Fixed per-user quote in 24-48 hours.

02

Plan

1-2 days · Microsoft 365 tenant provisioned, domains verified, MFA + security baseline deployed.

03

Migrate

Background · Server-side pre-stage sync runs invisibly. Users keep working on the old system until cutover.

04

Cutover

2-4 hrs off-hours · MX/SPF/DKIM flip, final delta sync, Autodiscover repoint. 30 days hypercare.

Who runs your migration

The engineers on your project.

No outsourced ticket triage. The same three engineers handle source assessment, tenant provisioning, cutover night, and post-migration support on every IceWarp engagement.

01

Sreenivasa Reddy

Founder & Principal Migration Engineer

MCSE Messaging · 25 yrs · 500+ migrations led

Owns the discovery call and migration architecture: source assessment, licensing right-size, and the compliance/security mapping that decides which M365 SKU mix you actually need.

02

Roshan Pujari

Senior Migration Engineer · Source Systems Lead

Microsoft Certified · M365 Administrator

Runs source-side assessment and extraction: credentials, throttling strategy, batch design, and the pre-stage sync that makes cutover weekends boring.

03

Bhargav

Senior Migration Engineer · Mail Flow + Cutover

Microsoft Certified · Exchange + M365 Messaging

MX/SPF/DKIM/DMARC cutover and Autodiscover repoint. Owns the 2-4 hour cutover window plus post-cutover Outlook profile and mobile device resync.

What makes IceWarp→M365 different

The IceWarp-specific realities.

Generic migration guides skip these. They are the operational details that decide whether your cutover weekend is boring — which is the goal.

01

IceWarp has no EWS — calendars/contacts move via scripted CalDAV/CardDAV exports, not mailbox-protocol magic

02

TeamChat history cannot land in Teams — we archive it readably and plan the Teams rollout as part of cutover comms

03

Self-hosted IceWarp boxes are often undersized for bulk export — sync pacing keeps production mail flowing during migration

FAQ

Frequently Asked Questions

Do IceWarp calendars and contacts migrate to Office 365?+
Yes — via scripted CalDAV/CardDAV exports (ICS/VCF) imported into Exchange Online and verified per user. IceWarp has no EWS, so the export path is the correct path, and it’s included in the flat rate.
What happens to IceWarp TeamChat?+
No tool migrates TeamChat history into Microsoft Teams. We export and archive it in a searchable format and plan your Teams rollout so the collaboration switch is announced, not discovered.
How long does an IceWarp to Office 365 migration take?+
A typical 30-user IceWarp server completes within a week: background IMAP sync, DAV exports, then a weekend MX cutover. $15/user plus $500 setup.
What is the downtime during a IceWarp to Microsoft 365 migration?+
Minimal — typically the 2-4 hour MX cutover window, scheduled off-hours (evenings or weekends). Data pre-stages in the background beforehand, and we run both systems in parallel during DNS propagation so no email is lost.
Is there any risk of data loss?+
We verify per-mailbox item counts after migration and keep the source system live until verification completes. Across 500+ migrations and 1.4 million users, we maintain a zero data loss record. Full rollback plans are documented for every cutover.
What does the migration include for $15/user?+
Discovery, tenant setup, background pre-stage sync, delta syncs, cutover night execution, DNS changes (MX/SPF/DKIM/DMARC), Autodiscover repoint, and 30 days of post-migration hypercare. One-time $500 project setup fee. PC setup available at +$25/user.

All-in-one, meet actually-all-in-one.

$15/user flat. Pre-staged sync, off-hours cutover, DNS handled, 30-day hypercare. Zero data loss record across 1.4M users.

GET FREE ASSESSMENT →OPEN CALCULATOR →

Microsoft Solutions Partner · BitTitan certified · Fixed-fee · 500+ migrations

VIEW PLANS →
From Our Blog

Cloud Migration Strategies & Step-by-Step Guides

Cloud Services

50 Cloud Migration Statistics for 2026 — Success & Failure Rates

A comprehensive roundup of 50 cloud migration statistics for 2026 covering success rates, failure causes, migration costs, timelines, repatriation trends, and multi-cloud strategy data from Gartner, IDC, Flexera, and Forrester.

17 min readMar 14, 2026
Cloud Services

55 Cloud Computing Statistics for 2026: Spending, Migration & Adoption

55 cloud computing statistics for 2026 covering global spending ($679B), migration timelines, multi-cloud adoption, data center investment, and SMB cloud budgets with sourced data.

16 min readMar 14, 2026
Email Migration

Google Workspace to Microsoft 365 Migration: The Complete 2026 Playbook (Gmail, Drive, and Shared Drives)

A step-by-step migration playbook for moving from Google Workspace to Microsoft 365 covering Gmail to Exchange Online, Drive to OneDrive/SharePoint, identity migration, DNS configuration, and post-migration security — with tool comparisons and timeline estimates.

24 min readMar 13, 2026
Microsoft 365 migration

Case study: Hosting panel-based IMAP to Microsoft 365 Migration for government services in Virginia 

Client overview A government services agency in Virginia, with over 1,000 employees, had been using a hosting panel-based IMAP system for their email and communication needs. As the agency grew, they faced challenges in managing email effectively, ensuring data security, and fostering collaboration across teams. Given the critical nature of their services, the agency needed a […]

7 min readOct 24, 2024