How to migrate GroupWise to Office 365? The route Microsoft documents is an IMAP migration. You turn on IMAP in GroupWise, create the users in Microsoft 365, then build an IMAP endpoint and a migration batch in the Exchange admin center. Microsoft says this method moves email only, not contacts, calendar items or tasks. Microsoft's own pages name GroupWise only as a platform that third-party tools handle, so there is no official GroupWise-specific guide.
Which Method Does Microsoft Document for GroupWise to Office 365?
Microsoft lists several ways to move mail into Microsoft 365: IMAP, cutover, staged, hybrid and third-party tools. In its migration best-practices page, Novell GroupWise appears only as a platform that third-party tools are used for.
The page does not give GroupWise-specific steps. The closest official path is the IMAP migration, because GroupWise can serve mail over IMAP. This guide follows that path.
What Does an IMAP Migration Move?
Microsoft states these facts:
- It migrates email from the inbox and other mail folders only.
- It does not migrate contacts, calendar items or tasks.
- Each mailbox can hold up to 500,000 items, migrated from newest to oldest.
- Each item can be up to 35 MB.
Step 1: Prepare Microsoft 365
Prepare the destination before any GroupWise to Office 365 mail is copied.
- Create each user in Microsoft 365 and assign a license. Microsoft says the mailboxes must exist before the migration.
- If you use the same domain on both systems, add it as an accepted domain before you create users.
- Disable any MRM and archival policies on the destination before you start. Microsoft says items those policies delete or archive show up as missing, which hides real data loss.
- Optional: lower the MX record TTL to 3,600 seconds or less. Microsoft says this reduces delivery delays after the later MX change.
Step 2: Turn On IMAP in GroupWise
The GroupWise Administration Guide describes the setting. In the admin console, open the Post Office Agent (POA), go to Agent Settings and select Enable IMAP. The guide gives these defaults:
- The default IMAP port is 143, and SSL connections use port 993.
- The default maximum number of IMAP threads is 40. Too few threads can slow IMAP clients.
Microsoft 365 connects from outside your network. The GroupWise 18 guide says IMAP clients outside the firewall must connect through the Internet Agent (GWIA), not the POA, because direct POA connections are meant for internal clients. The GroupWise 23 guide says IMAP4 on the GWIA is off by default. Open the GWIA object, select the POP3/IMAP4 tab, select Enable IMAP4 Service, then save.
Step 3: Build the CSV File
Microsoft says the file needs three headers, written exactly like this: EmailAddress, UserName and Password. The IMAP migration instructions set these rules:
- EmailAddress is the Microsoft 365 address of the user.
- UserName is the sign-in name on the source system.
- Password is the password of the source mailbox.
- The file can hold up to 50,000 mailboxes and be up to 10 MB.
Microsoft also allows admin credentials in the UserName column, but only gives formats for Exchange, Dovecot, Mirapoint, and Courier or Oracle IMAP. GroupWise is not in that list. For other systems Microsoft says to reset the passwords instead, and notes that users cannot reach their old mailboxes until they get the new ones.
Step 4: Create the Endpoint and Batch
Microsoft describes these steps in the Exchange admin center:
- Go to Migration, then Endpoints, then Add.
- Choose IMAP as the type, enter an endpoint name and enter your IMAP server name.
- Go to Migration, then Add migration batch. Use a batch name with no spaces or special characters.
- Select Migrate to Exchange Online and IMAP migration as the type.
- Pick the endpoint, upload the CSV file, set your options and save.
Start with a small batch. Check the status reports under Migration, then View details, and ask a test user to confirm that mail and folders appear in Outlook.
Step 5: Switch Mail Flow and Stop the Sync
To finish a GroupWise to Office 365 migration, change mail flow in this order:
- Change the MX record to point to Microsoft 365. Microsoft says senders can take up to 72 hours to pick up the change.
- Wait at least 72 hours and confirm users work only in Microsoft 365.
- Delete the migration batch. Microsoft says mail sent to the old system after this is no longer copied.
What About Calendar, Contacts and Archives?
IMAP does not carry them, per Microsoft. OpenText's own material says its GroupWise Migration Services can move email, appointments, tasks, calendars, address books, personal archives and shared folders to Exchange or Office 365 using its Retain Email product. That document is marketing. It gives no technical limits, so confirm the details with the vendor before you rely on it.
What Do These Sources Not Say?
- Microsoft gives no GroupWise-specific procedure and no GroupWise admin-credential format for the CSV file.
- Neither vendor says how to move GroupWise calendars and contacts with the IMAP method.
- The old GroupWise Connector and ConsoleOne steps are not covered by any source used here, so this guide drops them.
- Migration time is not stated for GroupWise. Microsoft's pages give limits, not durations.
Frequently Asked Questions
Can I migrate GroupWise to Office 365 directly?
Microsoft has no GroupWise-specific method. Its documented route is the IMAP migration, which needs IMAP turned on in GroupWise.
Does the IMAP method move calendar and contacts?
No. Microsoft says it moves email only, and not contacts, calendar items or tasks.
What are the IMAP migration limits?
Microsoft gives 500,000 items per mailbox and 35 MB per item. The CSV file can list up to 50,000 mailboxes and be up to 10 MB.
Do I need each user's password?
Microsoft lists admin-credential formats for some systems only, and GroupWise is not among them. For other systems it says to reset passwords.
Which ports does GroupWise use for IMAP?
GroupWise guides give 143 for IMAP and 993 for SSL by default. Confirm the values for your GroupWise version.
When should I stop the migration batch?
Microsoft says to wait at least 72 hours after the MX change, confirm users use only Microsoft 365, then delete the batch.
Key Takeaways
- Microsoft's documented route for GroupWise to Office 365 is an IMAP migration. It has no GroupWise-specific guide.
- IMAP moves email only. Plan calendars, contacts and tasks separately.
- Create licensed users first, build the CSV file, then create the endpoint and batch.
- Wait at least 72 hours after the MX change before you delete the batch.
- Back up your data first. Our guide on how to restore an Office 365 mailbox from backup shows the recovery side, and the SharePoint Online migration checklist is a useful model for planning.
Sources and References
Facts follow Microsoft Learn, the GroupWise guides and OpenText.
- What you need to know about migrating IMAP mailboxes to Microsoft 365 learn.microsoft.com
- Migrate other types of IMAP mailboxes learn.microsoft.com
- Microsoft 365 migration performance and best practices learn.microsoft.com
- Configuring User Access to the Post Office (GroupWise 18 Administration Guide) www.novell.com
- Enabling POP3/IMAP4 Services (GroupWise 23 Administration Guide) www.novell.com
- IMAP4 Switches (GroupWise 23 Administration Guide) www.novell.com
- Six Keys for Simple Email Migration (OpenText) www.microfocus.com