AI Studio: Migrate Existing Projects to SSR

TL;DR

Existing React/Vite projects in AI Studio can now be migrated to SSR. This creates a new project copy while leaving the original untouched.

Who this affects

HighLevel has not confirmed who this affects. Agency owners using AI Studio for React/Vite projects should be aware. Those not using AI Studio or React/Vite projects can safely ignore this.

What changed

A new 'Migrate to SSR' option is available in Project Settings for React/Vite projects. This option initiates a migration to SSR, server functions, or secrets.

Executing 'Migrate to SSR' creates a second project in the same sub-account. The new project is named "{project name} (TanStack)" by default.

This new project copy starts a new chat where the upgrade process runs. The original published project, its domains, and earlier versions remain untouched.

While the copy is migrating, publishing, code saving, version restoring, domain changes, slug changes, and remixing are blocked on the copy. Previewing, chatting, and deleting remain open on the copy during migration.

If the migration stops prematurely, a badge indicates this. 'Continue the migration' can be used in the copy's chat to resume. Starting 'Migrate to SSR' again from the original project creates another copy.

Workflow triggers will continue to listen to the original project. They must be re-pointed to the new project manually after migration.

HighLevel has not confirmed any limits or plan gating for this feature. HighLevel has not confirmed the rollout status.

Where to find it

This option is located within Project Settings, specifically next to 'Migrate to SSR'.

How agencies will use this

An agency owner has an existing React/Vite project in AI Studio for a client's custom booking portal. This project is currently live and integrated with workflows. To improve performance and SEO, the agency decides to migrate it to SSR.

They navigate to the Project Settings of the original project and select 'Migrate to SSR'. HighLevel then creates a copy of the project, named "Booking Portal (TanStack)". This new copy initiates a chat where the migration process runs.

During the migration, the original 'Booking Portal' remains live and unaffected, ensuring no downtime for the client. The agency can monitor the migration progress in the new project's chat. Once the migration is complete and thoroughly tested within the new 'Booking Portal (TanStack)' project, the agency updates any relevant workflow triggers to point to the newly migrated project. They can then update the domain to point to the new project and potentially archive the original if no longer needed.

Our take

This is a major update for agencies building custom React/Vite projects in AI Studio. The ability to migrate to SSR addresses significant performance and SEO considerations. The process is designed to be non-disruptive, creating a copy rather than modifying the live original. However, the manual step of re-pointing workflow triggers post-migration is crucial and could be overlooked. The lack of information on who this affects, rollout status, and any potential limits is a notable omission from HighLevel.