Service 04
SharePoint Storage, Migration & Archiving
TechRam migrates file servers and ageing SharePoint sites to SharePoint in four to ten weeks, restructuring the content on the way through rather than moving the mess. Where a migration sits in that range depends on how much content there is and how much of it is worth keeping. Underneath goes a retention plan, so the bill stops climbing.
- 4–10 weeks
Who it's for
Organisations paying to keep content nobody has opened in years, and holding content they're obliged to dispose of.
What we do
- Storage read by site, library and file age, so the bill is explainable
- Migration into the structure the operation actually needs
- Archive tiers for content you must keep but rarely touch
- Retention and disposal so obligations are met without a manual purge
How it works
Step 1
Analyse what you hold and what it costs
Step 2
Agree what moves, what archives and what goes
Step 3
Migrate in waves with validation at each one
Step 4
Set retention and hand over the reporting
The problem it answers
Storage grows because deleting things is nobody’s job. You’re paying to keep content nobody has opened in five years, at the same tier as the content your operation runs on every day.
The other half of the problem is the content you shouldn’t be holding at all. Retention obligations are easy to state and hard to evidence when the files are spread across a decade of sites.
What changes
Storage is read by site, library and file age, so the bill becomes explainable rather than a single number. What must be kept moves to a tier priced for keeping it. What must not be kept is gone, with the rule written down so it doesn’t have to be done again by hand next year.
Related reading
What is taking up all of our Microsoft 365 storage?
Read it → — What is using your Microsoft 365 storage
Start here for free
Storage Analyser
Deploys in under 30 min
Deploy it in your own tenant → — Storage Analyser
What this does for your AI
Content an assistant should never surface has to be archived rather than left in place. Retention is what makes that a rule instead of a hope.
Common questions
01. How long does a file-server-to-SharePoint migration take?
Four to ten weeks for most. Where a migration lands in that range depends on how much content there is and how much of it is worth keeping. The scope, and the date, are agreed in writing first.
02. Is anything deleted?
Nothing without your written sign-off on the rule, and nothing at all in the first pass. Retention applied to content nobody has classified deletes the wrong things, so classification comes first.
03. Can we migrate one department rather than the whole organisation?
Usually yes, and it's often the better way in. One department that works is a more persuasive business case internally than a plan covering all of them, and it gives us a real cost to scope the rest against.
04. What does a SharePoint migration or archive project cost?
Fixed scope, quoted in writing before work starts, and the number doesn't move because the work turned out harder than we expected. We don't publish a range, because the scope is what sets it and a range without a scope is a guess you would have to unlearn.
05. Do we need to buy anything new for a migration or archive project?
Almost never. We start with what is already in your Microsoft 365 licensing, and we don't resell licences or earn a margin on them. Where something genuinely isn't covered we'll say so before you commit, not after.
06. What happens when the migration is finished?
You own it: the systems, the documentation, and the ability to maintain them without us. Run & Improve exists if you would rather we kept it current, and it's monthly with no lock-in.