Import millions of records into Dataverse
Dataverse limits how fast any one user can write. MDPM gets as close to that limit as it safely can, and recovers on its own when Microsoft says slow down.
Step by step
- Drop in the file. CSV, Excel or JSON. Big files are streamed, so your browser stays responsive.
- Choose the table and mapping. Columns are matched to the table automatically and values are converted to the right types.
- Choose create or update. Create new records, or update existing ones by a key such as an account number.
- Do a dry run. See how many records would be created, updated or skipped.
- Run it. Pause and resume at any time. If anything goes wrong, undo the whole import.
Why teams use MDPM for this
- Large parallel batches with automatic back-off
- Resumes where it stopped after a dropped connection
- Undo removes exactly the records the import created
- Full log of every request
Common questions
How long will my import take?
It depends on your table and your Microsoft limits. Tables with many plug-ins or flows are slower. MDPM shows an estimate before you start.
Will it create duplicates if I run it twice?
Not if you choose update by key: the second run updates the same records.
Try it on your own data
The free plan includes one environment and 10,000 rows a month.