FileMaker in 2026: modernise it or move on?

FileMaker is not abandonware, and honest advice has to start by saying so. Claris, a subsidiary of Apple, develops it actively and sells it today as Claris FileMaker, on subscription. Whether your FileMaker system is an asset or a liability in 2026 depends less on the vendor and more on which FileMaker you are actually running.

The answer in one paragraph

Two situations share one name. A solution on a current Claris FileMaker subscription, maintained by someone who understands it and serving a small, stable team, is a perfectly defensible way to run a business; if that is you, staying put is reasonable, and we say so again below. An old .fp7 or early .fmp12 file on an ageing FileMaker Server that nobody dares upgrade is another matter entirely: that is legacy software in every way that counts, however healthy its vendor. The decision, when one is needed, is arithmetic rather than ideology: the cost of bringing the system current and paying per user indefinitely, set against the cost of rebuilding it once as a web application you own outright.

Two very different FileMaker situations

FileMaker has been building business databases since the 1980s, and it earned its longevity: it let a capable non-programmer build a genuine multi-user application without writing conventional code. A great many UK businesses still run on exactly that inheritance, which is why one product name covers two situations with almost nothing in common.

The healthy case is current software, currently maintained: a supported Claris FileMaker version, a server that gets updated, and a person, in-house or consultant, who owns it.

The risk case is a file created long ago and left alone. The .fp7 format was superseded by .fmp12 when FileMaker 12 shipped in 2012, so a .fp7 file has been due conversion work for well over a decade, and plenty of early .fmp12 conversions have not been touched meaningfully since. Claris keeps FileMaker current; nobody is keeping yours current, and those are different things.

What an ageing FileMaker system looks like

Four signs recur, and any two together are worth attention.

The server cannot be upgraded casually. Newer FileMaker Server releases want newer operating systems and a proper migration, so the machine stays on an old macOS or Windows version, and the gap widens each year the project is deferred.

The subscription grows with the business. Per-user licensing means the bill rises with every hire even though the system has not changed. That is not a criticism of Claris; it is how subscription software works, and it is a number worth watching as headcount grows.

The person who built it has moved on. FileMaker’s great strength, that one capable person can build the whole thing, becomes its weakness a decade later, because the whole thing lives in one head and the head has retired or changed careers.

Nobody dares edit the scripts. Years of accumulated behaviour, script names that read like archaeology, and a shared understanding that the safest change is no change. A system your own staff are afraid of is legacy, whatever the vendor ships next.

The comparison we run: renting forever or owning once

When a business asks us whether to modernise FileMaker or leave it, the comparison we run is the same shape every time. On one side: the cost of bringing the solution current, plus the per-user subscription for as long as you use it, rising as you hire. On the other: the one-off cost of a bespoke web application, plus modest hosting, owned outright with no per-user meter. We put real quotes on both sides over five and ten years with your actual headcount; we do not repeat Claris list prices here, because pricing depends on plan and count, and second-hand numbers age badly.

Two honest notes. A rebuild is a real project with real risk and a real invoice, while a subscription spreads its cost and includes the vendor’s ongoing development; and for a small, stable team the subscription side often wins. The underlying trade, custom against packaged, is the same one we set out in bespoke CRM vs off-the-shelf.

What a migration actually involves

Three parts, unevenly sized.

The data is the straightforward part. FileMaker exports its tables cleanly to standard formats; the real work is mapping fields and cleaning up what years of free-text entry leave behind.

The schema and scripts are rebuilt, not converted. No tool turns FileMaker layouts and scripts into a web application worth having, so the behaviour is re-specified from how your staff work today, which is also the moment to drop the steps nobody has needed for years.

The old system stays live throughout. Parallel running means FileMaker keeps doing the job while the replacement earns trust beside it, with outputs compared until cutover is boring. The method is written up in migration without downtime.

When staying on FileMaker is the right call

Plainly: if your team is small and stable, your version is current, your investment in the Claris platform is real and somebody competent maintains the solution, stay. Keep the subscription current, keep tested backups, keep the consultant’s number, and rerun the arithmetic when headcount or needs change. We tell businesses in that position to stay put, because the alternative is selling them a project they do not need, and that is not the trade we are in.

What to do next, calmly

If your situation is the ageing one, the first steps are unheroic: write down the file format, the FileMaker and server versions and the current per-user cost; confirm that a backup actually restores; then compare the two paths with real numbers rather than instincts. How we approach that comparison, and what a rebuild involves, is set out on the FileMaker modernisation page. The free Legacy Risk Audit applies whichever way you lean: a 30-minute call and a one-page written risk summary of your specific system, including, where it is true, the finding that you should stay exactly where you are.