Dataverse or SharePoint lists? The decision you pay for two years later
Starting with lists is cheap and often right. The problem is not knowing where the line is, and crossing it without noticing.
Every Power Platform application starts with the same decision: where the data lives. And it is almost always made on cost, which is the worst possible reason to make it.
SharePoint lists: when they are the right answer
There is nothing wrong with lists. They are the right choice when:
- The data belongs to one team and nobody else consumes it.
- Volume is counted in thousands of rows, not hundreds of thousands.
- Relationships between tables are few and simple.
- Nobody is going to audit who changed which field and when.
If that is your case, start there and do not overcomplicate it. Half the internal applications that work well live in lists and need nothing more.
Four signs you have already gone past the line
- The 5,000-item threshold. It is not that the list stops working: views and filters start behaving oddly and you find yourself working around it.
- You have lookup columns pointing at other lists, which point at others. You are building a relational database without a relational engine underneath.
- Somebody asks who changed that value. SharePoint version history is not an audit trail: it is document history being used as if it were one.
- You need two people not to edit the same record at once. Lists have no transactions. When this matters, it matters a lot.
The clearest signal is the conversation: when the team starts talking about “tricks” to keep the list working, the list has stopped being the right tool.
The real cost of migrating later
Moving from lists to Dataverse is not export and import. Relationships have to be rebuilt, every flow that touched the list has to be reviewed, and permissions have to be retested because they work differently. It is a project, not an afternoon.
That is why the decision should not be made by looking at today's licence price, but by answering one question: is this going to grow, or is it going to stay as it is? If the honest answer is that it will grow and connect to other things, starting on Dataverse costs more in the first month and far less in the second year.
A middle option people forget
It is not only lists or Dataverse. For high volume with simple relationships, an Azure SQL database connected through the standard connector often works out cheaper than Dataverse and scales far beyond a list. It loses the native integration with the Power Platform security model, so it suits cases where permissions are straightforward.
