"Replace it" is what the person pitching it sells.

A Salesforce partner will tell you the answer is Salesforce. A rebuild shop will tell you the answer is a rebuild. A FileMaker-only shop will tell you to stay. None of them are lying — their recommendation comes out the same regardless of what your system needs, because it's the recommendation their business depends on. The one you can trust is the one that could have gone the other way.

I build in and out of FileMaker. When I tell you to replace it, I'm turning down the smaller, safer job of extending what you already have. That's the whole reason a second opinion is useful here.

What the pitch gets right — and what it leaves out.

The pain is usually real. Something the business needs isn't happening: a customer portal, mobile access for the field, an integration with another system, a dashboard nobody can pull out of FileMaker. That part of the pitch is honest.

What the pitch tends to leave out is the rest of the picture: the cost of rebuilding fifteen years of business rules buried in your current system, the option to add the missing capability without replacing anything, and the value of the working system you already own and your staff already know.

The real question is usually narrower than "replace everything."

"We need to replace FileMaker" almost always turns out to mean "we need one thing FileMaker isn't giving us." Name that one thing out loud and the decision changes shape. A portal, a mobile workflow, a payment form, a live dashboard — each of these can be added next to the FileMaker you already run, without a migration. Your staff keep the system they know; the missing capability shows up as a new piece beside it.

That's the extend-instead path, and it resolves more of these situations than a replacement does. Here's how it works, and here's a worked example.

Most "replace the whole thing" pitches are really "we're missing one thing." Find the one thing first.

When replacing it is the right call.

Sometimes the pitch is right. Licensing takes a real bite out of the budget and keeps climbing. The business has outgrown what FileMaker does without a fight — many people working at once, connections that have to happen instantly, web screens for lots of customers. Hiring or keeping a FileMaker developer has gotten hard for your situation. An acquisition is on the horizon and clean, portable data is part of the business's value. When one of those is true, leaving is a sound decision — done as a staged project, with the current system running the whole time, not a rebuild all at once. Here's what leaving in stages looks like.

How to pressure-test the pitch.

Five questions sort a real recommendation from a sales reflex. Ask whoever is pitching:

  • What, specifically, can FileMaker not do here? A concrete gap, not "it's old."
  • Did you price the option of adding that capability without replacing the system?
  • What happens to fifteen years of business rules and data — and who verifies it all made it across?
  • Is this staged, with the current system running the whole time, or a cut-over-and-hope?
  • What's your stake in the platform you're recommending?

Vague answers mean it's a reflex. Specific answers that still point to leaving mean it's probably a real fit — and now you can weigh it honestly.

What to do next.

The free triage call is a second opinion from someone who builds both in and out of FileMaker. Describe the pitch you're getting and what the business actually needs. I'll tell you whether replacing is the right call, whether extending solves it for a fraction of the cost, or whether staying put is the honest answer. If the pitch is right, I'll say so.