I almost lost about forty saved projects because I put off dealing with this for way too long. If you used Google’s Whisk tool at any point before this year, you probably remember getting an email or a banner notification talking about moving your stuff over to Flow. That notification was about the whisk to flow migration opt in transfer, and if you’re reading this after the fact wondering what happened, or you’re trying to piece together whether your old projects are gone for good, I want to walk through exactly how this played out.

Quick Recap: Why Whisk Even Needed a Migration

Whisk was Google’s experimental image remixing tool. You’d drop in three references — one for subject, one for scene, one for style — and it would blend them into something new using Gemini and Imagen under the hood. It wasn’t a typical type-a-prompt-get-an-image tool. It worked almost entirely through visual references, which honestly made it feel more intuitive for people who weren’t great at writing prompts.

Google eventually decided to fold Whisk, along with ImageFX, into a single unified platform called Flow, which already handled video generation through Veo. Rather than running three separate tools, Google wanted one workspace that covered images, video, and eventually audio all in the same place. That consolidation is exactly why the whisk to flow migration opt in transfer became necessary in the first place — Whisk wasn’t just getting an update, it was being shut down entirely on April 30, 2026.

The Part That Caught People Off Guard: It Was Opt In, Not Automatic

Here’s the detail that tripped up a lot of users, myself included for a while. The whisk to flow migration opt in transfer was exactly that — opt in. Nothing moved on its own. Google made this clear in its Workspace announcement, stating plainly that migration was opt-in and assets would not transfer automatically. If you had projects sitting in Whisk and you assumed Google would just quietly shuffle them over to Flow in the background, that assumption was wrong, and it cost some people their entire libraries.

The way it worked was pretty straightforward once you understood what to look for. Users with active Whisk accounts got an email announcing the change, and an in-product notification appeared inside Whisk itself with instructions on how to move things over. You’d see a banner at the top of your dashboard prompting you to start the whisk to flow migration opt in transfer, and clicking through would kick off the process of moving your projects and assets into your Flow library.

What Happened If You Missed the Deadline

This is the part that genuinely stings for anyone who procrastinated. On April 30, 2026, Whisk was discontinued entirely. Any media still sitting in a user’s Whisk library after that date was permanently deleted, with no way to recover it. Google was not vague about this — the deletion was framed as final, with no server-side restore option available under any circumstances.

I’ve seen accounts from creators who simply never got around to completing the whisk to flow migration opt in transfer before the cutoff, and once April 30 passed, that was it. No support ticket, no appeal process, nothing brought those files back. The only real fallback for people in that position was recreating their work from scratch inside Flow, which, depending on how complex the original prompts and reference images were, could take anywhere from a few minutes to a genuinely frustrating afternoon.

How the Transfer Actually Worked, Step by Step

If you were doing this before the deadline, the whisk to flow migration opt in transfer process looked something like this. You’d log into Whisk and look for the migration banner at the top of the dashboard. Clicking “Migrate to Flow” would start the opt-in process — again, nothing automatic, you had to actively choose it. From there, your projects would begin appearing inside Flow’s Asset Grid, and it was worth double-checking that everything showed up correctly, since some titles occasionally looked slightly different after the reformatting that happened during transfer.

Google also gave users the option to download their data directly instead of, or in addition to, completing the transfer. This turned out to be a smart move for anyone who wanted a local backup just in case something went wrong during the whisk to flow migration opt in transfer itself. The exported file came as a ZIP archive containing your original images and videos, along with a metadata.json file preserving prompts and reference details. Anyone who grabbed that backup before April 30 still had their content sitting safely in their Downloads folder even after Whisk’s servers went dark, and could re-upload pieces into Flow manually whenever they wanted.

The One Thing That Genuinely Didn’t Require Any Action

Not everything about this transition demanded manual effort. Because Whisk and Flow ran on the same underlying AI credits platform, existing credits carried over without any extra steps. If you had an active Google One AI Pro or Ultra subscription, your remaining credits simply showed up inside Flow once you were using it, with zero action needed on your end. This was one of the few genuinely painless parts of the entire whisk to flow migration opt in transfer — the money side of things just worked.

What About Users Outside Supported Regions?

This is a detail that doesn’t get talked about enough, and it’s an important asterisk on the whole whisk to flow migration opt in transfer story. Flow wasn’t available everywhere Whisk had been. Whisk had rolled out to over 100 countries, but Flow’s rollout was more limited at the time of the shutdown. Users in unsupported regions — including the European Union, the United Kingdom, India, and Indonesia — lost access to Whisk on April 30 with no migration path available to them at all. For those users, visiting the old Whisk URL now simply displays a “service ended” message rather than redirecting into Flow, which is what happens for accounts in supported countries.

If you were in one of those excluded regions and had projects you cared about, the only real safety net was downloading your content directly before the deadline, since the opt-in transfer itself wasn’t even an option on the table for you.

Was It Worth Doing the Migration, or Should You Have Just Started Fresh?

Looking back at this now, I think the honest answer depends on how much you’d invested into Whisk specifically. If you had dozens of carefully built subject-scene-style combinations, going through the whisk to flow migration opt in transfer process was clearly worth the ten or fifteen minutes it took. Recreating that from memory inside Flow would have taken far longer, and some of the exact visual nuance from the original blends probably wouldn’t have come back the same way.

On the other hand, if you’d only dabbled with Whisk a handful of times, some people reasonably decided it was easier to just start fresh inside Flow rather than bother with the transfer at all. Flow’s interface works differently anyway — prompts are typed directly rather than generated and then edited through Whisk’s old notepad-style hidden prompt system — so even migrated projects required a bit of relearning once they landed in their new home.

What Changed Once Your Content Landed in Flow

Something worth mentioning for anyone who completed the whisk to flow migration opt in transfer and is now wondering why Flow feels different: it genuinely is different, not just visually but functionally. Flow brought in features Whisk never had, like a lasso tool paired with natural language editing, letting you select part of an image and describe a change in plain English instead of guessing at prompt wording. It also unified image generation with Veo-powered video animation, so a still image you migrated over could be turned directly into a short video clip using options like “Frames to Video” or “Ingredients to Video,” all inside the same workspace.

The trade-off, at least according to a lot of former Whisk users, is that Flow’s prompting feels more conventional and slightly less immediate than Whisk’s original visual-remixing concept. Whisk let you drop in three reference images and get something new almost instantly, without touching a text field. Flow leans more toward typed prompts with image references attached, which is powerful but does change the workflow you build muscle memory around.

Common Questions People Still Ask About This

Even now, months after the deadline passed, I still see people asking the same handful of questions about the whisk to flow migration opt in transfer, so it’s worth addressing them directly.

Did templates and remix combinations carry over? For the most part, yes. Flow inherited Whisk’s visual remixing capabilities, so templates built around the subject-scene-style format generally continued working after the transfer, even if the interface around them looked different.

Do I need to redo anything if I already migrated? Not necessarily, but it’s worth going back into your Flow library and confirming everything you expected to see is actually there. A few users found that certain titles were reformatted slightly during the whisk to flow migration opt in transfer, which occasionally made specific projects harder to locate at a glance, even though the underlying files were intact.

Can I still access Whisk directly to check something? No. The old Whisk URL now automatically redirects into Flow for anyone in a supported region, and shows a service-ended notice for excluded regions. There’s no legacy version or snapshot of the original tool sitting anywhere in reserve.

Is there any point complaining or requesting a manual recovery now? Realistically, no. Google has been unambiguous that the deletion tied to missing the whisk to flow migration opt in transfer window is permanent, with internal backups wiped in line with the terms of service Google announced ahead of the shutdown.

Final Thoughts

If you’re reading this well after the fact and wondering whether there’s still a way to salvage old Whisk content, the short and unfortunately blunt answer is no — anything not covered by the whisk to flow migration opt in transfer before April 30, 2026, or downloaded manually before that date, is gone for good. Google has been consistent and firm about that point across every official statement on the shutdown.

For anyone who did complete the transfer in time, your projects should be sitting safely inside your Flow library right now, credits and all, just with a slightly different workflow wrapped around them. And if you’re setting up a brand-new account today with no Whisk history to worry about, none of this really applies to you — you’re simply starting inside Flow as it exists now, without ever having to think about migrating anything at all.