Rewrite your old FileMaker solution

Got an old FileMaker database system that you're not happy with? Maybe a rewrite of your software will be of greater benefit to you.

If you have an old FileMaker solution that needs a revamp, you may want to consider having the system rewritten by a professional developer. A fresh rewrite can actually save you many thousands of dollars in the long run.

Sometimes, it's just more economical to scrap what you've already got and start over. We've seen many companies come to us that have made the mistake of choosing to stick with their old out-dated FileMaker Pro system for far too long, only to learn that they were much better off starting over.

We don't want you to make this same mistake. We want to help you. In many cases (not always), it's worth considering a complete rewrite. This may seem like a daunting task if you have a large FileMaker system built over the years, but in many cases it's a lot more cost affective to start over.

Here's when you should consider a rewrite

1. If the system was built by an inexperienced developer, chances are you should consider a professional rewrite of your FileMaker system. Would you consider going to an inexperienced doctor, or flying with an inexperienced pilot? No? Then why trust your company to an inexperienced developer?

2. If the system was built prior to FileMaker 7 (even if it has been converted over to a newer version of FileMaker), you may benefit from a rewrite. FileMaker changed significantly when FileMaker 7 was introduced and many older databases have trouble converting over to newer versions of FileMaker and require lots of on-going maintenance.

3. If the system has significant flaws or doesn't really do what you need, it may be easier to start over rather than continue with what you've got.

4. If the system is locked and the original developer cannot be found or wont unlock the system for you then you may need to consider rewriting the system.

5. If the current system is costing you dearly in hidden costs such as missed opportunities or lost productivity, then a rewrite may be more cost effective.

6. If your old system uses features that are no longer supported in newer versions of FileMaker or you are using old third-party plug-ins that are now obsolete, then a rewrite may be the better option.

Here's when you shouldn't consider a rewrite

1. If the old FileMaker system has been developed properly by a good developer and doesn't have many issues, then you may not need to consider a rewrite.

2. If the system was built after FileMaker 7, and it was built properly to begin with then you may not need a rewrite.

3. If the system is too large and will potentially cost too much to rewrite, then it may be best to keep what you've already got and just maintain it. However, it's best to speak to us first because in many cases it's not as complicated to rewrite as you may think.

4. If you just don't have the budget for a rewrite (although it's best to discuss cost with us first in case it's more feasible than you think).

5. If you're in a hurry and can't wait for the system to be re-written.

Contact us today to arrange an assessment

Before we can determine whether rewriting your FileMaker system is going to be more beneficial than maintaining it, we will first need to assess your existing system.