Can we use Microsoft Lists as a light database instead of Excel or a full app?

Microsoft Lists sits between Excel and a real business app. For customer lists, asset registries, simple tickets, contract overviews or inventory it works surprisingly well. For heavy transactional data pick something else, but that point arrives less quickly than people think.

Try this first

1. 1Lists fits: structured data with 5-30 columns, 100 to 30,000 rows, multiple people editing occasionally, and a need for filters and views. Examples: supplier contracts, IT asset registry, light customer CRM, project task list, candidate pipeline.
2. 2Lists doesn't fit: high write volumes (hundreds of updates per day), complex relations between tables (use Dataverse or a real database), or strict transactional requirements.
3. 3Create a list from the Microsoft Lists app or a SharePoint site. A SharePoint list is technically the same thing, just hosted in a specific site. Lists from the Lists app land in 'My Lists' or a chosen site.
4. 4Use column types well: Choice for fixed options, Person for referring to colleagues, Lookup for referring to another list, Calculated for derived values. Avoid free text where Choice fits, that gives consistent data.
5. 5Build views per use case (Open items, Mine, By status, Table vs Gallery). The same list feels very different with good views.
6. 6Need workflow (notify on status change, mail when deadline nears)? Power Automate ties in. Keep it simple: 1-2 flows per list, not 8.

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.