Moving an OpenClaw agent to another host
How to move an OpenClaw agent between hosts without losing its memory, persona or channels: what to export, in what order, and what to check after.
By OpenClawPro. Published October 25, 2026. Updated October 25, 2026.
Moving an agent is mostly about its state. OpenClaw keeps state, memory and credentials on the machine it runs on, so a migration is a careful copy of that state to a new server, a reconnection of the channels and a check that the agent still behaves the same. Done in the right order, the people who talk to the agent barely notice.
What do you need to take with you?
- The agent's workspace: memory, persona, configuration and installed skills.
- The list of channels and how each one is paired.
- The model provider settings, without copying keys in plain text.
- Any scheduled tasks.
If you are leaving a managed platform, ask for an export first. Some platforms provide one; for others, you may only be able to take the persona and rebuild the rest.
In what order?
- Prepare the new server and harden it before anything else: keys, firewall, updates.
- Install the same OpenClaw version as the old one, so the workspace format matches.
- Copy the workspace while the old agent is stopped, so nothing changes during the copy.
- Move secrets properly: create new keys where you can, and store them in a secrets store.
- Reconnect channels one by one and approve the senders again where needed.
- Test with a few known conversations before you switch everyone over.
- Update to the latest version once everything works.
What can go wrong?
Channel sessions that cannot be moved and must be paired again; skills that depend on a path or a service that no longer exists; a version mismatch that changes the workspace format. Each of these is easy to fix when you expect it, and annoying when you do not.
Having it done
Our migration add-on costs $149 and moves the memory, persona and channels in 48 hours, onto a server we manage for you or onto yours. Add it in the configurator.