Turning Excel into a web app takes five steps: tidy the file (one header row, one table per sheet), upload it as .xlsx or CSV, review what was understood about the columns and their types, adjust the proposed tables, screens, reports and roles, then build. In Fanann your rows are written into the app's database as they are, and a list, an entry form and a detail page are built around each table, so your team opens one link in any browser and finds the data ready.
- excel to web app
- how to convert excel to a web application
- turn excel spreadsheet into online app
- how do I make a web app from an excel file
- upload excel and create an app
- excel to web app without coding
What will I have at the end?
Our example is an AC maintenance company with one file and three sheets: Customers, Maintenance requests and Technicians. Today the receptionist fills in a row, photographs it and sends it to the technician on WhatsApp, and the manager spends two hours every week working out how many requests were closed.
Illustration- After converting
- One link for reception, technicians and the manager
- For each sheet
- A list, an entry form and a detail page
- For requests
- A stage board: New, Assigned, In progress, Closed
- For the manager
- Reports calculated from the data, always current
- The data
- The file's rows, imported from the first moment
For the difference between a sheet and a system and the other routes, start with how to turn an Excel sheet into a system.
Why a web app and not a program on the computer?
Shared work files are needed by several people in several places. A web app solves that by nature: one database, one link. It is not always the answer, though:
Pick the one that sounds like you to see the advice.
A web app. The office, the branch and the field rep open it on any device, and every update reaches everyone at once.
A Windows program with a local database fits better: it works with no internet on that computer, and you handle the backups. See Windows Studio.
Start with a web app opened in the phone's browser. If you need an iPhone and Android app, that is an option at build time on paid plans.
The full comparison is in desktop app or web app.
Step 1: what should the file look like?
This is what the maintenance company's file looked like, and what it became after 40 minutes of tidying:
- A merged title across the first 3 rows: September requests
- One sheet per month with the same columns
- Customer name and mobile typed into every request
- Closed requests shaded green
- Date column: yesterday, 12/9, Sunday
- A Total row at the bottom of every sheet
- Headers in the very first row
- One sheet for all requests, with a Request date column
- A Customers sheet with a customer number; requests carry only the number
- A Status column: New, Assigned, In progress, Closed
- A full date in one format in every row
- No total rows: the report will calculate them
Save the file as .xlsx (old .xls and password-protected files cannot be read) and keep it under 10 MB. If it is larger, delete the sheets you do not need or split the file.
Step 2: what is understood from my file when I upload it?
Open Excel to App and drop the file. Within moments, and without using any credits, you see your first rows with the detected type under each header:
| Column in our file | Expected type | What it means in the app |
|---|---|---|
| Request number | Whole number | A unique ID, flagged if repeated |
| Customer mobile | Mobile | A number field you can tap to call |
| Fault type | Choice list | A drop-down instead of free typing |
| Request date | Date | Sort and filter by month, and a calendar if you want |
| Cost | Amount | Summed in reports |
| Collected | Yes / no | A checkbox and a quick filter |
| Technician notes | Long text | A roomy text box in the form |
You also get frank notes: exact duplicate rows, repeated values in a column that should be unique, the share of empty cells, and which sheets are linked. It is a free data-quality check even if you build nothing.
Step 3: how do I review the app proposal?
Before asking for the proposal, write one sentence about what the file runs, such as: AC maintenance requests for a company with eight technicians in Sharjah and Ajman. Then the proposal appears: app modules (each sheet is now a table), screens, reports and permissions. Do not press Build before this review:
Three roles are ready: owner, manager and staff, and you add users from inside the app after it is built. If you need a finer split (a technician sees only their requests, an accountant sees only collections), write it in your builder note in the next step, and see roles and permissions for a staff app.
Step 4: build now, or plan first?
When you press Build my app you choose where it runs (a web app in our case) and how to start. Build now starts straight from the proposal you reviewed. Plan first shows you the build plan to adjust before anything is written; choose it when you have many business rules. Either way, write your note:
Add to the proposal: 1) A technician sees only the requests assigned to them, can change their status and add notes and parts cost, and cannot see revenue reports. 2) The receptionist creates the request and picks the customer from the list, or adds a new customer from the same form. 3) When a request is closed, the Cost field becomes required. 4) A manager screen highlights requests open for more than 3 days. 5) A monthly report: number of requests by fault type and by technician, and total collected. Arabic interface, right to left, and comfortable on a phone because technicians work from their phones.
Try it in FanannAt build time your rows are written into the app's database as they are, then the screens are built around them. Building screens uses credits according to the app's size, like any other app. Importing the data itself uses none.
Step 5: how do I open it to my team safely?
- 1Reconcile the data
Open the requests list and compare counts and totals with the file. Open 5 random records and confirm every field is where it belongs.
- 2Change things by describing
Ask for anything you dislike in a sentence: show the mobile number in the requests list, or sort the list newest first.
- 3Add users with their roles
Create an account for each person from inside the app. No shared accounts: a shared login cancels the point of permissions.
- 4Sign in as a staff member
See for yourself that they cannot view what is not theirs, and that they can finish their work without asking you for anything.
- 5Test the whole path
Create a request, assign it, close it, then find it in the report. On a computer and on a phone.
- 6Announce the switch day
From that day the old file is read-only. Print a five-line sheet on how to log a request and pin it at reception.
For a closer check before you rely on it, the QA Engineer on paid plans takes the app's address, writes test cases you can review, runs them in a real browser and re-tests after a fix. The manual method is in how to test a website before launch.
What commonly goes wrong, and how do I fix it?
| What you see | Likely cause | Fix |
|---|---|---|
| A message asking for .xlsx or CSV | The file is an old .xls or is password-protected | Open it in Excel and save as .xlsx with no password |
| Columns named Column 1, Column 2 | The header row is not at the top, or is merged | Delete the rows above the headers and unmerge |
| Empty cells after import | Values that do not match the field type, such as Not set in a number column | Unify the values in the file, or change the field type to text |
| Two sheets not linked | No shared column with matching values | Add a unique number that appears in both sheets |
| Rows left out of the import | The row limit for a table or for the app was reached | Import the newest first, then add the rest from the control center |
| A customer appears twice | The name is spelled two ways in the file | Unify names before uploading, or merge the records after |
One reassuring rule: your data is written by the platform itself exactly as it is in your file, and the AI builds the screens around it without changing it. So a wrong number in the app is most likely wrong in the file too. More: the Excel to system guide and design a database for your app.
Key takeaways
- A web app is a link everyone opens in a browser: nothing to install, no copies of the file.
- Each sheet in your file becomes a table with a list, an entry form and a detail page.
- Check column types before you build: a wrong type is one click to fix now and an hour later.
- A Status column deserves a stage board, and an appointment column deserves a calendar.
- Do not share the link until you have signed in as a staff member and seen what they see.
Frequently asked questions
How do I convert an Excel file into a web app?
How long does it take to turn an Excel file into an app?
Can several employees work at the same time?
Can I change the app after it is built?
Does it support a file with several sheets?
What if my file is larger than 10 MB?
Ask your AI assistant about this
Copy this prompt into the AI assistant you use, then add the details of your own case.
I am reading this guide: “From Excel to a web app, step by step: a full worked example” https://fanann.com/en/blog/excel-to-web-app-step-by-step/ My question: excel to web app Use that page as a source and explain the answer step by step for my situation, tell me what to check before I start, and cite the page link.