Online guide
Guide
AI and LLMs Inside FileMaker: What Actually Works in 2026
Production use cases: semantic search, extraction, classification and RAG, with provider choice and UK GDPR notes.
11 min read · Updated April 2026
Migrating Legacy FileMaker to FileMaker Cloud
A practical 2026 guide to moving an old FileMaker deployment to Claris FileMaker Cloud - or to a modern UK-hosted FileMaker Server. Format upgrades, plugin replacement, auth, cutover, costs.
Updated April 2026 · 10 min read · By Neptune Digital
About a third of the FileMaker systems we audit are running on something older than FileMaker Server 19. They still work. They are also blocking a decade of Claris platform improvements - REST APIs, OAuth, Claris Connect, JavaScript integration, Data API - and they usually cost more to change than they should. This guide walks through how we migrate legacy FileMaker solutions to Claris FileMaker Cloud (or to a modern UK-hosted FileMaker Server when compliance makes that the better call).
First: do you actually need to migrate?
Don't migrate for its own sake. Trigger points we consider legitimate reasons to move:
- You're still on FileMaker Server 17 or older (missing 6+ years of security patches).
- You're running .fp7 files (pre-FileMaker 12 format - no longer supported).
- Your integration partner needs the Data API or REST endpoints you don't have.
- You're migrating auth to Azure AD / Okta / Google Workspace and the old server can't do OAuth.
- Your hosting partner is decommissioning your tier, or is no longer UK-based.
- You need SSO + MFA for a compliance obligation (Cyber Essentials, ISO 27001, DSPT).
- Your server is on-prem and the office it lives in is closing or moving.
If none of those apply, a well-scoped Health Check might be a better investment than a full migration.
Cloud vs self-hosted - decide this before anything else
This is the most consequential decision of the project. In 2026, the rough split for UK buyers:
| Dimension | FileMaker Cloud | Self-hosted UK FileMaker Server |
|---|---|---|
| Time to stand up | Hours | Days |
| Data residency | EU (Ireland) - no UK region | UK-only (AWS UK, Azure UK, UK colo) |
| Plugins / Admin API | Restricted | Full access |
| Patching | Claris | You (or your managed host) |
| Accreditation | Inherits AWS SOC 2, ISO 27001 | Cyber Essentials / ISO 27001 via host |
| Typical fit | SMEs, light compliance, fast start | Public sector, healthcare, regulated, plugin-heavy |
| Annual cost (15 users, indicative) | ~£4,200 Claris + £0 infra | ~£3,800 Claris + £1,200–£3,000 UK hosting |
For UK GDPR and compliance specifics, see our FileMaker Security & UK GDPR guide.
The 8-step Cloud migration runbook
- Discovery & inventory (3–5 days). Every file, every plugin, every schedule, every external data source. If it isn't in the inventory, it will surprise you on cutover day.
- File format upgrade. Anything on .fp7 or earlier is converted to .fmp12 and opened in a supported version of FileMaker Pro. Old conversion artefacts (orphaned fields, stale custom menus) get tidied here.
- Plugin audit & replacement. Every server-side plugin is categorised as (a) no longer needed, (b) replaceable with native features, or (c) replaceable with Claris Connect / n8n. See our Claris Connect vs n8n vs Zapier guide for the replacement options.
- Authentication migration. Local FileMaker accounts retired where possible; users moved to Claris ID, Azure AD, Okta or Google Workspace SSO; MFA enforced.
- Parallel environment build. New Cloud (or UK-hosted Server) environment stood up; data restored from a recent backup; all integrations pointed at the new URL in a test profile.
- Integration & UAT. Every script, every integration, every report, every privilege set tested against the new environment. UAT by named business users, signed off against a test matrix.
- Cutover weekend. Live data frozen, final backup taken, data restored to new environment, DNS / client URLs switched, smoke tests, sign-off. Legacy server kept read-only for 30 days as a rollback safety net.
- Decommission & handover. After a clean 30-day hyper-care window, the old server is archived and decommissioned; runbooks, backup strategy and access reviews are handed over to the support team under a monthly support plan.
Typical UK costs in 2026
| Migration band | Typical cost | Timeline | Example |
|---|---|---|---|
| Small | £4,000 – £7,000 | 2–4 weeks | Single-file solution, 5–15 users, no plugins |
| Medium | £8,000 – £15,000 | 4–8 weeks | Multi-file, 15–40 users, 1–2 integrations, 1 plugin to replace |
| Large | £16,000 – £30,000+ | 8–16 weeks | 40+ users, multiple integrations, plugin-heavy, regulated data |
Full day-rate and project-band breakdown in our UK FileMaker Cost Guide.
Common pitfalls we see
- Plugin surprises on cutover day. Always solved by doing the plugin audit in step 3, never in step 7.
- Users who don't know their Claris ID / SSO password. Plan a reset window and a user comms before cutover.
- Integrations hard-coded to old server hostname. Change them first, in parallel, long before the cutover weekend.
- Schedules missing after migration. Cloud reschedules are restricted - document every schedule before you touch anything.
- Backup strategy not thought through. Cloud backups and self-hosted backups are fundamentally different; design the new one explicitly.
- No rollback plan. Keep the legacy server running, read-only, for 30 days post-cutover. Don't decommission until the new environment has gone through a month-end cleanly.
When to migrate to UK-hosted Server instead of Cloud
We default to recommending FileMaker Cloud for clients with no unusual compliance requirements and no heavy plugin dependencies. We recommend UK-hosted FileMaker Server when:
- Your sector requires UK data residency (NHS, public sector, defence-adjacent, legal).
- You rely on server-side plugins that don't have a clean Cloud replacement.
- You need Admin API for DevOps automation Claris Cloud doesn't expose.
- You have an ISO 27001 or Cyber Essentials Plus accreditation tied to your infrastructure.
- You want predictable cost at scale - Cloud's per-user model flips cheaper for self-host above roughly 40 users.
See also - FileMaker Security & UK GDPR, Best FileMaker Developers UK (2026), and Neptune Digital managed FileMaker hosting.
FileMaker Cloud migration FAQs
Generally, anything still running on FileMaker Server 17 or older, or on a .fp7 file format, or on a solution that hasn't had a major architectural refactor since before 2019. These systems work, but they lock you out of features newer Claris releases ship (OAuth/SSO, REST API, Data API, JavaScript integration, better performance), and every year they drift further from what modern FileMaker developers build against. A legacy system isn't broken - it's just expensive to change.
It depends on compliance, integrations and customisation. FileMaker Cloud is faster to stand up, maintained by Claris, inherits AWS SOC 2 / ISO 27001, but runs in the EU (Ireland) region with no UK-dedicated region as of 2026, and restricts server-side plugins and Admin API access. FileMaker Server on UK infrastructure gives you full control - Cyber Essentials inheritance, plugins, Admin API, on-prem if needed - at the cost of you (or your managed host) being responsible for patching and uptime. Healthcare, public sector and regulated finance clients usually self-host in the UK; SMEs often prefer Cloud.
For a well-maintained, modern solution already on FileMaker Server 19/20/21 the actual cutover is usually a weekend. The preparation - upgrading the file format, testing integrations, rebuilding authentication against Claris ID, validating backup strategy - takes 2–4 weeks for most systems, longer if the solution hasn't been touched in years. Plan 4–8 weeks end-to-end for anything with integrations or more than 10 files.
Server-side plugins are not supported on FileMaker Cloud - this is the single most common migration blocker. Common plugin use cases (SMTP, PDF generation, scripted ODBC, server-side scheduling) typically need to be re-implemented using native features that Claris has added since 2020 (Insert from URL for REST, native PDF, OAuth, Claris Connect for integrations) or replaced with Claris Connect / n8n / Zapier flows. We scope this work explicitly before quoting any Cloud migration.
They come across, but Cloud strongly favours Claris ID (or SSO via Azure AD / Okta / Google Workspace) over local FileMaker accounts. The migration is a natural moment to retire per-user local accounts, move everyone onto SSO with MFA, and tidy up privilege sets. Plan for a short password-reset/onboarding window with end users.
Most SME migrations land between £6,000 and £18,000 depending on solution complexity, plugin usage, integrations and how much code tidy-up is needed along the way. Plus Claris FileMaker Cloud subscriptions (billed per user connection) and, if you go the other way, your UK hosting costs. See our full UK FileMaker cost guide for numbers.
For most systems, yes - we do a parallel-run cutover. We stand up the new Cloud (or UK-hosted) environment, replicate the data, cut over in a planned window (usually a Friday evening or weekend), with a rollback plan to the legacy server if anything goes sideways. True zero-downtime is possible for larger engagements with read replicas, but rarely worth the extra engineering cost for FileMaker workloads.
For SMEs with modest compliance needs and limited in-house IT, yes - it removes a class of problems (patching, disk, backups, OS drift) that is disproportionately painful on FileMaker. For teams with UK-only data residency requirements, complex plugin dependencies, or an existing strong hosting partner, self-hosted FileMaker Server on UK infrastructure often remains the better call. Both options are credible; the decision is almost always about compliance and integrations, not price.
