Some of your SharePoint
sites are applications.
A publishing template, a form library, a workflow and somebody's JavaScript, assembled years ago to run a real business process by somebody who has since left. They have no owner, nobody has opened their admin centre entry in years, and they will keep working right up until the moment they do not.
£249 + VAT · one tenant · up to 100 SharePoint sites · fixed price
Read-only · nothing in your tenant is changed · access revoked when it's finished
A specialist practice of Innova Group.
- Company IntranetPublishing site · Aug 2026Modernise
- HR FormsTeam site (classic) · Sep 2026Rebuild
- Quality ManualTeam site (classic) · Sep 2026Rebuild
- Project AtlasTeam site (classic) · Nov 2022Retire
- SalesCommunication site · Sep 2026Keep
- OperationsTeam site · Sep 2026Keep
- Legal & CompliancePublishing site · Jul 2026Modernise
- FinanceTeam site · Sep 2026Keep
Microsoft has given this one a date.
Classic SharePoint pages are being retired in phases. Treated as a page problem that is a small job. It is not a page problem — the work is finding out which of your sites are quietly load-bearing, and that is worth doing while there is still time to rebuild rather than react.
1 March 2027
New classic publishing stops
6 months away
1 October 2028
Existing classic pages become read-only
25 months away
There is another reason not to leave it until 2028. Classic pages are not fully represented in the content Microsoft 365 Copilot works from, so legacy SharePoint can become an AI-readiness problem before it becomes an availability problem.
Every site, with one of four answers against it.
A count of old pages is not a plan. A disposal per site is, because the four answers cost wildly different amounts and most estates are mostly the cheap ones.
Retire
CheapestClassic markers, and nothing touched in years. Almost certainly finished work rather than a live system, so migrating it means paying to move something nobody opens. It still carries whatever was shared out of it, which is the reason to close it properly rather than leave it.
Keep
No workModern, owned, in use, and unaffected by the retirement dates. Worth naming explicitly — a review that only lists problems leaves you unable to tell what was checked and found healthy from what was never looked at.
Modernise
DaysClassic pages still being edited. Many are straightforward modernisation jobs. The ones that resist are the ones carrying custom code or business logic, and finding out which is which before you commit to a migration programme is most of the value here.
Rebuild
The real numberA form library, a workflow, and a business process that has quietly depended on them since before the current team arrived. This is an application, not a site. Power Apps and Power Automate cover most of what they were built to do, but somebody has to work out what the form is for first.
What the review looks at.
Classic publishing and classic pages
Read from each site's list templates rather than guessed from names. A library called Pages on a modern site is a document library; the classic publishing one is a different template entirely, and only the template tells them apart.
Form libraries and workflow remnants
The strongest signal that a site is really an application. InfoPath is now out of support, but the processes built on it have not necessarily stopped running.
Ownership and activity
Who owns each site, and when anything in it last changed. A site with no owner and no activity is a different decision from a site with no owner and daily use.
What we cannot see, stated plainly
Whether a site permits custom script is not readable through the interface the assessment uses, so it forms no part of the result and is called out rather than passed over. It matters for the same sites, and you are entitled to know the difference between checked-and-clean and not-checked.
How it runs.
Read-only access, for one scan
An administrator grants read-only access for the assessment. Nothing is installed, nothing in the tenant is changed, and access can be revoked when the review is complete.
Every site classified
Each site comes back as keep, modernise, rebuild or retire, with the markers that put it there — the template it was built on, the libraries it holds, who owns it and when it last changed. Sites we cannot reach are listed as unreachable rather than quietly omitted.
A conversation about the rebuilds
The retire and modernise piles mostly speak for themselves. The rebuild pile is where the money and the risk are, so we go through those with you — what the process is, who depends on it, and whether it is worth rebuilding at all.
A quote against a list, if you want one
Any migration work is quoted afterwards, against the actual list, by whoever you choose. The review is yours either way and it is written so somebody else can act on it.
SharePoint Modernisation Review
£249
+ VAT, per tenant
Up to 100 SharePoint sites. Larger estates quoted before anything runs, never after.
- Read-only assessment of one Microsoft 365 tenant
- Every reachable site classified Keep / Modernise / Rebuild / Retire
- The evidence behind each classification
- Potential business applications identified
- Priority findings, in the order worth acting on
- A findings call to go through the rebuild pile
- No subscription, and nothing to cancel
Find out which ones are load-bearing.
Get every reachable SharePoint site classified as Keep, Modernise, Rebuild or Retire — before Microsoft’s deadlines make the decision for you.