# Can I keep my blog comments when migrating off WordPress? > Usually yes, but only if you plan for them, because comments do not move automatically with your posts. Blog comments are stored in the WordPress database, separately from the post content, so a migration that copies your articles does not necessarily bring the discussion underneath them. You have three realistic options. First, if the new platform has its own native comment system, export your WordPress comments and import them, mapping each comment to its post. Second, move to a hosted comment service that stays independent of your platform, so the comments live there regardless of where the site is built. Third, if the new platform has no comments and you do not adopt a service, preserve the comments as archived content, for example by keeping the original discussion text on the page, so the words are not simply lost. Comments add real content, long tail relevance, and freshness, so deciding their fate before the move matters. WPBuildAI scans your site and returns the post content including the visible comments, so the discussion is captured rather than discarded when you switch. Source: https://wpbuildai.com/can-i-keep-blog-comments-when-migrating/ By lawrence-arya ยท 2026-06-12 --- Usually yes, you can keep your blog comments when migrating off WordPress, but only if you plan for them, because comments do not move automatically with your posts. The reason is structural: blog comments are stored in the WordPress database, separately from the post content, so a migration that copies your articles does not necessarily bring the discussion underneath them. You have three realistic options. First, if the new platform has its own native comment system, export your WordPress comments and import them, mapping each comment to its post. Second, move to a hosted comment service that stays independent of your platform, so the comments live there regardless of where the site is built. Third, if the new platform has no comments and you do not adopt a service, preserve the comments as archived content, for example by keeping the original discussion text on the page, so the words are not simply lost. Comments add real content, long tail relevance, and freshness, so deciding their fate before the move matters. WPBuildAI scans your site and returns the post content including the visible comments, so the discussion is captured rather than discarded when you switch. If a plugin is holding the comments, treat that as the fragile part of the export: Patchstack recorded [11,334 new WordPress vulnerabilities in 2025 with 91 percent of them in plugins and only six in core](https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/), and plugins that store data in their own tables are also the ones most likely to be abandoned before you migrate. ## Why comments do not travel by default Start with the structural fact, because it explains everything else. In WordPress, a post and its comments are separate records in the database, linked by the post they belong to. When you export or copy your posts, you are moving one kind of record, and the comments are another kind that has to be handled on its own. So a migration that successfully brings your articles across can still arrive with empty comment sections, not because anything failed, but because comments were never part of what was moved. This is why the honest answer begins with planning: you keep comments by treating them as a distinct dataset to migrate, not as something that rides along with the posts. ## Option one: export and import to native comments If the destination platform has its own comment system, the cleanest path is to export your WordPress comments and import them there, with each comment attached to the right post. This keeps the discussion native to the new site, displayed under the posts exactly as before. The work is in the mapping: every comment has to land on its correct post, and threaded replies should keep their structure. A clean export is the prerequisite, and export problems are common, as covered in [why a WordPress XML export fails](/why-wordpress-xml-export-fails). When it works, this option is the smoothest for readers, because the comments simply continue to live under the posts on the new platform. ## Option two: move to a hosted comment service The second option decouples comments from your platform entirely. A hosted comment service stores the discussion on its own infrastructure and embeds it into your pages, so the comments survive any future platform change, not just this one. This is appealing if you expect to change platforms again, or if your new platform has weak native comments. The trade off is that you depend on a third party service and embed its code, which adds an external dependency to your pages. Migrating existing WordPress comments into such a service is usually supported, so you can bring the history with you. For sites that value discussion long term, this option turns comments into something independent of where the site is built. ## Option three: preserve comments as archived content If the new platform has no comments and you do not adopt a service, you still do not have to lose the words. The third option is to preserve the existing comments as archived content, for example by keeping the original discussion as text on the page or in an appendix, so the content and its value remain even though new comments are not accepted. This is the fallback that prevents outright loss. It is less interactive, because readers can no longer add to the thread, but it keeps the unique content that the comments contributed. The point is that doing nothing is the only option that actually discards the discussion; archiving keeps it readable even when the live commenting feature does not survive. ## Why comments are worth keeping It is worth being clear eyed about value, neither overstating nor dismissing it. Genuine comments are unique content that you did not have to write, often full of the exact phrasings real people use, which adds long tail relevance to a page. They also signal engagement and add a sense of freshness as the discussion grows. None of this makes comments a primary ranking factor, and content and links remain what carry a page, as the [Ahrefs study](https://ahrefs.com/blog/search-traffic-study/) and [Backlinko analysis](https://backlinko.com/search-engine-ranking) show. But discarding years of real discussion throws away content that took time to accumulate, for no reason other than that it was inconvenient to move. Keeping it is usually the better default. ## Capture before you switch Whatever option you choose, capture the comments before the old site goes away, because once WordPress is shut down the database is gone. The safe move is to capture the visible discussion while the site is still live, so you have the content in hand regardless of which path you take. Web Almanac 2024 ([HTTP Archive](https://almanac.httparchive.org/en/2024/)) is a reminder of how much content a busy site accumulates, and active comment threads are part of that volume. WPBuildAI scans your site and returns the post content including the visible comments, so even if you have not decided between importing, a service, or archiving, the discussion is captured and not stranded on a server you are about to retire. ## Steps to keep comments through a migration 1. **Decide early** whether the new platform supports comments, or whether you will use a service. 2. **Capture the existing comments** while the old site is still live. 3. **Export the comments** mapped to their posts, with reply structure intact. 4. **Import to native comments** or migrate them into a hosted service. 5. **If neither applies, archive** the discussion as text on the page. 6. **Confirm comments appear** on the new site, or are preserved, before shutting down WordPress. ## Worked example: a discussion heavy blog changes platform Imagine a blog with hundreds of posts and lively comment threads moving to a platform with limited native comments. The team captures the visible comments first, so nothing depends on the old database surviving. They decide the new platform's comments are too basic, so they adopt an independent hosted comment service and migrate the existing WordPress comments into it, mapping each to its post. The service then embeds the threads into the new pages, so readers see the same discussion and can keep adding to it. For a handful of old posts that will not accept new comments, they archive the original threads as text so the content remains. After the move, the discussion survived the platform change because it was planned for, the same deliberate approach as a careful [WordPress migration overall](/migrate-wordpress-without-losing-seo). ## Limitation: comments depend on the destination's support It is honest to name the constraint. Whether comments can continue as live, interactive threads depends on what the new platform or a service supports, and that is not something the migration alone controls. If the destination genuinely has no comment capability and you choose not to use a service, the realistic outcome is archived discussion rather than ongoing conversation. So keeping comments is partly a platform decision made before the move, not only a data transfer done during it. Capturing the comments protects the content in every case; keeping them interactive depends on the home you give them, a trade off that fits the broader [risks of migrating to a new CMS](/what-are-the-risks-of-migrating-to-a-new-cms). ## Common mistakes - Assuming comments move automatically with the posts. - Shutting down WordPress before capturing the comment data. - Importing comments without mapping them to the correct posts. - Losing threaded reply structure during the transfer. - Discarding years of genuine discussion when archiving was an easy option. ## Key points You can usually keep your blog comments when migrating off WordPress, but you have to plan for them, because they live in the database separately from your posts and do not travel automatically. Capture the comments while the old site is live, then choose a path: export and import them into the new platform's native comments, move them to an independent hosted comment service, or, if neither applies, archive the discussion as text so the content survives. Comments add unique content, long tail relevance, and freshness, so they are worth keeping even though they are not a primary ranking factor. Map comments to their posts and preserve reply structure, and confirm they appear before shutting WordPress down. Capturing them pairs naturally with bringing the rest of your content, as in [export WordPress authors and posts](/export-wordpress-authors-posts-excel). WPBuildAI scans your site and returns the post content including the visible comments, so the discussion is captured rather than discarded when you switch. Send your web address for a free analysis. Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.