Somewhere in your office there's a Mac or PC that must never be updated, because it runs "the system." The system was built years ago, possibly by someone who's since retired, emigrated, or vanished into legend. It still works. Everyone's a bit afraid of it.
We meet this system a lot. We've been building and rescuing FileMaker solutions since 1998, which means we've personally witnessed every era of FileMaker that these stranded systems come from. This guide covers why systems get stuck, what staying stuck actually costs, and how to decide between upgrading and rebuilding — including when we'd honestly recommend each.
Why systems get stuck
Nobody plans to run business-critical software on a version from a decade ago. It happens through a series of individually reasonable decisions:
- "It works, don't touch it." True, right up until it isn't.
- The developer left. The person who understood the system moved on, and without them, any change feels like defusing a bomb by guesswork.
- A plugin pinned it. The system depends on a third-party plugin that was never updated for newer FileMaker versions, so the whole system stayed behind with it.
- The licensing change. FileMaker moved from buy-once perpetual licences to subscription over the years, and some businesses dug in on the last version they'd bought outright. Understandable — but that version is now aging out from under them.
- There was never a quiet moment. Upgrades need a bit of downtime and attention, and no quarter ever volunteers.
What staying put actually risks
The costs of an old system are mostly invisible until one of them isn't.
The operating system will move first. This is the one that catches everyone. Old FileMaker versions were built for old versions of macOS and Windows. Each year's OS updates break something else — first cosmetic glitches, then printing, then the application won't launch at all. The forced upgrade then happens on the worst possible day, at emergency pace, instead of as a planned project. Apple's macOS transitions have been particularly brutal to old FileMaker versions; if your system needs that one sacred machine kept off the internet and never updated, you're already in this failure mode.
No security updates. Claris supports recent versions and retires older ones on a published schedule — current details are on the Claris support pages. Out-of-support software gets no security patches. If your server is reachable from the internet (for remote workers, say), running an unsupported version is the kind of thing that makes cyber-insurance questionnaires very awkward.
Unsupported plugins. Old systems often lean on third-party plugins whose vendors have gone. Every OS update is a round of Russian roulette with that dependency.
The knowledge problem compounds. Every year, fewer people remember how the system works, and fewer developers are fluent in the old version's quirks. The rescue gets more expensive the longer it's deferred.
You're locked out of the good stuff. Modern FileMaker talks JSON to REST APIs natively, runs in web browsers via WebDirect, supports server-side automation, and connects to services like Xero and AI APIs. An old version can do none of this, which quietly rules out the integrations that deliver the biggest wins. One of our favourite outcomes came from modernising a construction workforce client's system: a holiday-tracking export that took 10 minutes now runs in about ten seconds.
What an upgrade project involves
An upgrade is not "install the new version and hope." A responsible project looks like this:
- Audit. We examine the system as-built: file format age, plugins, scripts using long-deprecated techniques, and how the pieces connect. Old systems are often a web of separate files with hidden interdependencies. This stage produces the honest answer to "how big is this job?"
- File conversion and compatibility pass. Older files need converting to the current format, and Claris provides tooling and documented paths for this. Conversion is the quick part; the real work is testing what the conversion changed — deprecated functions, layout rendering differences, plugin calls that no longer resolve.
- Replace what didn't survive. Dead plugins get replaced with modern equivalents or native features (a pleasing number of things that once needed plugins are built in now). Fragile old scripting gets rebuilt properly.
- Test against your real work, in parallel. The old system keeps running while the upgraded one is tested against real day-to-day scenarios by the people who'll use it. Nobody cuts over on faith.
- Planned cut-over. A scheduled switch, at a quiet time you choose, with the old system held as a fallback.
Through all of it, your data — usually the most valuable asset your business owns — is treated as the precious cargo it is.
When a rebuild beats an upgrade
Here's the part a less honest article would skip: sometimes upgrading the old system is the wrong move, and we'll tell you when.
Upgrade when the system's design still matches how you work, the structure is sound, and it mainly needs to be brought onto a current, supported version. This is the cheaper path and often the right one.
Rebuild when one or more of these is true:
- The business has changed so much that staff spend their day working around the system rather than in it.
- The original design has been patched by many hands over many years into something nobody can safely modify — upgrading it would mean paying to modernise the mess, then paying again to fix it.
- It's really several stitched-together files pretending to be one system.
- The wishlist (integrations, remote access, dashboards, mobile) amounts to a different system anyway.
A rebuild sounds drastic, but it doesn't happen as a terrifying big bang. We build the new system alongside the old, migrate the data, and switch over module by module — the old system keeps working until the moment it's no longer needed. And because we invoice monthly for completed work and you can stop at any time, you're never betting the farm on a promise; see how we charge.
What to do this week
Don't do nothing — that's the only wrong answer. Find out what version you're on, what it's running on, and whether anything depends on a machine that "must never be updated." Then get an assessment. We offer a free initial consultation, and the outcome is an honest read: upgrade, rebuild, or — occasionally — "you're fine for now, here's what to watch." More on how we approach this at FileMaker development.
Call 0330 113 0958 or email info@flaresoftware.co.uk. The system doesn't have to be scary forever.