ShareMaster V2 is in beta, a complete rebuild. See what is new and request access →
Features All features overview
Migration Tools Overview Structure and content OneDrive ↔ SharePoint Content only Structure only Move / Copy Upload from this computer Download to this computer Dropbox to SharePoint Resume and incremental runs
Recycling Bin Overview Browse a site's recycle bin Empty recycle bins in bulk Restore and purge history
Archive Overview Configure the tenant On Demand Archive Restore Archived Files Archive Savings Report Blob Viewer
Optimise Storage Tools Overview Delete all items in a list Delete all files and folders in a library Remove empty folders Remove duplicate files Reduce image sizes Delete sites and subsites
SharePoint Tools Overview Tenant Explorer SharePoint Explorer Easy Settings Fix renamed groups List Explorer Search the Preservation Hold Library
Replace Overview Replace in SharePoint Replace in local files Find password-protected files
Shared Links Overview Report shared links Report unique permissions Remove a person from sharing links Remove shared links Remove unique permissions
Version History Overview Version trimming Version trimming report Reset file version
Reports Overview Inventory report Folder inventory Site and subsite storage Security matrix Teams permissions Pre-migration analysis Compare items Dropbox to Microsoft 365 compare Duplicate file report Empty folder report Image size report Recycle bin report Unused licences Report history
V2 beta Pricing Demos Blog Guides Use cases Compare Tools Alerts FAQ Contact Sign in Start free trial
  1. Home
  2. Documentation
  3. Migration

Use a CSV

One row per local path and destination URL

Map many local files and folders to their destination URLs in one file. Unlike the browser path, rows can target different sites and different libraries, which makes this the one to use for a scripted bulk load.

Makes changes. Every row in the file is acted on. Check it before running.
On this page What it does How it runs How it works What you need What it will not do

What it does

  • Which local paths go where, in a file you can review and keep.
  • Which rows are valid, before the run: paths and URLs are resolved and reported first.

How it runs

  1. Download the template. Correct columns, ready to fill.
  2. Fill it in. One row per local path and its destination URL. Rows may span sites and libraries.
  3. Bring it back. Rows are validated and listed. A bad row is reported rather than guessed at.
  4. It runs. Row by row, per-file progress.

How it works

Each row names a local path and a destination URL. Rows that cannot be read are listed when the file loads and left out. Rows that share a destination URL upload together, as one pass of the upload engine; each destination is resolved to its site and library from the URL (the longest library address the URL starts with wins, and anything after it is the folder). A destination that cannot be resolved fails all of its rows, and the other destinations still upload.

The CSV method does not ask the options questions: dates follow the settings on the page, authors are not mapped, and the destination is not checked for existing files first. The whole file is recorded as one run in Migration history.

What you need

  • Write access to every destination named in the file.

What it will not do

  • A local path that no longer exists is a failed row, listed with its reason.
  • A CSV upload does not check the destination first. A file already at the same path is replaced by the uploaded one.
  • Rows can reach any site you have access to, so a mistyped URL can write somewhere you did not intend. The validation pass is there to catch that before the run.

See every feature