If you have a React project that needs server-rendered pages, server functions, or secrets, you can now upgrade it from Project Settings. AI Studio creates a second project in the same sub-account and runs the migration there, so your published project and domains stay unchanged.

What this solves

SSR, server functions, and secrets were available for new projects, but existing React sites did not have a safe way to adopt the new stack without risking the live project.

What’s included

The Migrate to SSR option appears in Project Settings (Advanced) for React/Vite projects when you have edit access. Projects already on TanStack do not show this action.

When you confirm, a new project is created next to the original:

• Your pages are copied into the new project
• You can rename the copy (suggested: “{project name} (TanStack)”)
• The new project starts as a draft; the live site and domains stay on the original
• Earlier versions remain with the original; the copy starts a new chat history

The upgrade runs in the new project’s chat. The dashboard will show “Migrating to SSR” until the new project is ready as a TanStack app.

While migration is in progress, publishing, code save, version restore, domain changes, slug changes, and remix are blocked on the copy. Preview, chat, and delete remain available.

How to run the migration

1. Open the React project that needs the new stack
2. Go to Project Settings and find Migrate to SSR
3. Confirm the copy’s name
4. Accept the notes
5. Click Migrate

If the run stops early, the migration badge stays on the copy. In that project’s chat, you can use “continue the migration” to resume. Starting migration again from the original creates another copy.

Before you publish the copy

• Use this when the project needs server rendering, server functions, or secrets.
• Conversion is charged like a normal build.
• Review the new project before publishing; you may need to fix minor issues.
• Workflow triggers continue to point to the original project until you update them.
• Publishing the copy, or moving a domain, is a separate decision from running the migration.
• The original project is not edited during the process.

Why this matters

This lets an existing React project move to an SSR stack without a rebuild and without a risky cutover. Projects that do not need SSR can remain on React.