Migrate from Conductor Cloud

Conductor is joining Meta. 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.

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. The rest of this page covers the same steps by hand.

Move my Conductor Cloud setup to Replicas. Read https://docs.replicas.dev/migrate/conductor-cloud.md first, then:

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.
Install the Replicas CLI with `npm install -g replicas-cli` and sign in with `replicas login`.
Check my repositories with `replicas repos list`, then create an environment with them: `replicas env create <name> -r <repo>,<repo>`.
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.
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.
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.
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
Cloud Computer (repositories, variables, secrets, installed software)	Environment. An organization can have many, plus personal ones and forks
Cloud Computer build	Warm pool build, shown as the environment’s status
Install software script	Environment or repository warm hook
Repository setup script	Repository start hook in `replicas.json`
Cloud Computer environment variables and secrets	Environment variables, with values marked Sensitive, or Doppler and Infisical sync
Cloud workspace	Workspace
Claude Code, Codex, and Cursor agents	Claude Code, Codex, Cursor, plus Muse Code, Opencode, and Pi
Subscriptions and API keys	Credentials, personal or shared with the organization
Routines (schedule or GitHub action)	Automations with schedule, GitHub, GitLab, Slack, Linear, Sentry, or webhook triggers
Workspace link sharing	Workspace sharing
Conductor API	API, CLI, and MCP server
iOS app	iOS app

Before November 13

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.

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).

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

Connect agents and repositories

Follow the Quickstart: connect a coding agent subscription or API key, connect GitHub or GitLab, and add your repositories. Replicas creates an environment with them.

Move setup scripts

Put slow, repeatable setup, such as system packages, runtimes, and dependency installs, in a warm hook. 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.Commit both to the repository so every environment that clones it gets them:

replicas.json

{
  "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.

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).

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).Replicas can’t import Conductor chats. Paste the relevant part of your export into the first message when the agent needs earlier context.

Recreate routines as automations

For each routine, create an automation with the same prompt and environment. Use a schedule trigger for scheduled routines and a GitHub trigger for routines run from GitHub. You can also set the agent, model, and workspace size per automation.

Invite your team

Invite teammates from Members and grant environment access with roles. 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, each with its own repositories, variables, and hooks
Git hosts	GitHub	GitHub and GitLab
Starting work	Desktop app, API, iOS app	Web, desktop, iOS, Slack, Linear, GitHub, API, CLI
Machine	8 vCPU, 16 GB RAM	`small`, `large`, or `ultra` sizes, up to 8 vCPU and 32 GB
Workspace computer	Linux microVM with Chrome installed	Linux VM with a desktop and Chrome that you and the agent can see and control
Billing	Pro, Teams, or Enterprise plan	Plan with included usage, billed per minute while a workspace is awake

Environments

Variables, files, skills, MCPs, and hooks.

Automations

Schedules and event triggers.

Repository config

The replicas.json schema.

Team

Members, roles, and access.

Get started

Migrate

Workspaces

Coding agents

Integrations

Build and automate

Apps

Admin

Updates

Migrate from Conductor Cloud

Migrate with your coding agent

Concept mapping

Before November 13

Move to Replicas

What’s different

Environments

Automations

Repository config

Team

​Migrate with your coding agent

​Concept mapping

​Before November 13

​Move to Replicas

​What’s different

​Related

Environments

Automations

Repository config

Team

Migrate with your coding agent

Concept mapping

Before November 13

Move to Replicas

What’s different

Related