Fillout: record updates and client handoffs

Price the response volume

Choose a plan against expected responses, then decide how much overflow you can tolerate. Seats and forms are separate from the response allowance.

Fillout pricing lists Free with unlimited forms and seats and 1,000 responses monthly. Fillout includes conditional logic and hidden fields on Free.

On annual billing, Fillout lists Starter at $15 monthly equivalent for 2,000 responses and Pro at $40 for 5,000 responses. Fillout lists unlimited responses and partial submissions on Business.

Fillout’s pricing FAQ says forms keep collecting after the submission limit. The FAQ does not settle access to over-limit responses or account enforcement, so get those terms before relying on overflow.

For a client whose campaign may exceed its allowance, record the expected response volume and who will retrieve overflow. Include that answer in the plan decision rather than treating continued collection as complete access.

Test the destination record

Choose whether a submission should create a record or update an existing lead before building the form. Inspect the destination after each test.

Fillout’s HubSpot page describes creating Contacts, Deals and Companies, updating existing contacts and prefilling from HubSpot. Use a synthetic known contact to test matching and field mapping; the description does not resolve collisions.

Fillout’s Airtable duplicate prevention guide describes matching a selected email or single-line field on Business and Enterprise. It describes preventing records from being saved to Airtable. Test simultaneous submissions separately, since the guide does not promise race-safe updates.

Try an empty answer and a changed answer against the same synthetic contact. Compare the resulting record with the expected values, including whether a second record appeared. A success screen alone cannot show that the destination is correct.

Control what an update link loads

Review data exposure and form behavior together when a known lead edits a record. Hiding a question is a separate decision from limiting loaded data.

Fillout’s update-form guide says update links load entire records by default. Restricted prefill limits loading to mapped question fields, while unmapped fields become unavailable to logic, calculations and answer piping.

Use a synthetic record with an extra field to inspect what the link loads. Then run the same branch with restricted prefill and compare the outcome. Give the client the result before deciding which fields the form needs.

Move the form and its history

Plan the form and response history as separate assets when a client takes ownership. A working template does not carry the whole account.

Fillout’s migration guide says form exports omit submissions and comments. Importing a Fillout form into another organization requires reconnecting integrations. Fillout’s third-party import copies structural items but excludes backend settings.

Fillout’s pricing FAQ lists CSV export and API access. Export the response history separately and inspect its fields. Reconnect the destination in the client workspace. Submit a synthetic lead through the imported form before retiring the original.

Name the owner of the form URL and the destination. Keep the response archive accessible to the client and document who will repair a broken connection.

How to compare the alternatives

Choose the alternative according to the boundary that matters: client ownership, a simple collection workflow or a more involved API action.

Tally’s pricing includes free forms and submissions with conditional logic and webhooks, subject to fair usage. Tally may fit a team that needs those features in one organization; its fair use policy limits sharing paid subscriptions outside the registered organization.

Feathery’s API action guide describes rule-based CRM lookups and custom validation. Feathery may fit a buyer who needs those actions and can evaluate a sales-led quote. Its pricing page distinguishes standard integrations from premium integrations sold à la carte.

Use the Tally alternatives comparison to compare the billing units and handoff. The form builder buying guide has a worksheet for testing the same synthetic lead across candidates.

Common questions

Does Fillout stop collecting at the response limit?

Fillout’s pricing FAQ says forms continue collecting above the submission limit. Confirm access to those responses and account enforcement.

Can Fillout update a HubSpot contact?

Fillout’s HubSpot page describes updating existing contacts. Test matching and field mapping with a synthetic record.

Does a Fillout form export include responses?

Fillout’s migration guide says form exports omit submissions and comments. Export the results separately.

Which alternative should I consider?

For free webhooks within one organization, consider Tally. For rule-based API actions, consider Feathery. Quote the required integration.

Sources and scope

We read the linked vendor pricing and documentation on October 29, 2026.

We have not tested the products, record matching or migrations. Confirm current account terms and access to over-limit records.