ChabuduoPractice
FileMaker 18: Standing Still Is Not an Option
Many companies have relied on FileMaker databases for years: customers, orders, appointments, inventory. Once purchased and set up, they keep the data available – with hardly any running costs. For businesses still working with older FileMaker versions, however, this quiet period is coming to an end. That applies above all to version 18 or older.
No security updates since 2021
The vendor, Claris, ended support for FileMaker 18 back in June 2021. Since then, this version has received neither bug fixes nor security updates.
On Windows computers there is a second problem: since Windows 10 stopped receiving regular updates in October 2025, most offices work with Windows 11. Claris only tested FileMaker for Windows 11 from version 19.4.1 onwards. FileMaker 18 runs there without any guarantee from the vendor.
On the Mac, the end already has a date: FileMaker 18 is not built for Apple processors and only runs on current Macs through Apple’s translation layer Rosetta. With macOS 28, expected in autumn 2027, Apple largely removes this technology. FileMaker 18 will then no longer launch on these computers. What the Mac warning “Support Ending for Intel-based Apps” means in practice is answered in our FileMaker 18 FAQ.
Keeping still is no solution
As long as everything works, why not simply carry on: old software, old operating system, no updates? But Art. 32 of the GDPR requires personal data to be protected with measures that reflect the state of the art. An application without security updates that holds customer and employee data hardly meets that standard any more.
Two paths – both legitimate
Upgrade. Moving to a current FileMaker version is the least invasive path: the database and the way people work with it stay as they are. However, a one-off purchase turns into an ongoing commitment. Licences are paid per user, and Claris supports each version for only about two years after release. Anyone who wants to move to new versions needs a subscription, a maintenance contract or has to buy the licences again.
Replace. A new application takes over the data and workflows of the legacy system – and is independent of vendor licences from then on.
Which path is right depends mainly on two factors:
- Number of users
- Complexity of the database
Replacing the system pays off especially where many people work with a manageable database, because every user costs a licence.
For a very complex solution with few users, upgrading can be the smarter choice. We support both paths.
Why replacing pays off
Acting now means you can switch in an orderly way instead of under time pressure.
Lighter workstations. The successor system is a web application. It runs in the browser, and the server does the actual work. The workstation only has to display a web page – on Windows, on the Mac or on a tablet.
No per-user licence costs. The new application is based on widely used open-source technologies. Bringing new staff on board means creating user accounts – not buying new licences.
Security through widespread use. These technologies are maintained by a large developer community. Security vulnerabilities are usually fixed quickly, and updates are released regularly.
Open interfaces. Whether accounting pulls data or another system delivers it: interfaces are built where they are needed – without licence-based volume limits.
Independence. The source code and documentation belong to you. Anyone familiar with the standard technologies used can take over support and maintenance.
No big bang
It starts with an assessment: what does your system do today, and who works with it how? Sometimes it turns out that existing standard software does the job better – in that case we support the switch to it.
If a custom solution makes sense, we solve the most pressing problems first. New features connect to the existing system and deliver value right away. During the migration, the old and new systems run in parallel for a limited transition period. FileMaker remains the leading system until the new database has proven itself in daily use. The legacy data is archived in an open format and remains readable without FileMaker.
Decide now – on a sound basis
Three questions are enough for the first step:
- Which FileMaker version are you running?
- What tasks does the database perform?
- How many people work with it?
The answers make it possible to judge which path is right for you.
Get in touch: info@chabuduo.de
Martin Raasch is the founder and managing director of Chabuduo GmbH in Berlin and has worked in IT projects since 1996. He helps companies replace legacy systems, adopt AI applications and handle data protection. More about Martin · LinkedIn