
To replace an Excel tracker with a Power App, move the data into a SharePoint list or a Dataverse table, build a form that asks each person only what they need to enter, and let Power Automate send the reminders people now send by hand. Keep Excel if one person owns the file and nobody has to chase anyone through it.
Most trackers start sensibly. Someone needs to keep an eye on requests or orders, so they make a sheet. Then it gets shared, and a year later it has 40 columns, three colour codes and a person whose job is partly to ask everyone else to update it.
How do you know a tracker has outgrown Excel?
A tracker has outgrown Excel when several people edit it and the file has started doing jobs a spreadsheet was never built for: telling someone a task is now theirs, chasing them when it runs late, and showing later who changed what. If three or more of these sound familiar, it is time to move it.
- Part of someone's week goes on reminding people to update the sheet.
- There are copies. "Tracker v3 FINAL (2)", or one per site, or one per manager.
- Status is shown by colouring cells, and the colours mean slightly different things to different people.
- A row gets overwritten or deleted, and nobody notices for a week.
- People who only need to add a row can see, and change, every other row.
- The weekly report is built by filtering, copying and pasting.
None of these are Excel's fault. Excel is a calculation tool being asked to run a process.
When should you keep the spreadsheet?
Keep Excel when the tracker is really one person's working file, when the data is mostly numbers you analyse rather than tasks you pass along, or when the process changes every few weeks. An app fixes the shape of a process. If nobody has agreed what that shape is, building an app just locks the disagreement in.
A few cases where I would tell a client to leave it alone:
- One owner. If only the finance lead edits it, the coordination problems above do not exist.
- Analysis, not workflow. Pivot tables, what-if scenarios and ad hoc sums are what Excel is best at. An app makes them harder.
- Short life. A tracker for a six-week project will be finished before an app is.
- No agreed process. Settle who does what first. Then build.
An app also needs an owner after it goes live, someone who can add a choice to a dropdown or a person to a role. If nobody will own it, the spreadsheet is the honest choice.
What changes when a tracker becomes an app?
The data stops being a grid anyone can type into and becomes records with rules. Each role sees its own part, status comes from a fixed list, reminders run on a schedule, and every change is tied to a person and a time. What you give up is the freedom to add a column on a whim, which is usually the freedom that caused the mess.
| Shared Excel tracker | Power App on a list or table | |
|---|---|---|
| Who can change what | Anyone with edit access, any cell | Each role edits only its own fields |
| Status | A colour or a free-text cell | A choice column with fixed values |
| Reminders | Whoever remembers | A scheduled flow |
| Who changed it | Version history of the whole file | A history on each record |
| On a phone | Painful | What it is designed for |
| Ad hoc analysis | Excellent | Export to Excel, or report in Power BI |
That last row matters. You can still analyse the data in Excel. It just stops being where the work is coordinated.
Can a Power App use the Excel file directly?
It can, and it is the weakest option. The Excel connector reads a formatted table from a file in OneDrive or SharePoint, so it looks like a quick start. In practice you take on the limits of a file and the limits of an app at the same time, and Microsoft's own guidance points away from it for anything busy.
Microsoft's performance guidance for canvas apps says the Excel connector only loads rows up to the app's data row limit, which is 500 by default and can be raised to 10,000, because few functions delegate to Excel. The same page says plainly that Excel isn't a relational database system and that apps with heavy transactions can suffer. The cloud-storage connection notes add that a table with a calculated column can't be used to build an app at all. (Both checked on Microsoft Learn, November 2026.)
So use the spreadsheet once, as the source for the import, and then retire it.
Where should the data live instead?
For most team trackers, a SharePoint list. It comes with Microsoft 365, it copes with the volumes a typical tracker reaches, and people can still open it in a grid that feels like a spreadsheet. Move to Dataverse when records relate to other records, when different people must see different rows, or when several apps and flows will work on the same data.
The full comparison, including the point where a list starts to struggle inside a Power App, is in Dataverse vs SharePoint Lists. The short version: if your tracker is one table with a status column, a list is the right and cheaper choice.
How do you move a tracker into a Power App, step by step?
Data first, then the form, then the automation, then a short and fixed overlap before the old file is locked. Doing it in that order means each step is tested on real records before the next one depends on it, and nobody is asked to change habits until the new version works.
- Go through every column. Most trackers have columns nobody fills in and columns doing two jobs at once, like "Status / notes". Split them or drop them now.
- Turn free text into choices. Status, priority, site, category. If an answer is one of a few, make it a choice column so it can be counted and filtered.
- Create the list and import the rows. Tidy the sheet first: one header row, no merged cells, dates stored as dates. Messy source data is where imports go wrong.
- Build the form around the person. Whoever logs an item needs four fields. Whoever closes it needs three different ones. Show each of them their part and nothing else.
- Add the flows. One flow tells the owner when an item is assigned to them. A second runs every morning and chases anything past its due date. Together they replace most of the reminding someone does by hand today.
- Overlap briefly, then lock the spreadsheet. Pick a date and make the old file read-only on it. While both are editable, people keep using the one they know.
If your tracker is really a queue of things waiting for sign-off, such as purchases or leave, the flow side is an approval. How to build a Power Automate approval flow covers that part, including what happens when an approver goes quiet.
What does a tracker app cost in licences?
Often nothing extra. Microsoft classes a canvas app that only uses standard connectors, such as SharePoint, Office 365 Outlook and Office 365 Users, as a Standard app, and people can run it with a Power Apps for Office 365 plan. Add Dataverse or any premium connector and every user needs a per app or per user plan instead.
That is from Microsoft's page on app license designation (checked November 2026). The same page lists a known issue worth knowing before you build: if the app calls a flow that uses a premium connector, the app can still show as Standard even though its users need premium rights. So check the connectors in each flow, as well as the label in the app's settings.
Frequently asked questions
Can people still see the data in Excel? Yes. A SharePoint list can be exported to Excel whenever someone wants to analyse it, and Power BI can report on it directly. What changes is where the data is entered and updated, not whether you can get it out.
Will my team actually use it? They will if it is quicker than the spreadsheet, so build it that way. Ask only what each person needs at that moment, use choices instead of typing, and make it work on the phone they already carry. Then watch someone use it for a day and fix whatever slows them down.
What happens to the old spreadsheet? Import the open items, decide whether closed history is worth importing too, and keep the original as a read-only archive. Deleting it on day one makes people nervous. Leaving it editable means it never really goes away.
Do I need Dataverse? Not for a typical tracker. Use a SharePoint list unless records relate to each other, different users must see different rows, or the volume will grow past what a list handles well inside an app.
Getting your tracker moved
If you would rather have it built than build it yourself, the Power Apps development service explains how I work. You can also book a free 30-minute consultation and talk me through the spreadsheet. Ten minutes looking at its columns usually tells us whether it should become an app or stay a sheet.
Last updated
- Power Apps
- SharePoint
- Process Automation
