Free tools Windows power users keep installed
One-click scans. No signup required.
A SharePoint list can work as a lightweight data store for team processes and simple apps. It is not a relational database. Whether it is “enough of a database” for you depends on four things: the shape of your data, how you query it, how tightly you must govern it, and how large it will grow. The 5,000-item limit people quote is not the list’s size cap. It is a processing threshold, and misreading it causes most of the bad decisions in both directions.
What the 5,000 and 30 million figures actually mean
Microsoft Learn states that the default SharePoint Online list view threshold is 5,000 items (Microsoft, 2025). That number limits how many items a single operation may need to process. SharePoint may throttle or block an operation that has to touch more than that, even if the final result would be small. A list can hold far more than 5,000 records.
![Microsoft Access Guide to Success: From Fundamentals to Mastery in Crafting Databases, Optimizing Tasks, & Making Unparalleled Impressions [III EDITION] (Career Office Elevator)](https://m.media-amazon.com/images/I/416hek78D3L._SL160_.jpg)
Microsoft’s SharePoint limits documentation puts the ceiling higher: “A list can have up to 30 million items and a library can have up to 30 million files and folders.” Microsoft’s 2022 Lists/Dataverse comparison also gives Lists up to 30 million rows. The same material says to look for additional guidance once a list passes 100,000 items.
These are two different kinds of number:
- 5,000 is about what one view, query or operation can process.
- 30 million is documented capacity. It does not promise that every view, flow or app will perform well at that size.
These figures describe SharePoint Online and Power Platform. They don’t cover every SharePoint Server version or tenant configuration.
#1 Best Overall
Why query shape matters more than row count
A list with 500,000 items can be pleasant to use. A list with 6,000 can be miserable. The difference is the query. Community guidance describes the threshold as applying to the items an operation must scan, not the items it returns. A filter on an unindexed column can therefore fail on a large list even when it would match ten rows.
- Build views that filter on indexed columns, and test the real view against realistic data volumes.
- Choose indexes based on the filters people actually use.
- Set indexes up before the list is large. Doing it after growth makes the work harder.
Where lists stop behaving like a database
Relationships and data modeling
Lists hold flat items well. Lookup columns give you simple references. They are not joins, constraints or normalized tables. Microsoft’s platform comparison contrasts Lists, which handle list, file and image data, with Dataverse, which handles relational data and offers broader security, integration and developer capabilities.
Permissions at scale
Above 100,000 items, permission inheritance cannot be broken or restored at list or folder scope (Microsoft, SharePoint limits). If your design depends on item- or folder-level security, plan that early. You can’t retrofit it once the list has grown.
Power Apps
Microsoft recommends limiting dynamic lookup columns and unneeded payload, including images and attachments. For lists with hundreds of thousands of records, it suggests considering partitioning by a field such as date or category.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Power Automate
The Get items action returns 100 items by default. Top Count can be raised to a maximum of 5,000. Beyond that, you need pagination and server-side filters. Microsoft documents a known filtering and pagination edge case when a list exceeds 5,000 items, so test flows against a list that is actually that big. This guidance is dated documentation, so recheck it against current behavior.
Lists or a real database: a decision table
| Requirement | SharePoint Lists may fit when… | Evaluate Dataverse or another database when… |
|---|---|---|
| Data shape | Records are mostly flat items with a few simple references. | The application depends on relational data and richer modeling. |
| Query and scale | Users work through carefully designed views and bounded queries. | Workloads need complex or frequent queries, predictable application behavior or heavy automation. |
| Security and governance | Site and list roles meet your requirements. | You need more complex enterprise security, auditing, business units or field-level controls. |
| App and integration needs | A team app can live within the SharePoint connector’s constraints. | You need broader platform integration, developer extension, offline support or managed business rules. |
| Operations | Owners can monitor growth and maintain views, indexes, permissions and flows. | The data is business-critical and needs stronger operational controls and a deliberate architecture. |
Check current licensing and capacity entitlements for your tenant before making a purchase decision. Microsoft’s comparison page is dated, and entitlements change.
Operating checklist for a list that is becoming a database
- Treat 5,000 as a design constraint for views and queries. It is neither a target nor a ceiling.
- Index the columns your filters use, before growth.
- Decide the permission model before the list reaches 100,000 items.
- In Power Apps, keep only the columns you need and be deliberate with attachments.
- In Power Automate, filter server-side, paginate, and raise Top Count only as needed.
- Plan for partitioning or migration if you expect hundreds of thousands of records.
The Bottom Line
Use a list when the data is flat, the views are designed around indexes, and the permissions are simple. Move to Dataverse or another database when you need relationships, richer security, or predictable behavior from heavy queries and automation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors
