Rescue the FileMaker system, or rebuild it?
Rescue means the FileMaker file you already run stays the system of record, and the first project is the bottleneck in front of you. A rebuild means a new file, or a new platform, and it is not the default. iRusty is Russell Haney’s practice in Brunswick, Georgia. This guide does not cite a client or a success rate.
Start from the system you have
Most inherited FileMaker systems are not empty. They hold orders, jobs, customers, and the scripts people are afraid to touch. Throwing that away is a larger risk than fixing the part that hurts.
Name the bottleneck
A slow report, a fragile script, a confusing layout, a broken import, or a stuck approval is a rescue project. “Make it modern” is not specific enough to choose rescue or rebuild.
Protect the file first
Passwords and production files do not belong in ordinary email. A first look uses redacted screenshots, a sanitized export, or a written description, plus a backup-aware plan before anything in production changes.
AI is not a reason to rebuild
Practical AI drafts against the records FileMaker already trusts. It does not require a new database. If the file is unstable, rescue comes before any assistant.
Common questions
Is a FileMaker rebuild the safer default?
No. If FileMaker already holds the business, the safer default is rescue: one bottleneck, a backup-aware plan, and a fix the team can review. A rebuild is a different project and should be named as one.
When is a rebuild the honest choice?
When the file cannot hold the work anymore: the relationships no longer match the business, nobody can change it safely, or the team has already decided to leave FileMaker. That decision should be stated. It should not be disguised as an integration.
Does rescue include AI?
Not as the first move. Rescue stabilizes the system. Practical AI comes after a person can review a draft against fields the team trusts. FileMaker stays the system of record either way.
How do rescue and rebuild differ?
The rows below are the decision, not a score. Nothing here is a measured client result.
| Question | Rescue | Rebuild |
|---|---|---|
| What stays | The FileMaker file that already runs the business. | A new file, or a different platform, replaces it. |
| First project | One bottleneck the team already knows. | A new structure for the whole operation. |
| Main risk | Changing a live script or layout without a backup and a review. | Losing rules that were never written down outside the old file. |
| When it fits | The file still holds the work, and one part of it hurts. | The file cannot represent the work, or the team has decided to leave it. |
| Where AI fits | After the records are stable enough for a person to review a draft. | Not as a disguise for the replacement. Say if the system of record is changing. |
The public first step for one problem is the $500 Rescue Diagnostic. It is a written look and a quote, not a production change. Other rates are on the pricing page.
Start with the problem in front of you.
Get a fixed-price $500 Rescue Diagnostic, or book a free 20-minute call.
Call (912) 736-3477 · Email russellhaney@irusty.com
Send the problem, not passwords or production files.
After delivery, keep it healthy with a monthly care plan.