GroupWise to Microsoft 365 migrations have become routine enough that the tooling, the rough timeline and the common pitfalls are all well understood. For an SME between fifty and two hundred and fifty mailboxes the project typically runs six to twelve weeks from kick-off to cutover. The work splits cleanly into three phases: discovery, pilot, and cutover. The single highest-risk item is almost always calendar data, not email, and the place most projects lose time is shared folders, not user mailboxes.

Discovery — know what you are actually moving

Before any tooling touches a mailbox you need a clean inventory: how many post offices, on which versions of GroupWise, how many mailboxes in total, broken down by user, resource, and shared folder. Capture mailbox sizes, the size of the on-disk archive if you have one, the number of delegated mailboxes, the number of GroupWise rules and the volume of documents held in shared folders. Capture it again from the Microsoft 365 side: how many licences you have, which plan, whether you have the right Entra ID P1 or P2 features for conditional access from day one. The aim is to know exactly what you are moving, how big it is, and which edge cases will need human handling.

The migration tool landscape

CloudM Migrate: a mature SaaS tool with strong GroupWise support, well-suited to IMAP-style or API pulls into Exchange Online.
Transend: a long-standing on-premise migration engine with explicit GroupWise connectors, useful for complex cutovers where you want full control of the pipeline.
Shoviv GroupWise to Office 365: a lower-cost tool aimed at smaller migrations and one-off mailbox moves; capable but light on enterprise features.
Microsoft FastTrack Partner-led: Microsoft-funded partner time for onboarding Microsoft 365 at scale, including migrations from competing platforms.
PowerShell and Graph scripting: appropriate for small numbers of resource mailboxes or bespoke shared-folder mapping, but not a substitute for a real migration tool at scale.

Pick the tool based on the inventory you built in discovery. For most SMEs between fifty and three hundred mailboxes the answer is CloudM or Transend with a partner running the engagement. For projects with heavy shared-folder usage, complex delegate chains or regulatory evidence requirements, the on-premise Transend approach gives more control. Tools are not interchangeable: each handles calendar quirks differently and each has a slightly different model for handling GroupWise rules and signatures.

Mail, contacts, calendar, free/busy, rules and signatures

Email migration itself is usually the easy bit — modern tooling moves years of mailbox content reliably, including folder structure and metadata. Contacts migrate cleanly when the source GroupWise contacts are well-maintained; expect to do a small amount of dedup work at the Exchange Online end. Calendar data is the most likely source of cutover-day surprises: recurring meetings with exceptions, shared calendars across multiple users and resource booking calendars all behave differently between GroupWise and Exchange. Free/busy data between users on the same platform migrates well in our experience; free/busy between migrated and not-yet-migrated users during the pilot phase does not, and that is one reason pilots are useful.

Shared folders and delegated mailboxes

Shared folders are the part of GroupWise that most resembles an old-fashioned file share inside the email client. Modern equivalents in Microsoft 365 are a combination of shared mailboxes, SharePoint document libraries and Microsoft 365 Groups. The mapping is not one-to-one and the design conversation is the most valuable part of the project: which shared folders genuinely remain shared mailboxes in Exchange Online, which become SharePoint sites, which become Microsoft 365 Groups with attached Teams channels, and which really should be retired because the business no longer needs the volume of historic data they contain. Delegate relationships — boss and PA setups — usually migrate cleanly if they were modelled correctly in the first place.

Pilot, cutover and order of operations

Pilot with five to ten representative users across two or three teams. Include at least one heavy shared-folder user and one heavy calendar user.
Run the pilot in parallel with GroupWise for a week or two. Users keep both clients and report on differences, missing data and odd behaviour.
Decide on a wave plan for the rest of the business, typically grouped by team or by post office. Avoid migrating the whole company in one weekend.
Schedule cutover out of hours for each wave, with rollback to GroupWise kept open for at least one business cycle.
Decommission GroupWise formally only once every mailbox has been migrated, the shared folders have been validated, and the legal hold / archive requirements have been confirmed in writing.

Common pitfalls to avoid

Three patterns account for most of the projects we have had to rescue. The first is starting the migration before the Microsoft 365 tenant is properly set up — domain verification, licence assignment, conditional access baseline and the security defaults you actually want are not optional. The second is leaving GroupWise DNS records in place too long after cutover, which results in a confusing period where mail lands in the wrong place and the helpdesk gets buried. The third is forgetting the on-disk GroupWise archive: it is rarely needed in the live migration because users have already moved what matters into the current mailbox, but it has to be retained for the legal retention period your business is committed to.

We help SMEs across Hertfordshire, Bedfordshire and London land on Microsoft 365 cleanly, including the GroupWise migrations we encounter most often in education, local government suppliers and long-established professional services firms. If you are weighing a move and would like a fixed-price scoping conversation, get in touch.