Migration
Platform Migration for Creative Studios: When to Change Your File Organization
When is a change in organization worth it?
Changing how a studio is organized costs time, so it should solve a real problem. Common signs it is worth doing:
People ask "where is the latest version?" several times a week.
Different artists name the same kind of file in different ways.
Handoffs to clients or freelancers keep breaking because of missing or misnamed files.
You are moving to a new platform, such as new cloud storage, a new server or a DAM.
The team or the client list has grown past what the old structure was built for.
Automation or search would help, but names are too inconsistent to use.
If none of these apply, leave a working system alone. A small fix, such as a clear naming pattern for new files, is often enough.
Why is a platform migration a good time to reset?
During a migration every file is copied, moved or imported anyway, so a reset adds little extra work. Doing it afterward means touching everything a second time and may break links that already moved.
A migration is also when old habits are easiest to leave behind. People expect the new platform to work differently, so a new structure meets less pushback than a change on its own.
How should I plan the move?
Decide your rules first. Write the naming pattern and folder structure before moving anything. Moving files into a structure you haven't defined only moves the mess.
Audit what you have. Count the projects, find what is active versus archived, and note the broken or duplicate names.
Decide what moves and what stays. Active projects usually move cleaned up. Old projects can often be archived as they are, with a note on where they came from.
Move a pilot project first. Pick one active project, move it, and check that projects relink and people can find things.
Keep a mapping of old to new paths. A simple list of old name and new name lets you fix broken links and answer "where did this go?"
Keep the old location read-only for a while before deleting anything, so a mistake can be recovered.
Move in stages, not the whole studio in a weekend.
Should I create a new root folder or use my existing folders?
Both are valid, and the right choice depends on how much of the current structure you want to keep.
A new root folder is a clean start. You create one top-level folder for the studio, build the structure you defined, and move active projects into it. Pick this when the old structure is inconsistent enough that adapting it would take longer than starting clean, or when you are moving to a new platform anyway.
Your existing folders keep what already works. You leave the current top-level structure in place and apply the rules from now on, to new projects and to files as they are touched. Pick this when most of the structure is fine, when many people depend on the current paths, or when you can't afford a big move right now.
Many studios combine the two: a new root for new work, and existing folders kept as an archive that is cleaned only when needed.
How does Prisma help with either approach?
Prisma is built around the idea that you define your own naming rules. You set your rules once in Prisma Hub, and it supports whichever way you go:
New root: set up a new root folder and project folders using your naming rules.
Existing folders: the free Prisma Scanner flags which existing names break good naming practice, and the Prisma plugins suggest names that follow your rules for you to copy. One-click Apply rename is on Prisma Hub's paid Creator and Studio plans. Prisma Hub and the plugins run on your Mac and work offline; Prisma Scanner checks the names and paths you paste, in your browser.
Because the rules are yours, the same setup can carry over if you later move to another platform.
How can I check my file names before a migration?
Paste a few of your current file names into Prisma Scanner and see how they score. It is free and needs no signup. The score is a heuristic read of the text you paste, not a full audit, but it is a quick way to see how much cleanup a move would involve.
Check your file names free with Prisma Scanner
Open Prisma Scanner
Related Guides
Automation
File Hygiene at Creation: How Clean Names Power Automation and Your DAM
Automation and digital asset management (DAM) systems read file names and folder paths before anything else. When files are named and placed correctly at the moment they are created, scripts, watch folders and DAM imports can sort, tag and route them without a person stepping in.
Naming
File Naming Convention: Define Your Own Rules
A file naming convention is a written pattern, such as ACM_AcmeCompany_Launch_16x9_v03.mp4, that everyone on a project uses to name files. The best convention is the one your studio defines and then follows consistently.
Workflow
AI and Multi-App Round Tripping: How to Keep Pace Without Losing Your Files
AI tools are pushing creative work through more apps than ever, with files going out to one tool, back to another and out again. Every hop creates new files, copies and versions. The way to keep up without chaos is to set naming and folder rules before the first export, so each round trip lands where it should.
Workflow
Why Naming Rules in a 17-Page Onboarding Doc Fail (and What Works Instead)
Most studios define their file naming rules in a long onboarding document that new people skim once and forget. Rules that depend on memory are fragile. A tool that flags names that break the rules, with plugins that suggest rule-based names to copy, and one-click Apply rename on the paid Creator and Studio plans, helps keep the organization intact, logical and self-reinforcing.
Workflow
Why File Naming and Folder Structure Deserve Their Own Course
File naming and folder structure are usually taught in five minutes, if at all, yet they shape every hour a creative spends with their files. They sound boring. Learning them properly can save you years of searching, relinking and squinting at near-identical file names. Organization is speed, speed is iteration, iteration is quality.
Workflow
Why Good File Organization Pays Off Again and Again
File organization isn't a one-time chore that pays back once. Every consistent name and folder makes the next search, handoff, automation and creative session cheaper. The payoff builds on itself across cost, automation and flow, and messy files do the same thing in reverse.
Workflow
File Naming Best Practices: Separators, Case, Dates and the Mistakes Nobody Mentions
A good file name tells you what the file is without opening it, sorts in the right order, and works on every computer, server and app it touches. This guide covers vague names, ALL CAPS, underscores vs hyphens vs spaces, dates, version numbers, and the small habits that quietly break things. There's no single correct convention. Pick rules that fit how you work and use them every time.