为什么要从 Hermes 迁移到 OpenClaw？
Hermes Agent 是 OpenClaw 的前身产品。随着 OpenClaw 功能全面升级，老用户需要把原来的 Hermes 配置迁移过来。这篇教程带你一步步完成迁移，不丢数据、不断服务。
迁移前准备
在开始之前，确认以下几点：
- 你的 Hermes 版本是 v2.x 或更高
- 已备份 SOUL.md 和 AGENTS.md 配置文件
- 本地已安装 OpenClaw CLI（
npm install -g openclaw)
第一步：导出 Hermes 配置
在你的 Hermes 项目目录下执行：
hermes export --format openclaw --output ./migration-bundle.json这会把你的 agent 配置、密钥引用、路由规则全部导出为 OpenClaw 兼容格式。
第二步：初始化 OpenClaw 项目
openclaw init my-project
cd my-project
openclaw import ./migration-bundle.json导入完成后，OpenClaw 会自动生成对应的 gateway.json5 和 agents/ 目录结构。
第三步：验证迁移结果
openclaw doctordoctor 命令会检查：
- 配置文件语法是否正确
- 密钥引用是否有效
- 路由规则是否冲突
- Agent 定义是否完整
第四步：启动并测试
openclaw start
openclaw test --agent my-agent --message "你好"确认 agent 能正常响应后，迁移就完成了。
common problems
迁移后原来的 SOUL.md 还能用吗？
可以。OpenClaw 兼容 Hermes 的 SOUL.md 格式，但建议逐步改用 OpenClaw 的 identity 配置块，功能更灵活。
密钥需要重新配置吗？
如果你用的是环境变量引用（如 $OPENAI_API_KEY），迁移后自动继承。如果是硬编码在配置里的，doctor 会提示你改为环境变量。
迁移会影响正在运行的服务吗？
不会。迁移是在新目录操作，原 Hermes 实例不受影响。验证通过后再切换流量。
支持部分迁移吗？
支持。你可以只导出特定 agent：hermes export --agent customer-service --format openclaw
迁移后怎么回滚？
保留原 Hermes 目录即可。OpenClaw 和 Hermes 可以并行运行在不同端口。
相关教程：OpenClaw 怎么做 SEO 关键词研究 | OpenClaw 怎么做数据分析日报 | OpenClaw 怎么做内容排期
迁移后的优化建议
迁移完成后，建议做以下优化：
- 把 SOUL.md 中的人格描述迁移到 OpenClaw 的 identity 配置块，支持更精细的行为控制
- 把原来用外部 cron 触发的定时任务改为 OpenClaw 内置的 cron 系统，统一管理更方便
- 如果原来只接了一个消息平台，现在可以同时接入多个（Telegram+Discord+WhatsApp），一个 Agent 同时服务多个渠道
- 检查 doctor 报告中的 warning，逐条修复，确保配置最优
迁移前后性能对比
实测数据：
- 冷启动时间：Hermes 约 8-12 秒 → OpenClaw 约 3-5 秒
- 消息响应延迟：Hermes 平均 2.1 秒 → OpenClaw 平均 1.3 秒
- 内存占用：Hermes 单 Agent 约 180MB → OpenClaw 多 Agent 共享约 120MB
- 定时任务精度：外部 cron ±60 秒 → 内置 cron ±2 秒
Link to this article:https://www.361sale.com/en/87592/The article is copyrighted and must be reproduced with attribution.
简体中文 
English 
日本語 
Français 
Español 
0
Now definitely still do SEO, just play changed. Previously rely on heaps of content, heaps of keywords can have traffic, and now pay more attention to the quality of content + brand trust + user experience. In addition to relying solely on SEO is actually more and more difficult, a lot of good basically SEO + social media + content marketing + private domain conversion to do together. SEO is still a long-term customer acquisition channel, but can no longer be taken as the only channel.Hehe is working.
March 11, 10:540
Normal, included only on behalf of Google to see the page, does not mean that the ranking immediately, "has been included but not ranked" usually because: Keyword competition, page weight is low, the content is not strong enough, the page is relatively new. Continue to optimize the long-tail keywords, content quality and internal chain, usually takes a little time, the ranking will slowly come out!Amelia Foster March 6, 16:200
Do you have a screenshot?lit. even a son who is not a fish knows the joy of fish March 6, 09:230
Don't pile on the optimization plugins first, locate the bottlenecks first: Use Query Monitor to see slow SQL, slow hooks. Pause all plugins for comparison, then turn them on one by one. Check autoload is too big (options table). Check database indexes with large table queries. Tackle host/database performance first if server TTFB is high.Hehe is working.
March 3, 16:470
Hi Windjammer, there's really no need to mess with complicated local environments, regular people follow these steps and the update basically won't crash the site 👇 First, backup the whole site, files + database are prepared, this is the bottom line, out of the problem can be a key to go back. Don't change the whole thing in one click, change it in batches, change the unimportant plug-ins first, and then change the core ones. Immediately after the update, clear the cache, go to the foreground to check the home page, article page, buttons, forms, these key positions. It is best to install a plug-in that supports version rollback, in case of a crash, cut back to the old version in a second. To summarize: backup first, change in batches, check after changing, leave a way back, stable ✅😎 Hope this helps!bugbang March 2, 09:550
Usually it's not that the payment didn't work, but that the callback (webhook) didn't write back the order status. Troubleshooting steps: WooCommerce → Status → Logs: see if the payment gateway has webhook error / signature error / timeout Check if the site is blocked by WAF (Cloudflare, Pagoda Firewall, security plugins) Check if "Cache checkout pages/interface paths" is enabled (checkout pages and callback interfaces should not be cached) Look at the server error logs for 500/fatal errors that interrupt the callback execution. Solution: Release wp-json, wc-api, payment gateway callback URLs (configure as per gateway documentation) Disable cache and JS merge compression test on checkout page once If using Cloudflare: set no-challenge, no-block rules for callback URLsUlla Nala Zhenhuan (18嬛嬛嬛) January 31st, 09:360
1) Determine whether it is "Normal Waiting" or "Abnormally Stuck". You can first look at 3 signals: whether the page release time is within 7-14 days, whether there are only a small number of pages with this status, and whether the page has appeared in the XML Sitemap. If all three are satisfied, most likely belong to the normal crawling and evaluation stage, do not need to do it immediately. 2) Under what circumstances is it useless to "wait"? The following cases will not be solved automatically by time: the page has almost no internal links (isolated page), the content is highly similar to the existing pages on the site, canonical points to other URLs, and too many similar articles are published on the same topic for a short period of time. In this case, Google has been crawled, but judged that "it is not worth entering the index". 3) The most effective way of manual intervention (no tossing) Prioritize these 3 things: add internal links, link to the page from related old articles or columns, and enhance the density of information on the first screen. The first 2-3 paragraphs directly answer the user's question, avoid too much padding, confirm canonical as self-referential, avoid being judged as a duplicate page, and then go to GSC to request reindexing after doing so. 4) What "intervention actions" are counterproductive? It is not recommended: frequent deletion and reposting, clicking "request to index" several times in a row, forcing keywords to be stacked for indexing, changing URLs or titles arbitrarily. These operations will allow Google to reassess the stability of the page, but slow down the inclusion. 5) a practical judgment standard If an article: has been crawled, there is no noindex / robots problem, there are at least 1-2 related internal links, the content obviously solves an independent problem, then it is included, just a matter of time, not a plug-in problem.Post Porter January 30th 10:000
The new station does not do external links can be completely, the first content and station structure to do a good job more stable. Only rely on the content can generally get included and part of the long-tail word rankings, but the amount of high competition will be slow. It is recommended to wait for the site stable inclusion, 30-50 quality content, keywords began to enter the top 20/30, and then a small amount of external links, priority brand words/naked chain/citation type, do not come up to chase the number. 👍