Skip to Content
DocsGetting StartedYcode Legacy Shutdown

Ycode Legacy Shutdown

Ycode Legacy was permanently retired on July 1, 2026. The Legacy login, builder, API, and legacy-hosted sites are all offline — there is no way to sign in to Ycode Legacy anymore. All active projects were migrated to the new Ycode ahead of the shutdown.

What Happened

The old Ycode Legacy platform has been replaced by the new open source Ycode and Ycode Cloud — a rebuilt visual builder with a modern editor, CMS, localization, animations, static export, and much more.

Every active Legacy project was migrated to the new platform before July 1, 2026. Your project should already be available in your Ycode Cloud dashboard, signed in with the email address you used on Ycode Legacy.

What Was Transferred

Migration brought over the full project:

  • Pages and layouts — All pages with their layer structure, styles, and settings
  • Components — Reusable components and their configurations
  • CMS data — Collections, fields, items, and all content
  • Assets — Images, files, and other uploaded media
  • Forms — Form configurations and submission data
  • Fonts — Custom and Google Fonts settings
  • Site settings — Global configuration, SEO settings, and custom code
  • Subscription — Your existing plan and pricing carried over automatically

Your Subscription

If you had a paid subscription on Ycode Legacy, it carries over to the new Ycode at your existing price. You do not need to set up billing again. See the migration note in Billing for details.

Can’t Find Your Project?

If you can’t find a project you had on Ycode Legacy, or something looks wrong after the migration:

  1. Make sure you’re signed in to Ycode Cloud with the same email address you used on Ycode Legacy
  2. Check every workspace in the workspace switcher
  3. If it’s still missing, contact us on Discord  or email info@ycode.com — we’ll help you locate it

Next Steps

Now that you’re on the new Ycode:

  • Open your migrated project from the Ycode Cloud dashboard
  • Review each page and CMS collection to confirm content transferred correctly
  • Point your custom domain at the new Ycode following the Custom Domains guide
  • Publish when you’re ready
Last updated on