Claris FileMaker
Upgrade From FileMaker 18
FileMaker 18 is years past its support date. Time to move it on before something forces the issue.
FileMaker 18 arrived back in 2019 and Claris has long since stopped supporting it, which means no security patches, no bug fixes, and no help if something goes wrong. It also predates a genuinely significant amount of platform evolution, including major improvements to WebDirect, JSON handling, and the underlying architecture that later versions build on. If you're still running it, you're not just missing features, you're running exposed. From Bicester we upgrade FileMaker 18 solutions for businesses across the UK, carefully checking custom functions, plug-ins and third-party integrations for compatibility before anything gets touched. Twenty-five years of doing this means we know exactly where FileMaker 18 solutions tend to trip up on the way through.
Features and benefits
What you get
Restores security support
Move off an unsupported version and back onto one that actually receives security updates.
Plug-in compatibility checked first
FileMaker 18 solutions often lean on older plug-ins. We verify what still works before migrating.
JSON and scripting improvements
Later versions offer far better native JSON handling, useful if your solution talks to any modern API.
Improved WebDirect performance
WebDirect has moved on considerably since FileMaker 18. Browser-based access is faster and more reliable now.
Layout and theme review
We check that older layout themes and custom styling still render correctly on the newer engine.
Minimal disruption migration
We test thoroughly on a copy before touching your live system, so day-to-day work continues uninterrupted.
Expert insight
Why FileMaker 18 specifically needs attention now
FileMaker 18 is old enough now that Claris support for it has long since ended, and every FileMaker release since has quietly widened the gap between what it can do and what current versions can do. That gap doesn't matter until it suddenly does, usually when a plug-in stops working, a client demands secure web access, or a security review flags the unsupported version as a liability.
The specific risk with FileMaker 18 is compounding age. It's not just this version that's unsupported, it's several versions' worth of accumulated changes you haven't had, in security, in scripting capability, and in how the server handles concurrent users.
Migration from 18 is very manageable when done properly, mainly because the underlying file format has stayed broadly compatible across versions. The real work is in checking custom functions, plug-ins and any scripted workarounds for things that later versions now handle natively.
How we do it
Six steps to implementation
- 01
Compatibility audit
We check every plug-in, custom function and script for compatibility with the target version.
- 02
Test environment build
We create a working copy of your solution on a current FileMaker version for full testing.
- 03
Functional testing
We run through every major workflow to catch anything that behaves differently on the newer engine.
- 04
Layout and UI review
We check appearance and usability across desktop, WebDirect and mobile access points.
- 05
Server upgrade
We upgrade or migrate your hosting environment to a current, supported version of FileMaker Server.
- 06
Go-live and monitoring
We switch users over and monitor closely for the first few days to catch anything unexpected.
25+
Years of FileMaker upgrade work
100+
Solutions migrated
UK-wide
Businesses supported
Questions
Frequently asked
Is FileMaker 18 still safe to use?+
No, it's out of support, which means no security patches from Claris at all. Any vulnerability discovered from now on simply stays unfixed, leaving your business exposed for as long as the system keeps running on it. This matters more the longer a solution has been live, since accumulated risk doesn't announce itself until something goes wrong. Upgrading is the straightforward way to close that gap and get back onto a version Claris actively supports.
Will our custom scripts still work after upgrading?+
Almost always, though we test everything thoroughly first as part of a proper FileMaker upgrade, since some older plug-ins and scripted workarounds do need adjusting for the newer engine. A compatibility audit at the start of the project identifies exactly what needs attention before anything touches your live system. Most FileMaker 18 logic carries across cleanly because the underlying file format has stayed broadly compatible over the years. Anything that doesn't gets fixed on a test copy, not discovered live.
How disruptive is the upgrade process?+
We do the heavy lifting on a test copy, so your live system carries on working normally right up until a planned go-live moment. That means your team keeps operating as usual while migration, testing and fixes happen behind the scenes. Only once we're confident the tested version behaves correctly does the switchover happen, usually scheduled to minimise disruption. It's a deliberately cautious process because a poorly managed migration causes far more disruption than the upgrade itself.
Which version should we upgrade to?+
We'll recommend the most sensible current version based on your solution's needs and your ongoing support requirements, not simply whichever release happens to be newest. Sometimes that means the latest version, and sometimes a slightly earlier supported release is the more pragmatic choice depending on plug-ins or integrations. This decision is part of the compatibility audit we carry out before migration begins. The goal is a stable, supported system, not chasing version numbers for their own sake.
Can you support us remotely if we're not near Oxfordshire?+
Yes, FileMaker upgrades and ongoing support are delivered to clients right across the UK, almost entirely remotely from our base in Bicester. Test environments, screen sharing and remote server access mean location rarely affects how the work gets done. Plenty of clients we've upgraded from FileMaker 18 have never needed an on-site visit. Wherever you're based in the UK, the same careful migration process applies.