There is no automatic Frame.io-to-Frooty importer, and any tool that promises one-click migration history is lying to you. The honest path is a structured manual move - masters downloaded, projects recreated, review links rebuilt, open feedback re-anchored - and for most teams it is a weekend of work, not a quarter. This guide is exactly what moves, what does not, and the order to do it in.
Before you migrate: run the pricing check
Migrations are rationalized after the fact, but they are decided on the bill. The usual trigger is roster math: Frame.io's Team plan is $25 per member per month (as of November 2026) with a 15-member cap, so a growing roster hits both a rising bill and a sales conversation. Frooty Studio is $39/month flat with unlimited members and reviewers. Run the Frame.io pricing math for your roster before touching a single file - if the math does not favor a switch, stop here.
What transfers - and what does not
| Data | Moves over? | How |
|---|---|---|
| Masters and exports | Yes | Download originals from Frame.io, upload to Frooty |
| Project structure | Rebuilt | Recreate workspace, projects, folders - a few hours |
| Current review cuts | Yes | Upload as version stacks in the new projects |
| Review links | Rebuilt | Recreate with the same controls: password, expiry, watermark |
| Comments and annotations | No | Export what you still need; re-anchor open notes manually |
| Approval history | No | Keep the Frame.io account read-only as the archive |
The two rows that matter are the last two. Old feedback that was already addressed is history - it lives in the archive, and you do not need to move it. What you do need is every open note on live projects: transcribe those, anchored to the frame they describe, before you freeze the old account.
The migration, step by step
- Pick the live projects only. Anything not active in the next 90 days does not migrate - it stays in the Frame.io archive. Migrations die under the weight of dead projects.
- Download masters from Frame.io. Original-quality files for live projects, organized per project on your storage.
- Recreate the structure in Frooty. One project per live deliverable - see the organization system for the shape that survives growth.
- Upload the current cut of each project as version 1. Version history starts fresh; the old stack remains in the archive if anyone asks.
- Recreate review links with the same controls. Same passwords, same watermark policy, fresh expiry dates for the new round windows.
- Move open feedback. Transcribe unresolved notes from live projects into review comments, anchored to the frames they refer to. Addressed notes stay in the archive.
- Freeze Frame.io read-only. One system becomes authoritative; the other becomes a museum. Announce the switch date to your team and clients.
Run both systems in parallel
For two to four weeks, new work lives only in Frooty while the Frame.io archive stays reachable. Do not try to migrate mid-flight: finish any project currently in a client round where it is, and start the next one in Frooty. The parallel window is also your safety net - if something is missing, it is still in the old account, downloadable at any time.
When not to switch
Honesty cuts both ways: if your team runs deep Frame.io Enterprise integrations - custom automation on its API, Camera-to-Cloud device pipelines, or a Creative Cloud-bundled workflow with heavy Adobe round-trips your process depends on - the switching cost may genuinely outweigh the pricing win. The teams that benefit most from moving are growing rosters paying per-member prices for collaboration that should be flat-rate.
What you get on the other side
Frame-accurate comments and annotations, watermarked review links, version stacks with recorded approvals, and flat pricing that stops charging you for collaboration. Plus, when a cut is approved, it can go straight to your connected publishing channels instead of being downloaded and re-uploaded somewhere else - the approval workflow and the delivery step live in the same place.
See the full Frame.io comparison for the feature-by-feature picture, or current Frooty plans.
FAQ
Can I import comments and annotations from Frame.io?
No - there is no importer that carries comment history between tools. Export or note the feedback that still matters on live projects and re-anchor it in the new workspace; addressed feedback stays in the old account as history.
Will my existing Frame.io review links keep working?
They point at media stored in Frame.io, so they keep working as long as the account exists - which is exactly why you keep it read-only as an archive rather than deleting it. New rounds run on new links from the new workspace.
How long does a migration take?
For a small team with 5-15 live projects: a focused weekend for the move itself, plus a two-to-four-week parallel window before the old account goes read-only. Teams with hundreds of archived projects should simply not migrate the archive - pick the live work and go.
Do I need to re-upload everything?
Only what is live. Masters and current cuts for active projects come across; finished and archived work stays in the Frame.io archive, downloadable whenever a client asks for an old master.