Move from the legacy admin to Studio
Plan editor migration separately from a Fresh-to-new-Blocks framework migration.
The former deco.cx admin and the Studio Site Editor are different editing surfaces. The legacy admin archive preserves the old screens; the current editor guides describe the Studio implementation.
Fresh and the former deco.cx admin are retired. Use released Blocks 7.x for the website runtime and Studio Site Editor for current content work.
Choose the migration you need
| Change | What it changes | Where to start |
|---|---|---|
| Adopt Studio Site Editor | The content editing and publishing surface | Connect a site |
| Move Fresh to TanStack | Runtime, React components, build and deployment | Framework migration |
| Adopt Blocks next | The new framework contract, currently in preview | Preview quickstart and Studio compatibility |
Do not assume one change completes the others. Keep runtime migration and editor migration independently reviewable, even when you deliver them together.
Prepare an existing site
- Identify the repository, production branch, running preview URL, and people allowed to publish.
- Inventory pages, saved sections, provider apps, assets, matchers, SEO, redirects, and any database or blog functionality.
- Import the repository into Studio, enable content editing, and configure its preview server. Use the connection guide.
- Associate the site's file storage with the project. Existing managed assets need the correct site/storage association; repository access alone does not migrate that association.
- Verify representative routes: home, product, category, campaign, and any blog or custom page.
- Make a small draft change, verify shared content and variants, and exercise publication under the project's chosen policy before moving the team's daily work.
Compare capabilities before cutover
| Former workflow | Studio workflow or dependency |
|---|---|
| Pages and reusable sections | Pages and Sections |
| Staging, Publish now, Releases | Branch-based publishing and request review; use repository history for published reversions |
| Assets | Site asset browser and image picker, with configured storage |
| SEO and redirects | SEO and Redirects, backed by site runtime integrations |
| Segments and experiments | Matcher-driven variants; verify experiment measurement separately |
| App installation | Install/register the dependency in code; then configure its blocks |
| Blog | Blog collections, with version-dependent status and scheduling support |
| Domains and apex redirects | Use the site's hosting provider workflow; old managed-admin instructions are archived |
For migrating a retired Fresh blog, the historical deco-cx/apps line added publication status in 0.161.0 and scheduling in 0.162.0. These thresholds describe archived compatibility, not a supported setup for new sites. Move the blog runtime and saved content to the released 7.x integration and verify publication and scheduled posts before cutover.
Gaps to resolve for your site
The former Records setup wizard is not a general database collection in the reviewed Studio content browser. Preserve your database, credentials, and application code; establish the supported management workflow with your team before relying on an equivalent UI. The archived Records screen is historical documentation.
The old GTM guide configures an Analytics section through the former admin. For a current site, install and register the analytics integration supported by its framework, verify events in the receiving service, and only then move ongoing operation to Studio. This migration does not document an unverified replacement wizard.
Confirm roles, storage ownership, deployment triggers, review policy, and rollback with the project owners. Successful preview rendering alone is not a complete cutover.
Using archived documentation
Fresh reference keeps runtime-specific imports, conventions, and troubleshooting. Legacy getting-started guides retain old screenshots and offers for historical context. Their labels do not establish current plan limits or availability.
Keep old inbound links mapped to their specific preserved page or a verified replacement. The archive helps existing teams interpret their installations while daily work moves to the current editor.
Implementation references: Studio content collections, site import.