Migrate from Ycode Legacy

Legacy Ycode is being replaced with the new open source and Ycode Cloud platform. After July 1, Legacy Ycode will no longer be accessible and any projects still hosted on the legacy platform will go offline. We recommend migrating sooner rather than later so you have plenty of time to review everything before the shutdown. If you run into any issues, reach out to us on Discord or email us at info@ycode.com — we’re happy to help.

You can transfer your entire Ycode Legacy project to the new Ycode — including design, pages, CMS content, assets, and your subscription. The migration pulls your project data using your Legacy API key and recreates everything in the new platform.

If you migrate to Ycode Cloud, you keep your current pricing. The Ycode Cloud plan includes unlimited pages, 20,000 CMS items, unlimited form entries, unlimited languages, and more. See Ycode Cloud pricing for details.

If you are on an annual plan and prefer not to migrate, you are entitled to a pro-rated refund of your remaining subscription. To request a refund, email info@ycode.com with the subject line “Refund Request” before June 30, 2026.

What Gets Transferred

The migration brings over your 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 current billing plan transfers to the new Ycode

Before You Start

Make sure your Ycode Legacy project is on a paid plan. API tokens are only available on paid project plans, and you need a token to authorize the migration.

Migration Steps

Get your API key from Ycode Legacy

Open your project in the Ycode Legacy builder
Go to Settings in the sidebar
Click API Tokens (under the “API access” heading)
Click Add API token
Enter a name for the token (e.g., “Migration”)
Click Create token
Copy the token immediately — it is only shown once and cannot be retrieved after closing the dialog

You can also click Download to save the token as a text file.

The API token secret is displayed only at creation time. If you lose it, you will need to create a new token.

Create a new project in Ycode

Go to the new Ycode and click New project
In the project creation dialog, you will see two options:
- Start from scratch — Begin with a blank project or template
- Import from Legacy — Migrate an existing Ycode Legacy project
Select Import from Legacy

Enter your Legacy API key

Paste the API token you copied from Ycode Legacy
Click Import to start the migration

Ycode connects to your Legacy project, reads all project data through the API, and recreates it in the new platform. This includes pages, layers, components, CMS collections and items, assets, settings, and your subscription.

Wait for the migration to complete

The migration may take a few moments depending on the size of your project (number of pages, CMS items, and assets). You will see a progress indicator while the transfer is in progress.

Once complete, your project opens in the new Ycode editor with all your content and design intact.

Connect your domain

After the migration, update your domain’s DNS settings to point to the new Ycode. Go to your domain registrar and update the DNS records as described in the Custom Domains documentation. Once the DNS changes propagate, your site will be served from the new Ycode.

After Migration

Review your pages — Open each page to verify the layout and content transferred correctly
Check CMS data — Browse your collections to confirm items and field values are present
Test forms — Verify form configurations and any connected integrations
Verify assets — Confirm images and files are displaying correctly
Connect your domain — Update your DNS settings to point to the new Ycode (see Custom Domains)
Publish — When everything looks good, publish your site from the new Ycode

Your subscription plan from Ycode Legacy carries over to the new Ycode automatically. You do not need to set up billing again.

Troubleshooting

Issue	Solution
”Tokens are available on paid project plans”	Upgrade your Legacy project to a paid plan before creating an API token
Token not working	Ensure you copied the full token. If lost, create a new one in Legacy under Settings → API Tokens
Migration seems stuck	Large projects with many assets may take longer. Wait for the process to complete before refreshing
Missing content after migration	Check that the content existed in the Legacy project before migration. Some draft or deleted items may not transfer