For eleven years, GroupWise was the quiet backbone of our company's communication. Nobody thought about it, and that was the highest compliment an email system could earn. Then, one Monday morning, it became the only thing anyone in IT could think about.

This is the story of how our team moved from Novell GroupWise to Office 365, what nearly went wrong, and what we would tell any admin still sitting on the fence.

The Breaking Point

We're a mid-sized logistics company with about 180 employees across three offices. GroupWise had served us well, but the cracks had been showing for a while:

• Mobile access was clunky. Our field managers wanted email and calendars on their phones without workarounds.
• Collaboration had moved on. Everyone else we worked with was on Teams, SharePoint, and shared Microsoft calendars. We were the odd ones out, emailing attachments back and forth.
• Finding GroupWise expertise got harder every year. When our longtime GroupWise administrator retired, we realized the knowledge of how our server was configured had left with him.
• Server maintenance was becoming a burden. Aging hardware, patching, and backups all fell on a small IT team already stretched thin.

The final push came when a hardware fault on our mail server took email down for most of a working day. Leadership asked one question: "Why are we still running this ourselves?"

The decision to move to Office 365 was made in that meeting. The harder question was how.

The Part Nobody Warns You About

I assumed that migrating email would be a fairly standard job. It isn't, not from GroupWise. Here's what we ran into during planning:

1. GroupWise data doesn't map neatly onto Office 365. Emails, contacts, calendars, and folder structures are stored differently. Without a proper conversion process, you risk flattened folders, missing calendar entries, or contacts that don't carry over cleanly.

2. Archives are easy to forget. Many of our employees had years of archived mail stored locally. If we only migrated live mailboxes, that history would have been stranded. For our finance and compliance teams, that wasn't an option.

3. Manual methods don't scale. We looked at exporting mailboxes one at a time. With 180 users, that meant weeks of repetitive work and a lot of room for human error.

4. Interruptions are inevitable. Network drops, throttling, a laptop going to sleep at the wrong moment: on a migration this size, something will interrupt the process. What matters is whether you can pick up where you left off or have to start over and risk duplicates.

We needed something that could handle multiple mailboxes at once, include archives, and recover gracefully from interruptions.

How We Approached It

After comparing options, we tested Shoviv GroupWise to Office 365 Migration Tool using its free trial version on a handful of pilot mailboxes before committing. That trial run was valuable, because it let us check the results with real data instead of trusting a feature list.

Here's how the migration went, in broad strokes:

Step 1: Pilot with a small group. We picked five mailboxes, including one heavy user with a very large archive, and migrated them first. We compared folder structures, calendar entries, and contacts side by side with the originals.

Step 2: Connect to GroupWise and Office 365. The tool lets you set up the connection to your GroupWise source and your Office 365 destination in a guided way, so our team didn't need deep GroupWise scripting knowledge, which was a relief given our history.

Step 3: Use filters to migrate only what mattered. Some users had years of clutter. Using the filter options, we chose what to bring across instead of moving everything blindly, which shortened the migration window and kept the new mailboxes cleaner.

Step 4: Migrate mailboxes in batches. Rather than one user at a time, we ran multiple mailboxes concurrently, batching by department. Finance went first, since they had the strictest requirements for preserving history.

Step 5: Include the archives. GroupWise archive data was migrated to the Office 365 mailboxes too, so nobody lost access to old correspondence.

Step 6: Resume, don't restart. In the middle of our second batch, our office internet connection dropped for about twenty minutes. In the past, that would have meant restarting and cleaning up duplicates. With the incremental export capability, we resumed the job and it continued from where it stopped, without re-copying items that had already moved.

What Changed After the Move

Within a few weeks of completing the migration, the difference was noticeable:

• Field managers got proper mobile email and calendar access, and the complaints about "clunky" mail stopped.
• Collaboration improved. Teams and shared calendars replaced the endless attachment chains.
• Our server headaches disappeared. No more patching a mail server, no more hardware failure risk, and no more single-person dependency for email administration.
• Nobody lost history. Finance could still search years of archived correspondence, which was the one thing leadership had insisted on.

What I'd Tell Other Admins Considering the Move

If I could go back and advise my past self, here's what I'd say:

• Start with a pilot. Testing on a few mailboxes, including your messiest ones, will reveal issues before they affect everyone.
• Don't forget archives. Ask every department where their old mail lives.
• Plan for interruptions. Choose an approach that can resume cleanly, not one that forces a restart.
• Communicate with users early. The technical migration was the easy part. Getting people comfortable with a new interface took more effort than moving the data.
• Don't try to do it manually at scale. The time you think you're saving by avoiding a tool gets spent many times over on repetitive work and fixing mistakes.

Final Thoughts

Leaving GroupWise felt like a big decision, but the migration itself turned out to be far less painful than the years of putting it off. If your organization is still running GroupWise and wondering whether it's time, the honest answer is that the longer you wait, the harder it gets, as expertise thins out and hardware ages.

If you'd like to see how the process works with your own data, Shoviv offers a free trial version of its GroupWise to Office 365 Migration Tool, so you can test it on a few mailboxes before committing to a full migration.