What your client receives at the end
Every Liscaragh Migrate run writes a single self-contained HTML report. It is the evidence the migration was done properly, and it is built to hand straight to a client or a manager.
The report is generated from the per-file audit trail, not from a summary count, so the numbers in it are the record of what actually happened. It opens in any browser, needs no internet connection and no login, and can be saved or printed to PDF as a permanent record.
This is a sample report with neutral placeholder data, not a real migration.
Sample report with neutral placeholder data. Your report carries your own figures.
What the report covers
Headline totals
Files recorded, copied, skipped and failed, data moved, average speed and duration, all at a glance at the top.
A row per project
Each project or folder with its destination, and its own copied, skipped, error and data figures, so a multi-project job reconciles on one page.
Every name tidied for SharePoint
Reserved names, illegal characters and over-length paths are corrected automatically, and each original and stored name is recorded, so nothing changes silently.
Source versus destination
An honest note on why Office files are stored at a slightly different size (Microsoft rewrites them on upload) so a size comparison is never mistaken for data loss.
How each file was verified
Non-Office files checked byte-for-byte by size and content hash, Office files verified as stored, and a count of anything that needed a retry and then succeeded.
The security posture of the run
A plain statement that the data moved directly into your tenant, over TLS, with staged files encrypted at rest and the source read-only throughout.
Beyond the report
For a formal sign-off, Liscaragh Migrate also produces a one-page completion certificate for the client, and a tamper-evident provenance pack: a manifest of every migrated file's path, size, content hashes and original modified date, countersigned by an independent RFC 3161 timestamp authority. Only the manifest's 32-byte hash ever leaves the machine.
Want to see it against your own data? Run an evaluation, or book a walkthrough.