Rollback365

The gap Microsoft leaves open

Version history

Restore a previous version — of one file, by hand. Fine for one. Useless for 400.

Restore this library

Rolls the whole library back to a point in time: everyone's good changes along with the bad ones. And only within the last 30 days.

The missing middle is: select a precise subset by search, then roll only that subset back to a point in time. That's the product.

What it does

Find the damage. Filter a library by modified-between, modified-by (people picker), path, extension, filename pattern (ransomware suffixes), size change, or version count. Filters combine; the match count updates as you type.
Roll back per file, not per version number. Each file goes to its own newest version created before your chosen time — version numbers differ per file, so "version 12" means nothing across a set.
Dry-run with five buckets. Restorable · created after the incident (flagged, not touched) · no prior version · checked out by someone else · already current. Counts by reason, never one number.
Batches, throttling, resume. Built for 20,000-item libraries, honours Retry-After, and picks up where it stopped if you close the tab.
Success and failure CSV, per item, before you leave the page.

What it will never do

Restoring a version creates a new current version and removes nothing; the old state stays in history. The product has exactly one write endpoint — restore file version by label — and no delete, purge, or version-removal call anywhere in the code. Same published-endpoint-list, same build-time check, same verifier as Undelete365.

Read this before you restore. SharePoint now thins version history by age: every version is kept for 30 days, then hourly ones to 60 days, daily to 180, weekly after that. So "roll back to Tuesday 14:02" is precise inside the first 30 days; past that, the nearest surviving version for a given file may be an hour, a day or a week earlier. Rollback365 shows you the actual timestamp it will restore, per file, in the dry-run — but it can't restore what SharePoint has already trimmed. It works within the history you have.

Scope of the first release

In	Not in v1
One document library at a time, on the site where you add it	Multiple libraries in one run; tenant-wide scans
Files, restored to content as of a point in time	List items; folders as objects; metadata columns restored separately
All filters above, dry-run, batch restore, resume, CSVs	Anything touching the recycle bin — that's Undelete365

Rollback365 has shipped

Rollback365 is no longer a pre-order — it ships live today, as one of the seven tools in TenantTools365. Pre-orders on this page are closed; head to TenantTools365 to buy Rollback365 on its own or as part of the full suite.

Live now · via TenantTools365

€399one-time · per tenant · ex VAT where applicable

Bulk version-history rollback with dry-run
Delivered instantly — no pre-order, no waiting
Also available as part of the full 7-tool bundle

Get Rollback365 on TenantTools365 →

Already have an Undelete365 Pro license? It's a separate product — Rollback365 needs its own key from TenantTools365.

Someone synced a bad folder over 400 files at 14:02. The files are still there. They are just all wrong.