MedhaCloud
GroupWise → M365GroupWise 7-23 SupportedPost-Office ExtractionProxy Rights MappedZero Downtime CutoverDelta Sync IncludedDNS Handled30-Day Hypercare$15/User FlatGroupWise → M365GroupWise 7-23 SupportedPost-Office ExtractionProxy Rights MappedZero Downtime CutoverDelta Sync IncludedDNS Handled30-Day Hypercare$15/User Flat

GroupWise to Office 365 Migration

Novell / Micro Focus / OpenText GroupWise → Microsoft 365. One of the last legacy-platform migrations still running in government, education, and long-established firms — and one that punishes inexperience. Specialist tooling, staged extraction, verified fidelity.

$0
Per-user starting
4-8wk
Typical timeline
0
Data loss
Pricing Engine · LiveGroupWise → M365
From
GroupWise
25remaining
To
0migrated
Microsoft 365
Microsoft 365
$0
M365 live by
JUL 18, 2026
25

BitTitan Certified · Zero Data Loss Record · DNS Handled

$0
Per-user starting
4-8wk
Typical timeline
2-4hr
MX Cutover Window
0
Data Loss Incidents
Apps + data we migrate

Every mailbox. Every folder. Verified.

Outlook
Outlook
Mail · calendar · contacts
Exchange
Exchange
Mailboxes · aliases · lists
OneDrive
OneDrive
Files · folders · shares
SharePoint
SharePoint
Sites · document libraries
Teams
Teams
Channels · chats · files
Microsoft 365
Microsoft 365
Full admin · direct tenant
Why leave GroupWise

What staying actually costs.

01 / 04 · Vanishing expertise
EOL

GroupWise admins are retiring and OpenText’s roadmap is maintenance-mode. Every year of delay makes the eventual migration harder and rarer-skilled.

02 / 04 · No 1:1 for proxy rights
PROXY

GroupWise proxy rights and shared folders have no direct Exchange equivalent — they map to delegation and shared mailboxes by explicit policy, documented per user.

03 / 04 · Archive sprawl
.ARC

Personal .arc archives on workstations are GroupWise’s version of PST sprawl. A collection pass gathers them so history isn’t abandoned.

04 / 04 · Legacy infrastructure
NW

Post offices on NetWare-era systems migrate via a staged extraction server we stand up — production GroupWise is never the bottleneck.

What's included

Everything handled. Nothing assumed.

01

Direct post-office extraction

Quest-class connectors read the GroupWise post office directly and write to Exchange Online — mail, calendars, contacts, frequent-contact lists.

02

Recurring-item verification

GroupWise recurring items and busy searches map imperfectly — every recurring meeting is explicitly verified after migration.

03

Proxy rights → delegation

A mapping sheet built during discovery converts GroupWise proxy rights to Exchange full-access/send-on-behalf — nothing is guessed.

04

Archive (.arc) collection

Workstation archives collected, converted, and imported — into mailboxes or Online Archives per policy.

05

Directory workstream

eDirectory → Entra ID mapping planned as its own workstream: identities, groups, and routing reconciled before data moves.

06

Staged extraction server

For legacy infrastructure we stand up a dedicated extraction host, so production GroupWise performance is never the constraint.

Delivery methodology

Assess. Plan. Migrate. Cutover.

01

Assess

1-2 days · Source audit, mailbox inventory, domain list. Fixed per-user quote in 24-48 hours.

02

Plan

1-2 days · Microsoft 365 tenant provisioned, domains verified, MFA + security baseline deployed.

03

Migrate

Background · Server-side pre-stage sync runs invisibly. Users keep working on the old system until cutover.

04

Cutover

2-4 hrs off-hours · MX/SPF/DKIM flip, final delta sync, Autodiscover repoint. 30 days hypercare.

Who runs your migration

The engineers on your project.

No outsourced ticket triage. The same three engineers handle source assessment, tenant provisioning, cutover night, and post-migration support on every GroupWise engagement.

01

Sreenivasa Reddy

Founder & Principal Migration Engineer

MCSE Messaging · 25 yrs · 500+ migrations led

Owns the discovery call and migration architecture: source assessment, licensing right-size, and the compliance/security mapping that decides which M365 SKU mix you actually need.

02

Roshan Pujari

Senior Migration Engineer · Source Systems Lead

Microsoft Certified · M365 Administrator

Runs source-side assessment and extraction: credentials, throttling strategy, batch design, and the pre-stage sync that makes cutover weekends boring.

03

Bhargav

Senior Migration Engineer · Mail Flow + Cutover

Microsoft Certified · Exchange + M365 Messaging

MX/SPF/DKIM/DMARC cutover and Autodiscover repoint. Owns the 2-4 hour cutover window plus post-cutover Outlook profile and mobile device resync.

What makes GroupWise→M365 different

The GroupWise-specific realities.

Generic migration guides skip these. They are the operational details that decide whether your cutover weekend is boring — which is the goal.

01

GroupWise shared folders and proxy rights have no 1:1 Exchange equivalent — mapped to shared mailboxes and delegation by documented policy

02

Personal .arc archives on workstations need a collection pass — they’re the GroupWise version of PST sprawl and are always forgotten

03

Old post offices on NetWare-era infrastructure migrate via a staged extraction server we stand up — production is never the bottleneck

FAQ

Frequently Asked Questions

Which GroupWise versions can you migrate?+
GroupWise 7 through 18/23.x. The older the system, the more the staged-extraction approach matters — and we bring it as standard.
How are GroupWise proxy rights handled in Office 365?+
They map to Exchange delegation (full access / send-on-behalf). We produce a per-user mapping sheet during discovery so access is converted by policy, not guessed.
How long does a GroupWise to Office 365 migration take?+
Plan 4-8 weeks for a 100-user system: directory workstream, pilot, staged batches, archive collection, and recurring-item verification. It’s the least rushable migration we run.
What is the downtime during a GroupWise to Microsoft 365 migration?+
Minimal — typically the 2-4 hour MX cutover window, scheduled off-hours (evenings or weekends). Data pre-stages in the background beforehand, and we run both systems in parallel during DNS propagation so no email is lost.
Is there any risk of data loss?+
We verify per-mailbox item counts after migration and keep the source system live until verification completes. Across 500+ migrations and 1.4 million users, we maintain a zero data loss record. Full rollback plans are documented for every cutover.
What does the migration include for $15/user?+
Discovery, tenant setup, background pre-stage sync, delta syncs, cutover night execution, DNS changes (MX/SPF/DKIM/DMARC), Autodiscover repoint, and 30 days of post-migration hypercare. One-time $500 project setup fee. PC setup available at +$25/user.

GroupWise: honored. Retired.

$15/user flat. Pre-staged sync, off-hours cutover, DNS handled, 30-day hypercare. Zero data loss record across 1.4M users.

GET FREE ASSESSMENT →OPEN CALCULATOR →

Microsoft Solutions Partner · BitTitan certified · Fixed-fee · 500+ migrations

VIEW PLANS →
From Our Blog

Cloud Migration Strategies & Step-by-Step Guides

Cloud Services

50 Cloud Migration Statistics for 2026 — Success & Failure Rates

A comprehensive roundup of 50 cloud migration statistics for 2026 covering success rates, failure causes, migration costs, timelines, repatriation trends, and multi-cloud strategy data from Gartner, IDC, Flexera, and Forrester.

17 min readMar 14, 2026
Cloud Services

55 Cloud Computing Statistics for 2026: Spending, Migration & Adoption

55 cloud computing statistics for 2026 covering global spending ($679B), migration timelines, multi-cloud adoption, data center investment, and SMB cloud budgets with sourced data.

16 min readMar 14, 2026
Email Migration

Google Workspace to Microsoft 365 Migration: The Complete 2026 Playbook (Gmail, Drive, and Shared Drives)

A step-by-step migration playbook for moving from Google Workspace to Microsoft 365 covering Gmail to Exchange Online, Drive to OneDrive/SharePoint, identity migration, DNS configuration, and post-migration security — with tool comparisons and timeline estimates.

24 min readMar 13, 2026
Microsoft 365 migration

Case study: Hosting panel-based IMAP to Microsoft 365 Migration for government services in Virginia 

Client overview A government services agency in Virginia, with over 1,000 employees, had been using a hosting panel-based IMAP system for their email and communication needs. As the agency grew, they faced challenges in managing email effectively, ensuring data security, and fostering collaboration across teams. Given the critical nature of their services, the agency needed a […]

7 min readOct 24, 2024