AI Studio: Migrate Existing Projects to SSR

A React project that needs server-rendered pages, server functions, or secrets can now be upgraded from Project Settings. AI Studio makes a second project in the same sub-account and runs the upgrade there. The published project stays as it is, domains included. React projects that don't need the new stack stay on React.

🔍 Problem

SSR, server functions, and secrets shipped for new projects. An existing React site that needs those capabilities had no way to get them. Rebuilding inside the live project would have put the published site and its domains at risk.

📦 What shipped

Migrate to SSR is in Project Settings, marked Advanced. It shows on React/Vite projects when you can edit the project. Projects that are already on TanStack do not get the action, and a React project stays on React until someone runs this.

Confirming creates a new project next to the original, in the same account:

• Your pages come with it
• Suggested name: "{project name} (TanStack)". You can change it first
• The copy is a draft. The live site and its domain stay on the original
• Earlier versions stay with the original. The copy starts a new chat

You land in that project and the upgrade starts in chat. On the dashboard the card shows Migrating to SSR until the new project is ready as a TanStack app.

Until then, publish, code save, version restore, domain changes, slug changes, and remix are blocked on the copy. Preview, chat, and delete stay open.

⬇️ How to run it

• Open the React project that needs the new stack
• Project Settings → Migrate next to Migrate to SSR
• Confirm the copy’s name
• Accept the notes
• Click Migrate

Watch the chat. It reads the app, rewrites it onto TanStack Start, and the card clears once the new project is a normal SSR project.

If the run stops short, the badge stays. In that project’s chat, “continue the migration” picks up the same copy. Starting Migrate again from the original creates another copy.

⚠️ Before you publish the copy

• Use it when the project needs server rendering, server functions, or secrets.
• Charged like a normal build. Agents do the conversion.
• Walk the new project before publishing. The pass can leave something to fix.
• Workflow triggers still listen to the original until they are pointed at the new project.
• The published site and its domains stay where they are. Publishing the copy, or moving a domain, is a separate choice.
• Walking away from the copy is safe. The original was never edited.

✅ Why this matters

A React project that needs server rendering, a real backend, or secrets can move onto that stack without a rebuild and without a cutover. Projects that don't need it stay on React.