Claris FileMaker
Upgrade From FileMaker 19
FileMaker 19 did some things well. It's still time to move on before support gaps become your problem.
FileMaker 19 was a genuinely solid release, introducing the modern JavaScript-based WebDirect engine and better performance across the board. But it's since been superseded several times over, Claris support has moved on, and solutions still running on it are missing meaningful improvements in performance, security and Claris Studio-adjacent tooling introduced in later releases. We upgrade FileMaker 19 solutions for businesses across the UK from our base in Bicester, checking every custom function and integration before anything moves. After 25 years of these migrations, we know exactly which parts of a FileMaker 19 solution deserve a closer look before going anywhere near the live system.
Features and benefits
What you get
Move onto a supported version
Get back onto a release that receives security patches and vendor support.
Performance gains
Later FileMaker versions include genuine speed improvements, particularly noticeable on larger solutions.
Modern authentication options
Newer versions support improved external authentication methods that FileMaker 19 lacks or handles less securely.
Better OData and Data API support
If you're integrating externally, later versions offer more robust API handling than FileMaker 19.
Script and calculation review
We check your existing logic against the target version to catch any behavioural differences early.
Careful, tested migration
Every migration is tested thoroughly on a copy before your live solution is touched at all.
Expert insight
FileMaker 19 was good, but the world's moved on
FileMaker 19 rebuilt WebDirect on a proper modern web engine, which was a genuine step forward at the time. Businesses that adopted it early got real benefit from that. The trouble is that 'at the time' was a while ago now, and every version since has kept building on that foundation while FileMaker 19 has stood still.
Where this bites hardest is security and integration. External authentication standards move on, API expectations move on, and a version that's fallen out of support simply stops keeping pace, quietly, until something you rely on stops working properly.
The migration path from 19 tends to be smoother than from older versions, precisely because the underlying architecture is closer to current releases. That doesn't mean it's a five-minute job, but it does mean the risk is manageable with proper testing.
How we do it
Six steps to implementation
- 01
Solution review
We go through your FileMaker 19 solution to identify anything that needs particular attention during migration.
- 02
Compatibility testing
We test scripts, calculations and integrations against the target version in a safe copy.
- 03
Authentication and security update
We review and update authentication methods to take advantage of improvements in later versions.
- 04
API and integration checks
We confirm any OData, Data API or third-party integrations behave correctly post-upgrade.
- 05
Server migration
We move your hosting to a current, supported FileMaker Server environment.
- 06
Go-live support
We're on hand at cutover and in the days following, to catch anything that needs adjusting.
25+
Years of FileMaker upgrade work
100+
Solutions migrated
UK-wide
Businesses supported
Questions
Frequently asked
Is FileMaker 19 that much of a risk to keep running?+
It's unsupported, so yes, any new vulnerability discovered from now on has no vendor fix coming from Claris. That risk sits quietly in the background until a security review, a client requirement or an actual incident forces the issue. FileMaker 19 was a solid release in its day, but 'solid at the time' isn't the same as 'safe now'. Upgrading closes that gap and gets you back onto a version receiving proper security patches.
Will WebDirect behave differently after upgrading?+
It may render and perform slightly differently, which is exactly what we test for thoroughly before go-live rather than leaving you to discover it. Later versions have continued refining the WebDirect engine that FileMaker 19 introduced, generally for the better in terms of speed and browser compatibility. We check every major workflow through WebDirect on a test copy first, covering the browsers and devices your team actually uses. Any layout quirks get fixed before your live system ever sees the new version.
Do we need new hardware to upgrade?+
Not usually, though we always check your current server specification meets the requirements of the newer FileMaker Server version before committing to anything. Most businesses running FileMaker 19 on reasonably current hardware can upgrade without any infrastructure changes. Where a server genuinely does need attention, we'll flag it early as part of the assessment rather than as a surprise mid-project. Either way, hosting requirements are confirmed before migration begins, not after.
How long does an upgrade from 19 typically take?+
It varies with solution complexity, but migrating from FileMaker 19 is generally a quicker path than upgrading from older, more heavily patched versions. The closer architecture to current releases means less needs adjusting, which shortens the testing phase considerably. We'll give you a realistic timeframe once we've reviewed your specific solution and its scripts and integrations. Either way, the work happens on a test copy so your live system isn't disrupted while it's underway.
Can you help if we're based outside Oxfordshire?+
Yes, we support FileMaker upgrades for clients across the whole UK, almost entirely remotely from our base in Bicester. Test environments and remote server access mean geography rarely factors into how smoothly an upgrade goes. Most FileMaker 19 migrations we handle involve no site visit at all. Wherever you're based, the same careful, tested approach to upgrading applies.