How to migrate from bbPress without losing data

Sofia Romano Sofia Romano 2 months ago Resolved

Reference guide. The bbPress importer preserves original dates, maps forums to spaces and forum categories to Jetonomy categories, and supports a dry run.

  1. Back up your database.
  2. Run wp jetonomy import bbpress --dry-run to preview.
  3. Run the import; it batches large datasets to avoid timeouts.
5

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

Strong agree. Good defaults beat a wall of toggles every single time.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

One caveat for larger communities: keep an eye on the indexes. At a few thousand rows the difference is night and day.

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

One caveat for larger communities: keep an eye on the indexes. At a few thousand rows the difference is night and day.

Following this thread closely. We are about to face the exact same decision and the replies here are gold.

For what it is worth, the same approach works with the PMPro adapter — the membership side is identical from here.

We ran into the same situation last quarter. What worked for us was starting small and only adding complexity when a real need showed up.

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

Following this thread closely. We are about to face the exact same decision and the replies here are gold.

Strong agree. Good defaults beat a wall of toggles every single time.

This is the answer I wish I had found six months ago. Would have saved me a weekend of trial and error.

This is expected behavior, not a bug. The guard you are hitting is intentional — it protects against a class of mistakes that used to cause data loss.

If you need the other behavior, there is a documented filter you can hook to override it per site.

This is the answer I wish I had found six months ago. Would have saved me a weekend of trial and error.

Great point. I had not considered the angle you raised in the second paragraph — it reframes the whole thing for me.

Appreciate the clear steps. The dry-run tip in particular saved me from a mistake I would not have caught otherwise.

Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.

Great point. I had not considered the angle you raised in the second paragraph — it reframes the whole thing for me.

Strong agree. Good defaults beat a wall of toggles every single time.

Tried this on a staging copy first and it behaved exactly as described. Confident enough to roll it to production now.

I respectfully disagree on one detail. In my setup the opposite held true, though I suspect it comes down to community size.

Could you say more about how you measured the result? I want to try this but I am not sure what success would look like.

Thanks for writing this up. Bookmarking it — the kind of thing I will want to reference again in a month.

Solid breakdown. The only thing I would add is to back up before making the change — better safe than sorry.