Journal
Two terabytes is a storage figure. It does not tell you how many versions, how many .pst files sitting inside project folders, how many CAD drawings with broken xrefs, or how many items have unique permissions.
We ran an inventory on the source shares. The headline volume was close to the guess. The object count was 1.8 million. Unique permission scopes numbered in the thousands. Nearly 40,000 files had extensions the target platform would block.
The migration partner’s first plan assumed a weekend cutover. After the inventory, the plan became a six-month programme with disposal of stale course materials, a blocked-type quarantine, and a decision to leave some research stores where they were.
None of that is glamorous. It is the difference between a move and a loss. A migration readiness assessment is an audit of the source application and the file system that has been pretending to be one.
If a vendor quotes a window before anyone has counted versions and permission scopes, ask them to wait. The calendar should follow the inventory.