How to Migrate from OpenClaw to Clawctl (Complete Guide)
You have a running OpenClaw installation. You want to move to Clawctl for the security features without starting over.
This guide walks through the migration process step by step.
What Gets Migrated
When you move to Clawctl, you can bring over:
- Agent configuration — Model settings, persona, system prompts
- LLM API keys — Entered securely in the dashboard, encrypted at rest
- Custom tools — Your integrations and custom skills
- Knowledge graph — All stored context and memory
- Channel connections — Re-authenticate Telegram, WhatsApp, Discord, etc.
Step 1: Sign Up for Clawctl
Head to clawctl.com/checkout and pick a plan:
| Plan | Price | Best For |
|---|---|---|
| Starter | $49/mo | Individual developers |
| Team | $299/mo | Teams with approval workflows |
| Business | $999/mo | Production systems, compliance |
Complete payment via Stripe. Your secure environment is provisioned automatically in under 60 seconds.
Step 2: Configure Your LLM Provider
Once provisioned, the dashboard setup wizard walks you through configuration:
- Select your LLM provider — Anthropic, OpenAI, or others
- Enter your API key — Clawctl validates the connection in real time
- Done — Your key is encrypted and injected at runtime (never stored in plaintext)
Grab the API keys from your existing ~/.openclaw/openclaw.json before you start. You'll paste them into the dashboard.
Step 3: Transfer Workspace Files
Your workspace files (skills, AGENTS.md, SOUL.md) need manual transfer. Use the Clawctl dashboard to upload files directly to your tenant workspace.
Step 4: Re-Authenticate Channels
Channel credentials can't be automatically transferred for security reasons. Re-authenticate each channel in the dashboard:
Telegram: Navigate to Channels > Telegram in your dashboard. Paste your bot token and update the webhook URL in BotFather to your new Clawctl endpoint.
WhatsApp: Navigate to Channels > WhatsApp. Scan the QR code with your WhatsApp Business app and wait for pairing confirmation.
Discord / Slack: Update your bot configuration in the Discord/Slack developer portal. Point webhooks to your new Clawctl URL and re-authorize the bot.
Step 5: Update Webhook URLs
All external services pointing to your local OpenClaw need to point to Clawctl:
Before: http://localhost:18789 or http://your-server:18789
After: https://your-id.tenant.clawctl.com
Update webhooks in:
- Telegram Bot Settings
- Discord Developer Portal
- Slack App Settings
- GitHub Webhooks
- Any other integrations
Your tenant URL is visible in the dashboard under Credentials.
Step 6: Verify in the Dashboard
Open your Clawctl dashboard and confirm:
- Agent status shows "Running"
- LLM provider is connected and validated
- Channels show as active
- Audit logs are capturing events
Test your agent by sending a message through your connected channel or the built-in web chat.
What Changes
| Aspect | Before (Raw OpenClaw) | After (Clawctl) |
|---|---|---|
| Gateway binding | 0.0.0.0 (all interfaces) | 127.0.0.1 (loopback only) |
| Authentication | Localhost trusted | Token required |
| Credentials | Plaintext on disk | Encrypted vault |
| Control UI | Exposed | Disabled externally |
| Audit logging | None | 50+ event types |
| Network egress | Unrestricted | Domain allowlist |
| High-risk actions | Unrestricted | Approval required |
Rollback Option
The migration doesn't delete your original installation. If something goes wrong, your original OpenClaw setup is still there.
You can run both in parallel during testing before fully switching over.
Common Questions
Will my agent lose its memory?
Conversation history from your local installation stays on your local machine. New conversations on Clawctl start fresh with full logging and search built in.
What about custom tools?
Upload your custom tools to your Clawctl workspace via the dashboard. They work the same way.
Can I migrate from a remote server?
Yes. Grab your configuration files and API keys from the remote server, then enter them in the Clawctl dashboard.
What if I have a non-standard setup?
Review your local openclaw.json to identify API keys and settings. Enter them manually in the dashboard. If you hit issues, reach out to migration@mg.clawctl.com.
Next Steps
After migration:
- Review audit logs — See what your agent is doing
- Configure approvals — Customize which actions need approval
- Set up alerts — Get notified of security events
- Update integrations — Point external services to new endpoints