If your FileMaker solution still runs, it's easy to leave it alone. Why fix what isn't broken? Consider this: a nonprofit organization has run on FileMaker for more than 30 years, using it to deliver an educational program that reaches hundreds of thousands of students. Their system, still on FileMaker 17, is approaching the point where it will no longer be compatible with future versions of macOS. Nothing failed.
The system quietly kept doing its job, until an operating system update on the horizon became the forcing function. Now, after three decades of loyalty, they're at a genuine crossroads.
That's the quiet risk. Working and safe are not the same thing. The longer you stay on an outdated version, the wider that gap becomes and the more it costs you to close it later.
FileMaker sits at the center of how your organization operates. Your data, your workflows, your team's daily routines. Keeping it current is both a technical decision and a business one. It directly affects your security, your performance, and what's possible to build next.
What FileMaker version support actually means
Not all versions of FileMaker are equal. Claris supports each major version for two years from release. Any version older than that has reached end of support, sometimes called end of life, which means no more security patches, no updates, and no protection as new threats emerge.
If you're not sure which version you're running, now is a good time to find out.
The risk is real and growing
Cyberthreats aren't slowing down. Small and medium-sized businesses are increasingly at risk.
The latest research shows:
- 81% of SMBs experienced a security or data breach in the past year, 41% involving AI-powered attacks.¹
- 88% of data breaches affecting SMBs involved ransomware.²
- 62.5% of breached SMBs reported losses exceeding $250,000.³
- Confidence in SMB cybersecurity preparedness fell from 56% in 2024 to 38% in 2025.³
Here's what makes an unsupported version especially dangerous: every time a security vulnerability, known as a Common Vulnerability and Exposure (CVE), is discovered and logged, that information becomes public. Claris patches these vulnerabilities in supported versions. Unsupported versions stay exposed, permanently. With AI now actively assisting hackers in scanning for and exploiting known vulnerabilities, the window between discovery and attack has never been shorter.
Beyond security: performance and compatibility risks
Security is the most urgent reason to upgrade, but it's not the only one. The performance and compatibility costs are just as real, and often the ones that sneak up on you first.
Using an outdated version of Claris FileMaker carries risks, especially when the software is no longer supported. That means no more security updates to protect against cyberthreats, compatibility issues, slow processing speeds, and increasing bugs and crashes. You can, and should, avoid these problems by upgrading to the current FileMaker version.
James Ducker, founder and director, Decent Group, a Claris Platinum Partner
Older software degrades in ways that aren't always obvious at first. Processing slows down. Bugs accumulate. Compatibility with newer operating systems, hardware, and third-party tools begins to erode. What ran smoothly a few years ago may be quietly costing you time and productivity today, and those costs compound.
The nonprofit example above illustrates this perfectly. Their system didn't break. But the runway has an end date, and now they face a forced, urgent migration instead of a planned, incremental one. As Rick Kalman, FileMaker Platform Evangelist at Claris, puts it:
The comparison isn't risk versus no risk — it's planned, incremental risk versus eventual forced, urgent risk. Updating on a regular cadence is far easier to manage than being pushed into an emergency migration after something breaks or a vulnerability is exploited.
Think of staying current the way you think about making backups. It's an insurance policy, something you hope you never need, but one you'll be glad you have.
What you gain by upgrading to a supported FileMaker version
Upgrading to FileMaker 2026 isn't just about closing security gaps. It's about building on a platform that's actively improving.
Current versions deliver:
- Enterprise-grade security: Built on Apple's trusted security framework, with encryption, authentication controls, simplified SSL certificate setup, and improved user permissions that give you tighter control over your data.
- AI-ready platform: FileMaker 2026 is built to support agentic development, AI script steps, and large language model integration. The platform is ready when you are. What you connect and build on top of it is up to you.
- Enhanced performance: Faster processing, improved scalability, and infrastructure updates that keep your apps responsive as your organization grows.
- Compatibility: Stay aligned with the latest operating systems and integrations, so your FileMaker solution keeps pace with the rest of your technology stack.
If you're the one building and maintaining FileMaker solutions, staying current means more than staying safe. It means you can take on harder problems, build smarter solutions, and deliver things your clients haven't been able to ask for yet. The gap between what's possible in 2026 and what was possible even two versions ago is significant.
Your next steps
Getting current doesn't have to be a heavy lift. Here's where to start.
- Check your version. Log in to FileMaker and confirm which version of FileMaker you're running. If it's not FileMaker 2026, it's time to plan your path forward.
- Upgrade on your own. Claris publishes step-by-step guidance for upgrading to the current version. Visit the support knowledge base to get started.
- Talk to a Claris rep. If you're not sure where to start, you don't have to figure it out alone. A Claris team member can walk you through your options. Chat with a Claris rep.
The tools to protect your data and build a stronger business are within reach. The first step is making sure you're running software that's working as hard as you are.
Sources:
¹Sourced from BD Emerson cybersecurity article — April 23, 2026.
²Sourced from Verizon Data Breach Investigations Report — December 10, 2025.
³Sourced from IDTheftCenter.org Business Impact Report — December, 2025.