Skip to content
A records officer at work between walls of archive drawers.
Case study · Digital & IT

Carried out a file migration that used AI to rename, re-path and re-file a group's documents

A multi-entity business group · 4 min read

Moving onto one platform exposed a group's messy filing. We built the standard and the process that let AI rename, re-path and re-file more than 100,000 of its documents.

The client

Our client is a group that runs its business through several entities, each with its own documents and its own way of filing them.

The group was moving every entity onto one tech platform: a single cloud workplace where people store, share and find documents together. A move like this is a chance to fix how files are kept. It is also the moment every hidden problem surfaces, because each file has to land somewhere.

Some files needed special care, above all the group's Transaction Bibles. A Transaction Bible is the bound record of a completed deal: the signed agreements and closing documents, compiled into one indexed set once the deal is done. People turn to it when they need to check what was agreed, so its contents and order must stay exactly as they are.

Context

As the move got under way, the true state of the group's file estate became clear. The problem was not one messy folder. It was different filing habits, multiplied across every entity.

The same folders and files sat in several locations, so nobody could be sure which copy was current. File names followed no shared convention, so a contract in one entity looked nothing like a contract in the next. Some folder paths ran past the document platform's path-length limit, so those files could not move across as they were.

Documents sat in folders that did not reflect their content, and many could be found only by the person who had filed them. If that person was away, so was the document. Then there was the volume: far too many files to review one by one.

This is where file migrations often stall. Reviewing every file by hand takes more time than a business can spare. Copying everything across as it is just moves the mess.

To move onto one platform cleanly, the group needed:

  • One folder structure, applied the same way in every entity
  • A shared naming convention, so anyone could find any file
  • Folder paths short enough for the platform's limit
  • Every document filed where its content says it belongs
  • A way through the volume without a file-by-file review
  • Its deal records kept exactly as they were
Hands lifting tied files out of an archive box.

Approach

We agreed an 11-folder standard with the group, then built a repeatable ten-stage migration process to move each entity onto it, from inventory through to go-live.

The standard came first. The same 11 folders apply identically across every entity, with naming conventions and sub-structures defined beneath each one. That gave every file one right answer: one name, and one place it belongs.

We also drew a firm line around the Transaction Bibles. They were protected from renaming and relocation, so every deal record stayed intact.

With the standard agreed, AI did the renaming, re-pathing and re-filing. People set the rules and checked the plan before anything moved. For each entity, we:

  • Inventoried the source files as an auditable baseline
  • Mapped every file from its old name and location to its new one
  • Ran two levels of review before executing the migration
  • Issued a migration report for each asset group on completion

Running the same stages for every entity kept the work consistent and traceable, from a recorded baseline to a report of what moved and where.

A developer pointing at a laptop as a colleague takes a call.

Impact

The group now works from one platform and one standard, with its files where people expect to find them.

Every file renamed and re-filed

More than 100,000 files were reorganised to the approved convention and location using AI, a volume too large to review one by one.

One structure across the group

The 11-folder standard was verified across every entity, so a document sits in the same place whichever part of the group it belongs to.

A tenth of the manual effort

Compared with a file-by-file review, the approach cut manual effort tenfold. People's time went into review, not into renaming files one at a time.

For the group, the new platform started with a clean file estate rather than a copy of the old one. Documents are no longer findable only by the person who filed them, and the deal records that matter most came through exactly as they were.

If this reflects a situation in your organisation, we would welcome a conversation.

We use cookies

Essential cookies keep the site working. With your permission, analytics cookies show us how it is used. Read our cookie policy.