--- title: Moving from TurnPanel 1 description: TurnPanel 2 is a big change, not an update. Install it beside TurnPanel 1 and it brings your people, spaces, jobs, secrets, models and automations over. updated: 2026-10-29 canonical: https://turnpanel.com/docs/moving-from-v1 markdown: https://turnpanel.com/docs/moving-from-v1.md llms: https://turnpanel.com/llms.txt --- # Moving from TurnPanel 1 TurnPanel 2 is a big change, not an update. Install it beside TurnPanel 1 and it brings your people, spaces, jobs, secrets, models and automations over. ## A manual upgrade TurnPanel 2 is a new app, not an automatic update. You install it yourself, and nothing about TurnPanel 1 changes when you do. Spaces are now sandboxes, agents run inside them, and scripts, apps and schedules work in new ways. Plan to revisit the workflows you rely on. [The TurnPanel 1 docs](/docs/v1/quick-start) ## What happens on first start On first start, TurnPanel 2 looks for a TurnPanel 1 install on the same machine. If it finds one, an import page appears right after you create your account. 1. **Before.** The number of spaces, people, conversations, scripts, apps, schedules and models found, and the size of the TurnPanel 1 data that will be read. If this computer cannot run sandboxes, it warns that regular spaces will come over parked. Choose Bring it over, or Skip the import and come back later. 2. **During.** Real progress for people, spaces, jobs, secrets, models and automations. If it is interrupted, it resumes where it stopped. 3. **After.** A report. It first confirms that everything came over and that TurnPanel 1's files are unchanged, then lists what to look at and what was left behind. ## What comes over - **People.** Everyone who had signed in becomes a person with the same email, and a member of the spaces they could reach. People who were only invited become invitations. Anyone without an email address is left out, so invite them again. - **Spaces.** Your main assistant becomes Computer, the space that runs on the host, and the report offers to turn it into a regular space instead. Every other space becomes a regular space with its name, icon and people. Memory and skills are copied as they are, apart from the memory index, which is rewritten. - **Jobs.** Conversations with TurnPanel 1's built-in agent become idle jobs on pi, with their messages. You can send a message and carry on. Jobs from tools like Claude Code and Codex keep their transcripts, but you install and sign in to those agents again in each space. - **Secrets and models.** Provider keys become workspace secrets and are registered with the model manager. Downloaded models are registered where they are, and you can move them into TurnPanel's folder later from Models. Your tunnel licence is kept too: connect a TurnPanel account and install the tunnel add-on to keep the same address. - **Automations.** Schedules become automations in their spaces, running as the person who made them. - **Scripts and apps.** Scripts are copied into the space's bin folder, marked for review. They were written for TurnPanel 1's Python SDK, which TurnPanel 2 does not have, so most will need changes. Web apps are copied but not installed. You review each one, install it and approve what it asks for. Apps built on TurnPanel 1's view-tree runtime are not imported. The report lists them so you can ask an agent to rebuild them as web apps. - **MCP servers.** They become connections in every imported space. OAuth connections ask you to sign in again once. ## What you need to do - Set a password or add a passkey. TurnPanel 1's web password and sessions do not come over. Other people get a set-password link, which the report shows to the owner to share. - Sign in to each agent again, per person. - On Windows, and on Macs or Linux machines that cannot run sandboxes, regular spaces are imported parked. Their data is stored and visible, but they cannot run until an admin moves them to a machine that can. - Provider keys that TurnPanel 1 stored with the operating system's own store (Windows and Linux desktops) cannot be opened, so the report lists them to enter again. - Allow notifications again. Telemetry starts off, and you are asked once. ## What does not come over - MARS models and settings, hybrid routing and the command guard (removed). - The API gateway and the ROI calculator (removed). - The agent browser's cookies and signed-in sites. Agents sign in again. - Web sessions and push notification subscriptions. - Usage history, the managed Python runtime and its packages, and developer settings. - Extensions. The report lists them for reinstalling from the marketplace. ## TurnPanel 1 keeps working The import only reads TurnPanel 1's data. It stays untouched, so you can keep using TurnPanel 1 while you move over. When the import is checked, TurnPanel 2 records a date 30 days later when you may want to delete TurnPanel 1 yourself. TurnPanel 2 never deletes anything of TurnPanel 1's. > **Old links still work** > Links in TurnPanel 1 apps to documentation pages open the TurnPanel 1 docs under /docs/v1.