Still on GroupWise? How to Migrate to Office 365 Without Losing a Single Email

For years, Novell GroupWise quietly did its job for businesses, universities and government offices. But today many organisations are finding that it no longer fits how teams work. Collaboration tools, mobile access, security updates and integrations all point one way: Microsoft 365 (formerly Office 365). If your organisation is still running GroupWise and the move feels risky, this guide explains why companies migrate, what usually goes wrong, and how the Shoviv GroupWise to Office 365 Migrator makes the move predictable.

Why Are Organisations Moving from GroupWise to Office 365?

• Collaboration. Teams, SharePoint, OneDrive and shared calendars give people one place to chat, meet and share files. GroupWise was never built for that kind of workflow.
• Fewer on-premises headaches. Running your own GroupWise servers means patching, backups, hardware refreshes and specialist admin skills that are getting harder to find.
• Better mobile and remote access. Microsoft 365 works smoothly on phones, tablets and browsers, which matters for hybrid and remote teams.
• Security and compliance. Cloud-based security controls, retention policies and audit tools are built in, rather than bolted on.
• Compatibility. Clients, partners and vendors almost all use Outlook-compatible tools, so everyday communication gets easier.

Why GroupWise Migration Is Not as Simple as It Sounds

GroupWise and Microsoft 365 store and structure data differently, so a simple export-and-import rarely works cleanly. Common problems include:

• Mailbox structure differences. GroupWise folders, items and archives do not map one-to-one to Exchange Online.
• Calendar and task formatting. Appointments, recurring events and tasks can lose details if they are converted poorly.
• Archives. Users often have years of local or server archives that are easy to overlook until after the cutover.
• Large user counts. Moving mailboxes one by one by hand is slow and error-prone.
• Downtime fears. Nobody wants a weekend without email, or a Monday morning full of missing messages.

This is exactly where a dedicated migration tool earns its keep.

A Real-World Scenario: A Manufacturing Group Retires Its GroupWise Servers

The following situation is illustrative, but it reflects what many organisations experience.

A mid-sized manufacturing group had used GroupWise for more than fifteen years. Around 200 employees across the head office, two plants and a sales team relied on it daily. The IT team was just two people, led by an administrator named Vikram.

The pressure to move came from several directions at once:

• The server hardware hosting GroupWise was ageing and out of warranty.
• Management wanted Microsoft Teams for plant-to-office communication.
• The sales team could not reliably access email on their phones.
• Auditors asked for stronger retention and security controls on company email.

Vikram decided to move everyone to Microsoft 365. His real worry was data. Several senior managers had more than a decade of email, along with calendars full of recurring meetings and contact lists they could not afford to lose. Finance also had archived mail needed for compliance.

What Vikram Considered First

He looked at doing it manually, exporting user data and importing it to Microsoft 365 through client-side steps. A short trial showed the problems:

1. It would need hands-on work for every one of the 200 mailboxes.
2. Calendar entries and contacts did not always come across cleanly.
3. There was no easy way to check what had moved and what had failed.
4. Users would be locked out or confused for longer than the business could accept.

How the Shoviv GroupWise to Office 365 Migrator Fit In

Vikram then evaluated the Shoviv GroupWise to Office 365 Migrator. His plan looked like this:

1. Prepare the target. He created the user accounts and licences in Microsoft 365 first, so every GroupWise mailbox had a destination.
2. Connect the source and the destination. He added the GroupWise source and signed in to the Microsoft 365 tenant using the tool.
3. Map mailboxes. He matched each GroupWise user to the correct Microsoft 365 mailbox. For a large user list, he used a CSV file rather than mapping them one at a time.
4. Apply filters. For users with decades of mail, he used date filters to move recent mail first, leaving older mail for a later batch.
5. Run a pilot. He migrated five users from different departments and asked them to check their mail, calendars and contacts.
6. Migrate in batches. After the pilot passed, he moved the remaining users department by department, outside working hours.
7. Review reports. After each batch, he checked the migration report to confirm item counts and spot anything that failed.

The result: users signed in to Microsoft 365 on the cutover Monday and found their folders, emails, calendars and contacts in place. Vikram's team kept the GroupWise servers running in read-only mode for a short period as a safety net before retiring them.

What Should You Check Before Migrating?

1. Audit your users and data. Count mailboxes, archives, shared folders and any special accounts such as resource mailboxes.
2. Clean up first. Remove dormant accounts and obvious junk. Migrating less data is faster and cheaper.
3. Prepare Microsoft 365. Set up your tenant, licences and domain configuration before migration day.
4. Plan the order. Start with a small pilot group, then move departments in batches.
5. Communicate with users. Tell people the date, what will change and who to contact for help.
6. Plan the cutover for mail flow. Decide when to update your MX records so incoming mail lands in the right place.
7. Keep the old system for a while. Do not decommission GroupWise until users have confirmed their data is complete.

Key Benefits of Using a Dedicated GroupWise Migration Tool

• Mailbox mapping at scale. Match many source and destination mailboxes quickly, rather than one by one.
• Filters. Migrate by date range or by folder, so you control what moves and when.
• Batch processing. Move users in groups and reduce the risk of overloading your network or your team.
• Reporting. Review what was migrated and what was not, instead of guessing.
• Less downtime. A planned, tested process means smaller disruption for users.

Manual Migration vs. Shoviv GroupWise to Office 365 Migrator

Final Thoughts

Moving from GroupWise to Office 365 is less about technology and more about trust. People need to know their email history, meetings and contacts will still be there on day one. With careful planning, a pilot group and a purpose-built tool, the move can be calm instead of chaotic.

If your organisation is still running GroupWise, now is a good time to start planning. Download the free demo of the Shoviv GroupWise to Office 365 Migrator, test it on a few mailboxes, and see how your own data behaves before you commit to the full move.

Frequently Asked Questions

Can I migrate GroupWise archives as well as live mailboxes? Archives are an important part of most migrations. Check the current product page for the exact archive formats and options supported.

Will calendars, contacts and tasks be migrated? A good migration should carry these across along with email. Run a pilot to confirm how your own calendar and contact data appears in Microsoft 365.

Can I migrate only part of a mailbox? Yes, filters let you limit what moves, for example by date range, so you can migrate recent mail first and older mail later.

Do users need to be offline during the migration? Not necessarily. Many organisations migrate in batches outside working hours and cut over mail flow once data has been verified.

What if something fails during migration? Review the migration report, fix the cause, and re-run for the affected items or mailboxes. This is another reason to run a pilot first.

Is there a free trial? Shoviv usually offers a demo version with limits. Check the product page for the current terms.