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

# Migrating

# Migrating crocbot to a new machine

This guide migrates a crocbot Gateway from one machine to another **without redoing onboarding**.

The migration is simple conceptually:

* Copy the **state directory** (`$CROCBOT_STATE_DIR`, default: `~/.crocbot/`) — this includes config, auth, sessions, and channel state.
* Copy your **workspace** (`~/croc/` by default) — this includes your agent files (memory, prompts, etc.).

But there are common footguns around **profiles**, **permissions**, and **partial copies**.

## Before you start (what you are migrating)

### 1) Identify your state directory

Most installs use the default:

* **State dir:** `~/.crocbot/`

But it may be different if you use:

* `--profile <name>` (often becomes `~/.crocbot-<profile>/`)
* `CROCBOT_STATE_DIR=/some/path`

If you’re not sure, run on the **old** machine:

```bash theme={null}
crocbot status
```

Look for mentions of `CROCBOT_STATE_DIR` / profile in the output. If you run multiple gateways, repeat for each profile.

### 2) Identify your workspace

Common defaults:

* `~/croc/` (recommended workspace)
* a custom folder you created

Your workspace is where files like `MEMORY.md`, `USER.md`, and `memory/*.md` live.

### 3) Understand what you will preserve

If you copy **both** the state dir and workspace, you keep:

* Gateway configuration (`crocbot.json`)
* Auth profiles / API keys / OAuth tokens
* Session history + agent state
* Channel state (e.g. Telegram login/session)
* Your workspace files (memory, skills notes, etc.)

If you copy **only** the workspace (e.g., via Git), you do **not** preserve:

* sessions
* credentials
* channel logins

Those live under `$CROCBOT_STATE_DIR`.

## Migration steps (recommended)

### Step 0 — Make a backup (old machine)

On the **old** machine, stop the gateway first so files aren’t changing mid-copy:

```bash theme={null}
crocbot gateway stop
```

(Optional but recommended) archive the state dir and workspace:

```bash theme={null}
# Adjust paths if you use a profile or custom locations
cd ~
tar -czf crocbot-state.tgz .crocbot

tar -czf croc-workspace.tgz croc
```

If you have multiple profiles/state dirs (e.g. `~/.crocbot-main`, `~/.crocbot-work`), archive each.

### Step 1 — Install crocbot on the new machine

On the **new** machine, install the CLI (and Node if needed):

* See: [Install](/install)

At this stage, it’s OK if onboarding creates a fresh `~/.crocbot/` — you will overwrite it in the next step.

### Step 2 — Copy the state dir + workspace to the new machine

Copy **both**:

* `$CROCBOT_STATE_DIR` (default `~/.crocbot/`)
* your workspace (default `~/croc/`)

Common approaches:

* `scp` the tarballs and extract
* `rsync -a` over SSH
* external drive

After copying, ensure:

* Hidden directories were included (e.g. `.crocbot/`)
* File ownership is correct for the user running the gateway

### Step 3 — Run Doctor (migrations + service repair)

On the **new** machine:

```bash theme={null}
crocbot doctor
```

Doctor is the “safe boring” command. It repairs services, applies config migrations, and warns about mismatches.

Then:

```bash theme={null}
crocbot gateway restart
crocbot status
```

## Common footguns (and how to avoid them)

### Footgun: profile / state-dir mismatch

If you ran the old gateway with a profile (or `CROCBOT_STATE_DIR`), and the new gateway uses a different one, you’ll see symptoms like:

* config changes not taking effect
* channels missing / logged out
* empty session history

Fix: run the gateway/service using the **same** profile/state dir you migrated, then rerun:

```bash theme={null}
crocbot doctor
```

### Footgun: copying only `crocbot.json`

`crocbot.json` is not enough. Many providers store state under:

* `$CROCBOT_STATE_DIR/credentials/`
* `$CROCBOT_STATE_DIR/agents/<agentId>/...`

Always migrate the entire `$CROCBOT_STATE_DIR` folder.

### Footgun: permissions / ownership

If you copied as root or changed users, the gateway may fail to read credentials/sessions.

Fix: ensure the state dir + workspace are owned by the user running the gateway.

### Footgun: migrating between remote/local modes

* If your UI (WebUI/TUI) points at a **remote** gateway, the remote host owns the session store + workspace.
* Migrating your laptop won’t move the remote gateway’s state.

If you’re in remote mode, migrate the **gateway host**.

### Footgun: secrets in backups

`$CROCBOT_STATE_DIR` contains secrets (API keys, OAuth tokens, channel credentials). Treat backups like production secrets:

* store encrypted
* avoid sharing over insecure channels
* rotate keys if you suspect exposure

## Verification checklist

On the new machine, confirm:

* `crocbot status` shows the gateway running
* Your channels are still connected (e.g. Telegram doesn't require re-login)
* The dashboard opens and shows existing sessions
* Your workspace files (memory, configs) are present

## Related

* [Doctor](/gateway/doctor)
* [Gateway troubleshooting](/gateway/troubleshooting)
* [Where does crocbot store its data?](/help/faq#where-does-crocbot-store-its-data)