Two firms can quote the same migration and land six figures apart. The cheaper one almost always priced it by the gigabyte, or handed over a fixed bid before anyone looked at the content. That kind of quote is a warning sign, and we will get to why. The short version is that the price of a SharePoint migration is set by how much your data has to be restructured, and moving the files is the cheap part.
How much does a SharePoint migration cost?
A SharePoint migration is priced by the work it takes to restructure your content, not by the volume of data you move. Two organizations with identical data sizes can pay very different amounts, because one arrives with a clean, well-organized source and the other has fifteen years of nested folders that need to be rebuilt into a real architecture. Any quote worth trusting starts with discovery rather than a per-gigabyte rate.
We are not going to print a single dollar figure here, because a one-size number would be dishonest. The cost scales with the condition of your source, the number of systems you are moving from, how tangled the permissions are, and what compliance demands you carry. If you want a planning estimate tailored to your size and complexity, model it with the Migration ROI Calculator, then refine it with a real scoping conversation. What follows is where the money actually goes, so you can read any quote you receive with clear eyes.
Moving the files is the cheap part
In most migrations, copying content is not where the budget goes. Modern migration tools move files, libraries, and whole sites reliably and at scale, and that part is close to a solved problem. The expensive, skilled work is taking a deep, nested folder structure and rebuilding it as a flat architecture with content types and metadata, so people can find what they need on the other side.
This is the single most common reason a real quote looks higher than a client expected. They budgeted for the move, which is straightforward, and the move was never the hard part. We made the longer version of this case in the SharePoint migration myth, and the reason the restructuring matters so much comes down to why folders fall short and metadata holds up. Planning that rebuild is its own discipline, which is why we treat mapping legacy folders to metadata as a design step, not an afterthought.
What actually drives the cost of a SharePoint migration
The price moves with a handful of factors, and most of them trace back to the state of your current environment rather than its raw size. In rough order of how much they swing the number:
The condition of your source data. Deep nesting, duplicate files, and orphaned content all add restructuring hours, and a messy source is the biggest cost multiplier there is.
The number and type of sources. File shares, on-premises SharePoint, Box or Google Drive, and tenant-to-tenant moves each carry different work, and consolidating several at once compounds it.
Permissions. Untangling and remediating years of folder-level permissions is often the slowest stretch of the whole project.
The information architecture and metadata design. This is the real engineering, and it is what turns storage into a usable system. It is also where a firm earns its fee, which is why we treat architecture and governance as the core of the work.
Content types, templates, and document structure.
Compliance and retention requirements, which add design and validation effort, especially in regulated environments. The records management and retention layer has to be built in, not bolted on later.
Integrations with Teams, Power Platform, and line-of-business systems.
Change management, so people actually use the result instead of drifting back to the old drive.
The fastest way to see which of these apply to you is a structured look at your environment, which is the whole point of a migration readiness assessment.
Why per-GB and fixed-bid migration quotes are a red flag
If a vendor prices your migration by the gigabyte or terabyte, or commits to a fixed bid before discovery, be concerned. dataBridge will not price a migration that way, and you should treat that kind of quote as a signal about what you are actually buying. A per-volume number almost always describes a lift and shift, where your folders move across exactly as they are and you pay to relocate the same mess into a more expensive home.
The math is seductive and the outcome is poor. A per-GB quote prices the part that is easy, the move, and ignores the part that is hard, the restructuring. It also transfers the risk of bad scoping onto you, because the moment the work turns out to be more than a copy job, you are the one holding the gap. This is the easiest and most common way to lose adoption and watch employees stop trusting SharePoint, because nothing got better, it just moved. We see the wreckage often enough that we wrote up the mistakes we find after a migration, and they connect straight to why employees stop trusting SharePoint and why adoption fails.
How dataBridge prices and runs a migration
We scope migrations to the actual work, after a discovery phase, on a time-and-materials basis, because the restructuring effort is the variable and a fair price has to reflect it. A fixed number pulled before anyone has seen your content is either padded to cover the unknown or set up to cut corners when reality hits. Neither serves you.
The sequence is consistent. We start with discovery to understand the content and the real failure points, design the architecture and governance the new environment needs, run the migration as a restructuring rather than a copy, and support adoption so the result sticks. If you want the full method before you talk to anyone, it is laid out in the complete guide to SharePoint Online migrations. When you are ready to put a number to your own project, the Migration ROI Calculator is the place to start.
What the higher number actually buys
The migration that costs more upfront is usually the one that pays back. You land in a flat, governed environment where search returns the right file, the current version is obvious, and the platform is ready for Copilot instead of feeding it years of folder sprawl. That readiness is not a side benefit, it is increasingly the reason organizations migrate at all, and it depends entirely on the structure you build during the move. It is the same structure that makes SharePoint a real document management system and a trustworthy source for Copilot readiness.
The lift and shift saves money on the invoice and spends it later, in lost productivity and a system nobody trusts. The restructured migration costs more on paper and returns it in a workspace people actually use.
Frequently asked questions
How much does a SharePoint migration cost per user or per GB?
Per-user and per-GB pricing is the wrong model for a migration, because cost tracks the restructuring work, not the volume of data. A reputable firm scopes the project after discovery. If you are handed a per-GB number, you are almost certainly being quoted a lift and shift.
Why is one vendor’s migration quote so much higher than another’s?
Usually because you are comparing two different scopes. The cheaper quote often covers moving the files and little else, while the higher one includes rebuilding the architecture, applying metadata, and remediating permissions. You are not looking at the same project priced two ways.
Is a lift-and-shift migration ever the right choice?
Rarely, and only when the source is already well-structured with clean permissions and a sensible organization. For most organizations coming off legacy file shares, a straight lift and shift carries the existing problems into SharePoint and undermines adoption from day one.
How long does a SharePoint migration take, and does that change the cost?
Timeline and cost move together, because both are driven by how much restructuring the content needs. A clean source migrates quickly. A tangled one takes longer, because the architecture has to be rebuilt, and that effort is where the hours and the dollars go.
Can a calculator estimate my SharePoint migration cost?
A calculator gives you a useful starting estimate based on your size and complexity, which is why we built the Migration ROI Calculator. Treat the output as a planning range, then sharpen it with a discovery conversation about the actual state of your content.
If you want a real number for your environment instead of a per-GB guess, model your starting range with the Migration ROI Calculator, then talk to us about a discovery so the estimate reflects your content, not an average.
Reviewed By
