I recently completed a large-scale file reorganization project with the assistance of Claude. The experience is worth sharing for anyone considering similar work.
The Problem
For years, my documents had accumulated inside iCloud Drive’s application-specific containers, each app maintaining its own folder hierarchy entirely separate from every other app. Files lived under iCloud/Pages, iCloud/Keynote, iCloud/Numbers, iCloud/iA Writer, iCloud/MindNode, iCloud/OmniOutliner, and similar locations. Finding a document required remembering which application had created it. Searching across topics was practically impossible because related files were siloed by tool rather than organized by subject. Moving to a new device, switching applications, or locating something from a mobile device was far harder than it should have been.
The goal was to move every file out of those application containers and into a single, unified Documents folder organized by topic and purpose, a structure that would remain coherent regardless of which application created or opened a given file.
A secondary goal was to ensure that my files were being backed up. Like many in this forum, I discovered to my chagrin that BackBlaze was not backing up files stored in iCloud. 
That discovery alone required moving the files and transitioning to a different backup service.
What the Work Actually Required
Before any file could be moved, I consolidated the source material. The application folders, Pages alone contained thousands of files, were copied into a staging folder (00 Source) so the work could proceed while the originals remained protected. The destination organizational structure had to be designed from scratch: seventeen numbered topic folders, each containing format-named subfolders along with asset folders for images, video, audio, and ZIP files.
Across all the application folders, there were more than 18,500 raw files to process. According to Claude, the project involved 3,109 distinct logical items spanning eighteen file types across seventeen destination folders. Every file had to be examined to determine its correct destination, moved to the appropriate topic and format subfolder, and verified. Beyond moving files, the work required identifying format violations, converting legacy plain-text files to Markdown, consolidating scattered blog content under a unified folder so that iA Writer could treat it as a single library, and creating asset folders throughout.
At a conservative estimate of two minutes per logical item, the manual work would have required roughly one hundred hours. At three minutes per item, it would have exceeded one hundred fifty hours. That estimate does not account for designing the seventeen-folder structure, creating every destination subfolder, running verification passes, correcting mistakes, handling the blog consolidation, or producing a final inventory. A realistic estimate would approach several full work weeks. I believe it. In fact, the prospect was so daunting that I would not have undertaken it on my own. I would have simply copied my existing structure from iCloud into the Documents folder and been left with the same inefficient arrangement I had started with.
What Claude Did
Over approximately twenty-four hours spread across two days, with my active supervision and direction, Claude designed and built the entire destination folder structure, wrote and executed all the scripts to copy and move files into their correct locations, ran multiple compliance scans to identify format violations and misplaced items, corrected every violation it found, consolidated the blog’s Markdown content under a unified parent folder, created asset folders wherever needed, and converted all legacy plain-text files to Markdown. When I identified problems, and there were several, from Finder screenshots, Claude diagnosed the root cause, corrected its logic, and re-verified. When its first approach to the blog consolidation produced an incorrect result, it revised the method until the structure was exactly right.
This is a fitting illustration of President Reagan’s maxim: trust, but verify.
At the conclusion of the project, Claude produced a two-sheet Excel manifest: a Summary tab showing file counts by folder and file type, and a complete File Manifest tab with one row per logical item, recording the destination folder, topic subfolder, format folder, file type, extension, filename, and relative path. That manifest now serves as the authoritative inventory before I remove the original application containers from iCloud.
The Benefit
The reorganized structure is application-agnostic. Files are grouped by subject and purpose rather than by the tool that created them. Any application on any device can locate what it needs. Related files from different applications now sit in the same topic folder. The iA Writer library reflects my actual editorial categories. And when I am ready to delete the original application-specific containers, I have a verified manifest confirming that every file was accounted for and correctly placed.
This was not a project I would have completed on my own. The volume made it impractical, and the tedium would have guaranteed errors and would have driven me crazy!
What Claude accomplished in a matter of hours, with my supervision and oversight throughout, would have represented weeks of careful, painstaking work. For anyone managing a large, disorganized file library across multiple applications, this kind of AI-assisted reorganization deserves serious consideration.
The donkey completed its work, but proved stubborn at times. 