How to Migrate From Conductor Cloud to Cloudroom Before November 20

Conductor joined Meta on November 4, 2026. Conductor Cloud goes read-only on November 13 and shuts down on November 20, when Conductor begins deleting cloud data. To move to Cloudroom, get your workspaces out of Conductor Cloud, import the chats with Settings → Import chats, then Teleport the threads you want back in the cloud. Cloudroom is an open-source desktop app that runs Claude Code, Codex and more agents on your computer or in a cloud sandbox, on your own subscriptions. We build Cloudroom, so weigh that as you read.

TL;DR

• Before November 20: push your branches, then use Transfer to local or Export data in Conductor.
• Import: Settings → Import chats in Cloudroom, or room-cli import conductor.
• Back to the cloud: Teleport to Cloud on any imported thread.
• What you keep: Claude Code chats keep their full memory. Some other chats come over as text.
• The honest gap: Cloudroom has no team multiplayer today.

When does Conductor Cloud shut down?

These dates come from Conductor's announcement.

So cloud work has to finish by November 13, and your data has to be out by November 20.

Step 1: Get your work out of Conductor Cloud

Push your branches to GitHub first. Your code is plain Git, so a pushed branch is safe whatever happens next.

Conductor then gives you two ways to take the chats with you:

• Transfer to local. Right-click a cloud workspace and choose Transfer to local. It moves the workspace and its chats to your Mac.
• Export data. Go to Settings → Account → Export data. It downloads an archive of all your Conductor data.

Transfer the workspaces you are still working in. Export everything as a backup. Cloudroom reads both.

Step 2: Import your chats into Cloudroom

1. Install Cloudroom and sign in to the agents you use, such as Claude Code and Codex.
2. Open Settings → Import chats. Cloudroom finds the Conductor chats on your Mac, including the workspaces you transferred to local.
3. Pick Conductor and how far back to go: 7 days, 30 days or all time.
4. For a Conductor Cloud export, unzip the archive, click Import a Conductor Cloud export and pick the folder.

The same works from the terminal:

# List the Conductor chats on this Mac without importing them
room-cli import conductor --dry-run

# Import the chats from the last 90 days
room-cli import conductor --days 90

# Import a Conductor Cloud export, zipped or unzipped
room-cli import conductor --path ~/Downloads/conductor-export.zip

A few things to know:

• Conductor is never changed. Cloudroom only reads its data, so your originals stay as they are.
• Importing starts no agents. Chats arrive as idle Local threads and use no tokens until you send a message.
• One project per repo. All the workspaces of a repo land in one project, and each thread runs in the worktree it had in Conductor.
• No duplicates. A chat that came over both ways shows once.

Step 3: Send threads back to the cloud

Imported chats are Local threads on your Mac. To continue one in the cloud, send it one message, then pick Teleport to Cloud in the thread menu or send /teleport. The cloud agent continues the same conversation in its own sandbox, on its own Git branch. When the thread shows "You can close your laptop", you can.

Teleport works for Claude Code, Codex, Pi Agent and OpenCode, in both directions. For new work, you can also just start a new Cloud thread.

What carries over, and what does not

Keeps its full memory. The agent resumes the old session instead of rereading it.

• Claude Code chats, from your Mac and from a Cloud export. This works even when Claude Code has already deleted its own transcript, because Cloudroom rebuilds the session from the messages Conductor saved.
• Codex chats on your Mac, when the transcript and the worktree still exist.

Comes over as text. The agent reads the old messages as context and starts a fresh session.

• Codex chats from a Cloud export.
• Cursor and OpenCode chats.
• Chats whose agent is not installed. They move to Claude Code, or to Codex.

Does not carry over.

• Secrets and environment variables. Add them again in Settings → Cloud environment.
• Your Cloud Computer setup. Write the installs once as a setup script, and every new sandbox runs it.
• Automations. Create them again in Automations.
• Tool calls in the timeline. An imported chat shows your messages and the agent's replies only.

We checked the importer against a real Conductor Cloud export on November 6, 2026. We have not checked shared chats that contain a teammate's messages.

How Conductor maps to Cloudroom

Conductor cells come from Conductor's pricing and docs pages and from our Conductor review. Cloudroom cells come from Cloudroom's docs.

Where Cloudroom is weaker than Conductor

• No team multiplayer. Several people cannot work inside the same thread. If your team lived in shared Conductor chats, this is the biggest change.
• No native iOS app. The phone app is a web app you add to your Home Screen.
• A less polished editor. Our review gave Conductor the win on its file tree and code editing.
• Cursor stays local. Cursor chats import as text, and Cursor does not run in Cloud threads.

Can you just stay on local Conductor?

For a while, yes. Conductor says the local app keeps working and gets new models and critical bug fixes until early 2027. If you only use local workspaces, nothing breaks this month.

Two things change this month. Agents stop when your Mac sleeps, because the cloud is gone. And nobody new can join, because sign-ups and downloads closed on November 4.

The short version

Push your branches, then Transfer to local or Export data before November 20. Import the chats into Cloudroom from Settings → Import chats, and Teleport the ones you need back to the cloud. Claude Code chats keep their memory. Team multiplayer is the one thing you will miss.

You can get started with Cloudroom on the free plan, read the other Conductor alternatives, or see how cloud coding agents compare.

Sources: Every Conductor date and export step comes from Conductor's announcement and its 0.93.0 changelog, checked on November 11, 2026.