<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Migration on Margrop Blog</title>
    <link>https://blog.margrop.net/en/tag/migration/</link>
    <description>Recent content in Migration on Margrop Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 09 Jul 2026 10:30:00 +0800</lastBuildDate>
    <atom:link href="https://blog.margrop.net/en/tag/migration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Do Not Just Copy QingLong Into BaiHu: A Real Safe Migration Drill</title>
      <link>https://blog.margrop.net/en/post/qinglong-to-baihu-safe-migration/</link>
      <pubDate>Thu, 09 Jul 2026 10:30:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/qinglong-to-baihu-safe-migration/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;Bottom line first&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Migrating from QingLong Panel to BaiHu Panel is not a directory-copy exercise. I ran a real migration drill in an isolated Docker environment: a fresh QingLong instance with sample environment variables, scripts, labels, and cron jobs; then a fresh BaiHu instance; then an actual conversion and verification pass.&lt;/p&gt;&#xA;&lt;p&gt;The reliable migration unit is not the whole QingLong data directory. It is a set of assets: script files, environment variables, scheduled tasks, tags, enabled/disabled state, and task-variable relations. QingLong uses numeric IDs; BaiHu uses string IDs and relation tables. QingLong commands such as &lt;code&gt;task daily_check.py&lt;/code&gt; also need to become executable BaiHu commands such as &lt;code&gt;python /app/data/scripts/qinglong-migrated/daily_check.py&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This article contains no full private IP address, private registry address, host name, token, cookie, or production secret. The screenshots come from a disposable lab, and the variables are redacted sample data.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>The Complete AI Agent Migration Guide: A Real-World Journey from Scratch with 9 Pitfalls and Fixes</title>
      <link>https://blog.margrop.net/en/post/ai-agent-complete-migration-guide-from-scratch/</link>
      <pubDate>Sat, 30 May 2026 08:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/ai-agent-complete-migration-guide-from-scratch/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;Migrating from one AI Agent platform to another sounds like a &amp;ldquo;copy and paste&amp;rdquo; job. In reality, it&amp;rsquo;s a systems engineering challenge involving data migration, channel integration, scheduled tasks, auto-start configuration, proxy settings, and module compatibility.&lt;/p&gt;&#xA;&lt;p&gt;This article documents my complete migration journey: from installing the new platform, migrating memories and skills, configuring messaging channels, debugging mysterious failures, to achieving fully automated operation. 9 pitfalls encountered, 9 solutions found — all shared here.&lt;/p&gt;&#xA;&lt;/blockquote&gt;</description>
    </item>
    <item>
      <title>Migrating from OpenClaw to HermesAgent: A Smooth AI Agent Migration in Practice</title>
      <link>https://blog.margrop.net/en/post/openclaw-to-hermesagent-migration/</link>
      <pubDate>Fri, 29 May 2026 08:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/openclaw-to-hermesagent-migration/</guid>
      <description>&lt;h2 id=&#34;introduction-why-am-i-moving&#34;&gt;Introduction: Why Am I &amp;ldquo;Moving&amp;rdquo;?&lt;/h2&gt;&#xA;&lt;p&gt;In 2026, the AI agent landscape is evolving at an incredible pace. Tools that were cutting-edge six months ago might already be surpassed by more powerful alternatives. As someone who relies heavily on AI agents for daily work, I&amp;rsquo;ve been closely following the latest developments in this field.&lt;/p&gt;&#xA;&lt;p&gt;Recently, I completed a full migration from OpenClaw to HermesAgent. This wasn&amp;rsquo;t an impulsive decision, but a thoughtful choice made after experiencing the differences between the two tools in real-world usage.&lt;/p&gt;&#xA;&lt;p&gt;This article will share in detail:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;&lt;strong&gt;Background&lt;/strong&gt;: What OpenClaw and HermesAgent are&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Migration Reasons&lt;/strong&gt;: Why I decided to migrate&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Migration Process&lt;/strong&gt;: Step-by-step guide to complete the migration&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Pitfalls Encountered&lt;/strong&gt;: Problems and solutions during migration&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Post-Migration Cleanup&lt;/strong&gt;: How to completely remove OpenClaw residuals&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Post-Migration Experience&lt;/strong&gt;: New capabilities gained from HermesAgent&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Q&amp;amp;A&lt;/strong&gt;: Frequently asked questions&lt;/li&gt;&#xA;&lt;/ol&gt;</description>
    </item>
    <item>
      <title>Gitalk Broken After Migration from Gridea to Hugo: Complete Troubleshooting and Fix Log</title>
      <link>https://blog.margrop.net/en/post/gitalk-migration-from-gridea-to-hugo-complete-fix/</link>
      <pubDate>Sun, 01 Mar 2026 09:30:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/gitalk-migration-from-gridea-to-hugo-complete-fix/</guid>
      <description>&lt;h1 id=&#34;background&#34;&gt;Background&lt;/h1&gt;&#xA;&lt;p&gt;After migrating the blog entirely from &lt;code&gt;Gridea&lt;/code&gt; to &lt;code&gt;Hugo&lt;/code&gt;, pages load normally, but the comment section &lt;code&gt;Gitalk&lt;/code&gt; appears to be malfunctioning:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;No obvious errors are reported on the page, but the comment section doesn&amp;rsquo;t load or display historical comments.&lt;/li&gt;&#xA;&lt;li&gt;Historical articles are not associated with their original issues.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;This article documents a complete troubleshooting and fix process for future reference when migrating similar sites.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Completely Migrate Gridea to Hugo (Including Pitfalls and Fixes)</title>
      <link>https://blog.margrop.net/en/post/how-to-migrate-gridea-to-hugo-completely/</link>
      <pubDate>Sat, 28 Feb 2026 21:00:00 +0800</pubDate>
      <guid>https://blog.margrop.net/en/post/how-to-migrate-gridea-to-hugo-completely/</guid>
      <description>&lt;p&gt;I recently migrated my blog from &lt;code&gt;Gridea&lt;/code&gt; to &lt;code&gt;Hugo&lt;/code&gt;. It might seem like a simple &amp;ldquo;static blog framework switch&amp;rdquo;, but there are quite a few pitfalls.&#xA;This post documents the entire process in full, especially those issues you only discover after migration.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
