Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
Every hosted form backend can shut down, get acquired, or change its pricing overnight. Here are the questions worth asking before you depend on one, regardless of which vendor you pick.
Get an instant summary, key takeaways, action items, and answers to your questions about this article.
Before depending on any form backend, confirm you can export your submission history in a usable format at any time, understand how long they retain your data and files, and know roughly what notice you'd get before a shutdown or major change. Treat these as due-diligence questions for any vendor, not just the one you're currently using.
Hosted services shut down. They get acquired and sunset. They quietly stop investing in a feature you built your workflow around. None of that is a reason to avoid using one — it's a reason to ask a few questions up front, regardless of which form backend you're evaluating.
This is the question that matters most. If a vendor disappeared tomorrow with no warning, could you still retrieve six months of submission history? Look specifically for a self-serve export — a CSV download you can trigger yourself — rather than an export that requires opening a support ticket and waiting. A feature you've never actually tried is not a safety net; test it once when you set the account up, not the week you need it.
Ask, or look for, answers to: How long are submissions kept while your subscription is active? What happens to that history if you downgrade to a free tier or cancel — is it deleted immediately, or kept for some window? Are uploaded files retained on the same schedule as the submission records they're attached to, or separately? A vague answer to any of these is worth following up on before you route business-critical inquiries through the service.
Terms of service usually reserve the right to deprecate a feature or shut down with some notice period, often 30 days, sometimes less. That's rarely advertised at signup — it's buried in the legal terms. It's worth a five-minute read before you build anything you couldn't quickly replace.
None of this is specific to any one form backend, including FormBridge. It's the same due diligence worth applying to any tool a business depends on without owning the infrastructure underneath it.
Whether you can get your submission data out in a portable format, like a CSV export, at any time without needing the vendor's cooperation after the fact. That's the difference between a temporary inconvenience if they shut down and a genuine data-loss event.
Somewhat less. If the service is only relaying submissions to your own inbox, that data already lives in your email. The bigger risk is data that only lives in the vendor's dashboard: file uploads, submission history, and any routing or automation you've configured.
At least once when you first set up the account, and again any time you make major changes to your forms. An export option you've never tried is a theoretical safety net, not a real one.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.