How to save form entries to a database and keep leads as rows you can use

By Ranjit Bhinge, founder of Blur Studio · Updated · 11 min read

Short answer: A form entry becomes a usable lead when it lands as one row in a table with named columns: contact details, the message, where it came from, a status and an owner. You can do that with a shared spreadsheet, the inbox built into your website tool, a CRM (customer relationship manager, software that tracks contacts and deals), or a database such as the one inside Ploy, an AI website platform. Pick the simplest one your team will actually open every day, test the export before you rely on it, and set a date for deleting old entries.

Ranjit Bhinge

You have leads arriving as emails, form notifications and spreadsheet scraps, and you want every entry in one table you can sort, filter and follow up from.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Start with the columns, not the tool. A lead you can use has at least these fields: when it arrived, who sent it, how to reach them, what they asked, which page and campaign it came from, what happened next and who owns it. Any tool that stores those as columns will work. A tool that stores a whole entry as one block of text will not.

The cost of skipping this is familiar: entries sit in email notifications, a half-updated spreadsheet and somebody's memory, so nobody can answer "how many enquiries did we get last month and how many did we reply to." Ploy is one of the places you can keep them, because it stores content as tables and rows that feed your site, forms and AI agent. It is one option of several, and this page is written so you can finish the job without it.

This page may contain affiliate links from which Blur Studio earns commissions.

The lead table: what to put in each column

Here is a table design I would start from. The status values are a typical pattern from form and CRM tools, not a standard, so rename them to match how your team talks.

ColumnTypeWhy it earns its place
Submitted atDate and timeLets you measure how fast you reply
NameTextUsed in the reply
EmailEmailThe key for spotting duplicates
PhoneTextText, not number, so leading zeros and plus signs survive
MessageLong textWhat they asked
Source pageURLShows which page produced the lead
Campaign tagsTextUTM tags are labels added to a link, such as utm_source=google, that record which campaign sent the visitor
ConsentCheckboxRecords whether they agreed to be contacted by the channel you plan to use
StatusSingle choiceNew, contacted, qualified, won, lost, spam
OwnerPersonOne named person, not "the team"
Next step dateDatePowers a daily "who is overdue" filter
NotesLong textCall outcomes
Delete byDateYour own retention date, explained below

Keep the form itself short. Every extra field lowers completion, and you can ask for the rest on the first call. Do not collect payment card numbers or government ID numbers in a form entry table, whichever tool you use. Check your platform's terms for data it does not want you to store, and read the security questions to ask any website or marketing platform before you put customer details anywhere new.

Your options, from least to most effort

OptionWhat it isBest whenWatch out for
One shared spreadsheet, filled by handSomeone copies each notification into a sheetUnder about 10 entries a monthCopy errors, missed entries, no history
Your website tool's own entries tableThe inbox built into your site builderYou only need to read and export entriesLimited columns and no follow-up fields (see below)
A CRM such as HubSpot (a customer relationship manager with free and paid tiers) or an email tool such as Mailchimp (email marketing software)Entries create a contact recordYou follow up by email or phone dailyPrice and limits change: check each vendor's page for your contact count
A database table inside your site platformEntries and your own columns in one placeYou want leads, content and site pages in one systemExport limits and plan limits, covered below
Custom app or admin screenBuilt for your exact processSeveral people, approvals, rolesCost and care. Skip until a table is not enough

If you already work out of a CRM, store the lead there and stop reading. A second table that nobody opens is worse than none. My other page on building a lead capture flow that writes to your CRM covers that path in detail.

What website tools store by default

Two common builders show how much a built-in inbox gives you. Both statements come from the vendors' own help pages.

  • Wix, a website builder: each form gets a submissions table with the submission time, name, email and message. It has Spam and Trash tabs. Spam is kept 30 days and then permanently deleted; Trash is kept 180 days. Old forms export to CSV (a plain file of rows and columns that opens in a spreadsheet) as the whole collection, the filtered data or only the form fields; new forms export the submissions you select. Exported dates are in UTC (a single worldwide time standard), so convert before you compare with local time.
  • Webflow, a website builder with a visual designer: submissions are stored automatically with the form and can be exported as CSV with columns named after your form fields. Its training page does not state a retention period or plan limits, so check Webflow's current help before you rely on it as your only copy.

Both give you the entry, but neither gives you a status, an owner or a next step date out of the box. That is the gap a lead table fills.

Where Ploy fits, and where it does not

Ploy has two separate places for form data, and mixing them up causes confusion.

  • Submissions inbox. Forms built into a Ploy site capture entries automatically. You review them under Sites, then Dashboard, then Submissions, and add notification emails in Notifications. Per Ploy's docs (updated November 18, 2026), built-in submissions are text only and each is limited to 128 KB (kilobytes, a small size limit, roughly tens of thousands of words). Ploy's docs describe the inbox for viewing entries and sending notifications, and do not describe a status field, assignment or notes, so check Ploy before you plan to manage leads there.
  • PloyDB tables. PloyDB is Ploy's built-in database. Its docs describe a spreadsheet-style table view with inline editing, filtering and sorting on any column, drag to reorder, and live updates that include new form submissions. Column types include text, long text, number, currency, percent, checkbox, single and multi select, status, people, date, URL, email, file and relation (a link to a row in another table). That is enough to build every column in the table above, including a status column. See Ploy's database and CMS explained for what PloyDB does for site pages.

Limits that matter for a lead table, as of November 2026 per Ploy's docs: up to 97 columns per table, 128 KB per text value, CSV import up to 32 MB, and CSV export of up to 10,000 rows per export of the current view (the dashboard warns when an export is cut short). The docs give no total row cap per table. Ploy's plans, from its pricing page: Free $0, Starter $50 a month, Pro $300 a month, Enterprise by quote. Ploy's credits docs say unused credits do not carry over. Credits are what AI work costs, so a plain table you edit by hand does not use them. Check Ploy's pricing explained for the plan details.

One trap with files: a form that accepts a file upload writes its row to a table with a File column, and per the docs those rows do not appear in the Submissions inbox or in form email notifications. Files also work only on the published site, not in the in-app preview, and a public form that accepts files should have spam protection. Ploy's docs do not list spam protection, a CAPTCHA (a puzzle that blocks bots) or a consent checkbox as built in, so ask Ploy's agent to add them or put them in your own form and test.

Step by step

  1. List what you need to ask the table. Write three real questions, such as "which leads have no reply after 24 hours" or "which page brings the most enquiries." If a question needs a column you do not have, add it now.
  2. Build the columns above in your chosen tool. Use dropdown types for status and owner so nobody types "Contacted", "contacted" and "Called" as three values.
  3. Connect the form. In Ploy, ask the agent to send form entries to your table, or check Ploy's docs for how a form writes to a table. In another tool, use its CRM or spreadsheet connector, or a connector service such as Zapier (an automation service that moves data between apps).
  4. Send five test entries. Use names that include an apostrophe, an accent, a long message and a phone number starting with a zero. Check every column.
  5. Set up the views. Make one view for new leads with no owner, one for overdue next steps, and one for the last 30 days by source page.
  6. Run the export test. Export the table, open it in a spreadsheet and look for broken characters, merged columns and missing rows. Ploy's docs say exports use labels for choices, semicolons for lists, true or false for checkboxes and file names only, and that exports "aren't lossless backups" and may not re-import exactly. So keep an export as a convenience copy, not as your backup plan.
  7. Write down the owner and the daily check. One person opens the new-leads view each morning.

Duplicates and spam

Real tables fill with junk fast. Decide these rules before the first lead arrives.

  • Duplicates. Match on email. If the same email arrives again, add a note to the old row rather than creating a new lead, or tick a "repeat" column. Two rows for one person doubles the chance of two people replying.
  • Spam. Add a honeypot (a hidden form field that people never fill in but bots do) or a CAPTCHA. Mark junk with a spam status instead of deleting it straight away, so you can see which patterns to block.
  • Who can see rows. A lead table holds personal data. Limit access to the people who follow up. In Ploy, only owners and admins can restore database history, and access keys can be scoped to one database with read or write per table.
  • Plan changes. Before you downgrade a plan, export the table and check what happens to your data under the new plan. Ploy's pricing page and terms are the place to read that.

How long to keep entries

This is information, not legal advice, so check local law. Under the EU's GDPR (General Data Protection Regulation), Article 5 says personal data should be limited to what is necessary and kept in identifiable form for no longer than is necessary for its purpose (text as shown at gdpr-info.eu, a convenience copy of the regulation). It sets no fixed number of months. So the rule that works in practice is to write one sentence for each table: "We keep website enquiries to answer them and to follow up, and we review them every six months." The six months is an example I made up; choose a period that fits your business. Then fill the "Delete by" column on arrival and run a monthly filter for rows past that date. Related reading: is website visitor tracking allowed under privacy law.

A worked example (made-up numbers)

A small bathroom remodeler gets about 40 form entries a month. Today each one arrives by email, one person pastes some into a sheet, and nobody knows how many got a reply. They build a table with the columns above. In the first month the new-leads view shows 6 entries with no owner and 9 whose next step date has passed. They assign owners that morning. A filter on source page shows 22 of the 40 entries came from one service page, which is where they put their next photo set. None of this needs a new tool, only a table with the right columns and one person who opens it. The numbers are invented to show the method, and your own counts will differ.

Test plan with pass and fail rules

TestPassFail
Five test entries with odd charactersAll five show correctly in every columnBroken characters or a merged column
Submit the same email twiceYou can see it is a repeat within one minuteTwo unrelated rows
Export to CSV and open itRow count matches the table and dates read correctlyMissing rows or shifted dates
Ask a teammate to find all overdue leadsThey do it in under a minute from a saved viewThey ask you how
Send a spam testIt lands as spam or is blockedIt appears as a new lead

Who should skip this

  • Under about 10 entries a month: a shared spreadsheet is fine.
  • You already live in a CRM: send entries there.
  • You need roles, approvals or a customer-facing portal: a table is the wrong tool and a custom build fits better. See signs you need an app or portal.
  • Your leads include sensitive data, such as health or financial details: get advice on where it may be stored before you build anything.

How I'd approach this

I would not start by choosing software. I would pick the three questions I want the table to answer, add the columns, and run the export test on whichever tool I already pay for. If the tool already gives me filters, a status and an owner, I would stay there. If leads, site content and forms are all scattered and I am already on Ploy or about to move there, the PloyDB table is a reasonable single place, as long as the export test passes and I treat exports as copies, not backups.

First week: day 1, build the columns and the three views. Day 2, send five test entries. Day 3, run the export test and write your retention sentence. Day 4, name the owner and the daily check. Day 5, review spam and duplicates. If you outgrow a table, Blur Studio builds the custom version, with an admin screen, CRM and calendar connections and ongoing care. See what a custom build includes. If you do try Ploy's Free plan, run the export test before you move real leads into it.

A closely related page covers the same ground from another angle: Waitlist and RSVP Forms Without Buying Another Tool.

For the next step, see A Directory of Team Members, Properties or Distributors on Your Site.

Related guide: How to Edit Website Pages From Your Phone.

A closely related page covers the same ground from another angle: How to Run Facebook and Instagram Ads With Fewer Tools.

Questions people ask

What is the simplest way to save form entries to a database?

Use the table your form tool already gives you, add the columns you need for follow-up, and test the export. A shared spreadsheet is enough for a few entries a month. Move to a CRM or a database table when you need filters, owners and history.

Should I use Google Sheets or a database for leads?

Use a spreadsheet while one or two people handle a small number of entries. Move to a database or CRM when several people edit at once, when you need filters saved as views, or when entries feed pages or automations. See storing small bits of data without running a database.

What columns should a lead table have?

Submitted at, name, email, phone, message, source page, campaign tags, consent, status, owner, next step date, notes and a delete by date. Use a choice type for status and owner so values stay consistent.

Does Ploy store form entries as rows?

Ploy's Submissions inbox stores built-in form entries as text, up to 128 KB each. PloyDB is a separate spreadsheet-style database with a status column type, and its docs say the table view updates live, including new form submissions. Check Ploy's docs for how to point a form at a table, and see the PloyDB explainer.

Can I export my form entries from Ploy?

PloyDB tables export to CSV, up to 10,000 rows per export of the current view, and the docs say exports are not lossless backups. Ploy also keeps a rolling 30-day history of each database that owners and admins can restore. Run an export test before you depend on either.

How long should I keep form entries?

There is no single number. GDPR Article 5 says to keep personal data no longer than necessary for its purpose, so state the purpose, set a review date and delete or anonymize entries past it. This is not legal advice, so check local law.

Can I store payment card numbers or ID numbers in form entries?

Do not. Keep payment details with a payment provider and avoid collecting government ID numbers in a form entry table. Check your platform's terms for what it does not allow you to store.

When should I send leads to a CRM instead?

When you follow up by phone or email every day, want reminders and reports, or need several people on the same lead. See CRM for small business and the forms not sending leads checklist.

More in this topic: Websites: forms, directories and editing on the go (5 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…