The Advantages That Made FileMaker Great Are No Longer Reasons to Stay.

Development Speed

How FileMaker approaches it

An integrated database, layout designer, and scripting engine let small teams deliver working business applications quickly.

Where it gets harder

Over the years, layouts, scripts, and relationships accumulate. Without strong conventions, changes get slower and riskier.

Modern web approach

Component libraries, typed codebases, automated tests, and AI-assisted coding shorten the path from idea to working screen while keeping the code reviewable.

What changes

Faster iteration on new workflows, with changes covered by tests instead of repeated manual checking.

Layouts and UI Limitations

If You Need Web Viewers for Modern UI, Why Not Build a Web App?

How FileMaker approaches it

Interfaces are built from layouts bound to table occurrences, using a fixed set of layout objects.

Where it gets harder

Custom interaction patterns, responsive behavior, and brand-specific design often need Web Viewers, layout workarounds, or many duplicated layouts.

Modern web approach

Any interaction the browser supports: shared design systems, responsive grids, accessibility tooling, and reusable components.

What changes

Interfaces shaped around how people work, rather than around what the layout engine allows.

// JavaScript inside the Web Viewer
FileMaker.PerformScript(
  "Load Sales Chart",
  JSON.stringify({ region: "North" })
);

// FileMaker script
Perform JavaScript in Web Viewer [ "render" ; $json ]

// Component calls the API directly
const res = await fetch(
  "/api/sales?region=North"
);
const data = await res.json();
render(data);

FileMaker Find Mode

How FileMaker approaches it

Find Mode lets a user enter search criteria directly into layout fields, then switch to Browse Mode to work with the resulting found set. Scripts can also perform finds programmatically.

Where it gets harder

Find Mode is built around a single window working with one found set at a time. Reaching the same search logic from a browser, a mobile device, or another system usually means re-implementing it as a script exposed through the Data API, OData, or a plug-in.

Modern web approach

Web applications implement search as validated query parameters sent to a backend API, which runs parameterized database queries and returns results a client renders, filters, and paginates independently of any one window.

What changes

Find Mode is quick for trained users inside FileMaker. The question is whether the same searches must also be reachable from outside it.

Enter Find Mode []
Set Field [ Orders::Customer ; "" ]
Set Field [ Orders::Status ; "" ]
Set Field [ Orders::Total ; "" ]
Perform Find []

SELECT id, customer, status, city, total
FROM orders
ORDER BY id
LIMIT 50;

Related Records and Portals

How FileMaker approaches it

The relationship graph, table occurrences, and portals make joins approachable without writing SQL.

Where it gets harder

Large graphs with many table occurrences become hard to read, and changing a relationship can affect layouts, scripts, and calculations at once.

Modern web approach

Relational databases such as PostgreSQL with explicit schemas, foreign keys, migrations, and SQL. Data is modeled once and exposed through APIs.

What changes

A clearer data model, safer schema changes, and data that any tool that speaks SQL can reach.

Relationship:
  Customers::CustomerID = Orders::CustomerID

Portal on Orders
  filter: (none)
  sort:   Orders::id ascending
  rows:   5 per portal view, scroll for more

SELECT id, order_date, status, amount
FROM orders
WHERE customer_id = $1
ORDER BY id ASC
LIMIT 5 OFFSET 0;

Slow Reports and Summary Fields

How FileMaker approaches it

Summary fields, sub-summary parts, and found sets provide quick built-in reporting.

Where it gets harder

Unstored calculations and summaries over large found sets can slow reports down, and teams add scripts and helper tables to compensate.

Modern web approach

Indexed SQL queries, pre-aggregated tables or materialized views, and dashboards that query only what they display.

What changes

Reports designed around data volume, with performance work focused on measured queries.

We are not citing a benchmark here. Whether a given report is slow depends on your data volume, indexing, and calculation design, which is exactly what an audit checks before any migration estimate.

SELECT month, SUM(amount) AS total
FROM sales
GROUP BY month
ORDER BY total DESC;

-- supporting index
CREATE INDEX sales_month_idx
  ON sales (month);

Summary field: Total Amount = Total of Sales::amount
Layout: sub-summary part when sorted by month
Script: Sort Records [ month ] ; Preview Mode

Import and Export

How FileMaker approaches it

Import and export dialogs support common formats with field mapping and ordering.

Where it gets harder

Friendly column names, per-recipient formats, and repeatable exports usually need extra scripting or helper fields.

Modern web approach

User-configurable export templates (columns, labels, format) and import mapping with validation and preview. AI can suggest mappings for a person to review.

What changes

Less manual spreadsheet cleanup and fewer one-off export scripts.

cust_nm,ord_dt,ord_tot
Northwind Interiors,2026-03-04,4820
Kestrel Hospitality,2026-03-09,12990
Alder Studio,2026-03-12,980

Multilingual Applications

How FileMaker approaches it

Custom solutions can be made multilingual, commonly with translation tables, custom functions, or duplicated layouts.

Where it gets harder

Every new screen and label has to be wired into the chosen approach, and translations are easy to leave out of sync.

Modern web approach

Established internationalization libraries with translation files, locale-aware dates, numbers, and currencies, and AI-assisted translation drafts reviewed by people.

What changes

Adding a language becomes a content task rather than a rebuild.

Mobile and Responsive Design

How FileMaker approaches it

FileMaker Go and WebDirect provide mobile and browser access to your layouts.

Where it gets harder

Layouts are designed for specific screen sizes, so supporting phone, tablet, and desktop typically means separate layouts per form factor.

Modern web approach

Responsive layouts adapt a single interface across phone, tablet, and desktop, and can be installed as a progressive web app where useful.

What changes

One interface to maintain instead of one set of layouts per device.

Live Updates

How FileMaker approaches it

Records are shared in a multi-user solution, and users see saved changes when screens refresh or scripts re-query records.

Where it gets harder

Live-updating views typically depend on timers, script triggers, or manual refresh, which adds scripting and server load.

Modern web approach

WebSockets, server-sent events, or managed realtime services push changes to screens that are already open.

What changes

Dashboards and work queues that stay current without anyone pressing refresh.

Security

Security Is an Engineering Discipline, Not a Proprietary Platform Advantage.

How FileMaker approaches it

Privilege sets control access to records, layouts, fields, and scripts, with accounts managed in the file or through external authentication.

Where it gets harder

Fine-grained rules tend to spread across privilege sets, layouts, and script privileges, which can be hard to audit as the solution grows.

Modern web approach

Standard identity providers, role-based authorization enforced on the server, and centralized access policies that can be tested.

What changes

Access rules that can be reviewed, tested, and audited in one place.

FileMaker does provide real, documented security controls: privilege sets, account management, and encryption options. The point is not that FileMaker is insecure. It is that security comes from how access rules are designed, centralized, and tested, which applies equally to a FileMaker solution and a web application.

Licensing and Platform Dependency

How FileMaker approaches it

FileMaker is licensed under Claris terms, and the solution runs on the Claris platform. Check current terms with Claris.

Where it gets harder

Recurring license costs, dependence on one vendor roadmap, and a smaller pool of developers than mainstream web stacks.

Modern web approach

Open-source frameworks, standard hosting, source code you own, and the freedom to choose providers and developers. Web applications still have hosting and maintenance costs.

What changes

More choice in hosting, vendors, and hiring, with costs tied to your own usage. The calculator below lets you test this with your numbers.

FileMaker Server supports many concurrent users, with capacity depending on hardware, licensing, and solution design. Stateless application servers, managed databases, caching, and horizontal scaling let each part grow independently.

Scripts, plug-ins, the Data API, OData, and Claris Connect can connect FileMaker to other services. Standard REST, webhook, and queue patterns, a very large package ecosystem, typed SDKs, and durable workflow tooling.