Migrate Novell GroupWise content, OpenWorkgroupServer and Netware network shares to SharePoint Online and Microsoft 365: preservation of permissions and metadata, user directory remapping, change management, GroupWise email handling.
Novell (NetWare, GroupWise, OpenWorkgroupServer) was the dominant file and messaging system of the 1990s-2000s in public administrations, some industrial mid-caps, and European players. Today, Novell is in effective end-of-support: Micro Focus (which had bought Novell) sold the assets in 2024, community support is residual, new Microsoft 365 versions progressively abandon Novell connectors. Organizations staying on Novell inherit major security risks (unpatched vulnerabilities), growing maintenance costs, and progressive isolation from modern tools (cloud collaboration, mobile, AI).
For most Novell organizations, Microsoft 365 is the obvious target. SharePoint Online replaces NetWare network storage with modern document management, versioning, search, metadata. OneDrive replaces user personal directories. Exchange Online replaces GroupWise for messaging and calendar. Entra ID (formerly Azure AD) replaces the eDirectory directory. Teams replaces Novell collaborative tools. This consolidation enables cloud, mobile access, and native integration with Microsoft 365 Copilot for AI uses. See our Novell → SharePoint case for 7,000 users.
Three pitfalls structure any Novell migration. Metadata and permission preservation: Novell's eDirectory has a different ACL logic than NTFS and Active Directory — translation requires fine mapping. Historical volume: Novell organizations often have 15-25 years of files, much of it obsolete but hard to classify. Change management: users used to Novell GroupWise (integrated mail/calendar) find Outlook/Teams disorienting initially.
Novell GroupWise, OpenWorkgroupServer (OWG), NTFS network storage on Netware
SharePoint Online, OneDrive, Exchange Online, Microsoft 365 + Entra ID directory
Default choice. Coherent Novell → complete Microsoft 365 migration, native Office, Teams, Copilot integration. Main recommendation.
If the organization is Google-first or seeks a non-Microsoft alternative. Less native Office desktop integration, simpler on web collaboration.
Critical technological sovereignty (regulated public sector), on-premise deployment possible. Greater maintenance effort.
If migrating historical data is too expensive, GroupWise read-only archive + new switch to SharePoint. Transitional approach.
A Novell to SharePoint migration is structured as a sequence of functional batches, with the cadence set at scoping based on volume and complexity (number of users, Novell network storage, GroupWise, eDirectory). The typical cell combines an M365 architect, migration developers (.NET + PowerShell), an Exchange engineer, a SharePoint engineer, an eDirectory → Entra ID expert, a project manager, and change management. Composition and headcount are not fixed upfront: they are determined after the POC and scoping, once the real work has been measured.
Underestimating historical volume. Novell organizations often have 15-25 years of files — including much obsolete, duplicates, orphans. Migrating everything reproduces disorder in SharePoint.
Dedicated Discovery phase: automatic Novell storage analysis (size, modification dates, owners, duplicates), classification by access frequency, identification of content to archive vs migrate vs delete. Typical 30-50% scope reduction. See our Novell SharePoint 7000 users case.
Bad permission mapping eDirectory → Entra ID. Novell ACLs have different logic than Active Directory (inheritance, granular eDirectory rights).
Documented fine mapping: automated extraction of Novell ACLs, translation to Entra ID groups + SharePoint permissions, sample validation before mass migration. Access parity tests on 50-100 representative users before general cutover.
Migrating GroupWise without email plan. GroupWise stores emails, calendars, contacts in an integrated database. Migration to Exchange Online requires specialized tools.
Specialized migration tools (Quest On Demand Migration, Cloudiway, BitTitan) for GroupWise → Exchange Online. Wave migration by department, dual-run with parallel access for 2-4 weeks, upstream Outlook/Teams user training.
Insufficient change management. Novell users used for 15+ years to GroupWise find Outlook/Teams disorienting. Without support, 4-8 week productivity drop.
Change management plan from scoping: training by profile (standard user, super-user, admin), visual documentation and videos, 6-8 weeks of hyper-care post-cutover with reinforced presence, M365 ambassadors in each team.
Complete migration from a legacy Novell environment to Microsoft SharePoint 365 for a North American public organization. 150 administrative units, 7,000 users, 4,620 person-days delivered in co-delivery with a tier-1 prime contractor, nearshore team staffing in one month.
Migration is delivered in functional waves rather than big-bang: the cadence is set at scoping based on the number of users, data volume, and messaging. Cell composition and headcount are determined after the POC and scoping. The Discovery phase typically reduces scope by 30-50% through archiving.
For files: Quest On Demand Migration, Microsoft Mover, or custom PowerShell scripts depending on complexity. For GroupWise → Exchange: Quest On Demand Migration or BitTitan. For eDirectory → Entra ID: custom scripts + Microsoft Identity Manager. All validated by sample before mass migration.
Always by waves. Big-bang migration = unacceptable operational risk on critical organizations. Typical approach: pilot on 1 department (50-200 users), feedback, then successive waves by department or geographic unit. Novell-M365 coexistence for 6-12 months.
Three variables: the number of users and sites, the volume and age of data to transfer (legacy file trees often hold surprises in permissions and duplicates), and the level of permission mapping from Novell to Microsoft 365. Microsoft 365 licenses are always out of scope. Free initial scoping call, 30 minutes to 2 hours.
We frame the trajectory, the budget, and the deliverables in a first thirty-minute conversation. A short POC can be proposed before committing to the full program.
Start this path →