FileMaker system replacement
When a FileMaker system still works, but every change feels risky.
I help businesses decide whether an ageing FileMaker workflow should be rebuilt as owned web software, then map the data, scripts, layouts and edge cases before anything is replaced.
Problem diagnosis
FileMaker may not be wrong. It may simply have become legacy for this business.
- The system depends on old scripts, layouts or specialist knowledge that is hard to replace.
- The rest of the business now runs in web tools, but FileMaker still holds the operational truth.
- Access, integration, reporting, licensing or hosting decisions are now becoming strategic rather than routine.
The risk is dependence on a specialist platform and a small number of people when the workflow has become too important to be mysterious.
Responsibility
The honest question is whether to upgrade, keep or rebuild.
I do not treat FileMaker as automatically wrong. The first job is to understand what the system does, what still fits, and what would be safer as owned software outside the platform.
What I would build
The first useful version would be concrete.
- 01
A map of the FileMaker workflow
Layouts, scripts, tables, reports, users and manual exports are documented before replacement decisions are made.
- 02
A replacement data model
The operational records and relationships are preserved without copying old structure blindly.
- 03
Core browser workflows
The most important tasks can be rebuilt as web-based screens with clearer access and handover.
- 04
Data migration checks
Old records are moved carefully, with review points for fields that do not translate cleanly.
- 05
Integration routes
Manual exports can be replaced only where a safer connection is useful and maintainable.
Fit filter
Probably right, probably not.
Probably right when…
- FileMaker runs a real business workflow.
- The owner is considering replacement, not just support.
- Access, integration, maintainability or platform dependency is now painful.
Probably not me when…
- You only need FileMaker hosting, admin, upgrade or developer support.
- An experienced FileMaker specialist is obviously the right answer.
- The system is small and still fits the platform well.
First step
Start with diagnosis, not a big commitment.
The first step is a sober map of the current FileMaker system and the reasons replacement is being considered.
£150 per hour plus VAT where applicable. Two hours minimum for new clients. No retainer, no minimum term, no lock-in. You own everything I build.
Useful things to send before a call
- Screenshots or a walkthrough of layouts
- Exports or schema information if available
- Scripts, reports and integrations that matter
- The access, licensing or handover problems driving the decision
Objections
Questions this page should answer before you email.
Is FileMaker obsolete?
No. The question is narrower: whether this particular FileMaker system still fits the business risk, access and integration needs.
Can FileMaker data be migrated safely?
Often, yes, but it needs mapping and checks around relationships, history and fields that have business meaning.
Could the right answer be to keep FileMaker?
Yes. If upgrade or specialist support is the better route, that should come out early.
Next step
If this looks like your problem, send me the awkward bits.
The useful first email is short: what is breaking, what product or process cannot handle it, and what working would need to mean.