GTconsult - Blog #Microsoft

Why Your SharePoint Migration Timeline Is Wrong (And How to Fix It)

Tue, 29 Sep 2026 13:45:11 +0000

"It's just a weekend job" is the most expensive sentence in any migration project. Copying files across is the easy part. What actually eats the calendar is everything attached to those files: permissions, metadata, workflows, and the dependencies nobody mapped before quoting the job. By the time a client realises the estimate was wrong, the project has usually already started, which makes it a much harder conversation to have.

Why timelines slip

A SharePoint migration timeline isn't driven by data volume alone, and treating it like a simple copy job is where most estimates go wrong. It's driven by a handful of factors that rarely show up in an initial scoping conversation:

Permission complexity

Unique permissions on folders and items multiply the validation work far beyond a simple item count. A library with broken inheritance can take longer to migrate than a library ten times its size with clean permissions.

Customisations

Old workflows, InfoPath forms, and third party web parts often can't move as is. They need to be rebuilt or retired, and someone has to decide which before a date can be set.

Content hygiene

Duplicate files, outdated versions, and orphaned sites all need a decision before they're moved, not after. Migrating first and cleaning up later just moves the mess, it doesn't solve it.

User readiness

Training and change management run in parallel with the technical migration, not after it. A technically perfect migration with no user readiness plan still fails on the calendar, because adoption slips the go live date in practice even if not on paper.

Building an estimate that holds

A realistic scope starts with a content and permissions audit before any date gets promised to a client.

That audit surfaces the real variables, things like broken permission inheritance, workflow dependencies, and sites nobody's touched in years, that turn a two week job into a six week one.

The audit doesn't need to be exhaustive to be useful. Even a sample based review of a handful of representative sites and libraries usually surfaces the patterns that will slow the whole project down. What it should never be is skipped in the interest of giving a client a fast answer, because that fast answer is the one that gets renegotiated later, usually at a worse moment for everyone involved.

A good estimate also separates the migration itself from the surrounding work. Content cleanup, workflow rebuilds, and user training are often treated as part of migration when they're scoped, but they behave more like their own mini projects with their own timelines. Naming them separately in the plan makes it much easier to explain, later, why a date moved.

Questions you might have

How long does a SharePoint migration usually take?

It depends entirely on content volume, permission complexity, and customisations. A small, clean tenant can move in days. A large one with legacy workflows and unique permissions can take months.

Can migration timelines be shortened?

Yes, with proper pre-migration content cleanup and a phased cutover. Skipping the audit step to save time almost always costs more time later, once the real complexity surfaces mid-project instead of before it starts.

What's the biggest cause of migration delays?

Undocumented permission structures and legacy customisations that only surface once the migration is already underway, usually because nobody had visibility into them at the scoping stage.

Not sure where your own migration timeline would land? Try GTconsult's free migration cost and timeline calculator to get a realistic estimate based on your content volume and complexity, before you commit to a date.

Access our Migration Cost Calculator

Version History and Migration: What Actually Gets Moved (And What Doesn't)

Tue, 29 Sep 2026 13:45:11 +0000

Every organisation has that one file, 214 versions deep, nobody sure which one is actually final. Daily use lets that ambiguity sit quietly in the background. Migration forces the question out into the open, because someone now has to decide what's worth carrying forward and what's just noise.

What migration tools actually carry over

Most migration tools move version history by default, but not unlimited history. SharePoint Online enforces version limits per library, and very deep version chains can hit those limits or slow the migration significantly. Some tools offer options to cap how many versions transfer, trading history for speed, and that trade off is worth understanding before a migration starts rather than discovering it mid-run.

It also matters what a version means in the destination. A document with 200 minor autosave versions in the source system doesn't necessarily need 200 versions in SharePoint Online. Deciding what counts as a meaningful version, versus incidental noise from autosave, is a conversation worth having with the business before the technical work begins.

Why moving everything isn't a plan

Moving every version of every file sounds like the safe, conservative choice. In practice it usually isn't, for a few reasons:

It multiplies migration time and storage for content nobody will ever open again, which slows down the parts of the project people actually care about.

It buries the genuinely important version, the signed contract, the approved budget, under years of incidental noise, making it harder rather than easier to find what matters.

It delays go live for content that added no value in its old system either. Migrating a mess faithfully still leaves you with a mess, just in a new location.

A better approach

Decide version retention policy before migration starts, not during. Business critical libraries, contracts, financial records, board papers, may genuinely warrant full version history because of audit or legal requirements. General working folders, meeting notes, draft decks, day to day project files, usually don't need more than the last handful of versions to be useful.

This decision works best as a short policy statement agreed with stakeholders early, rather than a judgement call made library by library during the technical migration. It gives the migration team a clear rule to apply consistently, and it gives the business a chance to flag any library that genuinely needs an exception before it's too late to add one.

Questions you may have:

Does SharePoint migration keep all file versions?

Most tools can, but SharePoint Online's version limits and migration performance mean very long version histories are often trimmed or capped by design rather than by accident.

How many versions should I keep?

That depends on the content type. Regulated or contractual documents may need full history, while everyday working files usually don't need more than a handful of recent versions.

Can I recover an old version after migration if it wasn't moved?

Only if it still exists in the source system's backup. Once a migration is complete and the source is decommissioned, unmigrated versions are typically gone for good.

Before you decide what to carry over, run through GTconsult's SharePoint Migration Checklist. It covers content analysis up front and file integrity and version checks once the move is done.

Keep Reading

Check out our other blogs below:

The Copilot Readiness Checklist Nobody wants to do

Four SharePoint Vulnerabilities Are Being Actively Exploited: Here's What to Do

Why a Bigger Bucket Doesn't Help If the Holes Keep Moving

SharePoint 2016 and 2019 Are Now Unsupported. Here's What That Actually Means.

Expert insights: Why and how to migrate to SharePoint SE

Same Pattern, Different Week: Why 1,370 SharePoint Servers Are Still Sitting Exposed

Late Nights, Busy Weekends, & a Lot of Learning

Thu, 15 May 2025 09:21:33 +0000

Midnight’s Certification Journey

There’s a quiet kind of determination that often hides behind the scenes of IT support. It’s the kind that isn’t loud or boastful, but you see it in how someone shows up for the team, how they handle a difficult ticket, and how they quietly push themselves to grow. Midnight, one of our SharePoint Support Engineers, recently passed the Microsoft Certified: Security, Compliance, and Identity Fundamentals exam—and her story is a reminder that professional growth doesn’t always start with a formal plan. Sometimes, it starts with a nudge from leadership, a few too many tabs open, and a personal goal to prove something to yourself.

We sat down with Midnight to unpack her journey in full: the late nights, the surprises, the setbacks—and the sweet, surreal moment when she saw that she’d passed.

When you speak to Midnight about her latest achievement, her quiet confidence and curiosity shine through. As a SharePoint Support Engineer, she's always been interested in the mechanics behind her work—but now, with a new security certification under her belt, she’s got the theory to back it all up.

What exam did she pass?

The SC-900: Microsoft Security, Compliance, and Identity Fundamentals exam is designed to assess your foundational knowledge of security, compliance, and identity (SCI) concepts and related Microsoft solutions.

The SC-900 exam is intended for individuals who are looking to familiarize themselves with the fundamentals of SCI across cloud-based and related Microsoft services.This includes business stakeholders, new or existing IT professionals, and students.A basic understanding of Microsoft Azure and Microsoft 365 is recommended.

Key areas covered in the exam:

Concepts of security, compliance, and identity.
Capabilities of Microsoft Entra.
Capabilities of Microsoft security solutions.
Capabilities of Microsoft compliance solutions.

Why this exam?

The choice wasn’t random.

“It was part of the team's upskilling plan, identified by Brad for the support team.”

The certification was identified as a strategic step for the team, and Midnight leaned into it—recognizing that it wasn’t just about ticking a box, but about staying relevant and useful in a constantly evolving space.

Additionally, the certification wasn’t just a trophy; it was a tool. For Midnight, passing was just part of the mission. The real aim was to deepen her understanding of how security and compliance are embedded into hybrid infrastructure—something she works with every day.

Preparing for the exam

We asked how she prepared, and the answer was as real as it gets:

“A lot of sleepless nights, going through material on the laptop screen.”

No sugar-coating here. Midnight juggled her job and studies like many do—burning the midnight oil, quite literally. But the biggest challenge wasn’t the content itself.

“Sticking to the schedule and resisting the urge to play games.”

There’s something delightfully honest about that. When work and study take up all your hours, the call of an Xbox or a mobile game is loud. But she powered through.

Staying motivated

Every study journey has that moment where you ask, “Why am I doing this again?” For Midnight, the motivation came in an unexpected form:

“The upcoming long weekend and the prospect of rest.”

Sometimes, it's not a deep philosophical answer—it’s knowing that if you just keep going a little longer, there’s rest on the other side. That’s more relatable than most of us would like to admit.

Finding out she passed

When asked how it felt when she saw that “pass” on her screen.

“It felt unreal and surprising.”

“I gained the certification and more experience about the infrastructure being deployed for security and compliance.”

It’s more than just a certificate. For Midnight, it’s validation of her knowledge and a clearer understanding of the behind-the-scenes structure that supports secure business operations. It also deepens her ability to troubleshoot and support clients confidently.

How do you plan to apply what you’ve learned in your current role?

“Like I say, it's now—we're already working with these things. So now I just have a better understanding of why we implement these things.

Whereas, like I say, sometimes it was a case of your—management wants us to implement these things.

There's a very good reason why, but obviously I don't know quite the reason why beforehand.

And now I can actually know that this is—we need to implement this and do this because it can help us with this and this.”

“So yeah, I would say it helps identify why we have certain technologies in place—and rules as well—for the company environment.”

Her answer shows how impactful training can be when it’s tied to real-world application. She’s not just doing the work—she now understands the why behind it.

What’s your next goal after this awesome win? What are you looking to achieve next?

“The next goal I would say being the best auntie to my brother's child because it's only—they're only like 6 weeks away.

But yeah… my next goal would be, I would like to, and I'll ask whether this would be possible, but I would like to get more experience in being able to assist the devs with support tickets that need to be escalated to the devs—not only to help them with their workload and all of that, but because I find it extremely interesting. So I would say that would be my next goal. But that is now not a certification goal. The certification goal—I’ll find out which one is next.”

Midnight’s passion for deepening her knowledge is contagious. Whether it’s supporting her family or her dev team, she’s all-in.

Advice for anybody who wants to pursue this exam

“Yes, I would actually say it's worthwhile to do it because in this day and age, security is everything.
Even like—for a very stupid example, but a very real one that I feel like everyone can resonate with—is you have a security gate or a security alarm in your house, or something, something to secure your physical environment.”

“So with this, it just—it gives you a better understanding of how to secure—basically how to understand the security system within your, obviously, your business environment.”

“So yeah, that's why I would say this is definitely a good one to do. And yeah, I'm actually very glad I did it.”

Midnight keeps it real—and relevant. Whether you’re in IT or just securing your home Wi-Fi, she makes the importance of this exam easy to relate to.

Final Thoughts

Midnight’s achievement is more than a line on her résumé—it’s a stepping stone to what’s next. From becoming the best auntie to diving deeper into technical support, she’s embracing the opportunity to grow, ask questions, and lift others while she learns.

“I'm actually very glad I did it.”

And so are we.

Congratulations, Midnight!