Somewhere in your company a FileMaker solution runs a lab, a clinic, a studio, or an ops team — built over years by one consultant who has retired, moved on, or answers email twice a month. Marcus, Kinetech's AI Mendix developer, reads that solution's own design report — the entire app as XML — and rebuilds it as a governed, auditable Mendix application your IT organization can actually stand behind.
01 · The clock
Straight up: Claris ships FileMaker actively — FileMaker 2026 released in June 2026. If you expected an end-of-life scare here, we don't have one and won't invent one. The pressure is structural, not terminal:
02 · The differentiator
FileMaker may be the most machine-readable legacy platform we've studied. The Database Design Report exports the entire solution — schema, layouts, every script step, calculations, privilege sets — as documented XML. Even if your developer left no notes, the app documents itself.
| FileMaker artifact | What Marcus extracts | Where it lands in Mendix |
|---|---|---|
| Tables & fields (via DDR XML) | Full schema including field types, options, and calculation definitions | Entities and attributes; calculated attributes or microflows |
| Relationships Graph | Every table occurrence and join — the app's real data model | Entity associations |
| Layouts & layout objects | Screen inventory: forms, lists, fields, buttons, portals | Pages, with portals becoming data grids over associations |
| Scripts (every step, in XML) | The business logic — navigation, validation, imports, notifications | Microflows and nanoflows |
| Value lists | Controlled vocabularies | Enumerations or reference data |
| Privilege sets (incl. record-level access) | Who can see and edit what — down to per-record conditions | Module roles and XPath row-level constraints, verified by automated negative tests |
| Data & containers | All records via ODBC/JDBC; embedded files and images via sanctioned export paths — a solved problem, as existing FileMaker-to-SQL tooling shows | Your data in a real database; files as first-class documents |
A second sanctioned export — Save a Copy as XML, in FileMaker 18+ — cross-checks the DDR, and mature commercial DDR-analysis tools have proven for years that this XML is fully machine-tractable. Marcus doesn't reverse-engineer your app; it reads the format Claris built for exactly this.
03 · How a migration runs
The extracted spec — screens, rules, integrations, and what should not be rebuilt — approved by you before modeling starts.
Privilege sets translated to roles and row-level rules, in plain English — often the first time anyone has seen the app's security model written down.
Modern design directions derived from your brand, presented before pages are generated. The workflows' intent is preserved; the 2009 layout aesthetic is not.
The rebuilt app reaches you with all quality gates passed and data migrated to a parallel environment — cutover happens when you accept, not before.
04 · The date
Here is the commitment we will put in writing. The assessment does not end with a range — it ends with a date, sized from your actual extracted complexity. Miss that date and the assessment fee comes back. We can promise a date because we never quote a calendar before reading your source.
The assessment names the date. Miss it, and the assessment fee comes back.
That is a real term, not a slide. It is affordable to us for one reason: the clock below starts only when a complete artifact pack is in our hands, and it pauses only for your own approval gates.
| One FileMaker solution (all files) | Complete artifact pack → UAT-ready |
|---|---|
| Compact — ≤20 base tables, ≤30 layouts, ≤150 scripts, no plug-ins | 2–3 weeks |
| Departmental — 20–50 tables, 30–80 layouts, 150–400 scripts, 2–4 integrations | 4–6 weeks · ~30 days typical |
| Load-bearing — 50–120 tables, multi-file, Server schedules, plug-ins | 8–12 weeks |
| Each further solution in the same estate | 30–40% faster |
Sizing model, not a price list — the assessment reads your actual source and returns one date. Bands assume a single rebuild boundary agreed at the scope gate.
The date is only honest if the inputs are complete, so here is the whole list up front. Nothing on it is unusual, and most of it exists already.
Three approval gates are yours: scope, permission ratification, design sign-off. We answer each within three business days. Time beyond that on your side moves the date by exactly that much — and nothing else does.
Production cutover on your change calendar. SSO and network provisioning by your IT. Third-party licenses or vendor contracts we don't control. Remediation of source-data quality problems the assessment flagged. Anything added after the scope gate.
Functional parity against the approved specification, running on your migrated data in a parallel environment, with production security enforced and tested per role, all nine quality gates green, and documentation published. Your users click through it.
What moves a FileMaker date is rarely the build. It is unstored calculations chained across the relationship graph — those get redesigned, not translated — container volume, and layout-based print reports. Script count is the least useful number in the DDR: navigation scripts (Go to Layout, Enter Find Mode, Sort) do not carry forward at all, and the assessment tells you what share of your script count is real business logic.
05 · Why Mendix
The FileMaker solutions worth migrating are the ones that became load-bearing. Once an app matters to auditors, integrations, and more than one department, it needs things FileMaker was never designed to give you:
06 · Straight talk
| Area | The honest position |
|---|---|
| Your users' affection | FileMaker users genuinely love FileMaker — we won't pretend otherwise. The rebuild preserves the intent of their workflows and screens, not pixel-parity; the design gate exists so they choose what they land on. |
| Cost | This costs more than Claris seats — full stop. The honest comparison is against a six-figure hand-rebuild quote from a consultancy, or the ongoing risk of a business-critical app nobody can maintain. If neither describes your situation, keep FileMaker. |
| Calculation-field idioms | FileMaker's per-record calc engine encourages patterns (unstored calcs chained across relationships) that need genuine redesign, not translation. These are flagged per-app in the assessment with the proposed Mendix equivalent. |
| Container data | Embedded files and images migrate via sanctioned export paths — proven by existing FileMaker-to-SQL tooling. Volume and verification are scoped in the assessment, and the original file is archived until you confirm completeness. |
| FileMaker Go | iPad/iPhone use carries over to Mendix native mobile or responsive web — but mobile layouts are re-designed, not cloned. Field users see it before it ships. |
07 · Quality & security
Watch real build evidence land on the live Build Console, and see the delivery lifecycle at our interactive explainer.
08 · Engagement & pricing
Export the Database Design Report; Marcus reads it and returns a scored specification — schema, screens, scripts, security, calc-idiom flags, container volume — plus a fixed-bid rebuild quote. If the honest answer is "stay on FileMaker" or "use a simpler tool," that's what the report says.
Credited toward onboarding if you proceed.
The rebuild, quoted from the actual extracted complexity — built, tested per role, documented, delivered through the approval gates with published evidence and a parallel-run cutover.
The typical engagement for a single rescued application.
For organizations with several departmental apps to consolidate: Priced on what the work is, how many lanes run in parallel, and how fast you need it — always with Kinetech engineer review and an escalation SLA.
Bring your own Claude access: roughly 15–25% off the monthly.
Every figure here is an indicative range; your actual range is confirmed in writing before anything is charged. On bundled plans, heavy build months may incur metered usage beyond the included allowance; your quote states the allowance plainly. Your applications, models, and repositories are contractually yours.
09 · The questions you should ask
That's a legitimate path, and for a healthy solution with an available developer it's the cheap one. What it doesn't fix: the single-person dependency simply transfers to the next consultant, the re-licensing and OS-churn costs recur, and the app stays outside your governance, SSO, and integration landscape. If the app is business-critical enough that its continuity keeps coming up in meetings, the structural fix is a platform your whole IT organization can maintain.
They chose speed and self-determination — and a rebuild that ignores that will deserve the revolt. Two of the four approval gates exist for exactly this: the scope gate keeps their workflows' intent intact, and the design gate puts styled directions in front of them before a single page is generated. They keep what they built, conceptually; what changes is that it stops depending on one absent person.
We won't pretend it isn't. Per-seat, FileMaker is cheaper. The comparison that matters is total: recurring re-licensing, server hosting, consultant retainers at market rates, plus the unpriced risk of an unmaintainable critical app. Against a six-figure manual rebuild quote — the going rate for this rescue when done by hand — an extraction-driven fixed bid is the disciplined option. And if the assessment says the economics don't work for your app, the report says so and we part friends, and you keep the report.
They migrate. Container data exports through sanctioned paths — ODBC/JDBC retrieval and scripted export — and existing FileMaker-to-SQL migration tooling has proven the pattern for years. The assessment measures your actual container volume, the migration is verified by count and checksum, and the original file stays archived until you sign off on completeness.
Maybe — and if they do, the assessment is still the best money you can spend, because the DDR-derived specification is the documentation your solution has never had: schema, scripts, security, all written down and readable by any developer, FileMaker or otherwise. Whether you rebuild now or later, you stop being one resignation away from an undocumented black box.
10 · Next step
Export the Database Design Report from FileMaker Pro and send it over. Inside two weeks you get the scored specification, the honest recommendation — rebuild, simplify, or stay — and a fixed price if a rebuild makes sense. Judge the approach on your own solution, not on a slide.
Marc Lehane · Solutions Architect / CTO, Kinetech · [email protected]
Kinetech Cloud · San Antonio, TX · How we deliver · Live Build Console
You are reading Your platform — deeper detail on step 4, Why now?.
That is the pressure. What it costs to answer it is not one number — three things move it.