In Workspaces 2.0, you can export and import a complete workspace, not an individual app. Apps depend on their workspace’s database schema, so they need to stay together.
Duplicate an app
You can duplicate an app within its workspace. This is useful when you want to create a variation of an app while keeping it connected to the same workspace database. Duplicating a single app copies everything, including its version history.Duplicate a workspace
If you are building an app for a client, duplicate the workspace and choose not to include database records. This creates a copy of the workspace with its apps, forms, and database schema, but with an empty database. This gives your client a clean starting point without sharing the original workspace’s records. The copy keeps the original workspace’s integrations, so its apps keep working straight away and you don’t need to reconnect anything. The original and the copy are in the same organization, so they use the same connected accounts (for example the same Google or Slack account). If you’re preparing the copy for a client, check which accounts its integrations use before you hand it over. Duplicating a workspace also copies its shared secrets and each app’s own secrets. The Duplicate workspace dialog includes a Copy version history option. It is off by default. With it off, each app in the copy gets only its latest version. If the newest version didn’t finish building, the copy also includes the last version that did, so the copy still works and opens in the editor. Older versions aren’t carried over. Turn it on only if you need the full version history. Copying version history can take a lot longer. While the copy runs, the dialog shows progress step by step. If a copy is still being made, wait for it to finish rather than duplicating again. You can’t start another copy of the same workspace from the same browser tab while one is running. A copy that’s still being made shows that it’s still being copied, wherever you open it. If your connection drops while a copy is running, the copy may still appear, so wait rather than starting another. If Zite says the copy didn’t finish, delete it and duplicate the original workspace again.Export a workspace
You can export a complete workspace, including its code, database schema, apps, and forms. Database records and chat history are not included in the export. Individual apps cannot be exported separately because they rely on the database schema that belongs to their workspace.Import a workspace into another organization
After exporting a workspace, you can import it into a different organization:- Switch to the organization where you want to import the workspace.
- In the prompt box, click the
+button. - Select
Import>Existing Zite. - Choose the exported workspace file to import it.