Switch without losing your history
The fear that keeps people on a comment tool they dislike is losing years of discussion. It is a reasonable fear, and it is avoidable. A comment migration is mostly a data-mapping exercise: get your comments out of the old system, line them up against the right page URLs, load them into the new one, and confirm nothing broke. Done in order, it is straightforward. This checklist walks the whole path.
Before you start: take stock
- Confirm you can export from your current system. If you cannot get your comments out as a file, that is itself a reason to leave, and you may need to export via whatever route the tool offers before anything else.
- Note how your pages are addressed. Comment threads are keyed to a page URL, so you need to know your canonical URLs and whether any have changed over time.
- Decide whether URLs are staying the same. If you are also changing your site structure, do that separately or plan the redirects carefully. Migrating comments and moving URLs at once multiplies the ways things can go wrong.
Step one: export your existing comments
Export your archive from the current system. Disqus, native WordPress, and most established tools produce an export file. Keep the original file untouched as a backup. Gabden can import existing comments from Disqus, native WordPress, and other systems, so an export from any of those is a supported starting point.
Step two: map comments to page URLs
This is the step that protects both your threads and your SEO. Every comment needs to land on the correct page, and pages are matched by their canonical URL. Check that the URLs in your export match the canonical URLs on your live site. Watch for the usual mismatches: trailing slashes, http versus https, www versus non-www, and old paths from a previous site structure. Gabden maps imported comments to each page's URL, so getting these keys right is what makes the threads reappear in the right place.
Step three: import into the new system
Run the import. Start with a subset if you can, verify it, then do the full load. After importing, spot-check a range of pages: a high-traffic post, an old post, and a post whose URL you were unsure about. Confirm the comment counts and the threading look right.
Step four: install the new embed
Add the new comment widget to your templates. With Gabden this is one script tag keyed to the page's canonical URL:
<div id='gabden-conversations'></div>
<script async src='https://YOUR-SITE.gabden.com/conversations.js'
data-page='canonical'
data-theme='auto'></script>You copy your site's Gabden subdomain from the dashboard. Place the embed where the old comment section was in your template so imported threads show up under the right content.
Step five: verify before you remove the old tool
- Load several pages and confirm the imported comments appear on the correct URLs.
- Post a test comment and check that moderation behaves as you set it.
- Check page speed. A lighter embed, around 10KB, should not regress your Core Web Vitals; if anything it should help.
- Confirm nothing about the URL change broke internal links or canonical tags.
Only after this passes should you remove the old comment script. Running both briefly is fine; removing the old one before verifying is not.
Step six: clean up
Delete the old widget's script and any leftover markup so you are not shipping two comment systems. Keep your export backup. If your new system lets you export as JSON or CSV, do a fresh export from it once the dust settles, so you always have a current copy of your own data.
Protecting SEO through the move
The SEO risk in a comment migration is almost entirely about URLs. As long as your canonical URLs stay stable and comments map to them correctly, the user content that search engines already indexed stays in place. If URLs must change, set up redirects and update canonical tags so the value follows. Our post on comment growth patterns covers what to do once the migration is done and you want the section active again. When you are ready to import, you can create an account and the docs cover the import flow in detail.
Join the discussion