Excel to Form · Your App Cloud
Turn Excel columns into an online form
Upload the sheet where answers collect today. Sort its columns into questions people answer, fields your staff fill in later and values a formula works out. Then word each header as a question.
From columns to questions people answer.
Sort the columns first, word the questions second, and fill in the form yourself before anyone else does.
01
Sort the columns into three kinds
Use the upload button above to attach the workbook, and name the tab that holds the answers. In the prompt, list the columns a respondent fills in, the ones staff complete later, such as Status or Paid, and the ones a formula calculates.
02
Rewrite headers as questions
A header like DOB or Ph# works for whoever keeps the sheet, not for a stranger. Give each question plain wording, mark which answers are required, and paste in the options behind every dropdown.
03
Submit a test and read it back
Fill in the form on a phone. Leave a required answer empty, type an email address without an @, and press Submit twice. Then open the saved response and check that every answer landed in the field its column became.
Where each part of the sheet goes on the form.
Read across each row: what you see in Excel, what it can become on the form, and how to check it. Tab names and headers here are made-up samples.
| In your sheet | On the form | What to check |
|---|---|---|
| A column header such as DOB, Ph# or T-shirt | A question label written for someone who has never seen the sheet, such as Date of birth | Ask someone outside your team to read the form. Any label they need explained still needs rewording. |
| A Data Validation dropdown, including one whose options sit on a separate tab such as Lists | A choice question with the options you name, allowing one answer or several | Compare the form's options with the dropdown's source list. Pasted values skip the dropdown, so look in past rows for answers outside the list and say which option each belongs to. |
| A validation rule, such as a whole number between 1 and 10 or a date within a range | An answer rule on that question, plus the message someone sees when an answer breaks it | Type an answer just outside each rule, such as 11 or a date past the end of the range, and confirm the form refuses it and explains why. |
| The Input Message and Error Alert on a validation rule, or a note on a header cell | Help text under the question, and the wording of its error message | These messages aren't cell values, so paste them into the prompt yourself. Then confirm each one appears beside the right question. |
| A merged cell over a group of headers, such as Contact details above Email, Phone and ZIP code | A section heading, or a separate page on a long form | Scroll through each section on a phone. If one section runs several screens long, split it. |
| Columns staff fill in later, such as Status, Paid, Assigned to or Checked by | Fields left off the form that reviewers set on each saved response, with the access you describe for each collection | Open the form signed out and confirm none of these fields appear. Then sign in as a test reviewer and set one. |
| A formula column, such as Age from date of birth, a line total or a row number used as an ID | A value worked out after someone submits, never asked as a question | Submit two test responses and compare each worked-out value with what the formula gives for the same inputs in Excel. |
| Repeated column groups, such as Guest 1 name, Guest 2 name and Guest 3 name | A guests section someone can repeat, or a list of guests attached to each response | Decide the most anyone can add. Submit one response with no guests and one with the maximum, and check that both save. |
| Rows already in the sheet, often with a Date received column typed by hand | Past responses listed next to new ones, each keeping its original date | Compare the number of imported responses with the rows you meant to bring in, and confirm old dates didn't all turn into the import day. |
A sheet rarely says no. A form has to choose.
Anyone can leave a cell empty or add a row in the wrong place, and without a validation rule a date column takes 'n/a'. A form needs those decisions made in advance: which answers are required, what format each takes and what counts as a second submission.
One row per submission, or one row per person
Some sheets gain a row every time someone signs up. Others keep one row per person and add a column each week, such as Week 1 and Week 2. Say which yours is. The second kind needs a list of people plus a form that adds one entry per week.
Let the blanks show what's required
Filter each column for empty cells in the existing rows. A column that is almost always filled is a good candidate for a required question, and one that is mostly empty may not need asking. Where a rule has Ignore blank checked, the sheet let people skip it.
Formats no cell ever enforced
Email addresses without an @, phone numbers typed five ways and ZIP codes missing a leading zero sit in a sheet unnoticed. Say which format each answer should take. To find past values that break it, add a validation rule to that column on a copy of the sheet, then choose Circle Invalid Data under Data Validation on the Data tab.
What an x or an empty cell means
In a column of x marks, an empty cell might mean no or might mean nobody asked. Decide which before past rows come in, because a yes-or-no question will record one or the other.
A date the sheet stops taking rows
An upload is a snapshot. Once the form is live, answers are saved in the app, not added to the workbook. Pick a date after which nobody types into the sheet, and tell the people who used to.
An illustrative starting point
A form people fill in, not a sheet they edit.
Questions worded from your columns, choices from your dropdowns, staff-only fields on each response, and past rows kept beside new answers.
Questions from your columns
Ask for one question per respondent column, each with plain wording, a type such as date, email or number, and help text wherever the header cell carried a note or input message.
Choices that match your dropdowns
Name the options behind each dropdown, including lists kept on a hidden tab. Where one cell used to hold 'Mon, Wed', ask for a question that takes several answers.
Staff fields on every response
Ask for Status, Paid and Assigned to on each saved response for reviewers only, then check from a signed-out browser that respondents can't see them. Saved responses and sign-in need a backend.
A confirmation once the answers save
The app can email each respondent a copy of their answers or a reference. Send one to an address you control and read it before the form goes out.
Past answers beside new ones
Ask for imported rows and fresh responses in one list that filters by status or date across both. Keep the workbook, unchanged, until the form has handled a full round of sign-ups.
Together in your app cloud
The pieces behind the possibility.
Choose the models and services that support the experience you want to create.
Database
Keep data and context for apps and agents
Authentication
Give the right people access
Email
Keep conversations moving
A little more context
Good questions.
Will new responses still show up in my Excel sheet?
No. The upload supplies a snapshot, and from then on responses are saved in the app rather than written back to the workbook. If you need the answers elsewhere, you can export your app's data. Check what an export contains before you plan a report around it.
Can I bring in the answers I already collected?
Yes, as past responses. Bring in only the columns the form still asks, plus staff columns worth keeping, such as Status. Rows from before a question existed will be empty there, so decide whether that's allowed. Leave behind personal details the form no longer needs.
How do I stop people submitting twice?
Pick the answer that identifies a person, usually an email address. Decide what a second submission does: replace the first, save as a new response for review, or get turned away. Then submit twice with the same address and check the result is the one you chose.
Can respondents get a confirmation email?
Apps can send email, such as a confirmation with a copy of the answers. Decide what the message says and when it goes. Test it with an address you control, and check that a response which fails to save never triggers a confirmation.
Do people need an account to fill in the form?
Decide whether anyone with the address can answer, as on a public sign-up, or whether people sign in first, as on a members-only form. Staff who review responses also sign in to the published app, with the access you describe for them.
How do I collect a registration fee?
Keep collecting it through the payment page you already use, and link to it from the confirmation screen. Then replace the Paid column someone marks by hand with a paid status on each response, updated when the money arrives, and check it on a test response before the form goes live.
Will the form work on phones?
The form is published at a web address and opens in a browser, including on phones. A sheet thirty columns wide makes a long form on a small screen. Put the questions everyone must answer first, and move optional ones into a later section.
Which plan does a form built from a spreadsheet need?
Saving responses, signing reviewers in and sending confirmations all need a backend, so the form is an app with data, and putting it live needs a paid plan. A page that announces a sign-up would be a one-page site. Check the pricing page for current plans and how usage is metered.
Explore Pricing for plans, included capabilities, and usage details.
Keep exploring.
Build a data collection app ↗
See the outcome and the capabilities behind it.
Take event registrations ↗
When the sheet is an attendee list, see how sign-ups, the program and attendees' questions can sit in one app.
How to turn an Excel spreadsheet into an app ↗
When the rows need views, rules and follow-up after they arrive, not only a way in, start from the walkthrough.
Understand data and context ↗
Give information the right place in your app.
Prepare to publish ↗
Check the experience you will share.
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building