walkingtoyou and FileMaker
Modernising FileMaker
Your FileMaker solution has grown with your business over many years. It understands the way you work better than any off-the-shelf software ever could — and that is precisely its value. Yet sooner or later, a structure that has grown organically starts to hold you back more than it carries you forward.
When the database stops keeping pace
Plenty still works — but does it still run smoothly ?
Your FileMaker system is dependable in day-to-day use: orders are logged, customer records are kept up to date, and invoices and reports appear at the touch of a button. Even so, you sense that things no longer run quite as effortlessly as they once did.
New requirements can only be accommodated through workarounds. Changes get put off, because no one is quite sure what is connected to what behind the scenes. Over the years, scripts and layouts have been added quickly — without any consistent structure. Interfaces to other systems are missing, so data ends up back in Excel — the very thing a database is supposed to make unnecessary.
This is where we come in, with more than 25 years of FileMaker development behind us. We are not looking for a quick replacement. Instead, we sit down with you to look at your real-world processes and structures, and work out how to make your FileMaker database fit for the years ahead — one step at a time.
Does any of this sound familiar?
Warning signs
The more of these points make you nod, the more worthwhile it is to take a joint look at your solution:
One person, one risk. Only one mind truly understands the relationship graph, the scripts and the dependencies. If that person is unavailable, all further development grinds to a halt.
Every change becomes a leap of faith. Adjustments are postponed because no one can reliably predict the side effects in the jungle of layouts and scripts.
Excel as a secret second database. For analyses and reports, the team falls back on Excel, because going through FileMaker feels too cumbersome or unfamiliar.
Data moved by hand. Information is copied manually between FileMaker and your ERP, CRM or accounting system — slow and prone to error.
Onboarding takes far too long. New team members need weeks to find their way around a solution that no one has documented.
No map of the system. There is neither clear documentation nor a contingency plan for when the server goes down.
Security on trust alone. Backups, permissions and access rights have not been reviewed in years.
No one knows exactly what it does. Which processes are actually covered, and everything the database is really capable of, is no longer something anyone can say for certain.
Modernising FileMaker — there is more than one way
Four routes into the future — we find the one that fits you
Switching to off-the-shelf software rarely solves your individual requirements; it simply replaces them with someone else's. Your business works differently from every other, and today that process knowledge lives inside your FileMaker database. Rather than throwing it away, we build on it. Which of the following routes is the right one is something the analysis reveals — never gut feeling.
Modernise
The right route when the underlying logic is sound and the solution works reliably, but the interface, maintainability or connectivity are no longer up to date. We rework the interface, build clear and intuitive navigation, simplify maintenance, and bring security and stability back up to current standards. Your solution stays — but tidied up, documented and optimised.
Extend
The right route when FileMaker should remain the heart of the system, but individual tasks are better handled elsewhere. We develop precisely fitted interfaces to ERP, CRM, accounting or web systems — via the FileMaker Data API if you wish. Your core data stays in FileMaker, while you also draw on the strengths of other tools.
Migrate
The right route when it no longer makes technical sense to keep developing the existing solution. In that case we transfer your data into our standard software, blue.project — with proven, clearly defined processes that prove their worth in many companies every day. If a feature is missing, we build it specifically for you. The result is a stable, modern system founded on more than 25 years of experience.
Rebuild
The right route when blue.project is not the right fit, or old structures are holding you back too much. A fresh FileMaker build lets you define processes clearly, simplify workflows, and rethink the architecture properly from the ground up — modern, flexible and built to last, tailored exactly to your needs today and in the years to come.
Our approach — the steps to modernising your FileMaker database
Analyse. Understand. Develop.
We understand your solution before we change it.
Most FileMaker solutions have grown over time — without an overarching plan. That is precisely why we never begin by asking about the target system, but with an honest look at what you have today.
01
Current-state analysis
We capture the entire structure of your database: tables, fields, relationships, layouts, scripts, calculations and interfaces. We record not only the technology, but every point where you hit friction in everyday work. The result is a clear, honest picture of your solution — including security, backups and failure scenarios.
02
Target-state analysis
Your organically grown database is not dead weight; it is concentrated process knowledge. Building on the current-state analysis, we work with you to draw up a requirements specification and set out the realistic ways forward. We think not only about today, but about the next ten years — so that we set the structural course correctly, rather than just patching symptoms.
03
Routes into the future
Both analyses come together in a clear, readable report setting out the recommended work. We prioritise it together: what is urgent, what can wait, and in what order a sustainable future is best built. Throughout, sovereignty over your data always stays with you — no lock-in to a single provider.
04
Flexible delivery
We develop in modules and in clearly defined steps. For us, software development is not a one-off project but an ongoing process. You set the pace, the order and the budget — all plannable and transparent. And because we insist on a clean structure, you will be able to maintain your solution yourself later on.
New possibilities from old data
What you are left with
From grown-by-accident back to thought-through
What remains after modernisation is, above all, clarity. The interface looks tidier — but more important is that the inner workings of your solution become transparent again. You and your team can explain which data goes where, and where a change takes effect. Adjustments can be estimated, rather than avoided out of caution. The know-how lives in the documentation, not in a single head alone. New wishes are implemented in a planned way, without a makeshift fix alongside. In this way, your hard-won application supports you once again — both in everyday work and through the next stages of growth.
Why walkingtoyou
Bespoke software that is 100% yours
Despite AI tools and a flood of "ready-made" solutions, software that works exactly to your requirements remains unbeatable. We build precisely that kind of solution — and we make sure it belongs to you.
Full data sovereignty, no lock-in
Your data and your processes remain under your control at all times. You are not dependent on any single provider.
You can keep maintaining it yourself
We leave behind a clean, documented structure. So your solution stays adaptable — even without us.
A genuine partner, not a one-off project
walkingtoyou works alongside you over the years, from the first conversation to ongoing development — modular, plannable and guided by your priorities.
Flexible hosting
Whether on a virtual Linux or macOS server on your own premises, or in the FileMaker Cloud with walkingtoweb — you decide where your data lives.
Common questions about modernisation
FAQ
FileMaker (today Claris FileMaker) has been a platform for bespoke database applications since 1985. Businesses use it to model their own processes — stock control, project management, reporting, CRM or costing — exactly as they actually work. That is precisely what makes FileMaker so powerful: the solution adapts to your business, rather than your business adapting to off-the-shelf software.
-
When should I modernise my FileMaker solution ?
When your solution costs more energy than it saves. Watch for these patterns: the system effectively runs inside one person's head, and no one else dares touch it; routine tasks are done by hand, even though the database ought to take them off your plate; and exchanging data with other programs only works through workarounds. You don't have to wait for a breakdown — the sooner we take a look, the more room you have to manoeuvre.
-
What is the difference between modernising and replacing ?
Modernising means keeping FileMaker as the foundation: we untangle the structure, set it down in writing and make it more robust — which makes sense as long as your underlying logic still holds and the platform still fits. Replacing means changing the foundation — for example to our standard software, blue.project — when your existing structure simply can no longer keep up. Which route is right is answered by the analysis, not by gut feeling.
-
Will we have to halt operations for this ?
No. We deliberately work in clearly defined steps, with no "big bang". Your solution stays in use while we modernise it area by area — according to your priorities and your budget.
-
What does a FileMaker modernisation cost ?
A serious figure is only possible after the current-state analysis — flat-rate numbers are guesswork. What drives the effort: how large and intricate your application is, how well it is documented today, how many external systems are involved, and whether we are simply tidying up workflows or setting them up afresh. That is exactly why, with us, the analysis comes first — long before we talk about budget.
-
Do we keep control of our data ?
Yes, completely. Your data and your process knowledge stay with you at all times. We don't build dependencies; we build a clean foundation that you can also maintain yourself. Whether your data sits locally on a Linux or macOS server, or in the FileMaker Cloud with walkingtoweb, is your decision.
-
Is FileMaker still future-proof today ?
The platform: yes. Claris develops FileMaker continuously — most recently with AI features, open APIs and a fixed release cadence. The more important question is the second one: will your own solution still carry you through the coming years? A well-maintained, well-documented application lasts a long time without trouble. The risk only arises when all the knowledge is undocumented and depends on a single person — and that is exactly where we come in.
-
Do you work with FileMaker plugins ?
As rarely as possible. FileMaker offers enormous depth of functionality out of the box, covering almost every requirement — without additional dependencies. Every plugin is a component that has to be licensed, maintained and re-checked separately at each version change. We use plugins only where they bring real added value and cannot be solved cleanly with built-in tools. That keeps your solution maintainable and independent.
