← All journeys

Migration · Migration space · for Site owner / WordPress admin

The bbPress migration journey: from 2009 forum to a modern community

One-click importers move your topics, replies, users, and metadata. Members keep their post history. The forum stops looking like 2009.

What you’re building

A safe path from a legacy forum plugin (bbPress, wpForo, or Asgaros) to Jetonomy. Your existing topics, replies, and users move over with their post counts and timestamps intact. Members keep their reputation. The URL structure can be preserved with a redirect map so search rankings don’t disappear.

The why: bbPress is unmaintained, wpForo’s UX feels dated, Asgaros works but doesn’t scale past a few thousand topics. All three store data in wp_posts, which means more topics = slower main site. Jetonomy uses custom tables — the forum scales independently from the rest of the site.

The site-owner journey

What you do, end to end, to migrate a 5,000-topic forum:

  1. Pre-flight (1 hour). Full database backup. Note your current forum URL structure (/forums/topic/{slug} or whatever pattern). Document your current trust / moderation rules so you can mirror them.
  2. Install Jetonomy in parallel. Don’t disable the old forum yet. Jetonomy installs cleanly alongside bbPress / wpForo / Asgaros.
  3. Configure the new structure. Create your categories + spaces. Decide which old forum maps to which new space. (Often 1:1, but migration is a good time to consolidate.)
  4. Run the importer. From admin → Jetonomy → Tools → Import → pick your source plugin. The importer handles topics, replies, users, attachments, and basic categories. For a 5,000-topic forum, expect 5-15 minutes.
  5. Review the import report. Lists what came over, what was skipped, any conflicts. Skipped items are usually deleted users or orphaned replies — review and either accept or manually fix.
  6. Test on a private URL first. Don’t expose the new forum publicly yet. Click around, post a test topic, verify the import looks right.
  7. Set up redirects. The old /forums/topic/{slug} URLs need to redirect to the new Jetonomy URLs to preserve SEO. The importer generates a redirect map you load into a redirect plugin (or your Cloudflare / Nginx rules).
  8. Cutover. Disable the old forum plugin. Publish the new Jetonomy forum at the old URL prefix. Verify redirects work.
  9. Communicate to members. Post an announcement explaining the move and what’s new. Most members notice “wow, it’s faster” within a day.

The member journey (what they notice)

Members see one big change and several small ones:

  • Big: the forum looks modern, loads fast, works on mobile (most legacy forum plugins don’t).
  • Small: their post count is the same. Their old replies are still there. Their reputation didn’t reset.
  • Small: the compose button is in a slightly different place. The reply box is inline instead of below.
  • Small: they can finally upvote helpful posts (legacy forum plugins don’t have voting).
  • (Pro): they can react to posts with emoji.

Most members don’t comment on the change at all. They just keep using the forum. That’s the success metric.

What the importers handle (and what they don’t)

Handled by the bbPress / wpForo / Asgaros importers:

  • Topics with author + timestamp + content
  • Replies + nested thread structure
  • Users (linked by user_id)
  • Categories / forums → mapped to Jetonomy spaces
  • Tags (where the source supports them)
  • Attached images (uploaded to wp-content/uploads stay accessible)
  • Subscription / favorite relationships (where applicable)

Manual or partial migration:

  • Custom roles / capabilities — review against Jetonomy trust levels and re-create
  • Add-on plugin data (bbPress Voting, wpForo Polls, etc.) — usually requires a custom mapping
  • Email subscriptions per topic — easier to ask members to re-subscribe after launch
  • Custom CSS / theme integration — Jetonomy uses CSS custom properties, redo the styling

Run the importer on a staging copy first to see exactly what comes through. The import report is detailed enough to plan the manual cleanup before you cutover production.

Redirect strategy (don’t skip this)

Search rankings depend on URL stability. If you change forum URLs without redirects, you lose months of SEO equity.

The importer generates a CSV mapping old URLs to new ones. Load it into:

  • Cloudflare Workers (best for performance)
  • An Nginx rewrite map (if you control the server)
  • A WordPress redirect plugin like Redirection (easiest, slightly slower per-hit)

Test 20 random old URLs after redirect setup. Verify they 301 to the right Jetonomy URLs and the new pages load correctly.

What changes after migration

  • Page load times drop significantly (custom tables vs wp_posts queries)
  • Mobile experience finally works
  • Members start using voting / accepted answers / tags they never had before
  • Your moderation queue is one place instead of three (forum admin + spam plugin + ticket system)
  • The forum can scale to 50,000+ topics without slowing the main site

Common questions

Will my member URLs change? Usernames stay the same. Member profile URLs may change format — generate redirects from the importer report.

What about old SEO equity? Preserved if you set up the 301 redirects from the importer’s CSV. Google re-crawls and updates rankings within weeks.

Can I run both plugins in parallel? Yes during migration testing. Don’t do it long-term — members get confused which forum to post in.

How long does the full migration take on a real site? 5,000 topics = 1-2 hours including testing + redirect setup. 50,000 topics = a full day with staging tests + careful cutover. Plan accordingly.

Try it

Spin up the demo. The demo doesn’t come pre-loaded with bbPress, but the import tools are visible in admin → Jetonomy → Tools → Import. Read the importer docs at the store docs for the full walkthrough.