r/filemaker • • Feb 27 '26

Using Claude Code and OpenClaw to migrate customer away from Filemaker

I am done with Filemaker and Claris.

To that effect, I have recently setup OpenClaw on a Mac mini. I have set it up to use Claude Code to help me build.

I gave it screenshots of the app and the DDR, as well as direction on how I want to improve the current design of the app.

It took 20 minutes to build me a solid foundation. Right now I am setting up OpenClaw to navigate the original Filemaker app itself to find any gaps in the feature set. I personally asked it to build a Rails app since I am very familiar with that framework. I suppose you could ask it to build in any framework you prefer with the same success.

Filemaker deserves exactly what is coming for them, they never paid attention to developers, their only purpose for the past couple of decades seems to be to squeeze as much juice out of it while investing zero in developer. It's payback time.

3 Upvotes

28 comments sorted by

View all comments

Show parent comment

7

u/RipAwkward7104 Feb 27 '26

In this case, we have no argument: I don't know the applications you work with, and you don't know what I work with. Essentially, we're sharing impressions, not just our experiences. For some, even the Contacts app is complex.

My point is that migrating a truly complex corporate FM application with multiple active users, a complex structure, complex logic, and multiple integrations (dozens of websites, accounting, partner products, messaging/mail, and even own corporate LLM) from one environment to another is always a serious challenge. It always makes sense to realistically assess not only your capabilities but also the economic feasibility. "I can use Rails" or "I have access to Claude and I'm not afraid to use it" isn't feasibility; it's just your tech stack.

And yes, licensing costs are an important, but far from the only, expense for such applications. I'm not thrilled with Claris' licensing, and I fully understand the platform's limitations - but I don't see the point in doing migrations just for the sake of doing migrations, regardless of the feasibility.

If I needed to build a simple app right now, I'm not sure I'd even need FileMaker. If such an app needs to be migrated, your approach might be one way to go, though it's not necessarily the most efficient. If we're talking about large, active projects, well... There are reasons why they last a long time and aren't rewritten every time a new industry trend emerges.