Claris is discontinuing Claris Studio, effective March 15, 2027. If you have solutions running in Studio today, your apps and forms will keep working right up until that date, and FileMaker, Claris Connect, and Claris MCP are not affected.
As a Claris Platinum Partner and FileMaker Growth Partner of the Year for the Americas, we have helped organizations move workflows between platforms for over two decades. In this guide, we will walk you through what happens to your data, shared links, and licenses, as well as the four paths available to you to move forward. Here is what you need to know before you plan the work.
Your Claris Studio Data Gets Deleted
You're working with a hard deadline, not a rolling one. Claris Studio runs as normal through March 15, 2027. Once that date hits, anything still sitting in Studio gets permanently removed under Claris's retention policy.
That risk stays contained to Studio itself. Your FileMaker file is a separate system, and nothing about it changes. What's actually at stake is anything that only ever existed inside Studio:
Submitted form responses
Data collected from customers or vendors outside your FileMaker file
Any spreadsheet a department builds directly in Claris Studio without syncing it back
CSV Is the Only Way Out
The documented way to get your data out is the CSV table export in Claris Studio, table by table.
CSV gets your rows out. It does not get your work out. A CSV file is data and nothing else, so everything you configured on top of that data stays behind. Spreadsheets, form views, kanban boards, dashboards, and custom views are all configurations, not records, and they do not travel with an export.
Plan the export as a project, not a click. The CSV download is the easy part. Rebuilding the views and forms that made the data usable is the actual work, and it is worth scoping now while you still have a working system to reference.
Every Claris Studio Link You Shared Goes Dead
Claris Studio URLs will stop working after March 15, 2027, and there will be no redirects for individual form links. A customer clicking on an old intake form will get an error, not your new form.
It is worth thinking about where those links actually live:
Your website
Email signatures
Automated FileMaker notifications
Printed QR codes and vendor onboarding packets
A partner site you do not control
Finding them all is usually harder than replacing them, so start that list early.
There Is No Pricing Adjustment
Claris Studio was included in the FileMaker license agreement, and there is no price change as a result of its removal. If you moved to a Max tier partly for unlimited Claris Studio shared views, your cost stays the same.
Practically, that means the budget for replacing Claris Studio is a new budget. Nothing frees up when it shuts down, which is worth knowing before you plan the work.
Your Options
We build in FileMaker and custom web applications, so the honest answer is that the right destination varies from one Claris Studio asset to the next. These are ordered from the most native path to the least native path.
FileMaker WebDirect
The native FileMaker path for authenticated, external-facing access to your data. It runs directly from FileMaker Server with nothing extra to buy, and your existing security model comes with it. Strong fit for known users; weaker for high-volume anonymous traffic. It is worth confirming your server can handle the added WebDirect load.
A Custom Web App on the FileMaker Data API
Where WebDirect falls short, usually on public traffic or a customer-facing experience that has to look and feel like your brand, build the portal or form as a real web application that talks to FileMaker through the Data API. You control the design, the user experience, and the scale, and nothing about it depends on a product roadmap decision you do not make—the highest-effort and only option that permanently removes this category of risk.
Third Party Form Tools
Typeform integrates with FileMaker through Claris Connect. JotForm and Tally can connect through Claris Connect or the FileMaker Data API. Good fit for lightweight or anonymous public data collection where you do not need much control over the experience. The form itself is easy. The integration is where these tend to break, so plan for the field mapping and error handling.
Export and Retire It
Pull the CSV, retire the workflow, and go back to how it was handled before. Good fit if Claris Studio was a pilot that never became load-bearing. Be honest about whether that is true. The teams most at risk are the ones who find out in February 2027 that a Claris Studio form is the front door to their intake process.
Most organizations end up using more than one of these. A customer portal goes to WebDirect or a custom build; a one-off signup form goes to a third-party tool; and a few abandoned views get retired.
Summary
March 2027 feels far off until you map out the actual work: rebuilding every view and form, updating every published link, and running both systems in parallel long enough to trust the new one. That timeline shrinks fast.
Here's what you're working against: your data is deleted at shutdown; CSV exports rows but not your views or forms; shared links stop resolving with no redirects; and none of this reduces your license cost.
Start with the assets that have links already out in the world. Those are the ones that break loudest.
Schedule a Claris Studio Migration Review with our team. We'll map each of your Claris Studio workflows to the right destination and get you there ahead of the deadline!
Did you know we are an authorized reseller for Claris FileMaker Licensing?
Contact us to discuss upgrading your Claris FileMaker software.
