SharePoint migration cost is the line in a quote that nobody explains properly, and the one that moves most between providers. Ask three firms to price the same move from an ageing file server into SharePoint Online and the spread will be wider than on almost any other cloud migration you ever run. The reason is rarely dishonesty. Each firm has quietly assumed a different answer to one question: how much of your existing mess are we fixing on the way through?
This guide answers that question in the open. It sets out what a SharePoint migration cost is actually made of, what UK organisations of different sizes really pay in 2026, how long the work takes week by week, and which mistakes turn a tidy project into an expensive one. The figures are the ones a competent provider would recognise, not the optimistic numbers on a landing page.
Two things are worth saying before the money. First, the volume of data you are moving is a poor predictor of effort — the structure and permissions around that data decide the SharePoint migration cost far more than the gigabyte count. Second, the cheapest quote on the table is usually the one that has priced a copy operation rather than a migration, and the difference between those two things is paid for later by your staff.
If you are moving mailboxes, identity and Teams at the same time, that is a wider programme with its own budget — our guide to Microsoft 365 migration planning covers that ground. This article stays with documents: file shares, on-premises SharePoint, and everything that lives in a folder somebody made in 2014.
Table of contents
- What a SharePoint migration cost actually covers
- SharePoint migration cost by business size in the UK
- The hidden extras that inflate a SharePoint migration cost
- What migration tooling adds to the bill
- A realistic SharePoint migration timeline, week by week
- What makes a SharePoint migration timeline slip
- Common mistakes that inflate SharePoint migration cost
- How your starting point changes the SharePoint migration cost
- Questions that expose the real SharePoint migration cost
- Getting your SharePoint migration cost under control
What a SharePoint migration cost actually covers
Before you compare two quotes, you need a shared vocabulary for what is being priced. A SharePoint migration cost is built from six distinct components, and most quotes include some of them while silently omitting others.
Discovery and content assessment
Somebody has to scan what you have: total volume, item counts, folder depth, file types, path lengths, permission structures, how much has not been opened in five years, and which shares belong to which team. This is typically two to five days of work. It is the component providers cut first to look competitive, and it is the one that protects every other line in the SharePoint migration cost.
Information architecture design
Deciding what the destination looks like — how many sites, which libraries, what metadata, which content goes to Teams and which to a communication site, and how sharing will work. This is a design exercise involving your people, not a technical task. It usually consumes three to eight days across the project and is the single best predictor of whether staff will use the result.
Migration tooling and licences
Commercial migration software is charged per gigabyte, per user or per project. On a mid-sized move this is a real line, not a rounding error, and it belongs in the SharePoint migration cost you are shown rather than buried in a provider’s margin.
Data movement and remediation
The transfer itself, plus fixing everything that will not move cleanly: over-long paths, illegal characters, files locked open, versions nobody needs, and the folder that turns out to contain a database. Remediation is almost always larger than the transfer.
Cutover, permissions and hypercare
Applying the final permission model, running the delta pass, redirecting shortcuts and mapped drives, and then one to two weeks of elevated support while people find the things testing never surfaces.
Governance, training and adoption
The line item cut first and regretted most. A SharePoint migration cost that excludes adoption simply moves the money into your service desk for the following year, where it appears as tickets instead of a project fee.
SharePoint migration cost by business size in the UK
Real numbers help more than formulas. The ranges below are professional-services figures for a UK provider in 2026, excluding VAT and excluding Microsoft 365 licences, for a move from a Windows file server into SharePoint Online.
Under twenty-five users
A straightforward migration lands between £1,800 and £5,500. At this size the work is dominated by fixed tasks — discovery, architecture, testing — rather than per-user effort, so the SharePoint migration cost per head looks high while the total stays modest. Most of these complete inside three to four weeks.
Twenty-five to one hundred users
Expect £5,500 to £22,000. This is the most common band for UK SMEs and the one where quotes diverge most sharply, because it is the band in which a provider can either redesign your content or copy it. A realistic per-user SharePoint migration cost here is £120 to £260 once discovery and architecture are properly included.
One hundred to three hundred users
Expect £22,000 to £65,000. At this size you almost certainly have several terabytes, a permissions structure built by people who have left, at least one department running its own shadow system, and a genuine need for staged waves. The SharePoint migration cost is driven far more by those realities than by user count.
Three hundred users and above
Above three hundred users a SharePoint migration cost of £65,000 to £180,000 is normal, and the project starts to look like a programme: a named project manager, a change workstream, formal wave planning, and a pilot group that runs for weeks rather than days.
Why per-gigabyte pricing misleads
Per-gigabyte maths is useful for sanity-checking a quote and useless for producing one. Two terabytes of well-structured project archives is a quieter job than four hundred gigabytes of nested departmental folders with unique permissions at every level. Any SharePoint migration cost built purely on volume is pricing the wrong variable.
Nearly every overspend traces back to a short list of items. None is exotic. All are foreseeable in week one, which is precisely why discovery pays for itself.
File share permissions nobody owns
The biggest single hidden cost. Years of nested security groups, individual user grants and folders shared “just for now” produce a structure that cannot be lifted as-is. Microsoft recommends keeping unique permissions in a library to around five thousand, and a mature file share routinely carries many times that. Somebody has to decide what the model should be, and that is a business decision consuming management time as well as engineering hours.
Path lengths and illegal characters
SharePoint caps the whole decoded path at four hundred characters, and deep folder trees breach that far more often than people expect. Filenames containing characters the platform will not accept have to be found and fixed before they fail mid-transfer. Tooling reports them quickly; deciding who is allowed to rename them takes far longer, and that delay is where the SharePoint migration cost quietly grows.
Versions, duplicates and abandoned content
A share that has never been cleaned typically carries thirty to sixty per cent content nobody has opened in three years. Moving it costs tooling, time and storage. Not moving it costs a decision, which is cheaper but requires somebody with authority to make it.
On-premises SharePoint customisations
Moving from SharePoint Server rather than a file share adds workflows, InfoPath forms, custom web parts and branding, none of which survive the trip. Each needs a decision — rebuild, replace or retire — and rebuilding is invariably the most expensive of the three.
Third-party integrations and mapped drives
Line-of-business applications that write to a UNC path, scan-to-folder devices, and scripts that expect a mapped drive all need reworking. These are usually discovered late, and each one is a small project of its own bolted onto your SharePoint migration cost.
What migration tooling adds to the bill
Tooling choice is one of the few decisions that visibly moves the number, and it is worth understanding before you accept a quote.
Microsoft’s own options
Migration Manager and the SharePoint Migration Tool are included with your subscription and handle straightforward file-share moves competently. For simple content with shallow permissions they are frequently the right answer, and they remove a line from the SharePoint migration cost entirely.
Commercial migration platforms
Tools such as ShareGate, AvePoint and Metalogix charge per gigabyte or per project, commonly £1,500 to £12,000 depending on scale. They earn that fee on complex jobs through better permission mapping, pre-flight reporting, incremental passes and, above all, credible reporting on what actually moved.
When the free tool is a false economy
If your content has unique permissions at depth, large version histories, or an on-premises SharePoint source, the free tooling will consume more consulting hours than the commercial licence would have cost. The tool looks free; the engineer working around it does not.
A realistic SharePoint migration timeline, week by week
Providers quote wildly different durations because they are describing different scopes. Below is what a well-run hundred-user project genuinely looks like. Smaller projects compress this; larger ones add waves rather than new phases.
Weeks one and two: discovery and scanning
Automated scanning of every share, an inventory by size, age and permission complexity, interviews with each department about how they actually work, and a remediation list. You end this phase knowing exactly what you are moving and what you are deliberately leaving behind.
Weeks three and four: architecture and pilot
Site and library design, metadata decisions, the permission model, naming conventions, and a pilot migration for one willing department. The pilot is where estimates become real, and where a provisional SharePoint migration cost either holds or is honestly revised.
Weeks five to eight: bulk migration in waves
Content moves department by department, out of hours, with source shares still live and read-only where practical. Each wave is verified before the next begins. This is the longest phase and the one most affected by Microsoft’s throttling of high-volume transfers.
Weeks nine and ten: delta pass and cutover
A final incremental pass catches everything changed since each wave, permissions are applied, the old shares are set to read-only, and drive mappings and shortcuts are redirected. Cutover itself is usually a single weekend.
Weeks eleven and twelve: hypercare and decommissioning
Elevated support while people find broken links and missing shortcuts, training sessions for teams that need them, then a controlled decommissioning of the file server once nobody has touched it for a fortnight.
What makes a SharePoint migration timeline slip
Three things account for most overruns, and only one of them is technical.
Throttling and available bandwidth
Microsoft limits sustained transfer rates, so several terabytes takes days of wall-clock time regardless of your connection. This is planned around, not solved, and any timeline that ignores it was written optimistically.
Decisions waiting on people
The commonest cause of delay is not the transfer but the answer to “who owns this folder and can we archive it?” A project can lose a fortnight waiting for a department head to make a decision that takes ten minutes.
Content that will not stop changing
Every day between scan and cutover, staff keep working, so the delta grows. Long projects with active shares need more incremental passes, and each pass adds to the SharePoint migration cost in a way the original quote rarely showed.
Common mistakes that inflate SharePoint migration cost
These are the mistakes that separate a project delivered near its estimate from one that doubles. Each is avoidable at the planning stage and expensive afterwards.
Lifting the file server across as-is
The most common and most costly mistake. Copying a twenty-year-old folder tree into SharePoint moves the problem rather than solving it, and you pay a second time when somebody has to restructure it properly in eighteen months. A lift-and-shift always looks like the low SharePoint migration cost until you count that second project.
Treating SharePoint as a bigger shared drive
SharePoint is a document management platform with libraries, metadata, versioning and search. Used as a folder tree it delivers none of that, and staff experience it as a slower H: drive. Good change management matters more here than any technical decision.
Leaving permissions until cutover weekend
Permission design is a business exercise that takes weeks of conversation, not a task for the engineer on the Friday night. Deferring it produces either wide-open libraries or a queue of access requests, and remediating either afterwards costs several times what designing it up front would have.
Skipping the pilot
The pilot is where you find the scanner that writes to a UNC path, the folder with eleven thousand items, and the team whose entire workflow depends on a spreadsheet with links. Skipping it does not remove those problems; it just moves them into cutover weekend at a worse hourly rate.
Migrating absolutely everything
Moving content nobody has opened since 2018 is the easiest saving in the project, and the one most often declined because deciding what to archive requires ownership. Archiving cold content to cheaper storage cuts tooling fees, transfer time and, ultimately, the SharePoint migration cost.
Forgetting search, metadata and retention
If nobody configures managed metadata, retention labels and search refiners, users cannot find anything and quietly revert to email attachments. Retention also carries a compliance dimension — a platform holding personal data needs a defensible data protection position, not just working links.
No plan for the old file server
Leaving the old share writable “just in case” guarantees two sources of truth and a second migration later. Set it read-only at cutover, keep it for an agreed period, then decommission it deliberately. This one costs nothing to get right and a great deal to get wrong.
Underestimating cybersecurity and access review
A migration is the best opportunity you will ever get to remove access that should have lapsed years ago. Skipping that review carries the old estate’s problems into a platform that is far easier to share from, which is a cybersecurity risk rather than a filing inconvenience.
How your starting point changes the SharePoint migration cost
Where you are migrating from changes the work more than how many users you have, and it is the first thing an experienced provider asks about.
From a Windows file server
The most common scenario and the best understood. Effort concentrates on permissions, path remediation and architecture. Tooling is mature, and a SharePoint migration cost here is the most predictable of any starting point.
From SharePoint Server on-premises
More expensive, because customisations, workflows and site templates do not transfer. Expect to add thirty to sixty per cent over the file-server equivalent, most of it spent deciding what to rebuild and what to abandon. The technical migration is the easy half.
From Google Drive or Dropbox
Cheaper on remediation — permissions are simpler and paths are shorter — but heavier on change management, because staff are moving between genuinely different ways of working. Budget the saving straight back into training rather than banking it.
From an existing but disorganised SharePoint Online
A tenant-to-tenant move or an internal restructure is its own discipline. The SharePoint migration cost here is dominated by untangling what exists, and the cheapest version of this project is nearly always the one that starts with ruthless archiving.
Questions that expose the real SharePoint migration cost
If two quotes differ by a factor of three, these questions will usually explain why within ten minutes. Ask every provider the same five, and compare the answers rather than the totals.
What exactly is in scope, in gigabytes and item counts?
A quote without a number for both is a guess. Item count matters more than volume, because a million small files is a slower job than a hundred thousand large ones.
Who designs the information architecture, and how many days is that?
If the answer is “we’ll mirror your existing folders”, you are buying a copy operation. That is a legitimate choice, but it should be priced and labelled as one, not presented as the whole SharePoint migration cost.
How are permissions handled, and who approves the model?
You want to hear about a design workshop, a documented model and a named approver on your side. You do not want to hear that permissions will be “carried across”.
What is explicitly excluded?
Archiving, PST files, on-premises workflow rebuilds, third-party integrations and training are the usual exclusions. Every one of them is a future invoice unless it is named now.
What does hypercare include, and for how long?
Two weeks of responsive support after cutover is a reasonable expectation. A provider whose SharePoint migration cost ends at the moment data lands has priced only the easy part of the project.
Getting your SharePoint migration cost under control
The organisations that land near their estimate do three unglamorous things, and none of them requires a bigger budget.
Budget in three buckets, not one
Separate the one-off project fee, the tooling licence and the ongoing platform management. Blending them produces the comparison errors that make one quote look half the price of another, when it is simply describing less. Ongoing support belongs with your managed IT services arrangement rather than the project.
Spend early to save late
Every pound spent on discovery and architecture removes several from remediation and rework. This is the most reliable relationship in the whole exercise, and the one most often inverted by a procurement process that rewards the lowest headline SharePoint migration cost.
Decide what not to move, and decide it early
Archiving is the only lever that reduces tooling fees, transfer time, remediation effort and post-migration clutter simultaneously. It costs a decision rather than a budget, and it needs somebody senior enough to make it before scanning finishes.
Treat it as a change project with a technical component
The migration succeeds or fails on whether people use the result. Sound IT governance, a named internal owner and a genuine communications plan do more for the return on a SharePoint migration cost than any tooling decision, and they are the parts a provider cannot do for you.
A well-planned move into SharePoint is one of the highest-return projects a mid-sized organisation can run, provided the scope is honest and the mess is dealt with rather than relocated. Before signing anything, read Microsoft’s published SharePoint Online limits so that the constraints shaping your timeline are ones you chose to work with, not ones you discovered in week seven. A realistic SharePoint migration cost, agreed with clear eyes about what is being fixed and what is merely being moved, is the difference between a platform your staff adopt and an expensive copy of the folder tree you already had.
