The folders inside each FileCabinet CS drawer are years of filing decisions: tax years, engagement types, permanent files, correspondence. When firms export, that structure is usually the first casualty. Here’s why it happens, how to work around it by hand, and what to check in the system you’re moving to.
What FileCabinet’s own export does with folders
- No setting keeps the tree. Thomson Reuters’ guidance is that if you want documents separated by folder, you need a separate export for each folder association (Thomson Reuters).
- Folder names can go in the file name instead. Send to > File can append the Drawer ID, Drawer Name, Folder or Creation Date to each file name, but not alongside custom file names (Thomson Reuters).
- Drawer families mix documents. If a drawer is linked into a family, the export list includes documents from the other drawers too, so name files by Drawer ID to keep clients apart.
The result is a flat folder of long file names that someone has to sort back into clients and years.
The manual workaround, and what it costs
- Export one folder association at a time, into a destination folder named to match.
- Turn on the Drawer ID and Folder file-name options so stray files can still be traced.
- Repeat for every folder in every drawer.
The math adds up fast. A firm with 400 drawers and six folders each is looking at 2,400 separate exports before anyone checks whether every document made it.
Plan the new structure before you export
Decide what the folders should look like in the new system first, because each destination has its own rules:
- SharePoint and OneDrive: the full path, including the file name, can’t exceed 400 characters (Microsoft), and Microsoft advises against folder trees more than one or two levels deep, favoring metadata columns instead (Microsoft). See FileCabinet CS to SharePoint.
- SmartVault: folders come from templates tied to client type and engagement, such as a tax engagement by year (SmartVault). See FileCabinet CS to SmartVault.
- CCH Axcess Document: each client follows a folder template for its entity type, and every file needs a class and subclass when it’s added (Wolters Kluwer). See FileCabinet CS to CCH Axcess Document.
- NetDocuments: everything lives in a cabinet, with up to 500 subfolders per folder (NetDocuments). See FileCabinet CS to NetDocuments.
Wherever you land, avoid characters most systems reject in names: " * : < > ? / \ |.
Recurring and yearly folders
If you’re considering Thomson Reuters’ Onvio, note that its migration flattens recurring folders to a single level, separated by year (Thomson Reuters). Check that layout against how your staff search before you commit.
How TekBryte keeps your folders
Our bulk export writes each drawer to its own folder with FileCabinet’s folders inside it and document names intact, and carries annotations and drawer notes along. Staff open the new system and find files where they always were, and the verification report proves nothing went missing on the way.
Want your folders to survive the move?
Ask for a free export assessment and we’ll show you how your drawers will land. Replies within one business day.
Exports run on TekBryte FileCabinet Recover, our own bulk-export software.