---
title: "Export Conductor workspaces before the shutdown"
description: "How to export Conductor workspaces before the shutdown: Transfer to local for cloud workspaces, Export data, and saving every local worktree in git."
url: "https://micromanager.win/export-conductor-workspaces"
updated: "2026-11-08"
---

# How to export your Conductor workspaces

Move each Conductor Cloud workspace to your Mac with “Transfer to local”, safest before the cloud is read-only from 13 November 2026, and download everything with Settings → Account → Export data; Conductor deletes cloud data from 20 November 2026. Local workspaces are git worktrees, so committing and pushing their branches saves the code itself.

Updated 8 November 2026

## How do I export everything, step by step?

1. ### Move each cloud workspace to your Mac

   In Conductor, right-click a cloud workspace and choose Transfer to local. It comes to your Mac with its chats and becomes a local workspace. Conductor has not said whether this works once Conductor Cloud is read-only, from 13 November 2026, so that is the safe deadline.

2. ### Download an archive of your data

   In Conductor, open Settings → Account → Export data to download an archive of everything. Conductor says exports keep working while the cloud is read-only, until cloud data is deleted from 20 November 2026.

3. ### Find every local workspace

   Conductor workspaces are git worktrees of your repositories. In each repository, git worktree list prints every worktree folder and its branch, and git status --short in a folder shows what is not committed yet.

4. ### Commit and push what you want to keep

   Commit the work in each workspace you care about and push its branch. Once a branch is on your remote, it no longer depends on Conductor or on that folder.

5. ### Keep working in microManager (optional)

   On a Mac, microManager’s Import from Conductor reads Conductor’s local data read-only and opens the same worktrees with their chats, including the workspaces you transferred from the cloud.

## What are the deadlines?

| Date                       | What changes                                                                 | What to have done                                                                    |
| -------------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Friday 13 November 2026    | Conductor Cloud read-only: chats can be read and exported, not continued.    | Cloud workspaces transferred to local.                                               |
| Friday 20 November 2026    | Conductor Cloud shut down; deletion of cloud data begins.                    | Everything you need from the cloud exported.                                         |
| Early 2027 (no exact date) | The local Mac app stops getting updates and Conductor deletes its user data. | Branches you care about committed and pushed; your daily work moved to another tool. |

The [shutdown timeline](https://micromanager.win/conductor-shutdown) has each date with its sources.

## How do I find and save my local workspaces?

Conductor’s documentation says it creates each workspace as a git worktree on its own branch, so your repository already knows about every one of them. In each repository:

```sh
# In each repository: every worktree, its folder and its branch
git worktree list

# In a workspace folder: anything not yet committed?
git status --short
```

For each workspace you want to keep, commit and push its branch:

```sh
# In the workspace folder: commit the work and push the branch
git add -A
git commit -m "Work in progress from Conductor"
git push -u origin HEAD
```

Pushed branches are safe whatever happens to Conductor. Notes in a workspace’s `.context` folder are not committed, so copy any you want to keep.

## What about my chat history?

Cloud chats come to your Mac with Transfer to local, and Export data downloads everything. For local workspaces, the agents keep their own transcripts: Claude Code under `~/.claude/projects` and Codex under `~/.codex/sessions`. microManager’s import reads those, so imported chats show their earlier messages and continue the same agent sessions.

## Where should the workspaces go next?

If you want to keep working the same way, [microManager](https://micromanager.win/) imports your local Conductor repositories, workspaces and chats in one click and leaves every worktree where it is; the [migration guide](https://micromanager.win/migrate-from-conductor) covers each step. To compare other tools, see [the alternatives](https://micromanager.win/alternatives).

## Sources

1. [Conductor is joining Meta](https://www.conductor.build/announcement), Conductor. Read 8 November 2026.
2. [Meta acquires AI coding startup Conductor, whose app runs several coding agents at once](https://siliconangle.com/2026/11/04/meta-acquires-ai-coding-startup-conductor-whose-app-runs-several-coding-agents-at-once/), SiliconANGLE, Duncan Riley, 4 November 2026. Read 8 November 2026.
3. [Conductor documentation: workspaces and branches](https://www.conductor.build/docs/concepts/workspaces-and-branches), Conductor. Read 8 November 2026.

## Questions about exporting

### How do I export a Conductor Cloud workspace?

Right-click it in Conductor and choose Transfer to local, which moves it and its chats to your Mac, or use Settings → Account → Export data to download an archive of everything. Conductor Cloud is read-only from 13 November 2026 and shut down from 20 November 2026, when Conductor starts deleting the data stored there.

### Can I export once Conductor Cloud is read-only?

Yes, until cloud data is deleted from 20 November 2026. Conductor says read-only cloud workspaces can be read and exported, but not sent new messages. It has not said whether Transfer to local works once the cloud is read-only, from 13 November 2026.

### Do local Conductor workspaces need exporting?

Not to keep your code. A local workspace is a git worktree folder on your Mac, so its commits live in your repository. Commit and push anything you want to keep, because uncommitted changes exist only in that folder.

### Can microManager import the Export data archive?

No. microManager imports from the Conductor data on your Mac, read-only, not from the archive. Transfer cloud workspaces to local first; they then import like any other local workspace.

### What happens to my local Conductor data in early 2027?

Conductor says the Mac app keeps getting new models and critical fixes until early 2027, and that it will delete Conductor user data when the app shuts down then. It has not given an exact date.