Intranet migrations go wrong in a predictable way. The content moves, the permissions do not come with it, nobody decided what to leave behind, and six months later you have the same mess you had before in a newer interface. The tooling is rarely the hard part. The decisions about what moves, who owns it and what gets deleted are, and those are decisions no supplier can make for you.
This guide covers how to scope a migration before you approach anyone, what actually drives the cost, the questions that separate suppliers, and what the UK market publishes about this work.
Scope the migration before you talk to suppliers
Four pieces of work will change your quotes more than your choice of supplier will.
Count what you have, then count what is used
Inventory the sites, libraries and volume, then find out how much of it has been opened in the last two years. On most migrations the answer is well under half. That number is the single biggest lever you have on cost and duration, and it is the one most organisations never look at before going out to market.
Decide what is not moving
Every migration has content that should be archived or deleted, and the only moment anyone will engage with that decision is when a move forces it. Skip this and you pay to migrate content you will never open, then pay again to store it. Agreeing an archive and deletion policy up front is the cheapest decision available to you.
Treat permissions as a redesign, not a transfer
Permissions that grew organically over a decade will not survive contact with a new structure, and inheriting them wholesale is how organisations end up with a tenant that Copilot cannot be safely pointed at. A migration is the practical moment to redesign the model, and that work should appear in the plan explicitly rather than being assumed.
Budget for the tail
A migration finishes when the last team stops using the old system, not when the data lands. That means communications, training and a period where both systems exist. It is routinely left out of plans and it is routinely where the overrun comes from.
Lift and shift or restructure?
| Lift and shift | Restructure on the way across | |
|---|---|---|
| Cost and speed | Lower and faster | Higher, more discovery up front |
| What you end up with | Your current structure on a supported platform | A structure designed around how people look for things |
| Findability | Unchanged, including the parts people complain about | Addressed directly |
| Copilot readiness | Inherits existing permissions and content sprawl | Permissions and metadata sorted as part of the work |
| Makes sense when | You need off an unsupported platform quickly | The reason for moving is that nobody can find anything |
If your main driver is getting off an unsupported or discontinued platform before a deadline, lift and shift has a legitimate case. If the driver is that people cannot find anything, it does not, because you will be paying to reproduce the problem.
What to ask a migration supplier
Which source platforms have you moved from? Moving from file shares is a different job from moving off Confluence, Box, Dropbox, Google Workspace or a discontinued intranet product. Defined paths exist in the UK market for all of those, but not every supplier covers all of them, and the ones involving a retired product are about reproducing functionality rather than moving files.
How do you handle permissions? Expect redesign, not transfer. If the answer is that permissions come across automatically, ask what happens to the ones that should never have existed.
What is included and what is extra? Content restructuring, metadata design, training, communications and the dual-running period are the five things most often scoped out. Ask about each by name.
What does the price depend on? Fixed-price models exist in this market, usually scoped against a site count. They give useful cost certainty but they are only fixed against the scope you agreed, so ask what happens when discovery finds more content than expected.
What happens after go-live? Ask whether support is a published service with a scope and a price. Published support pricing exists in the UK market and tends to start around £600 a month for incident cover.
What the UK market publishes
From a review of UK SharePoint migration providers' published material in November 2026:
Project pricing is rarely published. ThinkShare publishes a SharePoint migration range of £20,000 to £50,000, which is unusual. Most suppliers quote on request. Where numbers do appear elsewhere they are more often for ongoing support than for the migration itself.
Published timescales cluster at four to twelve weeks for a SharePoint intranet project. Tighter scopes go faster: a charity whose previous intranet product was discontinued had a replacement out-of-the-box SharePoint intranet live within a month.
Source platform coverage varies widely and is often not itemised on supplier websites. Ask rather than assuming, particularly for Confluence, Box, Dropbox, Google Workspace and tenant-to-tenant moves.
Some suppliers frame migration as a records exercise, bundling retention schedules and Microsoft Purview configuration with the move. For organisations with regulatory retention obligations that framing fits the problem better than a pure content move.
Common mistakes
Going to market before the content audit. You will get quotes based on guesses, and they will all be wrong in the same direction.
Treating the migration as an IT project. The decisions that matter are about ownership and retention, which are business decisions, and they need business people in the room from the start.
Leaving the deletion rule until after the move. Once content has landed in the new system, the political window for deleting it has closed.
Assuming the old system can be switched off on the launch date. It cannot, and planning as though it can is how dual running becomes an unbudgeted surprise.
How ThinkShare approaches it
We restructure content as it moves rather than copying the existing shape into SharePoint Online, with the information architecture, metadata and permissions model agreed before anything is moved. We publish our migration pricing at £20,000 to £50,000 so the budgeting conversation can happen early.
We have moved organisations off LiveTiles, Valo, older SharePoint versions and file shares, including rebuilding one charity's intranet on out-of-the-box SharePoint within a month after their previous product was retired. Where a product-based destination suits better than a bespoke build, we offer Omnia and Involv as well as SharePoint out of the box.
If you want to talk through what is involved in moving your intranet, book a call with our team.
Frequently asked questions
How much does a SharePoint intranet migration cost in the UK?
ThinkShare publishes £20,000 to £50,000. Most UK suppliers quote on request, and fixed-price models scoped on site count are also available in this market. Add ongoing support afterwards, which where published tends to start around £600 a month.
How long does an intranet migration take?
Four to twelve weeks is the range UK providers typically publish for a SharePoint intranet project. A month is achievable for a tightly scoped out-of-the-box rebuild. Duration depends far more on how much content you are willing to leave behind than on the technology.
Do we need to migrate everything?
Almost certainly not. Most organisations find a large share of their content has not been opened in years. Agreeing an archive and deletion policy before the move is the cheapest decision available to you and the one that most reduces cost.
What happens to permissions during a migration?
They do not transfer cleanly and should not be expected to. A migration is the practical moment to redesign the permissions model, and this matters more than it used to because Microsoft 365 Copilot surfaces whatever a user technically has access to.
Should we lift and shift or restructure?
Lift and shift is faster and cheaper and recreates your existing structure, including the parts people complain about. Restructuring costs more up front and is the only approach that fixes findability. If you are racing off an unsupported platform, lift and shift has a case. If nobody can find anything, it does not.
What should we do before approaching suppliers?
Audit your content, find out how much of it is actually used, agree what will not be moving, and decide who owns the intranet after launch. Those four pieces of work will change your quotes more than your choice of supplier will.