To turn an Excel file into a complete system: prepare the file (one header row, one column per piece of information, one row per record), then upload it to “Excel to App” in Fanann as .xlsx or .csv, up to 10 MB. Fanann reads the columns and their types and proposes the system: modules, screens, reports and roles. Review and adjust the proposal, then build, and the system is created with your data inside. Test it against your numbers and set a cutover day when editing the old file stops.
How do you know the Excel file is no longer enough?
Excel is an excellent tool for calculating and analysing. It starts to strain when it becomes the “system” a team works in every day. These are the signs:
- More than one person edits the file, so conflicting copies appear and you cannot tell which is right.
- You need each person to see only part of the data, and a file shows everyone everything.
- You type the same thing in several sheets: the customer name in orders, in invoices and in follow-ups.
- Reports cost you an hour of sorting and copying every week.
- One wrong cell or formula spoils numbers you only notice late.
- You want customers or staff to enter their own data from their phones.
If two or more of these describe you, it is time for a system.
What is the difference between an Excel file and a complete system?
A “complete system” does not mean heavy software. It means your data lives in one database, with what you need around it to work on it safely:
| In an Excel file | In a complete system | |
|---|---|---|
| The data | Cells where anyone can type anything | Typed fields: date, money, phone, pick list |
| Working together | Copies that are sent around and conflict | One database everyone works in |
| Permissions | Whoever opens the file sees everything | Roles: each person sees and edits what concerns them |
| Data entry | A new row at the bottom of the table | A clear form that works on a phone |
| Reports | Manual sorting and pivot tables | Dashboards and numbers that update with every record |
| Changing it later | You rearrange columns by hand | You ask for the change in a sentence, and the code stays yours |
How do you prepare the Excel file before uploading?
Fanann reads the file as it is, but a tidy file gets a more accurate proposal. Go through this list before you upload:
- One header row at the top of each sheet: no merged two-line headers and no logo above the table.
- One column per piece of information: do not put name and phone in one cell, or city and district.
- One row per record: one customer, one item or one invoice per row, with no subtotal rows among the data.
- One format for dates and numbers down the whole column, and amounts as numbers with no currency symbol in the cell.
- Consistent spelling for repeated values: “Riyadh” every time, so it is read as one category.
- An identifier per record where you have one: a customer number, an item code, an invoice number. Sheets are linked through it.
- Remove what you do not want to move: old columns, scratch sheets, sensitive data the system does not need.
Clean a fresh copy and leave the original untouched. You will need it to compare numbers after the build.
Turning an Excel file into a system in six steps
- 1Prepare the file
Apply the checklist above: one header row, one column per piece of information, one row per record. Fifteen minutes here save many corrections later.
- 2Upload the file to “Excel to App”
In the Fanann dashboard open Excel to App and upload an .xlsx or .csv file (up to 10 MB). Download Google Sheets files in either format first.
- 3Review how Fanann read the file
For each sheet you see the header row, each column’s type and the row count, duplicates and blanks, and the columns that link one sheet to another. Correct any type that was not read as you want.
- 4Adjust the proposed system
Fanann proposes the modules with the number of records each will import, plus screens, reports and roles. Switch off what you do not need, rename fields, and describe how you work and what the proposal is missing.
- 5Build the system
Choose a web app or a mobile app, then “Plan first” to review the plan in plan mode or “Build now”. The system is created with your data inside: about 5,000 rows per sheet at build time.
- 6Test, then move
Compare the system’s numbers with the file’s, and try the everyday jobs signed in as each role. Then publish the system, invite your team and stop editing the old file on a set day.
What does each kind of column become in the system?
Reading the columns is what turns a table into a system: a column’s type decides the field in forms, the filters you get and the reports that are possible.
| Column type | Examples | Becomes in the system |
|---|---|---|
| Text | Customer name, description | A text field and a search field |
| Number | Quantity, balance | A numeric field you can total and compare |
| Money | Price, total | A money field shown in reports |
| Date | Order date, appointment | A date picker, time filters and a calendar |
| Phone / email | Phone, email | Contact fields in one format |
| Category | City, status, department | A pick list, a filter and a report by category |
| Yes / no | Paid? Active? | An on / off switch |
| A link between two sheets | The customer number in the orders sheet | A relation: a customer’s orders show on their card |
Which system fits your file?
The steps are the same, but the columns, reports and roles differ with the file. Each kind has a page with sample columns and what Fanann proposes:
Excel to App
The feature page: how Fanann reads your file, what it proposes and how it builds the system with your data inside.
See the featureCustomer management system (CRM)
Your customer sheet becomes a CRM: a card per customer, a contact log and follow-ups nobody forgets.
Customer namePhoneCitySourceSteps and columnsInventory and warehouse system
Your item sheet becomes an inventory system: live balances, low-stock alerts and a movement log per item.
Item nameItem code (SKU)QuantityReorder pointSteps and columnsInvoicing system
Your invoice log becomes a system: invoices per customer, a clear payment status and a list of what is overdue.
Invoice numberCustomerInvoice dateDue dateSteps and columnsReservations and booking system
Your appointment sheet becomes a booking system: a clear calendar, no double bookings and a history per client.
Client namePhoneServiceStaff memberSteps and columnsEmployee and HR tracker
Your staff sheet becomes a system: a file per employee, leave balances and requests that get approved instead of messaged.
Employee nameEmployee IDDepartmentJob titleSteps and columnsCutover day: from the file to the system
The hardest part of the move is not the build; it is getting the team to leave the old file. Make the switch a clear moment:
- Pick one day for the move and tell the team in advance.
- If the file changed since you uploaded it, import the new rows as a CSV from the Control Center.
- Make the old file read-only and keep it as an archive.
- In the first week check the numbers daily and ask for any change by chat as soon as it comes up.
What happens after the build?
The system that comes out of your file is a full app in Fanann, not a closed template. Three things you will use often:
Manage the data and the users
From the Control Center: browse and edit records, import and export CSV, invite users and set their roles. Included in every plan.
Change the look by clicking
The visual editor lets you select any element and change its colour, type and spacing.
Add what is missing by chat
A new report, a notification, a customer-facing page or a payment gateway from Connectors: ask for it in a sentence.
Common mistakes to avoid
- Uploading the file with all its mess. Merged cells and subtotal rows confuse the reading. Clean first.
- Expecting formulas to move. What moves is the data. Describe the calculations you need and they are built inside the system.
- Ignoring permissions. Decide who sees what before the build, especially for staff data and prices.
- Running the file and the system side by side. Two versions of the truth are worse than one incomplete version. Set the cutover day and keep to it.
- Trying to build everything at once. Start with what is in the file, then add features one at a time.
Key takeaways
- A good file is half the system: one header row, one column per piece of information, one row per record.
- Fanann reads the file and proposes; you decide: nothing is built before you review the modules, fields and roles.
- Your data moves as it is: about 5,000 rows per sheet at build time, the rest from the Control Center.
- Set one cutover day and make the old file a read-only archive.