Identify both locations
Choose separate source and destination folders. Check the actual external drive or network path; a familiar drive letter alone is not a durable identity. Confirm destination availability and space, and start with a small fixture folder.
Do not use a destination inside the source tree. Keep active databases, virtual machines and documents being edited out of an ordinary file-copy test unless you have a consistent snapshot or the owning application’s backup workflow.
Check coverage, not just totals
Compare relative paths, expected files, sizes, errors and skipped items. Equal file counts and byte totals do not establish equal contents. Report missing, different, conflicting and unexamined files separately.
A disconnected network share, access-denied item or provider placeholder leaves a gap. Do not count a skipped file as verified. A network copy also depends on the remote filesystem and permissions.
Use a content check where needed
A content hash checks the bytes read from a file. For an individual pair of stable files, PowerShell’s Get-FileHash can calculate SHA-256. Replace these example paths with your own copied test files and compare the Hash values:
Get-FileHash -LiteralPath 'C:\TestCopy\source.txt' -Algorithm SHA256
Get-FileHash -LiteralPath 'E:\TestCopy\source.txt' -Algorithm SHA256
Hashing reads contents. Cloud providers may download online-only data, and large files can take time. Matching main-file hashes do not certify identical permissions, alternate streams or all filesystem metadata. A successful read is not a guarantee against a later device failure.
Use WhimRoom’s reviewed copy
WhimRoom’s copy plans use separate approved folders and content-bound observations. They preserve sources and avoid overwriting occupied targets in the supported workflow. Review conflicts and exact tool limits, approve the native plan and inspect the final result.
Connected-storage tools distinguish local, external, network and Windows-connected cloud locations. The connected-storage copy plan leaves online-only entries and conflicts for review. Availability checks are observations, not permission grants or reservations of destination capacity.
Make source removal a later decision
Open representative outputs in their owning applications. Keep a usable backup where needed and make sure no project still depends on the original path. Recheck the destination before any later removal.
Copy verification does not authorize deleting the source. If a transfer failed or was interrupted, inspect partial results and recorded status before retrying. For combining existing folders, start with the missing-only guide; for cloud space, read OneDrive’s different actions.
Sources and scope
WhimRoom workflow descriptions use the 0.273 tool catalog. External documentation describes its own product. This guide is not a new speed benchmark or recovery guarantee.