How to Migrate CommuniGate to Microsoft 365
Summary: To migrate CommuniGate Pro mailboxes to Microsoft 365 with folders and attachments intact, you have three options. First, run an IMAP migration from the Microsoft 365 admin center for a free, in-place email move. Next, export each mailbox to PST and upload through the Network Upload (AzCopy) service. Finally, use a dedicated CommuniGate to Microsoft 365 migrator that preserves folders, calendars, contacts, and dates in one pass.
- IMAP migration is free and handles email only.
- PST network upload via AzCopy works well for large mailboxes.
- A dedicated tool migrates email, calendars, and contacts together.
CommuniGate Pro is a long-running on-premises mail server. Many organizations still run it for legacy reasons, but the maintenance burden keeps growing. As a result, most teams eventually move to Microsoft 365 for cloud reliability, Teams, and Exchange Online features. This guide walks through three proven migration paths in 2026.
In short, you can use Microsoft’s built-in IMAP migration, a PST upload through AzCopy, or a dedicated migrator. Pick the method that fits your mailbox count, mailbox size, and whether you need calendars and contacts.
Why Migrate from CommuniGate Pro to Microsoft 365
Microsoft 365 removes the cost of running a mail server in your data center. Therefore, you stop paying for hardware refreshes, OS patching, and 24×7 mail uptime. In addition, Microsoft 365 ships with Exchange Online, Teams, OneDrive, and SharePoint, all under one license.
Also, Microsoft 365 brings modern security features such as Defender for Office 365, conditional access, and built-in DLP. As a result, your mail platform inherits enterprise-grade phishing and malware protection without extra appliances.
Benefits of Microsoft 365 over CommuniGate Pro Server
- No server maintenance: Microsoft handles patching, scaling, and uptime.
- Bigger mailboxes: 50 GB or 100 GB per user depending on plan.
- Anywhere access: Outlook, OWA, and mobile apps work out of the box.
- Built-in collaboration: Teams, OneDrive, and SharePoint are included.
- Modern security: Defender, MFA, and conditional access by default.
- Compliance: retention, eDiscovery, and audit logs are native.
What You Need Before You Start
First, get global admin access on both ends. You need a Microsoft 365 tenant admin account and a CommuniGate Pro postmaster account. Next, license each target user in Microsoft 365 with a plan that includes Exchange Online, such as Business Standard or E3.
Then, audit mailbox sizes on CommuniGate. Mailboxes over 50 GB will not fit on standard plans, so plan splits or archiving. Finally, prepare your DNS. You will lower the MX record TTL to 300 seconds at least 48 hours before cutover.
Quick note: Keep CommuniGate Pro running during the migration window. Both IMAP and dedicated tools read from CommuniGate live, and a co-existence period prevents lost mail during MX cutover.
Method 1: IMAP Migration in the Microsoft 365 Admin Center
Microsoft’s built-in IMAP migration is free and works directly from the admin center. However, it copies email only, so calendars and contacts stay behind.
Step-by-step
- In CommuniGate Pro, confirm IMAP is enabled and reachable on port 993 with TLS.
- Create the target users in Microsoft 365 and assign Exchange Online licenses.
- Build a CSV file with three columns: EmailAddress, UserName, Password. UserName and Password are the CommuniGate credentials for each mailbox.
- In the Exchange admin center, go to Migration > Add migration batch > Migration to Exchange Online > IMAP migration.
- Enter the CommuniGate Pro server, port 993, TLS, then upload the CSV file.
- Start the batch and monitor progress in the migration dashboard.
Limitations to plan for
IMAP migration moves email only. In contrast, calendars, contacts, tasks, and rules stay on CommuniGate. Also, mailboxes are capped at 50 GB per user during IMAP migration, which is a hard Microsoft limit.
Method 2: Export Mailboxes to PST, Then Upload via Network Upload (AzCopy)
Network Upload is Microsoft’s bulk PST import service. Therefore, it suits large mailboxes that would time out over IMAP. The catch is that you must produce PST files from CommuniGate first.
Step-by-step
- Use a CommuniGate-to-PST converter or connect Outlook over IMAP and export each mailbox via File > Open & Export > Import/Export > Export to a file > Outlook Data File (.pst).
- In the Microsoft Purview compliance portal, open Data lifecycle management > Import > New import job.
- Name the job and choose Upload your data, then copy the SAS URL.
- Download AzCopy from Microsoft, then run
azcopy.exe copy "C:\PSTs" "[SAS-URL]" --recursive=trueto upload every PST. - Build the PST mapping CSV with the columns Microsoft documents (Workload, FilePath, Name, Mailbox, IsArchive, TargetRootFolder, ContentCodePage, SPFileContainer, SPManifestContainer, SPSiteUrl).
- Upload the mapping file, run analysis, then start the import.
When PST upload is faster than IMAP
PST upload wins when mailboxes are above about 10 GB or when your CommuniGate server has slow outbound bandwidth. Additionally, AzCopy ships data to Azure over an optimized link, so transfer rates beat IMAP by a large margin on big mailboxes.
Method 3: Use a Dedicated CommuniGate to Microsoft 365 Migrator
For a one-shot migration that moves email, calendars, contacts, and rules together, a dedicated tool is the simplest path. It connects to CommuniGate over IMAP and to Microsoft 365 over Modern Authentication, then maps every folder.
Step-by-step
- Install the CommuniGate to Microsoft 365 migrator on a Windows machine with network access to both servers.
- Add the CommuniGate Pro server, port, and a postmaster or impersonation account.
- Add the Microsoft 365 tenant using an app registration with the Mail.ReadWrite and Calendars.ReadWrite Graph scopes.
- Map source mailboxes to target mailboxes through a CSV or a built-in directory match.
- Apply optional filters such as date range, folder include or exclude, or item type.
- Run a small pilot batch first, validate, then start the full migration.
Why a dedicated migrator helps
The migrator handles email, calendars, and contacts in the same pass. Additionally, it preserves original dates, attachments, and folder hierarchy. Finally, throttling and retry logic prevent Microsoft 365 from cutting off your sessions during long jobs.
Post-Migration Steps
After the final data sync, switch your MX record to tenant.mail.protection.outlook.com. Then, watch mail flow for 24 to 48 hours and confirm no bounces. Next, decommission CommuniGate Pro in stages: stop external IMAP, then SMTP, then power off.
Also, validate Autodiscover, SPF, DKIM, and DMARC records in DNS. As a result, Outlook clients will auto-configure and outbound mail will pass alignment checks. Finally, run a tenant-wide search to confirm migrated items are searchable in Exchange Online.
Which Method Should You Choose?
- Email only, small mailboxes, free path: use Method 1 (IMAP migration).
- Large mailboxes, slow uplink, email only: use Method 2 (PST upload via AzCopy).
- Email plus calendars and contacts, low-risk cutover: use Method 3 (dedicated migrator).
In short, the free Microsoft paths cover email only. As a result, most organizations that rely on shared calendars or contact lists choose a dedicated migrator for a complete cutover.
Frequently Asked Questions
Can I migrate CommuniGate calendars and contacts to Microsoft 365?
Yes, but only with a dedicated migrator. The built-in IMAP migration handles email only. Therefore, if calendars and contacts matter, choose Method 3 or run a separate calendar export through CalDAV.
Will folder structure be preserved during the migration?
Yes. All three methods preserve the source folder tree. IMAP migration maps CommuniGate folders to Exchange folders one-to-one. In addition, PST upload and dedicated migrators recreate the same hierarchy in each target mailbox.
How long does a CommuniGate to Microsoft 365 migration take?
It depends on mailbox count, mailbox size, and bandwidth. As a rough guide, a 5 GB mailbox takes 1 to 3 hours over IMAP and 20 to 40 minutes via PST upload. Plan a weekend cutover window for any tenant over 100 users.
Do I need to keep CommuniGate Pro running during the migration?
Yes. Both IMAP and dedicated tools read from CommuniGate live, so the server must stay online until the final sync finishes. After the MX cutover, watch for stragglers for 24 to 48 hours before you shut CommuniGate down.
Can I migrate to Exchange Online without changing my domain?
Yes. You add your CommuniGate domain to Microsoft 365 as an accepted domain, verify it with a TXT record, and migrate mailboxes under that same domain. As a result, user email addresses stay identical after the move.
Does this work for Microsoft 365 Business and Enterprise plans?
Yes. Every method in this guide works across Business Basic, Business Standard, Business Premium, E1, E3, and E5. The only difference is mailbox size: 50 GB on Business and E1, 100 GB on E3 and E5.
Final Thoughts
Migrating CommuniGate Pro to Microsoft 365 is a well-trodden path in 2026. First, decide whether you need email only or a full cutover that includes calendars and contacts. Next, run a pilot batch on a small set of users to catch any data-shape surprises. Finally, plan an MX cutover window with a 48-hour overlap so no mail is lost. With the right method, your team will be on Exchange Online with their full history intact.
Related Guides
- How to Import a PST File to Microsoft 365: useful if you have local PST archives to bring over after the CommuniGate move.
- Convert Thunderbird to Microsoft 365: for users whose mail lives in Thunderbird profiles instead of the CommuniGate server.
- Backup Google Workspace Emails: a parallel guide if some of your users are on Google Workspace today.