If you’ve been building apps on SharePoint lists for a while, there comes a point where you start hitting walls — performance, security roles, relationships between tables, or just the general feeling that you’ve outgrown lists. That’s usually when Dataverse starts looking very attractive.
I’ve been through this migration more than once, and in this tutorial, I’ll walk you through exactly how to move your SharePoint Online list data into Dataverse. I’ll cover three methods so you can pick the one that best fits your situation.
Why Move from SharePoint Lists to Dataverse?
Before we get into the how, let me quickly explain why you’d want to do this in the first place.
SharePoint lists are great for simple scenarios — tracking tasks, logging requests, storing basic data. But they have limits:
- No real relationships — you can use lookup columns, but it’s not true relational data
- Limited row capacity — performance degrades noticeably past 5,000 items (the list view threshold)
- Weak security model — you can control access at the list level, but fine-grained, row-level security is painful to implement
- No server-side business logic — business rules, calculated rollups, and validations are hard to enforce
- Not ideal for model-driven apps — if you want to build enterprise-grade apps in Power Apps, Dataverse is the right foundation
Dataverse solves all of these. You get proper table relationships, row-level security, server-side business rules, and native support for model-driven Power Apps. Once you migrate, you’ll also unlock full Copilot Studio integration and better AI features across the Power Platform.
What You Need Before You Start
Let me save you some frustration. Before you begin the migration, make sure you have:
- A Power Apps environment — you need at least an environment with Dataverse enabled (not just Dataverse for Teams)
- The right permissions — you need the Environment Maker role or higher, plus write access to Dataverse
- Your SharePoint site URL handy — you’ll need it in every method
- A clean, well-structured list — if your SharePoint list has messy data, duplicate columns, or inconsistent values, clean it up first. Garbage in, garbage out.
- A Microsoft 365 or Power Platform license that includes Dataverse storage
Also, take a few minutes to map out your SharePoint columns to their Dataverse equivalents. Text columns map easily, but things like Person fields, Lookup columns, and Managed Metadata need special handling. I’ll flag those as we go.
Migrate SharePoint Online List to Dataverse
Here, I will show you two ways to migrate a SharePoint list to Dataverse, so you can choose the one that best suits your availability.
Method 1: Use “Create with SharePoint List” (The Quickest Way)
Microsoft added a really slick feature to Power Apps that lets you import a SharePoint list and create a Dataverse table—and a canvas app—in one go. If you’re starting fresh and just want to get your data into Dataverse quickly, this is the method I’d use first.
For this method i am using the Training Programs SharePoint list:
Here’s how to do it:
- Go to make.powerapps.com and make sure you’re in the right environment
- From the left-hand menu, select Tables.
- Select Create with SharePoint List
Note:
This is not the only way to reach this screen. There is another way: go to Apps in the left-hand menu, then click + New app. From the dropdown, select Start with data → Create new tables → Import a SharePoint list.
- Choose an existing SharePoint connection or create a new one
- Enter your SharePoint site URL (e.g.,
https://yourorg.sharepoint.com/sites/HR) - Pick the list you want to migrate from the dropdown