Our FileMaker system is old and per-user licences are costly. How do I move to something I own?
Short answer: Move in a fixed order: list what the system does, export the data, rebuild the screens and rules, run both systems side by side, then switch. FileMaker, made by Claris, is a tool for building custom database apps, and it is licensed per user. If the system works and the licence cost is small next to the cost of a rebuild, staying is a sound choice. If licences scale with your team, the system is hard to change, or nobody left understands it, a custom web app that you own can be cheaper over a few years. The deciding factors are the number of users, how much logic is hidden in scripts, and how much risk you can accept during the move.
You want a straight test for whether to leave FileMaker, and an order of work that does not put your business data at risk.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Should you leave at all?
Many FileMaker systems are old and still good. They were built by someone who understood the business, and they do exactly what the business needs. Replacing a working system is expensive and risky, so the first job is to test whether leaving is worth it. Score the five questions below.
- Is the licence cost growing? FileMaker is licensed per user. If you add staff, you add cost.
- Is it hard to change? If a small change needs a specialist and takes weeks, the system is holding you back.
- Does one person understand it? If that person leaves, you have a risk, not a system.
- Do you need it where FileMaker is awkward? Examples: customers logging in, a public booking page, or a mobile experience your staff actually like.
- Is the data getting stuck? If you export to spreadsheets every week to answer simple questions, the system is not serving you.
Zero or one yes answers: stay put. Two or three: plan the move for the next year and fix the biggest pain now. Four or five: start the move. The same method applies to how to replace an Access database with a web app.
What FileMaker licensing costs
As of November 2026, Claris lists FileMaker Cloud plans (its hosted version) on its pricing page. The Starter plan is US$22 per user per month, billed annually, for 5 to 10 users, with a hosting limit of 3 apps. The Max plan is US$45 per user per month, billed annually, for 5 to 99 users, with a hosting limit of 256 apps. Claris also offers a single licence of FileMaker Pro for people who do not need to share data, a self-hosted FileMaker Server option, and a contact-sales route for 100 or more licences or custom licensing. Check Claris's pricing page for current figures and for self-hosted pricing, which differs.
A worked example using those published prices, with a made-up team size: a business with 12 people on Max pays 12 x $45 x 12 months, which is $6,480 a year. Over five years that is $32,400, before any developer time. A business with 8 people on Starter pays 8 x $22 x 12, which is $2,112 a year, or $10,560 over five years.
Compare that with the cost of a rebuild, which depends heavily on how big the system is. A small, simple system may cost far less than five years of licences. A large system with hundreds of scripts may cost more. Get a fixed quote after the audit step below, not before.
Remember that the cost of a custom web app is not zero either: it needs hosting, backups and someone to fix problems. The difference is that the cost does not rise with each person you add, and you own the code.
What you actually own today
You own your data. The system's design, meaning the layouts, scripts and relationships, lives inside the FileMaker file and runs only on FileMaker. You cannot take it to another platform as it is. That is the main reason a move is a rebuild, not a copy.
Step 1: audit what the system does
Before touching anything, make four lists.
- Tables and fields. What things does the system track (customers, jobs, invoices), and what facts does it hold about each?
- Layouts. A layout is a screen or a printed form. List the ones people use every day, and the ones nobody has opened for a year.
- Scripts. A script is a stored set of steps, such as "create an invoice from this job" or "email the weekly report". List what each one does in plain words and who triggers it.
- Connections. What talks to the system: other software, email, a website, accounting, a barcode scanner.
Expect some of what you find to be unused. Cutting it is a free saving. FileMaker can produce a database design report as part of its development tools, which gives you a starting inventory, and Claris lists the script debugger and data viewer alongside it.
Step 2: export and protect the data
Do this early, even if you decide to stay. Make a backup, then export every table. The Import Records script step in the same help site shows how data goes the other way, which is useful if you keep using FileMaker for part of the job. FileMaker Pro's help describes an Export Records script step, and also Save Records as Excel and Save Records as JSONL script steps, so data can leave in common formats. Export each table separately, keep the field names, and keep the record IDs, because those tie tables together.
Check each export against the live data: row counts, a handful of spot-checked records, and any fields that hold files or images (these export differently and are often forgotten). Store the exports somewhere safe and dated.
Claris documents the FileMaker Data API, a REST interface that lets web services read and write records in a database hosted by FileMaker Server or FileMaker Cloud, and the pricing page also names OData, a standard way for software to read data. During a side-by-side period, these can keep a new app and the old system in sync, though the plan you are on affects the data transfer allowed. The pricing page lists an outbound data transfer allowance per user for FileMaker Cloud plans, so check it before you rely on it.
Step 3: decide what to rebuild and what to drop
Put every layout and script into one of three groups.
- Keep as it is. Core records, searches, and the reports people use every week.
- Improve. Things that work but annoy people: slow screens, awkward forms, manual steps that could be automatic.
- Drop. Anything unused. Do not rebuild it.
This is also the time to look for things a web app does better: customers who check their own job status, staff who use a phone, and email or text messages sent from the system. My guide to moving from Excel to a web app covers the same thinking for spreadsheets, and internal tools explains what a well-built custom tool looks like.
Step 4: the migration order
Move in this order, because each step depends on the one before.
- Data structure first. Build the tables and fields in the new system.
- Load a copy of the data. Import from the exports. Check counts and spot check again.
- Rebuild the daily screens. Start with the three or four screens people use every day.
- Rebuild the rules and scripts. Calculations, invoice creation, emails, reminders. This is the slowest part, because the rules are often undocumented. Sit with the person who uses each one and watch them do it.
- Rebuild reports and printouts. Invoices and forms that customers see should look right.
- Run both systems side by side. For two to four weeks, enter new work in the new system and compare with the old one.
- Switch, then keep the old one read-only. Set FileMaker to read-only for a few months in case someone needs to look something up, then retire it.
The tool you move to matters less than the order. Larger tools can come later: for finance and stock, see my guide to custom ERP (an ERP is one system that runs stock, orders and accounts), and if you are weighing a ready-made tool, my guide to Airtable alternatives shows what that route looks like. For the buy-or-build call, read build versus buy software.
Common failure points
- Hidden rules. A calculated field that adds a 3 percent surcharge for one customer type, known only to the person who built it. Interview staff before you rebuild.
- Dates and numbers. Date formats and rounding often differ between systems. Test with real records.
- Files and images. They get lost in exports. Check them one by one.
- Permissions. FileMaker has its own access rules for who may see what. Write down who may see what, and rebuild it deliberately.
- Cutting over in a busy week. Never switch in your peak season.
When staying is the right call
Stay when the system is stable, the cost is small compared to a rebuild, and the person who looks after it is not leaving. Spend a little on a documented backup, a written list of scripts, and a second person who understands it. Claris continues to release new versions (it lists FileMaker 2026 with a 45 day trial), so the product is not dead, and for some businesses it is the right home for years.
What a custom web app gives you, and what it does not
It gives you no per-user fee, ownership of the code, access from any browser, and the freedom to change it. It does not give you something free. You still need hosting, backups, security updates and someone to call. Ask any developer how they handle those, and what happens if they are unavailable. A web app that only its builder understands is the same risk you have today.
How I'd approach this
I would not start with a quote. I would start with the audit and the export, because they cost little, protect you either way, and make any quote accurate. Then I would rebuild the three or four screens people use daily, run them side by side with FileMaker, and move the rest in order of pain.
I would also be plain about the one thing that surprises people: the hidden rules cost more time than the screens. Budget for conversations with your staff. Blur Studio fixes and finishes start around $1,500, and bigger rebuilds are quoted after the audit. For the wider picture on where AI fits in such a move, see AI for small business.
Questions people ask
How much does FileMaker cost per user?
As of November 2026, Claris lists FileMaker Cloud Starter at US$22 per user per month and Max at US$45, both billed annually, with minimum and maximum user counts per plan. Check Claris's pricing page for current figures, and for self-hosted options.
Can I export my data out of FileMaker?
Yes. FileMaker Pro's help describes export script steps, including Save Records as Excel and Save Records as JSONL. Export each table, keep the record IDs, and check row counts. Your layouts and scripts do not carry over to another system, so they must be rebuilt.
Can I convert my FileMaker app automatically?
Your data moves over easily, but the layouts, scripts and relationships are built for FileMaker and have to be rebuilt in the new system. Plan the work around the scripts, not the data.
How long does a FileMaker replacement take?
It depends on how many layouts and scripts you keep. A small system can take weeks and a large one many months, so get a fixed quote after an audit. My guide to build versus buy software covers how to compare options.
Is there a ready-made alternative to a custom build?
Yes, such as low-code database tools, which are database-style spreadsheet apps you set up yourself. Many charge per user, so compare the five-year cost. See my guide to Airtable alternatives for an example of that route.
More in this topic: Problem solving: custom software (22 guides) →