Classic SharePoint pages are changing. Plan the move now

Microsoft is retiring classic publishing sites and classic pages in two phases. From 1 March 2027 new classic publishing sites cannot be created. From 1 October 2028 classic pages in existing tenants become read-only. We find what you have, decide what to keep, and modernise it.

Book a free first call

500+projects delivered
350+clients across 15+ industries
15+years building on Microsoft

The timeline

Two dates to plan around

Source: Microsoft Learn, checked on 29 October 2026. Your own Microsoft 365 Message Center notices take precedence for your tenant.

1 March 2027: Phase 1

Creating new classic publishing sites is disabled for all tenants, and so is turning on classic publishing features. Ten publishing related site templates can no longer be used to create sites.

From 1 March 2027: new tenants

Tenants created on or after this date get the classic page and custom script restrictions from the first day.

1 October 2028: Phase 2

Classic user-created pages in remaining existing tenants become read-only, and the custom script restrictions extend to them. Pages stay viewable but can no longer be edited.

What is affected

Five kinds of classic page become read-only

These are the page types Microsoft lists. They stay viewable after the change, so the risk is not losing content. The risk is not being able to maintain it.

  • Wiki pagesClassic wiki pages in team sites and knowledge bases.
  • Web Part pagesOlder pages assembled from classic web parts.
  • Blog pagesClassic blog sites and posts.
  • Publishing pagesPages in classic publishing portals, including intranet home pages and news pages.
  • Custom ASPX pagesPages built in SharePoint Designer or with third-party tools.

What does not change

This is not a deletion, and not every classic feature

The announcement is narrower than it sounds. We work out where your real exposure is before we recommend anything.

  • Your content is not deletedExisting classic sites and pages are not scheduled for removal by these changes.
  • List and library views stay editableMicrosoft says list views, library views and list form pages are not made read-only at this time.
  • Scripts are still a riskCustom scripts inside those views and forms fall under the custom script restrictions, so they still need review.
  • No full rebuild by defaultSome pages can be transformed in place. Heavily customised portals may need a new modern design.

Readiness check

How exposed are you? Six questions

Answer Yes, No or Not sure. You get an indicative result with an explanation of each answer straight away. Contacting us is optional.

  1. Do any of your sites use classic publishing features?For example a publishing portal or an Enterprise Wiki.
  2. Do people still edit classic wiki, web part or blog pages?Pages in the older look, not the modern page editor.
  3. Do any pages use Script Editor or Content Editor web parts, or custom JavaScript?Often found on intranet home pages and dashboards.
  4. Do you have custom ASPX pages, custom master pages or page layouts, or pages made in SharePoint Designer?
  5. Do you plan to create new classic publishing sites or subsites?This stops being possible from 1 March 2027.
  6. Do you know who owns your important classic pages, and whether people read or edit them?A No here adds to the exposure.
0 of 6 answered

How we work

From inventory to a modern, signed off site

We start with what you have, not with a bulk migration. Pages are grouped by how much they are used and how much they matter, then moved in waves with a test and a sign-off at each step.

  • An inventory of pages, owners, scripts and dependencies
  • Priority by use and business importance, not by age alone
  • Pilot pages first, then batches of similar pages
  • A fallback documented before each wave goes live
Five stagesDrag to move around
Five stages: discover, assess, prioritise, modernise and verify, with owner sign-off at each stage.
Five stages

Discover, assess, prioritise, modernise and verify, with owner sign-off at each stage.

What we do

Six services for classic modernisation

Take one, or the whole path. After a free first call we scope and price an assessment, then agree the rest from its findings.

Inventory and assessment

Find the classic pages, page types, scripts and owners, using Microsoft tools your administrator approves, and agree what each page should become.

Page modernisation

Transform suitable classic pages into modern pages, and rebuild the rest by hand. Every result is checked, because conversion is never perfect.

Scripts and customisations

Replace Script Editor and Content Editor code with supported modern web parts or SharePoint Framework solutions.

Publishing portal redesign

Redesign a classic publishing portal as a modern communication site or a set of hub-connected sites.

Migration to SharePoint Online

Move from SharePoint Server 2013, 2016 or 2019, with clean-up first, so you do not pay to move what nobody uses.

SharePoint migration →

Governance and support

Agree who owns which sites, set standards for new pages, and support your team after go-live.

Why not wait

What waiting costs

Pages you cannot update

Once a page is read-only, a wrong phone number or an expired policy stays on screen until it is rebuilt.

Scripts you cannot change

Custom scripts cannot be added or updated by default after the change, so a fix to one becomes a project.

No new classic sites

Plans that depend on creating a classic publishing site need a modern design from 1 March 2027.

A compressed finish

Inventory, owner decisions, testing and sign-off take time. Starting early leaves room for them before each date.

Classic SharePoint modernisation questions

What exactly is Microsoft changing?

From 1 March 2027, new classic publishing sites cannot be created and classic publishing features cannot be turned on, for all tenants. From 1 October 2028, classic user-created pages in remaining existing tenants become read-only and custom script restrictions extend to those tenants. Tenants created on or after 1 March 2027 get the page and script restrictions from the start.

Will our classic pages be deleted?

No. Microsoft does not say that classic sites or content will be deleted by these changes. Affected pages stay viewable, but they can no longer be edited once the phase that applies to you begins.

Which page types are affected?

Microsoft lists five: wiki pages, web part pages, blog pages, publishing pages and custom ASPX pages, including those made in SharePoint Designer or with third-party tools.

Are list views, libraries and forms affected?

Microsoft says list views, library views and list form pages are not made read-only at this time. Custom scripts inside them are still covered by the script restrictions, and Microsoft may address other classic features separately.

Do we have to rebuild the whole site?

Not necessarily. Some pages can be transformed to modern pages in place. Classic publishing portals and heavily customised pages often need a new modern design, which we confirm in the assessment.

Can pages be converted automatically?

Microsoft and the PnP community provide transformation tools that work well for suitable pages. They do not promise a perfect result for every page, so we test each pattern on sample pages first and check the output.

What happens to Script Editor and custom script code?

After Phase 2, adding or updating custom scripts is disabled by default for remaining existing tenants. We replace script based behaviour with supported modern web parts or SharePoint Framework solutions, or retire it if nobody needs it.

How do you find out what we have?

We build an inventory of classic pages, page types, scripts, owners and activity, using Microsoft tools such as the Microsoft 365 Assessment Tool and Purview audit data where your tenant has it. Your administrator approves the access. Audit data only covers a limited period, so a page with no recorded activity is not proof that nobody uses it.

How long will it take and what will it cost?

It depends on how many pages you have, how customised they are and how many owners must decide. We start with a free first call, then scope and price an assessment. The assessment gives you a plan, a priority order and an indicative effort for the rest.

We are still on SharePoint Server 2016 or 2019. Does this apply to us?

These Microsoft changes are for SharePoint Online. If you are on SharePoint Server, you may be planning a move to SharePoint Online or an upgrade to Subscription Edition, and classic pages are one of the things to deal with during that move.

Does this apply to our Microsoft 365 environment?

Microsoft lists the affected cloud environments in its published guidance. Check your own Message Center notices for the dates and scope that apply to your tenant, especially if you are on a government cloud. We can help you read them.

Who should be involved on our side?

Your Microsoft 365 administrator for access and permissions, the owners of important sites for decisions, and a few business users to test. We run the inventory and the technical work, and keep a log of each decision.

Contact

Start with a free first call