Add Excel rows to a SharePoint list you already have

Short answer: the "From Excel" import creates a new list. It does not add rows to a list you already have. Paste the rows in grid view for a small batch, or use a Power Automate flow that reads an Excel table for a large or repeated one. Match your columns first. The 5,000-row limit Microsoft gives is for creating a new list from a table, not for adding rows.

Why the wizard does not do this

Microsoft says importing an Excel file creates a new list. Its words: "This method converts the table headings to columns in the list, and the rest of the data is imported as list items." It also says: "You can use tables with up to 5,000 rows to create a list." So if you run it a second time, you get a second list, not more rows in the first one.

Microsoft adds: "When you're using a site template, it is no longer possible within SharePoint to create a list from an Excel workbook." Its page says you can still export data to SharePoint from Excel. If you are starting from nothing, the wizard is the right tool. For the full move from a spreadsheet to a list, see "Replace a spreadsheet tracker with a SharePoint list". This guide is for the other case: the list already exists, people already use it, and you need to add more rows from Excel.

Pick a method

A few dozen rows, one time: paste in grid view (Method 1).
Many rows, or the same job every week: a flow (Method 2).
Not sure: start with Method 1 on a test list. It needs no setup.

Exact menu and action names change over time, so exact names may differ on your screen.

Before you start: the pre-flight checklist

Check each one in your Excel file before you copy anything.

Make a copy of the Excel file. Work in the copy. Keep the original untouched.
Match the column names. Each Excel heading should match a column in the list. Open the list and write down its column names and types.
Match the column types. Microsoft says all values must match their column type. A date column needs real dates. A number column needs numbers. Text such as "TBD" in a date column will cause trouble.
Fill the Title column. If your Excel file has no Title column, put a short unique label in each row, such as an order number or a name.
Check required columns. Microsoft says you must enter a value in any column that has an asterisk in the list. Rows with blanks there will not go in.
Check Choice columns. The words in Excel must match the choices in the list exactly. If your Choice values are numbered, like 1 High, 2 Medium, 3 Low, copy the numbers into Excel too.
Check Person columns. A Person column in the list needs a real person. Use the work email address or the full name exactly as it shows in your organization. See the notes under Method 2.
Delete blank rows. A blank row can become a blank item.
Check for rows that are already in the list. See the duplicates section below.

Method 1. Paste the rows in grid view

This is the method Microsoft documents on its support page for adding list items. Steps follow it. Exact names may differ.

In Excel, select the rows you want. Select only the cells, not the headings. Copy them.
Open your list.
On the command bar, choose Edit in grid view. If you do not see it, make sure you are not already editing the list and have not selected any items.
Choose Add new item.
Put the cursor in the first blank column of the new row and paste. Microsoft says this starts the paste.
Look at the rows that appear. Check dates, names and choices.
When you are done, choose Exit grid view.

Notes from the same page:

You need at least Contribute permission on the list to add items.
You cannot attach a file to a list item while in grid view.
Our advice, not a Microsoft rule: paste lands by position, not by heading name. Put your Excel columns in the same order as the list columns on screen, and check the first rows.

If the paste lands in one cell, click outside the grid, then click the first blank cell again before you paste. Our advice, not a Microsoft rule.

Paste five rows first. If those look right, paste the rest.

Method 2. A Power Automate flow

Use this when you have many rows, or when the same file comes in again and again. The flow reads rows from an Excel table and creates one list item for each row. Microsoft documents the actions on its connector pages. Exact names may differ.

What you need:

The Excel data formatted as a table. The Excel connector works on tables. If your data is not in one, select it and use Format as Table on the Home tab.
The Excel file saved in OneDrive for Business or a SharePoint library. The connector works with files there.
A file in .xlsx format. Microsoft lists .xlsx and the binary workbook format as supported.
Edit access to the file and to the list.
Check with your admin whether your plan includes Power Automate and these connectors.

The steps:

In Power Automate, start a new flow you run by hand (an instant flow). Use a manual trigger while you test.
Add the Excel Online (Business) action called List rows present in a table. Choose the location, the library, the file and the table.
Turn on pagination for that action. Microsoft says it returns up to 256 rows by default, and that you turn on pagination to get all rows. Set the threshold higher than your row count.
Add the SharePoint action called Create item. Choose the site address and the list name.
Place the Create item action inside the loop that Power Automate adds around the rows. It runs once for every row.
Map each list column to the matching Excel column from the dynamic content. Map Title first.
Save the flow. Run it on a copy of the file and a test list.
Open the test list and check the items. Then point the flow at the real list and run it again.

Excel column types and list column types. Match them before you map.

Excel text goes into a Single line of text or Choice column. For Choice, the words must match a choice in the list.
Excel numbers go into a Number column.
Excel dates go into a Date and time column. Check the DateTime Format note below.
Excel names or emails go into a Person column through Resolve person, below.

Our advice, not a Microsoft rule: confirm each pairing on five test rows before the full load.

Dates. The List rows present in a table action has an optional DateTime Format setting. Excel can store a date as a plain number, so look at what the flow brings in. If a date looks wrong in your test list, set the DateTime Format option and run the test again.

People. The SharePoint connector has an action called Resolve person. Microsoft says it returns a single matching user so the value can go into a Person column. If there are no matches or more than one match, the action errors. So a name that two people share, or a misspelled one, will stop the run. Use email addresses when you can.

Limits on the Excel side, from Microsoft's connector page:

The largest Excel file the connector supports is 25 MB.
Rows for the first 500 columns come back by default.
Column headings that contain only a number can cause unexpected behavior. Rename them so they include other characters.
Do not edit the file by hand while the flow runs. Microsoft says simultaneous changes from other clients are not supported and can cause conflicts.
The connector page lists a throttling limit of 100 API calls per connection per 60 seconds. A long loop may slow down or return a 429 error. Microsoft suggests adding delays around the action.
A flow that runs twice creates every item twice.

Duplicate check inside the flow (Our advice, not a Microsoft rule): before Create item, add a SharePoint Get items action with a filter on your unique ID column set to the ID in the current Excel row. Then add a Condition that checks whether Get items returned no rows. Put Create item in the Yes branch. Test on a copy first.

Do not skip the duplicates check

Neither method knows which rows are already in the list. Paste the same rows twice and you get the rows twice. Run the flow twice and the same thing happens.

Add a column to the Excel file that says which rows are new, and copy only those. Or give the list a column for a unique ID (an order number, an invoice number) and sort by it after the first load, so repeats are easy to see. For more on keeping repeats out of a shared tracker, see "Stop duplicate entries in a shared spreadsheet".

Test with a copy first

Create a new test list with the same columns.
Load five rows into the test list.
Check each column type: dates, people, choices, numbers.
Load the full batch into the test list.
Compare the row count in Excel to the item count in the list.
Only then load the real list.

If something goes wrong in the real list, you can sort by the Created column and delete the bad items. Do that with care, and tell the team first.

What to avoid

Do not run the "From Excel" wizard hoping it adds rows. It makes a new list.
Do not paste straight into the live list on the first try.
Do not paste text into date, number or Choice columns that does not match.
Do not leave blank rows or notes above the headings in the file.
Do not edit the Excel file while a flow reads it.
Do not run the same flow twice on the same file.
If the old spreadsheet stays in use, versions will drift. See "Spreadsheet versions out of sync: why it happens and how to fix it".
If the file shows a lock message when the flow tries to read it, see "Excel file locked by another user: the fix and the long-term fix". Microsoft says a file can stay locked up to 6 minutes after the connector last used it.

Honest limits

Grid view paste is quick, but it is manual. A flow is repeatable, but it takes time to build and test, and it needs the right plan and permissions. Neither one removes the need to clean the data first. If your rows come in every week from people filling out Excel, a form that writes straight to the list may be a better long-term choice than a repeat import.

When to get help

You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: $5,000 for one, built in 2 weeks. See "What a SharePoint tracker costs to build". Bring one example of the problem to a free call.

Tell me what's still manual

I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.

See trackers I built: Tools I built

FAQ

Can the Excel import add rows to an existing list?

No. Microsoft describes it as a way to create a list from a spreadsheet. To add to a list you already have, paste rows in grid view or use a Power Automate flow.

How do I import items from Excel to an existing SharePoint list?

Paste the rows in grid view for a small batch, or use a flow with List rows present in a table and Create item for a large one. Test on a copy first.

How many rows can Excel import into a SharePoint list?

Microsoft says: "You can use tables with up to 5,000 rows to create a list." That limit is for creating a new list from a spreadsheet.

Why did only 256 rows load?

Microsoft says List rows present in a table returns up to 256 rows by default. Turn on pagination in the action settings to get all rows.

What happens if I load the same rows twice?

You get every row twice. Neither method checks for repeats. Check for duplicates before you load, and test with a copy first.