Duplicate a SharePoint site on the same tenant, or migrate it to a different one. Pick a source and a destination and V2 copies the structure and the content: lists, libraries, content types, views, items, files, versions and permissions.
A clone three minutes in, moving a 4 MB file. The header counts bytes both ways, the bars show the file in flight, and the status line says what it is waiting on instead of going quiet.
Every item it finds lands in the list below the counters, with its own status and the reason it was skipped or retried. Lists, Migration events and the Microsoft log each have their own tab, so you can watch Microsoft's migration job as well as ours.
The 595 skipped items here are things the destination already had, such as site features that were already switched on. Skipped is a count of work avoided, not a failure, and each one says why.
When the run finishes, one click runs a deep compare of every item and field value between source and destination, or a faster shallow compare of counts and missing items. This run came back 100% similar.
Every save in a versioned library keeps another copy of the file, and every copy counts against your SharePoint storage. Version trimming removes the versions you do not need under rules you set, and shows you exactly what it would remove before it removes anything.
Removing versions: 212 gone, 20 of 49 files done, nothing failed. Each file shows how many versions it keeps and how much space it gave back.
Keep the newest N versions, only remove versions older than a date, keep at most N a day, keep retained versions at least N hours apart, skip recently modified files, and narrow by extension or file name.
The same scan runs first as a preview that changes nothing: 531 versions across 49 files, about 5.1 MB, listed file by file as "Would remove". Only then does Remove versions become the next step.
Removed versions go to the site recycle bin unless you tick Permanently delete, so a trim you regret is a restore, not a support ticket. The screen says so too: the space is reclaimed once the bin is emptied. There is also a report-only version of the whole tool for sign-off before anyone trims.
Deleted files stay in the SharePoint recycle bin for 93 days, but the bin itself is a long list with a search box that matches on the item name only. V2 opens a site's first-stage or second-stage recycle bin as a filterable grid, so you can find deleted files and restore them in bulk.
83 items in a site's first-stage bin. Filter by title, original location, kind, who deleted it and when, then restore, move or delete what is left.
Filter by title, original location, item kind, the person who deleted it and a deleted-date range, then select the rows you want. Results are paged, 100 rows at a time by default, so a big bin stays quick to work through.
Choose what happens when a restored item meets something already in its place, such as skipping the folder or renaming the file, before you press Restore. The confirmation spells it out: which items, which site, which bin, and what happens on a clash.
Switch between the first-stage (site) bin and the second-stage bin from the same drop-down, move items to the second stage, or empty a bin when you mean to.
Close to your SharePoint storage limit? Microsoft's Storage Metrics page shows one site at a time. The storage report reads every site you select, finds their subsites, and measures each library and list, so you can see which ones are actually using the space.
Phase 3 of 4, measuring libraries across 250 sites and subsites. Totals fill in as each site completes, and the request in flight is shown with its retry count.
"Reading the selected sites and measuring their storage. Nothing is changed." The report never writes to your tenant.
It always reads SharePoint's own site-collection total as well as running its detailed scan, and shows the direct, calculated and authoritative figures side by side, so you can see where they disagree. Preservation hold libraries and both recycle bin stages can be counted too, which is often where the "missing" storage turns out to be.
Separate tabs for sites and subsites, libraries and lists, recycle bins, deleted sites and every request made to Microsoft 365, so a long run never looks stuck when it is not.
Sharing links are easy to create and easy to forget, and with external sharing on, some of them reach outside your organisation. The shared links report walks the libraries you choose and lists every link it finds, Anyone links, organisation-wide links and specific-people links alike, with what each one allows.
Seven links found across a site's libraries, each showing its scope and whether it grants view or edit.
Report every link, or filter by link scope, link type, or only links that have already expired, which makes a low-risk first clean-up. You can also match files by name.
The same scan runs across dozens of libraries and tens of thousands of items, counting as it goes, with findings appearing while it works rather than at the end.
The report changes nothing. Removing links, removing a person from links and removing unique permissions are separate tools in the same menu, for when you have decided what to do.
The same file saved in five places is five times the storage. V2 finds duplicate files across the SharePoint sites and OneDrive accounts you tick, including copies of the same file in different sites.
You decide what counts as a duplicate, from a quick name match to a byte-for-byte comparison of the contents.
Matching by name is free and says nothing about the contents. Name and size is usually right. Name, size and contents compares the actual bytes, using the hash SharePoint already stores for each file.
Optionally match byte-identical files whose names differ, such as "Q3 Report FINAL.docx" beside "Q3 Report.docx", and treat "Report (1).docx" and "Report - Copy.docx" as the same name.
Stage one is a read-only report: the duplicate sets, where they are, and how much keeping one copy of each would reclaim. It saves as Excel plus a CSV you can mark up, and removal is a separate stage that starts from a saved report.
Move a folder from a PC, or from a file server drive mapped on it, into a SharePoint library or OneDrive, folder structure and all. It is a file server to SharePoint migration without dragging folders into a browser.
150 files and 49.5 MB going up from a local folder. It runs on the same progress screen as a clone: the file in flight, counters, and every folder and file as it lands.
Created and Modified dates are preserved by default, so a library does not look as though every file was written the day you migrated.
Existing files at the destination are left alone. Turn on the destination check to skip files that are already there, or update the ones whose size has changed, which is what you want when re-running into a library that is already partly filled.
Optionally read each file's owner from disk and map it to a person at the destination, so Created By means something. It is best-effort by design: a file's owner is usually, but not always, its author.
The V2 beta is in the members area for anyone with a ShareMaster account, including a free Community account. It installs beside V1, and your existing licence carries across.