phpBB is standalone forum software; bbPress is a forum plugin built to run inside WordPress. If you’re moving a board from phpBB into bbPress, you’re not doing a like-for-like swap — you’re moving from a full-featured, independent forum system into a lightweight plugin that inherits WordPress’s user accounts, themes and permissions. Some things map cleanly. Others don’t exist in bbPress at all.
What phpBB is for, and why people move away from it
phpBB is a self-contained forum application with its own user database, permissions system, themes (styles), and a large library of extensions and mods. It runs on its own, separate from any CMS. People move it into bbPress usually because they already run a WordPress site and want the forum to share the same login, the same theme, and the same admin dashboard, rather than maintaining two separate systems.
That convenience comes at a cost. bbPress is deliberately minimal. It handles forums, topics and replies, and not much else out of the box. Anything phpBB does beyond that — private messaging, ranks, warnings, polls, rich BBCode, attachments — either needs a separate plugin or doesn’t have a direct equivalent.
What maps and what doesn’t
| phpBB feature | bbPress equivalent |
|---|---|
| Forums and sub-forums | Forums (bbPress supports parent/child forums) |
| Topics | Topics |
| Posts | Replies |
| User accounts | WordPress users (roles map to bbPress forum roles) |
| Moderator groups | bbPress moderator role, applied manually |
| Private messaging | No native equivalent — needs a separate plugin |
| Polls | No native equivalent |
| Attachments | Not built in — needs a plugin, and content usually has to be re-attached manually |
| Ranks, warnings, points | Not built in |
| BBCode | Not supported — bbPress uses plain text/HTML, so BBCode tags in old posts show up as literal text unless converted |
| Custom styles (prosilver, etc.) | No theme system of its own — bbPress inherits the active WordPress theme |
The core content — forums, topics, replies, and the relationships between them — transfers reasonably well because both systems store the same basic tree structure. Everything sitting around that content is where the work is.
Practical points before you start
- Decide what to do with BBCode in old posts. Left as-is, tags like
[b]or[quote]will display literally in bbPress. You either need to strip them, convert them to HTML, or accept the mess in the archive. - Attachments and avatars stored by phpBB in its own file structure won’t move automatically. Files need to be copied into WordPress’s media handling separately from the database import.
- User accounts need matching. If the same person has an account on both the WordPress site and the phpBB board, decide whether to merge by email or username before import, or you’ll end up with duplicates.
- Private messages have no home in bbPress. If members rely on them, budget time to pick and configure a separate messaging plugin, or tell users in advance that message history won’t carry over.
- Test permissions after import. bbPress roles (Keymaster, Moderator, Participant, Spectator, Blocked) don’t map one-to-one with phpBB’s group and permission system, so access levels usually need re-checking forum by forum.
Is bbPress the right fit
If the phpBB board is large, heavily customised with mods, or depends on private messaging, ranks, or rich formatting, bbPress will feel like a step down in functionality. It’s built for lighter community discussion bolted onto an existing WordPress site, not as a drop-in replacement for a mature standalone forum. If keeping the full phpBB feature set matters more than integration with WordPress, it’s worth checking whether phpBB should stay as-is rather than move at all.
For a broader view of which platforms are commonly involved in this kind of move, see the the platform index.