Knowledge Base

A FileMaker upgrade can affect more than the FileMaker Pro application installed on each workstation. Testing should cover the server, operating systems, plug-ins, integrations, scripts, reports, and the daily workflows your staff depends on.

Before upgrading, we will review the versions of FileMaker Server, Pro, Go, operating systems, plug-ins, and connected services. An upgrade should not begin until each required component is supported and a sequence has been established for updating the server and workstations. 

A verified backup should be completed before production systems are changed. We also recommend documenting how the previous environment will be restored if a significant problem is discovered during or immediately after the upgrade.

Identify the tasks your staff relies on every day, including creating records, searching, printing, emailing, importing, exporting, and producing reports. These workflows should be tested with representative users so that permission-based or department-specific issues are not overlooked. Any connection to accounting software, email providers, web services, APIs, payment systems, scanners, printers, or third-party plug-ins should be tested. 

A FileMaker feature may work correctly while an external component fails because of a changed security requirement or unsupported software version. Run important scripts and reports using realistic data, including processes that execute on FileMaker Server. Scheduled scripts, server-side imports, PDF generation, container storage, and automated email often require separate testing from ordinary workstation use.

Major upgrades should be scheduled when users can stop work and when key staff are available to test after the change. Portage Bay Solutions can help prepare the test plan, coordinate the rollout, and address issues before the upgraded system is returned to normal use.