FileCabinet CS to a Windows Network Drive: Keep Your Archive In-House

FileCabinet CS reaches end-of-life on December 31, 2027, and every firm on it has to move its archive somewhere. For firms that want their archive on their own hardware, a Windows network drive is a natural destination. Liscio will migrate your FileCabinet CS archive to a Windows network drive, with every document classified and searchable on arrival, and with no requirement to subscribe to Liscio to complete the move.

First, the files have to come out of FileCabinet CS properly

FileCabinet CS does not store documents as files in folders. It holds them as page objects in a legacy OLE Structured Storage format, so each document has to be reconstituted into a usable PDF before it can go anywhere. A raw export also strips the folder organization you see on screen. (Full detail here.) This is true no matter which destination you pick, and it is the part firms underestimate.

What Liscio does that a file transfer does not

A network drive gives you control but no search intelligence of its own; it is folders and files. That makes classification more important, not less. File Intelligence renames and tags each document to your firm’s standard before it lands, so even on a plain network drive the archive is navigable and searchable by issuer, year, entity, and form type rather than an opaque folder tree.

That is the through-line across every destination we support: the place holds the files, and File Intelligence makes them findable. See all destinations for the full list.

Why a Windows network drive as your destination

Some firms want their client archive on their own hardware, under their own control, not in anyone’s cloud. That is a legitimate choice, and it is the one destination no SaaS competitor will offer, because moving your files onto your own server ends their subscription. Liscio will migrate your FileCabinet CS archive to a Windows network drive, server, or NAS in your own office, so your files stay entirely in your control.

How the migration works

Liscio extracts your FileCabinet CS archive and reconstitutes each document into a complete, readable PDF.
File Intelligence classifies, tags, and renames each document to your firm’s standard.
The organized archive is placed in a Windows network drive, searchable by issuer, year, entity, and form type.
Your files are yours, in a Windows network drive, with no ongoing Liscio subscription required.

Ready to move your files out of FileCabinet CS?

Liscio migrates your archive to a Windows network drive with every document classified and ready to search.

See how Liscio’s FileCabinet CS file transfer service works →

Common questions

Can I migrate FileCabinet CS files to a network drive instead of the cloud?

Yes. Liscio will migrate your FileCabinet CS archive to a Windows network drive, server, or NAS in your own office. This is the destination most cloud-based competitors will not offer, because keeping your files in-house means there is no subscription to sell you.

Will files on a network drive still be organized and searchable?

Yes. File Intelligence classifies, tags, and renames each document to your firm's standard before it lands. That matters more on a network drive, which has no search intelligence of its own, so the naming and organization is what makes the archive navigable.

Is keeping my FileCabinet CS archive in-house more secure?

In-house storage keeps the archive within your own network and control, which some firms prefer for policy or compliance reasons. Security still depends on your own backup, access controls, and disaster recovery, since those become your responsibility rather than a cloud provider's. Weigh that trade-off against the control you gain.

Does migrating to a network drive lock me into Liscio?

No, and this is the least lock-in of any destination. The files sit on your own hardware under your control with no dependency on Liscio or any cloud vendor once the migration is complete.

First, the files have to come out of FileCabinet CS properly

What Liscio does that a file transfer does not

Why a Windows network drive as your destination

How the migration works

Common questions

See it on your own files