FileMaker Help and Support

Are you working with an existing FileMaker solution and need help with an error, a customization, or a new feature? Would you like to modernize an older FileMaker database, migrate it to a current version, or improve existing workflows?

We support businesses, self-employed professionals, associations, and organizations with their existing FileMaker solutions—even if the application wasn’t developed by us. From short-term troubleshooting and minor enhancements to the modernization of extensive database solutions, you’ll receive professional support backed by more than 30 years of experience with FileMaker and the development of business database systems.

Many tasks can be easily handled via remote support. This allows us to review your existing solution together, analyze any issues, and often make minor adjustments right during a support session.

Support for existing and older FileMaker solutions as well

Many FileMaker applications have evolved over the course of years or even decades. Sometimes the solution was developed by a former employee; other times, by an external developer or agency that is no longer available. Other applications are based on older templates and have been customized to meet specific needs over the years.

We also take on existing FileMaker solutions. It doesn’t matter at first whether it’s a small database for a single workstation or a comprehensive enterprise solution with numerous tables, layouts, and scripts. We’ll get an overview of the existing structure and work with you to determine what work makes sense and how much effort it’s likely to require.

Typical tasks include, for example, fixing errors, adapting to changes in business processes, adding new fields and reports, creating additional links between data, modifying layouts and print outputs, or expanding existing functions.

FileMaker Programming and Custom Extensions

An existing solution does not have to be completely redeveloped just because new requirements have been added. Often, additional features can be integrated into the existing system in a targeted manner.

These could include, for example, new search and filter functions, automatic checks for existing data records, additional relationships between tables, imports and exports, PDF output, email functions, interfaces to other applications, or automated workflows.

Even for smaller tasks, it’s often worth taking a moment to analyze the situation together. During a remote session, you can, if you’d like, directly track which changes are being made and how your existing solution is structured. Especially with smaller FileMaker systems, this approach allows you to implement many requirements without a large-scale development project.

Modernizing and Converting Legacy FileMaker Solutions

FileMaker has been in use for decades. Consequently, there are numerous solutions in productive use whose technical foundation is now significantly older than the computers and operating systems on which they run.

We can help you assess older FileMaker solutions and determine the best course of action for their continued use. This may involve converting older file formats, making necessary adjustments for current FileMaker versions, revising outdated features, or gradually modernizing an application that has evolved over time.

That doesn’t mean everything has to be redone from scratch. Especially with enterprise solutions that have been in use for many years, the existing database often contains years of experience and custom-developed workflows. The goal, therefore, is first and foremost to preserve what has proven effective and to intervene only where it makes sense from a technical or organizational standpoint.

Enhancing FileMaker with AI

Even an existing FileMaker solution can be enhanced with modern AI capabilities today. This does not necessarily require replacing the entire application or migrating it to a new platform.

Simply by integrating modern AI models, you can implement numerous practical functions. For example, AI can analyze texts and documents, summarize or classify content, and then return the results in a structured format to FileMaker fields. Possible applications include:

• automatic summaries of longer customer or project histories,
• Analysis and classification of incoming texts or documents,
• Recognition and extraction of specific information from free-form text,
• automatic assignment of tasks to categories,
• Drafts for emails, quotes, and other business documents,
• Converting unstructured input into structured FileMaker records,
• Analysis of existing data sets and assistance with research tasks,
• Smart assistants for recurring workflows.

The scope of this can vary greatly. A simple AI feature may, under certain circumstances, be integrated directly into an existing FileMaker solution. For more extensive requirements, knowledge bases or RAG systems can also be used, allowing the AI to access specific documents and corporate knowledge.

For more complex applications, knowledge graphs and agent-based systems are also possible. However, the appropriate technology always depends on the specific use case. Not every task requires a comprehensive AI infrastructure.

What kind of support is right for your FileMaker solution?

Not every FileMaker solution requires extensive modernization or a major development project. Often, the initial focus is on solving a specific problem, expanding an existing feature, or determining the next logical steps. The following overview shows typical starting points and the type of support best suited for each.

Consulting for FileMaker, AI, and the Future of Your Solution

Especially with older FileMaker systems, the question of which approach makes the most sense in the long term is becoming increasingly relevant today. Should the existing solution simply continue to be used? Is it worth modernizing it? What new possibilities does AI offer? Which parts of the existing application should be retained? And when might a phased migration to a different technical platform be advisable?

We provide technology-neutral advice on these issues, taking into account both your existing data and your actual business processes.

There’s no need to rush into replacing a proven FileMaker solution. At the same time, it can be wise to start planning for the coming years well in advance.

Hassle-Free FileMaker Support via Remote Maintenance

Many support and development tasks do not require an on-site visit. Through a shared remote session, we can view your FileMaker solution directly, troubleshoot issues, and discuss potential changes.

Depending on the task at hand, an initial session often lasts about 1.5 to 2 hours. For minor issues, the necessary adjustments can often be made during this session. If it turns out that more extensive work is required, we will discuss the next steps and the expected effort with you.

This way, you can keep costs under control and avoid having to commit to a large-scale development project right from the start.

Professional FileMaker Support Backed by Over 30 Years of Experience

Whether a FileMaker solution has been in use for just a few years or for decades does not, in and of itself, determine whether further development makes sense. Often, an application that has evolved over time contains a wealth of knowledge about a company’s actual business processes. That’s why we first examine the existing solution and the specific task at hand. This could involve fixing a single bug, making a minor enhancement, adding a new interface, modernizing older features, or even integrating new AI capabilities. 

We also assist companies when the original developer is no longer available or when the future technical development of an existing solution needs to be clarified. Often, a joint remote session is all it takes to determine the actual scope of work required.

Hourly rate for FileMaker support and custom development services: 

160.00 euros plus sales tax.

You are welcome to send us a description of your project initially, with no obligation, via e-mail or Contact form describe.

Frequently asked questions

1. Can I still hire you even if my FileMaker solution wasn't developed by you?
   Yes. We explicitly support FileMaker solutions created by other developers, agencies, former employees, or the company itself. Especially with older solutions, it’s common for the original developer to no longer be available or for the company’s requirements to have changed in the meantime. As a first step, we gain an overview of the existing application, the data model, key scripts, and the specific task at hand. For smaller solutions, this can often be done during a joint remote session. Afterward, it becomes much easier to assess which changes make sense and what level of effort is required. This means you don’t have to first migrate your existing solution to gFM-Business or have it completely redeveloped in order to receive support.
2. Is it even worth continuing to develop an older FileMaker solution?
   This depends less on the age of the solution than on its condition and its business value. A FileMaker application that has reliably supported a key business process for ten or fifteen years can be extremely valuable despite its age. It often incorporates workflows and insights that have been adapted over many years to the company’s actual operating practices. For this reason, we do not automatically recommend building a new application. The first step should be to assess which parts continue to function well, where technical risks exist, and what requirements are likely to arise in the coming years. Often, a phased modernization makes more economic sense than a complete rebuild. In other cases, however, it may be advisable to prepare for a migration early on. What matters most is a sober assessment of the existing solution—not just its version number.
3. Can you convert very old FileMaker files to current versions?
   In general, older FileMaker solutions can also be modernized and migrated to a newer technical foundation. However, the complexity of this process depends heavily on the age, file format, and structure of the specific application. For very old solutions, the conversion may require several intermediate steps. After the actual file conversion, it’s also important to verify whether scripts, calculations, print layouts, interfaces, and other functions continue to work as intended in a current version of FileMaker. A file that has been successfully opened from a technical standpoint is not a guarantee that the entire application will function without errors. For this reason, we always consider a conversion in conjunction with a functional test and an assessment of which older components can be meaningfully modernized during this process.
4. What happens during an initial FileMaker support session?
   Many tasks can be easily handled via remote support. During the session, we’ll review your existing FileMaker solution together, and you’ll be able to immediately point out where a problem is occurring or what kind of enhancement you need. Depending on the task at hand, an initial session often lasts about 1.5 to 2 hours. During this time, we can familiarize ourselves with the solution’s structure, analyze errors, and often make minor changes right away. If you’d like, you can follow along and ask questions. If it turns out that a problem is more extensive, we’ll first discuss the next steps before it develops into a larger development project. This way, the financial cost remains manageable, even for a FileMaker solution that is initially unfamiliar to us.
5. Can I request even minor changes to a FileMaker solution?
   Yes. Not every task has to turn into a large-scale development project. Especially with existing FileMaker solutions, the requirements are often very specific and minor: an additional field, a new relationship, an automatic validation, a layout adjustment, a modified report, or an additional step. Such tasks can often be implemented during a remote session. We start by reviewing how the existing solution is structured and determining the best place to integrate the change. Especially with applications that have evolved over time, it’s important not to simply add a feature somewhere, but to take existing structures and dependencies into account. This helps prevent a small change from causing unexpected side effects elsewhere.
6. How much does professional FileMaker support cost?
   FileMaker support and custom development services for existing third-party solutions are generally billed based on actual time spent. The standard hourly rate is 160.00 euros plus applicable VAT. For a typical initial remote session lasting about 1.5 to 2 hours, the cost would therefore range from 240 to 320 euros plus VAT. The total time required depends on the specific task at hand and the structure of the existing FileMaker solution. Especially with unfamiliar third-party solutions, providing a binding cost estimate before an initial analysis is often unreliable. That’s why we prefer to start with a manageable session and then decide together whether further work is necessary and economically feasible.
7. Can my existing FileMaker solution be enhanced with artificial intelligence?
   Yes. For many AI applications, there’s no need to replace an existing FileMaker solution. FileMaker can send data to modern AI services or language models and then save the generated results back to your own database for further processing. This opens up numerous practical applications. For example, AI can summarize customer and project histories, classify text, extract information from documents, convert free-form text into structured data, draft emails, or analyze existing data sets. The most appropriate integration depends on the specific workflow. We therefore first examine the problem to be solved and then select the appropriate technical implementation. Not every useful AI function requires extensive additional infrastructure.
8. Specifically, what tasks can AI handle within a FileMaker solution?
   Tasks in which people currently read, organize, summarize, or convert information from one format to another are particularly interesting. An existing FileMaker solution often already contains structured business data, while AI can handle the processing of unstructured information. For example, incoming emails could be analyzed and assigned to a customer or project, PDF documents could be evaluated, meeting notes could be summarized, or longer texts could be automatically categorized. AI can also generate structured field content from a free-form description, create suggested wording for correspondence, or summarize information from multiple data sets for the user. Industry-specific applications are also possible. The key is not to integrate AI everywhere possible, but to identify those work steps where it actually saves time or makes information more usable.
9. What is RAG, and can I use it to leverage my business knowledge in FileMaker?
   RAG stands for “Retrieval Augmented Generation.” Put simply, an AI model retrieves specific information from its own knowledge base before answering a question. This means the AI does not have to rely solely on its general training knowledge but can, for example, work with internal documentation, product information, manuals, or other company records. Such a knowledge layer can also be connected to an existing FileMaker solution. The user could then, for example, ask questions directly from within FileMaker, and the AI would automatically search for relevant internal documents and provide them as context. RAG, however, is already a more comprehensive form of AI integration. For many practical tasks, a direct connection between FileMaker and an AI model is sufficient to start with. We therefore assess whether an additional knowledge base is actually necessary or whether a simpler solution offers the same business value.
10. Can FileMaker also be connected to a knowledge graph or Neo4j?
    Generally speaking, yes. A knowledge graph can be useful when the goal is not just to find individual documents, but to map complex relationships between people, companies, projects, products, processes, and information. Systems like Neo4j store such relationships in a specialized graph structure. A FileMaker solution could continue to serve as a business application and user interface, while additional knowledge structures are built in the background and utilized by AI systems. However, such an architecture is significantly more complex than a simple AI integration and should only be implemented if the specific benefits justify the additional technical effort. For many companies, it makes more sense to start with manageable AI functions and expand the knowledge architecture later, as actual needs arise.
11. Do I need to replace FileMaker if I want to modernize my solution for the long term?
    No. Modernization and migration are two different things. An existing FileMaker solution can often be usefully maintained for many more years while being gradually improved. In many cases, new features, interfaces, automations, and even AI integrations can be incorporated without replacing the entire application. Nevertheless, for older or very large-scale solutions, it makes sense to develop a long-term strategy. This includes, for example, assessing dependencies on specific FileMaker versions, how data is structured, which external interfaces are used, and how a future migration could be prepared. Our goal is not to recommend a platform change as a matter of principle. Together, we’ll assess which solution is technically and economically best suited to your situation. Proven systems should not be replaced simply because newer technology is available.
12. What can I do if I barely understand my FileMaker solution or there is no documentation available?
    This is not uncommon with FileMaker solutions that have evolved over many years. Some applications have been expanded over the years by various people. Others were originally developed by an employee who has long since left the company. Often, there is only incomplete technical documentation—or none at all. In such cases, we begin with a structured assessment. This involves examining tables, relationships, key fields, scripts, layouts, and interfaces, as well as the workflows critical to day-to-day operations. The initial goal is not to fully document every single function, but rather to understand the areas relevant to your current needs. On this basis, errors can be corrected and enhancements can be implemented in a controlled manner. For more extensive solutions, it may also be advisable to build up technical documentation step by step. This makes the application more maintainable in the long term and reduces dependence on the knowledge of individual people.