What you get on v2
The upgrade is opt-in, and the new architecture is faster to work in:- Faster builds and reloads. Projects load and rebuild noticeably quicker.
- Cleaner code organization. A component-based structure with clearer imports and dependencies, so the agent (and you) can find things faster.
Upgrading creates a copy of your project on v2. The original is left untouched and stays open and editable, so there’s no risk in trying it.
How to upgrade
If a project is eligible, you’ll see an Upgrade to v2 button in the builder header. Older projects also show a “legacy” badge on your dashboard so you can tell at a glance which ones haven’t moved yet.Open the project and click Upgrade to v2
The button sits in the builder header for any project that’s still on the older architecture and that you can edit.
Choose what to bring over
Pick the resources to copy into the new project. You can bring over your:
- Domain, so your live URL points at the upgraded project
- Database, including every table, row, and your schema
- Users and authentication, including accounts, sessions, and auth configuration
Review and confirm
You’ll see a summary of the project name and exactly what’s going to transfer. When it looks right, click Start Migration.
What transfers
The upgrade creates a fresh v2 project and copies over what you select.| Resource | What moves |
|---|---|
| Domain | Your custom domain or *.anything.app URL points at the upgraded project |
| Database | All tables, rows, and schema, copied to the new project |
| Users and authentication | User accounts, sessions, and auth configuration |
| Code | Rewritten into the new component-based structure |
Migrating users carries your existing logins across. Password-based users keep their passwords and can sign in on the upgraded project without resetting them.
After the upgrade
The upgraded project is a new, separate project on v2. Open it from the link in the “ready” email or from your dashboard. Your original project stays on the older architecture, untouched and fully accessible. Nothing is deleted, so you can compare the two or fall back to the original if you need to. When you’re happy with the v2 copy, that’s the one to keep building in.Didn’t bring over your domain, database, or users the first time? You can run the upgrade again and include them. The original project is still there to migrate from.