Site owners have a peculiar kind of pride: «it’s been up since 2019, never crashed, nobody touched it — and it works». It sounds like praise for reliability. In reality it’s more often praise for luck, and luck runs out.
Bitrix is a hardy thing. A site on it can chug along for years without a single update and look fine from the outside. The trouble is that «looks fine» and «is fine» stopped being the same state a long time ago. Under the hood, what developers call tech debt is piling up. And like any debt, it quietly grows until one day the whole bill comes due at once.
What piles up while «everything works»
Three things, and all three are unpleasant.
First — security holes. An old version of the core and its modules is a published list of known vulnerabilities that bots run through automatically. You don’t need to be an interesting target — being vulnerable is enough. A hacked old Bitrix is almost never a virtuoso hacker; it’s a mass scanner that found an unpatched version.
Second — you’re chained to the past. The longer a site goes without updates, the scarier it becomes to do them: the gap between your version and the current one is a chasm, and leaping it turns into a project of its own. Updates don’t pile up linearly — they snowball. Skip a year, and you update in an evening. Skip five, and it’s a full relocation.
Third — the ground thins out around the site. The developers who remember the old editions move on. The modules everything rests on stop being maintained. At some point it turns out a simple fix has no one and nothing to do it — not because it’s hard, but because the whole structure stands on outdated props.
Why «but it works» is a bad argument
Because it describes today, and the risk is about tomorrow. A site that «just works» behaves predictably badly on the day it fails: it’s harder to restore than a fresh one, the backups may not fit the new environment, and whoever built it is long gone.
The analogy is simple. A car that hasn’t had an oil change in five years still drives. Right up until the morning it won’t start — and that’s when it turns out fixing it costs more than servicing it would have.
Update or rebuild — how to decide
There’s no single answer here, there’s a fork.
Updating makes sense when the site’s structure suits you on the whole and you haven’t fallen catastrophically behind. Then it’s planned work: raise the core and modules, check compatibility, close the holes. Unpleasant, but predictable.
Rebuilding — when the site is dated not just inside but outside too: awkward on a phone, slow, and every edit demands heroics. In that case pouring money into reviving the old one is fixing something you’ll have to replace anyway. Sometimes it’s more honest to build it afresh on a current Bitrix and settle the question for years ahead.
The fork isn’t resolved by eye but by inspection: the state of the core, how much custom code there is, what’s going on with performance and the mobile version. After that it’s clear where updating is cheaper and where starting over is.
What to do right now
You don’t have to launch a big project today. But it’s worth at least knowing where you stand: which core version, when the last update was, whether working backups exist and where they restore to. It’s cheap and removes the main uncertainty — you stop depending on luck.
Tech debt doesn’t fine you for existing. It fines you for being discovered at the worst possible moment. Better to find out on a calm one.