What a bad SharePoint migration actually costs
When people compare migration tools, they usually compare licence prices. That is rarely where the real cost sits.
A migration that appears to finish successfully can still leave weeks of avoidable work behind it. Support tickets begin arriving after users return to work. Someone discovers a document they expected to access no longer opens. An external partner clicks a familiar link and lands on an error page. An IT team spends days investigating issues that were never mentioned in the project plan.
The migration itself may have finished. The project hasn't.
Success isn't measured by a completed copy
Most migration software can tell you that it copied a set of files.
That is not the same as proving the migration was successful.
A completed transfer only confirms that data moved from one location to another. It says nothing about whether users can work as expected afterwards, whether permissions still make sense, whether sharing still functions, or whether every file that mattered actually arrived.
The problems that generate the most support work are rarely technical failures. They are operational ones.
Permissions rarely move cleanly
Permissions are one of the biggest assumptions in any migration.
Traditional file shares often contain years of inherited permissions, nested security groups and exceptions that evolved over time. SharePoint uses a different security model. There is no universal, automatic conversion between the two.
Some migration tools attempt to recreate equivalent permissions. Sometimes the result is close enough. Sometimes it isn't.
The outcome is familiar.
Someone who always had access suddenly doesn't.
Someone who should never have seen a folder now can.
Neither issue appears in a completion report. Both appear when a user starts working.
That is why permission planning should be treated as a design exercise rather than something delegated entirely to software.
External sharing breaks silently
Sharing links often receive even less attention.
Suppliers, customers, auditors and contractors frequently keep bookmarked links to documents they use regularly. Once content moves, those links may no longer work.
Nothing alerts you to the problem during the migration.
Instead, someone outside your organisation discovers it first, usually when they need the document urgently.
From their perspective, the issue is not that SharePoint changed.
The issue is that you shared something that no longer works.
The hidden cost is rework
Most migration overruns are not caused by software.
They are caused by work that nobody expected to perform.
Typical examples include:
- Migrating duplicate, obsolete or abandoned content that should have been removed before the project began.
- Choosing the wrong destination, placing content in SharePoint when it belonged in OneDrive, or the reverse.
- Files being renamed because of invalid characters or excessive path lengths, leaving users unable to find documents under their original names.
- Failed or skipped files being discovered weeks or months later because reporting only showed summary statistics rather than individual outcomes.
None of these issues is particularly large in isolation.
Together they can turn what looked like a finished migration into months of small but expensive clean-up work.
Throttling changes project timelines
Performance problems are not always caused by bandwidth.
Microsoft 365 services enforce rate limits to protect the platform. Every migration tool eventually encounters them.
A tool that simply pushes as hard as possible will eventually be throttled, forcing requests to retry and reducing throughput. Large migrations can slow dramatically, stall completely or require manual intervention before they continue.
A project expected to finish over a weekend can quietly extend into another week.
The important capability is not raw speed.
It is how intelligently a migration reacts when the platform asks it to slow down.
Built to back off before it breaks anything
Liscaragh Migrate eases off automatically as it approaches a platform's rate limits, and you can also set a manual bandwidth cap yourself if a migration needs to run quietly during business hours. See how throttling and bandwidth control actually works.
The costs nobody budgets for
For an MSP, post-migration support consumes profit.
Hours spent resolving issues after handover are hours that were never included in the original quotation.
For an internal IT team, the cost is different.
Confidence is harder to rebuild than data.
The next project attracts additional approvals, additional oversight and additional questions because the previous migration left uncertainty behind.
Neither outcome appears on an invoice.
Both are expensive.
Reducing the risk
Most migration problems are predictable.
The organisations that avoid them tend to do five things consistently.
- They assess the data before moving it, identifying duplicates, naming issues and destination suitability before migration begins.
- They review permissions deliberately instead of assuming software can reproduce years of accumulated access decisions automatically.
- They keep a complete per-file audit trail so every migrated, skipped and failed item can be traced individually.
- They plan for Microsoft 365 throttling by using tools that adapt automatically instead of driving directly into service limits.
- They prepare users for expected changes, particularly around permissions and external sharing, so necessary adjustments become planned activities rather than unexpected support calls.
The real measure of success
A successful migration is not one that copies every file.
It is one that lets users continue working without wondering what changed.
When questions do arise, the answers should already exist.
You should be able to show exactly what moved, what did not, what changed during the process and why.
That level of certainty is what prevents small issues becoming weeks of unnecessary support work.
Because the real cost of a migration is rarely the software that performed it.
It is everything left to discover afterwards.