> ## Documentation Index
> Fetch the complete documentation index at: https://zite.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Migrate to Workspaces 2.0
> Move your Zite apps to Workspaces 2.0 without rebuilding your app, data, or access.
## How it works
When you open an app or database that does not yet belong to a Workspaces 2.0 workspace, Zite asks you to migrate it. Your apps, forms, database, and existing access move together, so you do not need to rebuild anything.
## Apps without a Zite Database
For an app without a Zite Database, choose where to add one:
* **Create a new workspace:** Creates a workspace with its own database. You do not have to use the database right away, but it is ready when you need it.
* **Add to an existing workspace:** Choose a workspace from the list to move the app there. The app uses that workspace's database.
## Classic vs new workspaces
Existing workspaces, now called Classic workspaces, are visual folders for grouping apps, databases, and forms. In Workspaces 2.0, each workspace holds one database, its connected apps and forms, shared logic, and centralized user access.
This screenshot shows the previous `Members & roles` label. The button is now called `Users & roles`.
## What you get with a new workspace
Each workspace keeps the people, apps, and data for a project together. As it grows, you can add more apps and forms, manage editors, and control access for each app.
Quickly manage your database, apps, forms, users, and permissions from one place.
Keep the records, tables, and relationships that power your project together.
Add internal apps, public apps, and forms that all work from the same data.
Let Zite Agent work across the apps and data without needing to switch apps.
Open `Users & roles` to manage editors, app users, and database roles.
Share logic across your apps for better performance and reliability.
## Migration questions
You can either create a new workspace or add the app to an existing workspace.
* **Create a new workspace:** Zite creates a new Zite Database for the workspace. You do not have to use it, but it is ready if you need it later.
* **Add to an existing workspace:** The app uses the database that already belongs to that workspace.
When you create a workspace, name it and select `Done`. Zite adds the database alongside your app.
When you add an app to an existing workspace, select the workspace from the list, then select `Move`.
Zite moves the database and every app that shares it into a new workspace. People with database access become editors, and existing app users keep access to the apps they use.
Name the workspace, then select `Done` to complete the move.
Yes. People who can access the database become editors in the new workspace. Existing app users keep their app access.
No. Each workspace has one Zite Database. Add apps and forms to the same workspace when they should work from the same data.
That is fine. When a new workspace is created, Zite adds a Zite Database, but you can keep using your external data source and do not have to use the new database. It will be there if you need it later.
No. Migration to Workspaces 2.0 is a one-way process, so an app cannot return to the Classic workspace model after migration. However, once migrated, you can move the app between different Workspaces 2.0 workspaces.
Yes. Your app, data, access, and existing setup keep working after the migration. You do not need to rebuild anything.
Related topics