> ## Documentation Index
> Fetch the complete documentation index at: https://docs.replicas.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Migrate from Conductor Cloud

> Move Conductor Cloud workspaces, setup scripts, secrets, routines, and team to Replicas.

Conductor is [joining Meta](https://www.conductor.build/announcement). Conductor Cloud goes read-only on **November 13, 2026** and shuts down on **November 20, 2026**, when Conductor begins deleting cloud data. This guide moves that work to Replicas cloud workspaces.

For the background and reasoning, see the blog post [How to migrate from Conductor Cloud to Replicas](https://replicas.dev/blog/migrate-from-conductor-cloud).

## Migrate with your coding agent

Paste this prompt into Claude Code, Codex, or Cursor on the computer where you used Conductor. The agent reads your Conductor setup and creates the same setup in Replicas with the [CLI](https://docs.replicas.dev/features/cli.md). The rest of this page covers the same steps by hand.

```text wrap theme={null}
Move my Conductor Cloud setup to Replicas. Read https://docs.replicas.dev/migrate/conductor-cloud.md first, then:

1. Find my Conductor setup on this computer: the Conductor app's settings, any Conductor data export I downloaded, and .conductor/settings.toml or conductor.json in my repositories. Collect the repositories, the Cloud Computer install script, each repository's setup script, the names of my environment variables and secrets, and my routines. If something isn't on this computer, ask me to paste it.
2. Install the Replicas CLI with `npm install -g replicas-cli` and sign in with `replicas login`.
3. Check my repositories with `replicas repos list`, then create an environment with them: `replicas env create <name> -r <repo>,<repo>`.
4. Save the install script as the environment's warm hook with `replicas env warm-hooks save-test <env> --file <script>`. Combine the repository setup scripts into one start hook that changes into each repository under ~/workspaces/ first, test it with `replicas env start-hooks test <env> --file <script>`, then save it with `replicas env start-hooks save <env> --file <script>`. Remove references to CONDUCTOR_* variables.
5. Set each variable with `replicas env vars set <env> <KEY> "$VALUE"`, reading the value from my local .env files inside the shell. Never print a value. List any keys you couldn't find so I can add them in the Replicas app.
6. Recreate each routine with `replicas automation create "<name>" -e <env> -p "<prompt>"`, adding `--trigger-cron "<schedule>"` for scheduled routines or `--trigger-github <event>` for routines run from GitHub.
7. Tell me what you created and ask me to start a test workspace in the new environment at https://app.replicas.dev.
```

## Concept mapping

| Conductor Cloud | Replicas |
| - | - |
| Organization | Organization with [members and roles](https://docs.replicas.dev/admin/team.md) |
| Cloud Computer (repositories, variables, secrets, installed software) | [Environment](https://docs.replicas.dev/features/environments.md). An organization can have many, plus personal ones and [forks](https://docs.replicas.dev/features/environments.md#forks) |
| Cloud Computer build | [Warm pool](https://docs.replicas.dev/features/environments.md#warm-pools) build, shown as the environment's [status](https://docs.replicas.dev/features/environments.md#status) |
| Install software script | Environment or repository [warm hook](https://docs.replicas.dev/features/environments.md#warm-hooks) |
| Repository setup script | Repository [start hook](https://docs.replicas.dev/features/environments.md#start-hooks) in `replicas.json` |
| Cloud Computer environment variables and secrets | Environment [variables](https://docs.replicas.dev/features/environments.md#variables), with values marked **Sensitive**, or [Doppler](https://docs.replicas.dev/features/doppler.md) and [Infisical](https://docs.replicas.dev/features/infisical.md) sync |
| Cloud workspace | [Workspace](https://docs.replicas.dev/features/workspaces/overview.md) |
| Claude Code, Codex, and Cursor agents | [Claude Code](https://docs.replicas.dev/features/coding-agents/claude-code.md), [Codex](https://docs.replicas.dev/features/coding-agents/codex.md), [Cursor](https://docs.replicas.dev/features/coding-agents/cursor.md), plus [Muse Code](https://docs.replicas.dev/features/coding-agents/muse-code.md), [Opencode](https://docs.replicas.dev/features/coding-agents/opencode.md), and [Pi](https://docs.replicas.dev/features/coding-agents/pi.md) |
| Subscriptions and API keys | [Credentials](https://docs.replicas.dev/admin/credentials.md), personal or shared with the organization |
| Routines (schedule or GitHub action) | [Automations](https://docs.replicas.dev/features/automations.md) with schedule, GitHub, GitLab, Slack, Linear, Sentry, or webhook triggers |
| Workspace link sharing | [Workspace sharing](https://docs.replicas.dev/features/workspaces/overview.md#chats-and-collaboration) |
| Conductor API | [API](https://docs.replicas.dev/features/api.md), [CLI](https://docs.replicas.dev/features/cli.md), and [MCP server](https://docs.replicas.dev/features/mcp.md) |
| iOS app | [iOS app](https://docs.replicas.dev/features/mobile-app.md) |

## Before November 13

**1. Push every branch**

Commit and push each cloud workspace's branch, including untracked files you want to keep. Copy Git-ignored files, such as `.env`, somewhere safe.

**2. Export your data**

In Conductor, open **Settings → Account → Export data**. To keep a workspace and its chats on your Mac, right-click it and choose **Transfer to local** ([Conductor's announcement](https://www.conductor.build/announcement)).

**3. Copy your Cloud Computer settings**

Copy the install software script, each repository's setup script, and the names of your variables and secrets. Conductor hides saved values, so get them from their source, such as your password manager or secrets manager.

## Move to Replicas

**1. Connect agents and repositories**

Follow the [Quickstart](https://docs.replicas.dev/quickstart.md): connect a coding agent subscription or API key, connect [GitHub](https://docs.replicas.dev/features/github.md) or [GitLab](https://docs.replicas.dev/features/gitlab.md), and add your repositories. Replicas creates an environment with them.

**2. Move setup scripts**

Put slow, repeatable setup, such as system packages, runtimes, and dependency installs, in a [warm hook](https://docs.replicas.dev/features/environments.md#warm-hooks). It runs once per build, and workspaces start from the result. Put per-workspace steps, such as starting a dev server or running migrations, in a [start hook](https://docs.replicas.dev/features/environments.md#start-hooks).

Commit both to the repository so every environment that clones it gets them:

```json replicas.json theme={null}
{
  "warmHook": { "commands": ["pnpm install"] },
  "startHook": { "commands": ["pnpm db:migrate"] }
}
```

Remove references to `CONDUCTOR_*` variables. If a hook fails, select **Fix with agent** on the environment page.

**3. Add variables and secrets**

Open the environment, then **Environment Variables**. Paste a whole `.env` or use **Import .env**. Replicas marks keys whose names look like secrets as **Sensitive**; review the imported rows and check **Sensitive** on any other secret, such as a `DATABASE_URL` that contains a password, before saving. Sensitive values are never shown again. Don't add GitHub tokens: Replicas authenticates Git through its GitHub App.

If an agent finds a missing variable later, it asks for it with a form above the chat ([details](https://docs.replicas.dev/features/environments.md#when-an-agent-needs-a-variable)).

**4. Continue open branches**

On Home, choose the environment and the branch you pushed as the starting branch, then describe what's left. For an open pull request, comment `@tryreplicas` on it to start a workspace on that PR ([details](https://docs.replicas.dev/features/github.md#trigger-from-pull-requests)).

Replicas can't import Conductor chats. Paste the relevant part of your export into the first message when the agent needs earlier context.

**5. Recreate routines as automations**

For each routine, create an [automation](https://docs.replicas.dev/features/automations.md) with the same prompt and environment. Use a [schedule trigger](https://docs.replicas.dev/features/automations.md#schedule-triggers) for scheduled routines and a [GitHub trigger](https://docs.replicas.dev/features/automations.md#github-triggers) for routines run from GitHub. You can also set the agent, model, and workspace size per automation.

**6. Invite your team**

Invite teammates from [Members](https://docs.replicas.dev/admin/team.md#inviting-members) and grant environment access with [roles](https://docs.replicas.dev/admin/team.md#access). Teammates who own the connected GitHub account or belong to its GitHub organization can join during setup without an invite.

## What's different

| | Conductor Cloud | Replicas |
| - | - | - |
| Setup | One Cloud Computer per organization | Many [environments](https://docs.replicas.dev/features/environments.md), each with its own repositories, variables, and hooks |
| Git hosts | [GitHub](https://www.conductor.build/docs/cloud/faq) | [GitHub](https://docs.replicas.dev/features/github.md) and [GitLab](https://docs.replicas.dev/features/gitlab.md) |
| Starting work | [Desktop app, API](https://www.conductor.build/changelog/0.78.0-introducing-conductor-cloud), [iOS app](https://www.conductor.build/changelog/0.90.0-conductor-for-ios) | Web, [desktop](https://docs.replicas.dev/features/desktop-app.md), [iOS](https://docs.replicas.dev/features/mobile-app.md), [Slack](https://docs.replicas.dev/features/slack.md), [Linear](https://docs.replicas.dev/features/linear.md), GitHub, [API](https://docs.replicas.dev/features/api.md), [CLI](https://docs.replicas.dev/features/cli.md) |
| Machine | [8 vCPU, 16 GB RAM](https://www.conductor.build/docs/cloud/faq) | `small`, `large`, or `ultra` [sizes](https://docs.replicas.dev/admin/billing.md), up to 8 vCPU and 32 GB |
| Workspace computer | [Linux microVM with Chrome installed](https://www.conductor.build/docs/cloud/cloud-computer) | Linux VM with a [desktop and Chrome](https://docs.replicas.dev/features/workspaces/overview.md#desktop-tab) that you and the agent can see and control |
| Billing | [Pro, Teams, or Enterprise plan](https://www.conductor.build/docs/cloud/faq) | [Plan with included usage](https://docs.replicas.dev/admin/billing.md), billed per minute while a workspace is awake |

## Related

> [card] [Environments](https://docs.replicas.dev/features/environments.md)
>
> Variables, files, skills, MCPs, and hooks.

> [card] [Automations](https://docs.replicas.dev/features/automations.md)
>
> Schedules and event triggers.

> [card] [Repository config](https://docs.replicas.dev/features/workspaces/repository-configuration.md)
>
> The `replicas.json` schema.

> [card] [Team](https://docs.replicas.dev/admin/team.md)
>
> Members, roles, and access.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.