If we have a FileMaker deployment that we want to migrate to the cloud, you have to make several core considerations.įor example, you may only consider a re-purchase strategy if you plan to replace your FileMaker application with something else. As a Claris Platinum Partner, we have a depth of experience in helping SMBs transition their FileMaker applications to the cloud and want to share our insights with you. Each application in their tech stack requires a specific strategy and level of prioritization, and FileMaker is no exception. Many SMBs are more comfortable moving resources to the cloud in batches instead of going “all-in,” defined as a hybrid approach to cloud migration. You might also employ more than one strategy for different infrastructure and applications.

No one strategy is better than any other, necessarily your specific situation should dictate your strategy.

Retain: keeping what you have and revisiting at a later timeĮach of these strategies represents different options with a range of cost implications.Retire: removing applications that are no longer needed from your tech stack.Re-Purchase: moving from perpetual software license to a software-as-a-service model.Re-Factor or Re-Architect: completely rewriting an application in cloud-native technologies.Re-Platform: making minor adjustments to better leverage benefits of cloud services.Re-Host (“lift and shift”): moving existing infrastructure and recreate it in the cloud.As AWS consultants, we strive to help each client understand how a cloud-first strategy can benefit their business and built a custom plan to help them launch a cloud migration. However, many of our clients, mostly SMBs, are still trying to navigate the possibilities and plan their approach. The big enterprises are already fully migrated or working hard at completing the transition. In 2021, cloud data centers will process 94% of workloads ( Cisco).

Filemaker pro cloud migration