Skip to main content
The new project architecture (v2) is Anything’s next-generation way of building apps. Upgrading copies your project onto it. Your original stays exactly where it is, fully accessible.

​
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.

​
Before you upgrade

The upgrade is safe to try: it copies your project and leaves the original alone. But a v2 copy is a brand-new project, so before you move a live app over, read these first.
A published app won’t follow you to v2. Because the upgrade creates a new project, the v2 copy is a separate app from anything you’ve already shipped. If you’ve published the original to TestFlight or the App Store, the v2 copy publishes as its own app, not a new build of the existing listing. If staying on the same published app matters, keep shipping from the original project for now.
A few things worth knowing before you start:
  • Your live URL moves only if you bring the domain. Choose your domain during the upgrade if you want the live site to point at the v2 copy. Skip it and the original keeps serving traffic.
  • The original stays put. Nothing is deleted. You can keep building on the older project, compare the two, or fall back at any time.
  • You can migrate the rest later. If you skip your domain, database, or users the first time, run the upgrade again to include them.

​
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.
1

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.
2

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
Only the resources your project actually uses are offered. You can skip any of them and migrate them later.
3

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.
4

The upgrade runs in the background

You can close the window and keep working. We’ll email you when the upgraded project is ready, with a link to open it.
The agent makes a repair pass over the upgraded project so it builds cleanly on the new architecture. That pass is on us. It doesn’t use any of your credits.

​
What transfers

The upgrade creates a fresh v2 project and copies over what you select.
ResourceWhat moves
DomainYour custom domain or *.anything.app URL points at the upgraded project
DatabaseAll tables, rows, and schema, copied to the new project
Users and authenticationUser accounts, sessions, and auth configuration
CodeRewritten 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.