Knowledge Base

A FileMaker system can continue operating while small technical and workflow issues accumulate in the background. Periodic reviews help identify those concerns before they become urgent, while also confirming that the system still supports the way your organization works.

A general FileMaker system review should be completed at least once a year, even when users are not reporting major problems. The review provides an opportunity to identify unsupported software, backup concerns, performance trends, security changes, and business requirements that have developed gradually.

Do not wait for the annual review when your organization adds many users, changes departments, introduces remote work, replaces an accounting system, adopts new security requirements, or changes key workflows. These changes can affect licensing, server capacity, privileges, integrations, and the design of the solution. 

A review should occur before upgrading FileMaker Server, FileMaker Pro, the operating system, server hardware, or important plug-ins. Compatibility and testing requirements should be established before production systems are changed. 

Repeated slowdowns, disconnections, failed schedules, unusual backup growth, or increasing support requests are signs that the system should be reviewed promptly. Addressing the underlying cause is usually more effective than repeatedly treating individual incidents.

The scope may range from a server-maintenance review to a broader assessment of schema, scripts, layouts, security, and business workflows. Your Portage Bay Solutions project manager can help determine what level of review is appropriate based on the age, complexity, and current use of your system.