---
title: Older-install migration
nav: Older installs
summary: Keep older commands, state and download addresses working while moving to Agent J.
order: 62
---
# Older-install migration

<details>
<summary>Older compatibility details</summary>

Use this page only for an older install. Download and verify the current signed package using the current install guide: [install guide](https://agentj.app/install.md). Tell your human and get their consent before stopping the old service. Keep identity, pairing data and personal files.

- Check `uv tool list` (or `pipx list`) for the old host package. Do not identify an installation by command name alone.
- After verifying the new package's signature and checksum, stop the old service using its command's `service uninstall`. Remove the old package listed by your original install tool. Install `agentj` using the current guide. Never run an unverified download.
- The state moves from the old state folder to `~/.local/state/agentj` on the first run of `agentj` **after your human says yes** (Step 5: a terminal asks y/N; without one, `agentj --migrate-legacy status`). Paired phones, the approval passphrase and the Agent J account stay — no new pairing, no new login. A serve still running on the old folder keeps using it; a compatibility link to the old folder remains.
- Run `agentj migrate rollback` to undo the move, then reinstall the old program the same way, in reverse. Do not delete folders or pair again to fix migration.
- Migrated installations may keep an old compatibility command (a link to `agentj` if the name is free). It prints a notice pointing here. New installs never get the old command. Retiring old commands and state is a separate step.
- Use `agentj alias install` to add the optional short command `aj`. If it already exists, keep using `agentj`; the installer does not overwrite it.
- Optional short command `aj`: `agentj alias install`. It is skipped when `aj` already exists on the Agent J host — then tell
  your human that `aj` is taken and they keep using `agentj`.
- The phone keeps working at its old address; the new one is https://m.agentj.app (Step 11, nothing to re-pair if the old
  page still shows the Agent).

## Compatible download addresses

Older installations may still use the original download domain and its testing or API subdomains for `/install.md`, checksums and `/dl/`. Verify against the GitHub copy and current signatures. This documentation update does not move domains, API POST/WSS endpoints, mail, browser origins or stored pairing data.

The old visitor-storage origin remains compatible. This text-only step does not change its iframe, origin checks or browser storage.

</details>
