Migrate from FileMaker Server to FileMaker Cloud

Before you migrate from FileMaker Server to FileMaker Cloud, make sure you understand the differences in license model, authentication, user management, and available features.

Plan your migration

Use the following steps to plan and prepare for your migration.

Step 1: Understand FileMaker Cloud differences

It’s important to understand the following differences between FileMaker Cloud and FileMaker Server:

  • Authentication and licensing model: To create a FileMaker Cloud instance or to access apps hosted by FileMaker Cloud, each user needs to be a licensed FileMaker Cloud user with a unique Claris ID or external identity provider (IdP) account. (Claris ID is an integrated sign-on system used across several Claris products and services.) FileMaker Cloud doesn’t use a concurrent licensing model.

  • Managed service: For FileMaker Cloud, Claris manages the server. You don’t have direct access to the server.

  • Plug-ins: FileMaker Cloud doesn’t support server-side plug-ins.

  • SSL certificates: Your FileMaker Cloud host uses a custom, Claris-managed SSL certificate.

  • ODBC/JDBC: FileMaker Cloud can connect to supported external ODBC (but not JDBC) data sources. ODBC clients connecting to FileMaker Cloud as a data source isn't supported.

  • Backups: Automatic backups are created every 20 minutes. You can also create a manual backup, but you can’t create backup schedules.

  • FileMaker WebDirect homepage: FileMaker WebDirect users will go directly to the FileMaker Cloud WebDirect launch center.

  • User management: You need to use Claris Customer Console to invite and manage FileMaker Cloud users.

  • Custom Web Publishing: FileMaker Cloud doesn't support Custom Web Publishing with PHP or XML. Consider using the OData API or the FileMaker Data API instead.

Step 2: Create an inventory of your current FileMaker Server environment

  • List all your hosted .fmp12 files. Note the size of the files and any dependencies.

  • Write down the encryption password for each encrypted file and store it in a secure place.

  • Identify all users and their privilege sets, and document how they currently authenticate.

  • Document server-side schedules and scripts. Note what they do and any external resources they access.

  • List all plug-ins. Identify which plug-ins are installed on your FileMaker Server and used by your custom apps.

  • Check for external data sources (ESS, ODBC, JDBC) and note how they are configured.

  • Review your current FileMaker Data API and OData usage and configuration.

  • Note any custom SSL certificates you are currently using.

  • Identify any custom FileMaker WebDirect homepages.

Step 3: Back up your current FileMaker Server

Perform a full backup of all your databases. See Understanding backup options.

Step 4: Review your custom apps for FileMaker Cloud compatibility

  • Plug-ins: If your custom apps rely on server-side plug-ins, find alternative integration solutions.

  • Container data: FileMaker Cloud only supports secure storage of externally stored container data. If you have container fields configured with open storage, you must transfer the container data to secure storage using FileMaker Pro. See Transferring container data.

  • Server-side scripts: Review all server-side scripts. Script steps that interact with the operating system will likely fail or need modification.

  • External data sources: Ensure your external data sources can be accessed from FileMaker Cloud. You may need to configure firewall rules or VPNs for your external databases.

  • File references: Update any hard-coded file paths within your custom apps that point to local server resources.

  • CLI commands: The fmsadmin command line interface (CLI) commands are not supported in FileMaker Cloud. If you use the Perform Script on Server script step with an fmsadmin command in your script, you might see FileMaker error code 812, "Exceeded host's capacity."

Step 5: Choose the best time for the migration

Determine the best time for the migration to minimize impact on users. Communicate this clearly to all stakeholders.

Set up FileMaker Cloud and add users

  1. Set up FileMaker Cloud.

    Use your Claris ID to sign in to Claris Customer Console (console.claris.com), then set up your FileMaker Cloud instance. See Set up FileMaker Cloud.

    Claris Customer Console is a web application for working with FileMaker custom apps hosted by Claris FileMaker Cloud and for managing FileMaker Cloud teams. Use this console to also manage Claris ID accounts, users, groups, hosts, settings, and FileMaker Cloud subscriptions.

  2. If needed, set up authentication with an external IdP so that users can sign in with that provider account instead of Claris ID.

    See Using an external identity provider to authenticate Claris ID accounts.

  3. Invite users to your FileMaker Cloud team.

    Use Claris Customer Console to invite users to join your FileMaker Cloud team. If they don’t have a Claris ID, they will be prompted to create one. See Inviting users to a team.

    You can also create groups to organize Claris ID accounts in your team and allow Claris ID users in each group the same access privileges to team resources. See Creating or changing a group.

Migrate your custom apps to FileMaker Cloud

To migrate your custom apps, you must download your databases from FileMaker Server, then use FileMaker Pro to upload them to your FileMaker Cloud host.

Note  You must have a Claris ID account and be a team manager to upload a database file.

  1. In FileMaker Pro, create account access entries that authenticate users via the Claris ID identity provider or the external identity provider (IdP) for each database to upload. See Creating and editing account access.

  2. In FileMaker Server Admin Console, close the databases you want to download to prevent data corruption and ensure you get the latest data. See Closing hosted files.

    You can use FileMaker Server Admin Console to send warning messages to connected clients beforehand. See Sending messages to clients of a hosted database.

  3. In FileMaker Server Admin Console, download the databases to a local destination. See Downloading database files.

  4. In FileMaker Pro, upload the databases to FileMaker Cloud. See Uploading, encrypting, and opening database files.

  5. Use FileMaker Cloud Admin Console to configure the FileMaker Data API and OData and set up external ODBC data sources, if needed. See Managing connectors.

Notes 

  • If you upload an unencrypted custom app, FileMaker Cloud automatically encrypts the app and creates an encryption password. See About encryption passwords.

  • When you download a database that uses external storage for container data from FileMaker Server, the directory structure of database and container data is preserved. When you then upload the database to FileMaker Cloud, all files (including container data) are uploaded to the default storage destination.

  • In FileMaker Server, if you use an additional database folder for databases that include externally stored container data, you can specify a separate folder for this container data. FileMaker Cloud doesn’t allow you to specify destination database folders; all files are uploaded to the default storage destination.

  • To use the FileMaker Admin API to upload databases, See Uploading custom apps to FileMaker Cloud.

Test your migrated custom apps and settings

After you migrate to FileMaker Cloud, make sure to check your migrated custom apps, settings, and configuration.

  • Signing in to Claris ID: Test with different user accounts (Claris IDs) and privilege sets.

  • Data entry, modification, and deletion: Ensure all operations work correctly.

  • Scripts: Test all client-side and server-side scripts.

  • Layouts and reports: Verify display and printing.

  • External data sources: Confirm connections and data retrieval.

  • FileMaker WebDirect: Test access and functionality using a web browser.

  • FileMaker Data API and OData: Verify all your integrations are working.