Migrating FileMaker to a modern web app

Your FileMaker solution may have been running faithfully for fifteen years, handling order management, customer records, project planning and stock lists. Yet there are more and more signs that its future-proofing is eroding: in 2024 Claris (Apple) closed new Server licences to customers who did not already have one, developers with FileMaker experience are becoming rarer, and mobile access via WebDirect is hitting performance limits. We guide Dutch SMEs through a calm, phased migration to a modern web application, keeping your business logic and avoiding big-bang risk.

FileMaker Pro / Claris Pro DDR export JDBC/ODBC data migration Schema mapping Parallel run Custom web app
Discuss your migration View the reasons
FileMaker Pro migratie Nieuwe webapp REST API live Mobiel PWA Live

The point at which FileMaker stops being a future-proof choice

For years, FileMaker (which continues under the name Claris Pro since 2019) has held a unique position: quickly building something for a single team without setting up a full software department. For many Dutch SMEs, a FileMaker solution is still running behind the scenes, sometimes since FileMaker Pro 7 or 11. That has worked perfectly well. The question is not whether FileMaker was ever good, but whether it is still the right foundation for the next ten years.

In 2024, Claris announced that new organisations that were not previously customers can no longer buy Claris Server. Existing customers can renew, but the inflow of new users has effectively stopped. At the same time, the platform has been renamed Claris Pro and Claris Studio, with a stronger link to the Apple ecosystem. For your current solution this is not an acute problem yet, but it does indicate a direction: the pool of developers is shrinking, third-party tools are disappearing, and the roadmap is getting narrower rather than broader.

On top of that, the expectations of your employees and customers have fundamentally changed in recent years. Access through a browser on any device, real-time collaboration, mobile input in the field, integrations with accounting, e-commerce and logistics platforms: these are the demands on the table at every SME today. FileMaker WebDirect and the FileMaker Data API can do a lot, but they hit limits once the number of concurrent users rises or the UI becomes more complex than a set of layouts allows.

We are not an anti-FileMaker club. In some situations, such as a small departmental tool that has run stably for years, migrating is overkill. But if you recognise yourself in two or more of the six reasons below, it makes sense to plan the migration now, rather than when the platform forces you to jump.

Six practical reasons to replace your FileMaker solution

Not all the pain starts at the same time. Some organisations notice the cost increase first, while others get stuck finding a new developer. We see the six patterns below most often in conversations about a migration path.

📈

Rising licence costs per user

Claris uses per-user licensing that scales with your team. An organisation growing from fifteen to forty employees sees its annual FileMaker bill rise in proportion, whereas a custom web app typically has no additional licence costs per user. For a growing business, that is a structural cost difference that repeats every year.

🧑‍💻

A shortage of FileMaker developers

The pool of FileMaker developers in the Netherlands is small and ageing. Finding a good FileMaker developer for maintenance, extensions or a script engine issue takes ever longer and costs more. A web app built on mainstream stacks (TypeScript, PostgreSQL, REST/GraphQL) has a far broader developer base, including for maintenance five or ten years from now.

📱

The mobile experience falls short

FileMaker Go on iPad works for structured data entry, but Web Direct on smartphones feels slow and dated to anyone used to modern progressive web apps. For field engineers, sales teams on the road or customers ordering from their browser, the UX gap is now large enough to matter commercially.

🔌

Integrating with external systems gets complicated

The FileMaker Data API is functional, but building robust two-way integrations with, for example, Exact Online, Magento, Shopify, Microsoft Dynamics or a marketplace API takes a lot of work in script steps and cURL options. A web app with its own backend talks to these external APIs far more directly, with better error handling and logging.

⚡

Performance with larger datasets

FileMaker works well up to a few hundred thousand records, but with millions of records, complex relationships and heavy calculation fields, we see search and sort speeds decline. A PostgreSQL or MySQL backend with the right indexes can handle datasets that would make a FileMaker system unusably slow.

☁️

On-premises deployment no longer fits

Many FileMaker environments still run on their own server or a hosted FileMaker Server. For remote working, ISO 27001 requirements or customers who expect SaaS access, a cloud-native web app (containers, automatic backups, EU hosting) is a more logical foundation. Migrating is therefore an infrastructure modernisation, not just a software replacement.

How we safely migrate a FileMaker solution to a web app

A FileMaker migration is not an export-import. Your solution contains years of accumulated business logic, hidden in scripts, calculations, layouts and custom functions. We don't build a lift-and-shift copy; we reconstruct your solution as a modern web app, keeping what works and rethinking what had become too cumbersome in FileMaker.

The first step is always a schema extraction. Using FileMaker's Database Design Report (DDR), we export your complete table structure, field types, relationships, layouts, scripts, value lists and accounts to XML. For us, that XML is readable documentation of your solution, and the basis for mapping to a relational database schema (PostgreSQL or MySQL). We translate calculation fields into database functions or backend logic, and container fields into object storage with file references in the database.

For the data export, we use three techniques depending on volume: ExportFieldContents for binary files in container fields, JDBC/ODBC for bulk exports to staging tables, and the FileMaker Data API for incremental synchronisation during the parallel run. This lets us validate, table by table, that the data in the new web app is identical to the source before the old solution is switched off.

The business logic in your FM scripts is usually the most time-consuming part. We analyse every script (mature solutions often have hundreds) and group them by functional purpose: validation rules, workflow triggers, reporting and bulk operations. We rebuild the relevant rules as services in the new web app's backend, with unit tests where it's critical. Obsolete scripts (for example, for discontinued processes) don't make the move, which makes it a natural moment for a clean-up.

Finally, we run both systems in parallel for at least a few weeks: the FileMaker solution and the new web app are both live, with daily data synchronisation. Your team first works in both, or tests in the new environment alongside the old one, compares reports and flags discrepancies. FileMaker is only switched off once all stakeholders are confident in the new solution. No big-bang go-live, and no dependence on a single migration weekend that simply has to succeed.

The four phases of a FileMaker migration

Our approach is iterative and transparent. Each phase delivers something you can test, so you can adjust course or revisit the scope at any point, without being locked into an end result fixed in advance.

DDR analysis and scope

We export the Database Design Report from your FileMaker solution and catalogue all tables, relationships, layouts, scripts and custom functions. Based on that, we define the migration scope together: what moves across one-to-one, what gets simplified, and what is dropped.

Schema mapping and POC

We map your FileMaker schema to a relational database (usually PostgreSQL) and build a proof of concept of the most critical module. You see the new UX and the performance on real data, and can validate that the approach works before we start the full migration.

Build and parallel run

We build the full web app module by module. During the build phase, a data pipeline from FileMaker to the new environment is already running, so we can test against production data in every iteration. Your team keeps working in FileMaker while the web app grows alongside the old solution.

Cutover and decommissioning

Once all modules have been delivered and tested, we cut over. From then on your team works in the web app, while FileMaker remains available read-only for a few more weeks as a reference. After that, the Claris Server is phased out and the licence costs disappear.

Technologies we use for FileMaker migrations

The choice of technology depends on your situation: the number of concurrent users, the volume of data, your requirements for mobile use and your existing integrations. We work with proven open-source stacks that will still be maintainable in ten years, and we keep complexity as low as possible: if something can be built simply, we build it simply.

For data extraction from FileMaker we use the official DDR export (XML), JDBC and ODBC connectors, ExportFieldContents for container files, and the FileMaker Data API for incremental sync during the parallel run. On the web app side, we opt for TypeScript frameworks (React, Astro, Next.js or Remix) with a Node.js or Python backend, connected to PostgreSQL or MySQL. We prefer hosting in EU data centres for GDPR compliance.

FileMaker DDR (XML) JDBC / ODBC FileMaker Data API PostgreSQL MySQL TypeScript React Node.js Python REST / GraphQL Docker PWA

Real-world use cases we have modernised from FileMaker

FileMaker turns up in very different corners of a business. The three patterns below are the ones we see most often in SMEs looking to migrate.

Order management and quoting tools

A wholesaler that has managed orders, quotes and delivery notes in FileMaker for years is hitting a wall with its webshop and accounting integrations. We rebuild the existing workflow, from incoming order through picking to invoice, as a web app with a REST integration to the ERP. Field staff now work through a PWA on phone and tablet, and the warehouse manager sees stock levels in real time.

Customer administration and CRM

A service provider has a FileMaker CRM with customers, contact moments, contracts and invoices, built up over twelve years. The migration delivers a web app with the same data models, but with modern search, automated email templating, an integration with the telephone exchange and a customer portal where customers can view their own details and invoices.

Project planning and time tracking

An engineering firm uses FileMaker for projects, tasks and hours. The new web app keeps the same structure, with projects broken into phases and tasks with estimated and booked hours, but adds a Gantt view, automatic invoicing based on contract types and a mobile app for logging hours on the move. Reporting to clients is now done in the web app itself.

Inventory management and logistics

A manufacturer runs inventory, purchasing and quality control in FileMaker. We migrate to a web app with barcode scanning on the shop floor (a PWA on Android scanners), real-time dashboards for the production manager and API integrations with supplier portals. We rebuild the FileMaker reports as BI views in the new environment.

Why Appfront for your FileMaker migration

Respect for what works

Your FileMaker solution exists for a reason. We start by understanding why the platform was chosen at the time, and which logic is now crucial to your operations. No migration where half the functionality is lost because it had to be "modern".

Parallel run instead of big bang

We don't believe in migrations that hinge on a single weekend. Our approach is always parallel: the old and new solutions run side by side, with daily data sync. Your team can get used to the new system, compare and adjust before FileMaker is switched off.

A maintainable stack for the long term

We build on mainstream open-source frameworks that will still have developers available next year. No niche tech, no vendor lock-in. In five years you can switch supplier without panic, and we're confident enough that we'll still be here in five years anyway.

Frequently asked questions about FileMaker migration

Do I really need to move away from FileMaker now?
Not necessarily today. Existing Claris customers can renew their licences, and the platform will technically keep running for years. The question is rather: how much longer do you want to depend on a platform where Claris no longer sells new servers to new customers, and where the developer pool is shrinking? We recommend mapping out the migration path in any case, even if you want to stay for another two to three years.
Will I lose data or history during the migration?
No. Our migration approach is always reversible up to the cutover moment. During the parallel run, FileMaker stays fully operational, and after cutover the old environment remains available read-only for a few more weeks. Data is validated table by table: we compare record counts, checksums on critical fields and spot checks on edge cases. Only when all data is identical in the new environment is the old one switched off.
How long does a FileMaker migration take?
That depends on the size of your solution. A small departmental tool (twenty tables, fifty scripts, one team) can take six to twelve weeks. A mature business solution (a hundred tables, five hundred scripts, multiple teams and integrations) is typically a six-to-twelve-month project including the parallel run. We work in two-week iterations, so you always see progress.
What happens to our existing FileMaker scripts and custom functions?
We analyse them using the DDR export and group them by functional purpose. We then reconstruct the relevant logic in the backend of the new web app, usually in TypeScript or Python, with unit tests for critical rules. Obsolete scripts (from retired processes, debug routines, one-off imports) are left behind. That often cuts twenty to forty percent of the script file.
Will the new web app be as fast as FileMaker on the LAN?
In practice it is almost always faster with larger datasets. FileMaker is lightning fast on small sets over a fast LAN, but loses ground with millions of records or complex calculation fields. A well-indexed PostgreSQL database behind a modern web app keeps performing consistently well into the tens of millions of records. For mobile and remote users, a web app is generally considerably faster than FileMaker WebDirect.
Can we migrate modules one at a time instead of everything at once?
Yes, and that is often the sensible approach. For example, we can first migrate customer administration and CRM, then order processing, then reporting. During the transition both systems run side by side via a data sync, so customer data stays consistent between the web app and the part of FileMaker that is still live. This lowers the risk and spreads the investment.
What if we use external FileMaker plugins?
We take stock of plugins such as BaseElements, MBS, 360Works or Productive Computing during the DDR phase. For each plugin we determine whether the functionality is needed in the web app. There is usually an open-source or cloud equivalent (sending email, generating PDFs, OCR, FTP/SFTP). The plugin functionality is rebuilt in the backend, so after migration you no longer pay plugin licence fees.
Roughly what does a FileMaker migration cost?
The investment depends on the size of your solution and the UX and functionality improvements you want. We always start with a DDR analysis and a proof of concept on a single module. That gives you a realistic picture of scope, lead time and cost before you commit to a full project. There is no fixed project price up front, but you do get a transparent hour estimate per phase.

Want to get your FileMaker solution ready for the next ten years?

Schedule a no-obligation conversation. Together we will look at your current FileMaker environment, discuss a realistic migration path and, if you wish, start with a DDR analysis to get scope and lead time clear.

Schedule a call

Edit content