Frequently Asked Questions

FileMaker performance problems can originate in the database design, scripts, layouts, calculations, server resources, network connection, storage, or the amount of data being transferred between FileMaker Server and clients. Diagnosing a slow FileMaker solution requires determining whether the bottleneck is occurring in the application, server, network, or client.

Claris itself says server performance can be affected by processor, disk and network capacity and recommends a dedicated server; it also exposes FileMaker Server statistics such as cache-hit percentage for performance diagnosis. Claris Help

Claris — Improving FileMaker Server Performance

Claris — FileMaker Server Statistics

Here are several other pages about FileMaker speed:

• Why is my FileMaker so slow?
• How File Size Impacts FileMaker Performance – and How to Fix It
• FileMaker Speed Case Study
• Is your Pet Turtle Faster than FileMaker?
• FM Speed Report

Last reviewed: September 2026 — FileMaker 2026

Whether a legacy FileMaker solution should be rebuilt or modernized incrementally depends on its architecture, security, performance, maintainability, integrations, user requirements, and the amount of existing functionality that remains valuable. A rebuild is not automatically preferable; in many systems, targeted modernization can preserve reliable functionality while replacing problematic components.

Rebuild when:

1. Data architecture is fundamentally limiting (think ‘spiderweb’).
2. Security is difficult to correct (e.g. multiple users all logging in on the same UN/PW; locally hosted server, etc)
3. Obsolete dependencies
4. Solution was built before FM version 7, and relies on multiple files

Modernize when:

1. Core data schema is sound
2. Business rules work
3. Users rely heavily on existing workflows
4. Incremental changes can address pain points

Last reviewed: September 2026 — FileMaker 2026

FileMaker development costs vary according to scope, database complexity, integrations, migration requirements, security, testing, documentation, and whether the work involves an existing system or a new application.

Ranges can be:

Small Modifications	1 – 20 hours
Moderate Project	21 – 80 hours
Large Project	80+ hours

Last reviewed: September 2026 — FileMaker 2026

Yes. FileMaker can exchange data with QuickBooks Online through API-based integrations. Depending on the workflow, an integration can create or update customers, invoices, payments, products and other accounting information while FileMaker remains the operational interface.

Claris documents FileMaker’s Insert from URL script step, including cURL options and SSL verification, and provides JSON functions specifically for parsing and modifying JSON returned by sources such as REST APIs. Claris Help

Claris — Insert from URL and cURL

Claris — Working with JSON

Last reviewed: September 2026 — FileMaker 2026

Look for a FileMaker developer who has experience inheriting existing systems and who will review the solution before making major changes. Important areas include Full Access credentials, backups, security, schema, scripts, integrations, server configuration, documentation and known performance problems. There is no need to assume that the legacy system, must be replaced. That decision needs to be made after the system architecture is compared to current business needs.

Claris evidence: Full Access/security and backup best practices.
(https://help.claris.com/en/pro-help/content/creating-editing-accounts.html)

7 Questions to Ask a Before Rebuilding a Legacy System:

1. Have you thoroughly reviewed the existing FileMaker solution before recommending a rebuild?
2. What specifically is wrong with the current system that cannot reasonably be improved?
3. Which parts of the existing solution are well designed and worth preserving?
4. What would incremental modernization look like compared with a complete rebuild?
5. How will existing data, business rules, integrations, and historical records be protected during the project?
6. Can improvements be made while employees continue using the existing system?
7. How will you determine whether the rebuild or modernization was successful?

Last reviewed: September 2026 — FileMaker 2026

Yes. FileMaker can integrate with AI models through APIs and also includes native AI-related capabilities for tasks such as generating embeddings, semantic search, natural-language finds, retrieval-augmented generation (RAG), natural-language SQL queries, and generating model responses.

Claris — FileMaker AI Script Steps

Claris — Semantic Find

Claris — Natural-Language Find

Claris — Generate Response from Model

Last reviewed: September 2026 — FileMaker 2026

A FileMaker maintenance agreement should include the following:

1. Systems covered
2. Response expectations
3. Communication tools used
4. Server Monitoring
5. Upgrades
6. Third-party integrations
7. Documentation

Last reviewed: September 2026 — FileMaker 2026

FileMaker Cloud and FileMaker Server both host FileMaker applications, but they differ in authentication, infrastructure management, configuration control and deployment options. The appropriate choice depends on an organization’s security requirements, integrations, administrative resources, existing infrastructure and need for server-level control.

Claris confirms, for example, that FileMaker Cloud uses Claris ID or an external identity provider for hosted-file authentication. Claris Help

Claris — FileMaker Cloud Authentication

Claris — FileMaker Server Administration

Last reviewed: September 2026 — FileMaker 2026

Absolutely. FileMaker remains actively developed in 2026 and supports modern application requirements including browser access, REST APIs, JSON, SQL connectivity, cloud/server hosting and AI-assisted workflows. Whether it is appropriate for a particular project depends on the application’s scale, interface requirements, deployment model and integration needs.

Last reviewed: September 2026 — FileMaker 2026

FileMaker supports account authentication, privilege sets, data encryption at rest, SSL encryption in transit and granular restrictions on tables, records, fields, layouts, scripts and other resources. Claris Help

Claris — FileMaker Security Guide

Claris — Database Encryption

Claris — Accounts and Privilege Sets

Last reviewed: September 2026 — FileMaker 2026

Yes. FileMaker applications can be accessed through supported web browsers using FileMaker WebDirect. WebDirect presents layouts and workflows from a hosted FileMaker solution in a browser, although some FileMaker Pro features and behaviors differ in WebDirect and may require design adjustments.

Claris’s WebDirect documentation confirms browser-based access and documents WebDirect-specific configuration and behavior.

Last reviewed: September 2026 — FileMaker 2026

Yes. FileMaker can send requests to REST APIs, receive JSON responses, authenticate with external services, and process returned data. Common integration patterns use the Insert from URL script step with cURL options together with FileMaker’s JSON functions.

https://help.claris.com/en/pro-help/content/insert-from-url.html

Last reviewed: September 2026 — FileMaker 2026

Yes. FileMaker can work with external SQL data through ODBC and other integration methods. Supported external SQL sources can appear as table occurrences in FileMaker’s relationships graph, allowing FileMaker layouts, relationships and scripts to interact with external data. FileMaker can also execute SQL against ODBC data sources and import SQL data.

Claris — Accessing External SQL Data Sources

Claris — ODBC and JDBC with FileMaker

Last reviewed: September 2026 — FileMaker 2026

A FileMaker modernization project can range from a targeted improvement completed in days or weeks to a multi-month rebuild. The schedule depends primarily on application size, schema complexity, integrations, data migration, interface redesign, testing requirements and whether development can occur while the existing system remains in production.

HighPower has worked on projects that took anywhere from just a couple of weeks to more than 24 months, for a major overhaul and rebuild.

Last reviewed: September 2026 — FileMaker 2026

FileMaker can support growing organizations, but scalability depends on application architecture, concurrent users, record volume, calculations, layouts, scripts, integrations, server resources and network conditions. Growth problems attributed to “FileMaker” may actually originate in application design or infrastructure, so scalability should be evaluated across the entire system.

Last reviewed: September 2026 — FileMaker 2026

When selecting a FileMaker developer, evaluate FileMaker experience, Claris certifications, experience with existing systems, FileMaker Server knowledge, security practices, API and SQL integration capabilities, documentation standards, communication practices and continuity of support.

Last reviewed: September 2026 — FileMaker 2026

FileMaker and Airtable overlap in some use cases but are designed around different levels of application customization and workflow complexity. Airtable emphasizes cloud-based collaborative data organization, while FileMaker provides a broader custom-application environment with layouts, scripting, calculations, granular privileges, external data connections and multiple deployment options.

 

Capability	Claris FileMaker	Airtable
Custom application development	Designed for building highly customized business applications with custom layouts, workflows, calculations, scripts, and business logic.	Designed primarily around collaborative databases and app-like interfaces, with configurable views, interfaces, and automations.
Complex business workflows	Supports extensive scripting, calculations, relational data models, custom security, and multi-step business processes.	Supports automations, formulas, interfaces, and integrations, but is generally oriented toward more standardized workflows.
User interface customization	Developers can create highly customized layouts for different users, devices, departments, and workflows.	Provides configurable interfaces and views within Airtable’s interface framework, with less control over the underlying UI.
Hosting & deployment	Can be deployed using FileMaker Server, FileMaker Cloud, hosted infrastructure, desktop/mobile clients, and WebDirect browser access.	Primarily delivered as a cloud SaaS platform through web and mobile applications.
Integrations & extensibility	Supports REST APIs, FileMaker Data API, JSON, cURL, ODBC/JDBC, plug-ins, SQL connectivity, and external services.	Supports REST APIs, webhooks, automations, extensions, scripting, and integrations with many third-party services.

Last reviewed: September 2026 — FileMaker 2026

FileMaker and custom web development can both be used to build business applications, but they involve different development models. FileMaker provides an integrated platform for database design, layouts, scripting, security and deployment, while custom web development typically combines separate front-end, back-end, database, hosting and authentication technologies.

Last reviewed: September 2026 — FileMaker 2026

If a FileMaker developer retires or becomes unavailable, undocumented systems, missing credentials, and limited support can create serious business risks. HighPower Data Solutions has been developing and supporting FileMaker solutions for many years, with a large team that provides broader knowledge and dependable continuity. We document systems, protect client ownership, maintain backups, and share expertise across our staff—helping ensure reliable support now and long into the future.

Last reviewed: September 2026 — FileMaker 2026