Rencore
Why ShareGate Apricot's repositioning leaves a governance gap
Workleap's ShareGate Apricot continues to position as the friendly, project-shaped tool for M365 cleanup and migration. That works for a defined cleanup engagement. It is a poor fit for the ongoing governance many teams actually need.
ShareGate Apricot is Workleap's AI-assisted Microsoft 365 management tool that pairs the classic ShareGate migration and cleanup heritage with newer assistance features for tenant inventory, permissions review, and Copilot readiness. Apricot is well-positioned for time-bound cleanup engagements but, by design, does not provide the continuous policy enforcement, multi-service inventory, and lifecycle automation that organizations running governance as a programme rather than a project actually need.
ShareGate has spent the past two years repositioning around Apricot, the AI-assisted experience layered on top of its longstanding migration and management tools. Workleap, the parent company, has been clear about the direction: Apricot is the friendly assistant that helps M365 admins find what to clean up, what to migrate, and what to label. The marketing is good and the product is genuinely useful for the workflows it targets.
For organizations choosing a long-term M365 governance posture in 2026, the question is whether Apricot covers what governance now means. In our analysis, it does not. Naming the gap is the point of this piece.
What Apricot does well
Apricot is strong at three things ShareGate has always been strong at.
Migration and consolidation. Tenant-to-tenant moves, on-prem to cloud, and the dozens of edge cases that come with both. ShareGate’s heritage is here, and the tooling is mature.
Time-bound cleanup. A new admin lands in a tenant with years of orphaned sites, inactive Teams, and inherited permission mess. Apricot makes the assisted cleanup workflow approachable. The conversational interface lowers the activation cost for a one-time tidy.
Approachable UX for non-specialists. The interface is friendlier than most governance tools. For mid-market admins without a dedicated governance function, that matters.
If your active job-to-be-done is “clean up the tenant I just inherited” or “consolidate two tenants after an acquisition,” Apricot is a reasonable choice.
Where the gap opens
The structural difference between cleanup tooling and a governance platform is not features, it is operating model. Three gaps appear when the work changes from project to programme.
No continuous policy enforcement across all services. Cleanup tooling helps you find problems. A governance platform stops problems re-accumulating. The 250+ policy templates Rencore ships run continuously across SharePoint, Teams, OneDrive, Exchange, Power Platform, Copilot, and 15+ AI platforms. Apricot’s strength is identifying issues in a session, not enforcing rules across a tenant over time.
Limited coverage outside SharePoint, Teams, and OneDrive. Power Platform, Copilot, Copilot Studio agents, and third-party AI tools are now part of the M365 surface that needs governance. Apricot’s coverage of these surfaces is narrower than a governance platform built for them from the start.
No lifecycle automation engine. Cleanup is a moment in time. Lifecycle is a continuous process: provision with standards, monitor against drift, archive when inactive, decommission when ownership lapses. That requires an automation engine running on policy, not an assistant running on prompts.
No multi-tenant aggregation for MSPs. ShareGate is widely used by MSPs for migration. Operating governance across a fleet of client tenants from a single pane, with consolidated inventory and cross-tenant policy posture, is a different architecture.
When to choose what
The choice between Apricot and a governance platform is not a feature shootout, it is a question about what you are buying.
Choose Apricot when the job is migration, consolidation, or a defined cleanup with a budget, a start date, and an end date. The conversational UX makes the work palatable for teams who do not run M365 day to day.
Choose a governance platform when the job is continuous: ongoing policy enforcement, audit-ready evidence for DORA, NIS2, or the EU AI Act, lifecycle management across services Apricot does not cover, and a multi-tenant view for an MSP serving multiple clients. These are different operating models with different shapes of value.
Both can coexist. We see organizations use Apricot or its predecessors for a migration project and then bring in a governance platform once the project is done. The tools point at different problems. Confusing them is the expensive mistake.
See how Rencore approaches continuous governance across the M365 surface, or compare governance approaches.
