Capability

SharePoint & Modern Work

Get off the shared drive, run comms through an intranet people open, and finally use the Microsoft 365 licensing you are already paying for.

SharePoint & Modern Work is Kumo's SharePoint consulting practice. We move your documents, communication, and collaboration onto Microsoft 365, structured so Copilot can be trusted with them. Most work starts with a migration off shared drives, Box, or Dropbox; an intranet for org news; adoption of licensing you already own; or a custom SPFx or Copilot build.

12,000+

SharePoint sites migrated

40+ TB

of documents moved into Microsoft 365

40+

intranets launched

150,000+

users working in SharePoint we have migrated or built

What we deliver

SharePoint & Modern Work offerings

Value

Why it matters

Content Copilot can trust

Metadata and permissions built during the migration decide what AI can find and what it must never surface.

Reorganized, not relocated

Content owners, permissions, and metadata applied while every file is already in hand.

Use what you already license

Planner, Forms, shared mailboxes, and Teams are already in your subscription. We get people using them.

An intranet comms can run

Org news and departmental hubs published by marketing and HR, without a ticket to IT.

Approach

How it works

1

Map how you work

Where documents live, who communicates what to whom, and what is licensed but idle.

2

Design the structure

Sites, hubs, Teams, metadata, and permissions, settled before anything moves.

3

Migrate and restructure

Content arrives cleaned, tagged, owned, and permissioned, in one pass.

4

Roll out and extend

Training aimed at the work, then SPFx, embedded Power Apps, and Copilot where the platform stops.

Proof

Work we can point to

Inside the build

What it actually looks like

Screenshots from production work Kumo built and runs. Client branding and customer data are redacted.

Our own intranet: one search box, the eight things people look for most, and news the team actually posts. Names are blurred.
A structured content page: the delivery playbook our team works from, built as SharePoint pages instead of a folder of documents.
An engineering firm's intranet: company news, HR updates, and events in one place, replacing all-staff emails.
The deeper read

The structure Copilot reads from

Copilot answers from what it can access, inheriting SharePoint’s permissions and content quality exactly as they are. Good metadata and a correct permission model produce grounded answers with the right sources. A careless migration produces confident answers drawn from a document superseded three years ago, or a result nobody should have been able to see. Getting it right during the migration costs almost nothing extra.

Ten users, or tens of thousands

We have run a Teams workshop for a thirty-person business and migrations of 4,000 to 5,000 sites at a time for organizations with tens of thousands of users. What scales is the rigor: governance, rollout sequencing, and content ownership. What stays constant is whether people can find what they need, and trust it when they do.

Planning a move? See how a SharePoint migration works.

FAQ

Questions we hear a lot

Is SharePoint going away?

No. SharePoint in Microsoft 365 is the content layer underneath Teams, OneDrive, and Copilot. What ended is on-premises SharePoint Server 2016 and 2019, which reached end of support on July 14, 2026 and no longer receive security updates.

Can you migrate us off shared drives, Box, or Dropbox?

Yes, and it is the most common way this work starts. Network file shares, Box, Dropbox, legacy SharePoint versions, and third-party intranet platforms are all standard sources, and the content is restructured on the way in.

Why does SharePoint structure matter for Copilot?

Copilot inherits SharePoint's permissions and content quality. Good metadata and a correct permission model give grounded answers; a messy migration surfaces stale or sensitive files.

Can SharePoint work as our intranet and communications platform?

It is one of the things it does best. We design the information architecture and publishing paths so content keeps flowing after launch instead of going stale in month three.

How big does our organization need to be for this to make sense?

There is no floor or ceiling we have hit: from a thirty-person Teams workshop to single migrations of 4,000 to 5,000 sites. Scale changes the governance and rollout plan, not whether the platform fits.

Do you help with Teams structure, or only SharePoint?

Both. Every Team creates a SharePoint site underneath it, so we design the Teams and channel structure alongside the site and hub structure.

Start with SharePoint Migration Assessment

An inventory of your content and permissions, a target SharePoint structure, and a migration plan your leadership can decide from.