SharePoint is not a file dump

The migration pitch for Microsoft 365 is usually framed around Teams and SharePoint. Teams replaces email threads. SharePoint replaces the shared drive. Most organisations make this move, recreate their folder structure in SharePoint document libraries, and call the project complete. They have not changed how they work. They have changed where the files live.

This is a significant waste of a tool that, used correctly, functions as a structured operational database available to the entire organisation in real time.

What SharePoint Lists actually are

SharePoint document libraries store files. That is their purpose and they do it well. But SharePoint also has Lists, and Lists are an entirely different thing.

A SharePoint List is a structured table of records. Each item in the list is a row. Each column is a typed field — text, number, date, choice, person, lookup. Lists support calculated columns, conditional formatting, filtered views, and permissions down to the item level. They update in real time. They are accessible from Excel via Power Query. They connect directly to Power Automate. They feed Power BI dashboards without any intermediate data layer.

Most teams have never touched one. They are solving structured data problems with spreadsheets stored in document libraries, which means they are dealing with version conflicts, manual aggregation, and no visibility across the team — problems that a List would eliminate immediately.

Three places where a List beats a spreadsheet

Submission tracking. If you are running any kind of recurring submission cycle — expense claims, audit forms, monthly reports, compliance checklists — a SharePoint List is the correct tool. Each submission becomes a list item. Status, date, assignee, and any structured data fields are columns. Everyone with access can see the current state of all submissions in real time. There is no "final_v2_ACTUAL.xlsx" problem because there is no file to version.

Asset or resource registers. Any inventory or register that multiple people need to read from or update — equipment lists, contract registers, supplier databases, employee onboarding checklists — belongs in a List. A spreadsheet breaks the moment two people try to edit it simultaneously. A List handles concurrent access cleanly, logs every change, and can have different views for different audiences without duplicating the underlying data.

Operational dashboards. A List connected to Power BI creates a live dashboard that updates without any manual export step. The data lives in one place. The dashboard reads directly from it. When a record is updated in SharePoint, the dashboard reflects it. This is not a complex integration — it is how these tools are designed to work together. The reason more teams are not doing it is that they never moved their data out of spreadsheets in the first place.

The permission and access advantage

A SharePoint List has granular permission controls that a shared spreadsheet cannot match. You can give a manager read access to their region's records and no others. You can allow a team to add items but not edit or delete existing ones. You can create views that show different columns to different audiences without maintaining multiple versions of the data.

This matters most in organisations with regional structures or role-based access requirements. The alternative — maintaining separate spreadsheets per region and aggregating manually — is what most teams are doing. It works until someone sends the wrong file to the wrong person, or until the aggregation step fails silently and leadership is looking at last month's numbers.

The migration is not complicated

Moving from a spreadsheet to a SharePoint List is rarely a large project. Define the columns, import the existing data, set the permissions, connect Power Automate if there are workflows involved. The friction is almost entirely in changing the habit — people are comfortable with spreadsheets and unfamiliar with Lists.

That comfort is costing them. The infrastructure to do this better already exists in every Microsoft 365 licence. It is not being used because nobody explained that it was there.