Most teams running an ageing core platform have the same data written down somewhere. The year mainstream support ends. It sits in roadmap block, maybe a risk register, treated as a comfortably distant boundary. Plenty of runway. We'll plan the move before it arrives.
It's a sensible-sounding plan. It also quietly misreads the actual constraint.
The date is shared. That's the whole problem.
A support deadline feels like a private matter between you and your vendor. It isn't. Every other organisation on the same platform is looking at the same number. And a large share of them, more than half by most counts, still haven't started moving.
That means the demand for the people who do this work, the experienced architects, the data-migration leads, the testing and cutover specialists, doesn't rise gently. It spikes, all at once, toward the end. The supply of those people does not spike to match. It can't. You don't build a senior migration architect in a quarter.
So the resource you'll need most becomes the resource everyone needs at exactly the same time.
What that does to your project
Three things happen to the organisations that wait, and none of them are abstract.
Rates climb. When demand outruns supply, day rates follow. The final stretch before a deadline is the most expensive moment to buy the scarcest skill.
Quality thins. The best teams get committed to the earliest movers. Wait long enough and you're not choosing between a good partner and a great one. You're choosing from whoever is still free.
Timelines compress. A migration that wants eighteen months doesn't get shorter because you started late. It gets crammed. And the phases that get sacrificed under time pressure, testing, parallel running, user readiness, are the ones whose absence you feel after go-live, not before.
The teams that move early don't get a slightly better version of this. They get a fundamentally different experience: their pick of partner, room to negotiate, and a timeline with slack in it for the things that always go wrong.
This is not the usual "your system is getting old" message
It's worth being precise here, because the market is flooded with vague warnings about legacy systems aging out. This isn't that.
The point isn't that your platform is old. Plenty of old systems run fine. The point is structural and time-bound: a fixed cutoff, set by someone other than you, that forces a large population to act inside the same narrow window, against a supply of help that physically cannot scale to meet them.
That combination is rare. And it has a name most people don't like saying out loud.
The deadline is what dependency looks like with the lights on
For years the cost of running on a single dominant platform was invisible. It sat in the background as a maintenance line item. Stable. Predictable. Easy to renew without reading.
A forced, deadline-driven, whole-market migration is the moment that cost stops being invisible. You don't control the date. You don't control the price of the help. You don't control how many of your peers are competing for the same teams. You are, briefly and expensively, reminded who actually sets the terms.
That's not an argument for panic. It's an argument for seeing the situation clearly while you still have options the late movers won't.
The better question
The question most leadership teams are asking is some version of: can we finish the migration before the cutoff?
It's the wrong question, or at least an incomplete one. The more useful question is two-part:
Where in the queue are we right now, given our starting point and our target date?
And, separately: is migrating to the next version of the same dependency the outcome we actually want, or just the one in front of us?
You don't have to answer the second question today. But you should answer the first one soon, because the answer changes every month you wait. The runway you think you have is the runway minus everyone else's decision to use theirs at the same time as you.
Where to start
You don't have to scope anything today. But you should get an honest read on where you stand, how far you are from the cutoff, how big the move actually is from where you stand, and whether the people to do it are still within reach or already spoken for.
Book a 30-minute review and we'll map it with you. No commitment, just a clear picture of your runway and your options.
