Splitting a sharepoint list used as database

New Contributor


I recently became the owner of a Powerapps application to code calls for our call center. Though I understand data, know some very basic coding and know my way around excel, I am still relatively green when it comes to the more technical aspects of storing and managing larger sets of data. 


Here is my problem : 
The powerapp was created internally by a manager with what he had learned online. The app itself works perfectly however the data entries from the call coding are pushed to a sharepoint list that is used as a database. In the past, this allowed us to extract to excel from sharepoint and manipulate to gain insight, however the list has reached 1,07 million entries, which makes it very slow to extract and handle, on top of losing out on some of the data for having reached excel limit. 


Would it be possible for me to split the list so I could archive year by year therefor reducing the amount of entries to extract? Or is there a better solution that is accessible for someone with my level of experience? 


Thanks in advance for any help. 

4 Replies

Hi @Riverain96,


Splitting the list by year is a good approach.


I would create additional Views that filter based on year and export those rows to Excel. From Excel, I would export to a new SharePoint List. Removing the archived rows is time-consuming and I would suggest looking into Powershell to do it, specifically Remove-PnPListItem.


I would not change the default view that is referenced by the PowerApp. Also, consider a yearly archive and purge to keep performance high (in its current state anyway).


I hope this helps.



Thanks for the reply!

I will look into powershell to see if I can make it work that way, though it seems more and more that a sharepoint list just isnt the proper way to store our data.

Also - I looked into creating a flow to archive part of the list into a new list but the 5000 line limit seems to make it impossible.

Thanks again for the help!

@Riverain96 views that filter based on year should overcome the 5,000 limits.