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 map

Run a map you made or edited

Run a Move/Copy map: the same file browse and pick writes when you plan or run. Plan in the GUI, change where things land in Excel, then load it here - or write one from the template. Best when the destination layout comes from a spreadsheet.

Makes changes. Every row in the file is acted on. Check it before running.

What it does

  • Exactly which items go where, in a file you can review, share and keep.
  • The same run again next month, because the file is the definition.

How it runs

  1. Get a map. Plan the run with browse and pick, or download the template. Both are the same format.
  2. Edit it. The first row (Initial) names the source and destination sites. Each row under it is a folder to make or an item to copy or move, with where it lands.
  3. Load it. The rows are checked and listed before anything runs. A file that isn't a run map is refused, not guessed at.
  4. It runs. Exactly the rows you were shown, from a fresh copy saved with your other run maps, on the same loader and engine as every Move/Copy - so it can be resumed, checked or undone.

How it works

The CSV method loads a run map, not a format of its own: the same columns browse and pick writes. Its first row names the source and destination sites, and each row under it names an operation, its source and where it lands. The file is checked before anything runs, and a file that is not a run map is refused. What runs is a fresh copy of exactly the rows you were shown, saved beside your other run maps; the file you loaded is not changed.

It runs on the same engine as a resume, so a row the map already records as complete is not done again, and progress, undo and Check results work exactly as for any other run. A row whose source or destination cannot be resolved fails on its own and the rest of the map carries on.

What you need

  • Write access to the destination, and read access to the source. For a move, write access to the source too.

What it will not do

  • One source site and one destination site per map - the two the Initial row names. Rows may use any library in them.
  • A typo in a path is a failed row rather than a wrong write: each row reports its own failure and the rest carry on.

See every feature