“Should we use Discourse or a real forum?” is a category mistake that still wastes a year. Discourse is forum software. It is not phpBB with a new coat of paint, and it is not trying to be. Traditional forums — phpBB, vBulletin, the XenForo-shaped tree, the MyBB board you can still find on a $5 host — assume a directory of rooms. Discourse assumes a stream of topics plus tags, with trust levels instead of a hand-built usergroup ladder. The 2026 choice is which category of product matches how your people already find a conversation.
This is not the XenForo versus Discourse feature matrix. That article is a row-by-row of nodes, widgets, add-ons, license-plus-VPS, and official importers. This one treats XenForo as a member of the traditional forum family when the question is “tree versus stream,” and it treats phpBB and vBulletin as the same family even when their code is older. It is also not the beginner’s first week and not the opinionated XenForo ops close. If you already know you need a 40-child Xbox tree and a credits shop, you can stop after the first two sections and stay traditional. If you are starting a public discussion site in 2026 and you do not have that tree, keep going.
What “traditional forum” means here
Traditional is a shape, not an insult.
A traditional forum expects:
- A board index: categories as headings, forums as rooms, last-post columns, subforum lists.
- A thread that belongs to one room. Moving it is a moderation event.
- Usergroups staff invent (Registered, VIP, Banned, Xbox EU, Donators). Permissions hang off groups and forums.
- A new-user who can usually post as soon as they confirm an email, unless staff built a sandbox.
- Customization as styles, templates, and a plugin culture that grew up around PHP.
- Hosting as “PHP and MySQL on a VPS or cPanel.” You already have a hundred of these.
phpBB is the open-source default of that shape. vBulletin is the commercial default a lot of big 2000s communities never left. XenForo is the maintained, modern implementation of that shape — friendlier URLs, widgets, a real permission analyzer — but it is still a tree of nodes. MyBB and older IPS forum-only setups sit in the same category when they are used as board indexes.
If your members say “I’ll post it in Help Desk → Billing,” they are traditional navigators. The software that greets them with a list of rooms is speaking their language.
What Discourse means here
Discourse expects:
- A homepage of Latest topics (also Top, New, Unread). Meta’s new-user guide: the homepage “shows all Latest conversations” and you filter by category, tag, or activity.
- A topic (their word for a thread) that lives in one category and can wear many tags.
- A category as “the primary way of organizing topics… similar to forums on other sites” — similar, not identical. Deep nesting is not the culture.
- A tag as “a marker used to describe a topic.” Multiple tags per topic. Users may be allowed to create tags; you can also lock that down with tag groups and per-category required tags.
- Trust levels that sandbox new accounts and promote readers automatically. TL3 is a 100-day rolling window. TL4 is staff-only.
- Customization as themes, theme components (front end), and plugins (Ruby, server-side).
- Hosting as official Docker on Linux (2 GB RAM recommended) or official Discourse hosted plans.
If your members say “I’ll search” or “I’ll follow the tag,” they are Discourse-shaped already — even if they are doing it today inside phpBB’s search box and ignoring your 60 forums.
1. Navigation: trees versus topics and tags
This is the product difference. Everything else is support.
The tree
Traditional software makes place the primary key. Help is a room. Billing is a child of Help. EU Billing is a child of Billing if someone got enthusiastic in 2014. The index is a map. Power users memorize it. New users bounce off it. Staff solve confusion by adding another child board, which makes the map worse.
That pattern is not stupid. It matches organizations that really are trees: game factions, regional chapters, product lines with legal walls, staff-only children, archive boards you cannot delete because of permalinks. Traditional software is still the right category when the room is the product.
The stream
Discourse makes recency the primary key and category + tags the filter. You land on Latest. You subscribe to a category. You watch a tag. A topic about a billing outage in EU sits in Support (or Billing) and wears eu and outage. You do not need Support → EU → Outages as three nested rooms.
Meta culture, repeated whenever a phpBB migrant arrives with 200 boards: collapse to a handful of categories, push the tail into tags, require a tag if you must. Category settings exist for “minimum number of tags” and for restricting which tag groups apply. That is the intended replacement for the child-board maze.
| Need | Traditional tree | Discourse stream |
|---|---|---|
| “Where do I post?” | Pick a room on the index | Pick a category, then tags |
| “Where do I read?” | Open my usual room | Latest / watched / tag |
| Cross-cutting topic | Duplicate thread or off-topic | One topic, extra tags |
| 40 micro-rooms | Easy to create, hard to use | A smell; use tags |
| Deep private hierarchy | Natural (forums + groups) | Possible via groups + categories, not a 12-level tree |
| Feeling of “a forum” | Immediate | Feels like a modern discussion site |
A migration that copies every phpBB forum to a Discourse category is how you get a Discourse that members describe as “confusing and empty.” You did not change category. You changed the CSS.
Worked map: 40 phpBB forums, one afternoon
A typical neglected phpBB or vBulletin tree looks like this (compressed):
- News, Introductions
- General, Off-topic, Memes
- Game → PC → EU / NA / Suggestions / Bugs
- Game → Console → same children
- Support → Billing / Technical / Chargebacks / “Read this first”
- Staff, Moderator lounge, Archive 2014, Archive 2016, Archive 2019
- Classifieds, Reviews, Media
A Discourse-shaped map of the same community is not 40 categories. It is closer to:
| Discourse category | What happened to the old rooms |
|---|---|
| Announcements | News, “Read this first” (staff-create) |
| General | General, Introductions, Off-topic (tag off-topic if you must) |
| Play | Game PC/Console rooms → tags pc, console, eu, na |
| Support | Billing / Technical / Chargebacks → tags billing, technical, chargeback |
| Meta | Site talk |
| Staff (private) | Staff + moderator lounge |
| Do not migrate as live rooms | Memes (or a tag), classifieds (or stay traditional), archives (read-only category or leave on the old domain) |
If classifieds, a server list, or an application board is load-bearing, that row is a veto: stay traditional (usually XenForo). Tags will not give you a directory. If the archives are the only reason you still pay for the old host, export them and stop pretending they are a community.
Do this mapping on paper with two veteran moderators before you mention a cutover date. If they cannot agree which of the 40 rooms is a tag, you are not migrating this quarter. You are arguing about the sitemap, which is the actual work.
2. People: usergroups versus trust levels
Traditional forums treat access as something staff design. You create groups. You assign them. You maybe run a promotion that says “100 posts → Veteran.” phpBB and vBulletin veterans know this in their sleep. XenForo’s version is the most complete: default groups you cannot remove, Never > Yes > No, Analyze permissions, hourly promotions for recently-active users. Still: you drew the ladder.
Discourse treats the first four rungs as something the software runs. Meta’s 2026 trust-level reference is the current explanation:
- TL0 New — default for new users. Sandboxed so they cannot accidentally hurt themselves or others (the original Jeff Atwood framing, still the product idea).
- TL1 Basic — automatic from reading (5 topics, 30 posts, 10 minutes by default). Invited users often start here. Permanent once earned.
- TL2 Member — automatic from sustained participation (visits, replies in different topics, a like given and received, more reading). Permanent once earned.
- TL3 Regular — automatic from a 100-day rolling window. Can be lost. Daily job. Designed so regulars, not just post-counters, get extra tools.
- TL4 Leader — manual, staff only. Not a grind.
Discourse still has groups, and categories can be limited to groups. That is how you build “staff,” “customers,” “beta.” Groups can also grant a minimum trust level. What you should not do is recreate Veteran I–IV as groups because that is how phpBB felt. You would be fighting the automation and confusing members who already see a trust-level name on the profile.
Traditional sandboxing is optional and usually forgotten. That is why classic forums leak spam into the first three boards until someone installs a plugin. Discourse’s sandbox is on by default. That single category difference — new users are limited until they read — is why a lot of public 2026 communities pick Discourse without ever caring about tags.
Traditional paid / VIP / faction access is still easier to reason about on a tree with forum permissions. If your community is a map of private rooms, trust levels will not replace the map. They will sit beside a group design you still have to do.
3. Defaults: what you get before you hire a designer
Traditional forums, out of the box, often still look like 2008 until you buy a style. phpBB’s stock index is honest and dated. vBulletin’s depends on the era you are stuck on. XenForo’s stock is the best of the family — responsive, 2.3 light/dark variations, widgets — but the mental model is still the index.
Discourse’s stock is a mobile-first topic list, infinite scroll / timeline, a composer that drafts while you keep reading, quoting by selecting text, @ mentions, oneboxes (link previews), Markdown plus a rich editor, notification levels per topic / category / tag, and a PWA-shaped install. Meta’s new-user guide is basically “you already know how to use this if you have used a modern web app.” That is the pitch, and for greenfield communities it is true.
It is also why traditional members complain. They want the last-post column, the subforum list, the “mark forum read” muscle memory, the feeling that a quiet board is empty in its room rather than missing from Latest. Those are not stupid complaints. They are category loyalty.
If you need the traditional index for political reasons (the veterans will leave), stay traditional — preferably on a maintained product in that family, not on an abandoned vBulletin you cannot patch. If you need the modern defaults because your new members bounce off phpBB in five seconds, Discourse is the category that optimized for them.
4. Moderation and the “civilized discussion” bet
Discourse’s original marketing line was civilized discussion. The mechanism is not a pinkie promise. It is:
- TL0 limits (new-user media, link, and messaging limits — adjustable in site settings; do not invent numbers here, look at Trust Level Permissions Reference on Meta).
- Flags that scale into TL3 consensus tools (multiple TL3 flags on a TL0 post can auto-silence — Meta’s “sufficient diversity” means more than one regular).
- Edit windows, hide-until-reviewed patterns, and a culture of rewriting the original post instead of a 400-reply derailment. Staff can move posts and merge topics; the UI expects it.
- A daily TL3 job that can demote people who stopped being regulars or who got suspended.
Traditional moderation is staff tools plus groups. XenForo’s warning system, report queue, and moderator permissions are mature; we already wrote that guide. phpBB and vBulletin can be fine with a disciplined team and miserable without one. Nothing automatic promotes a phpBB user into a junior moderator because they read 25% of last quarter’s topics.
Pick Discourse if you want regulars to absorb a slice of moderation and you accept that a quiet month can take TL3 away. Pick traditional if moderation must stay a named staff group with a documented hierarchy — especially around private data, bans, and legal holds.
5. Email, accounts, and “it works on a phone”
Traditional forums can do email. Many do it badly: PHP mail() on a residential VPS, no bounce handling, members who never confirm. XenForo at least documents transports (PHP built-in mail preferred, SMTP, Google OAuth) and bounce addresses. phpBB’s email is whatever you configured in 2011.
Discourse treats email as part of the product (digests, mailing-list mode, reply-by-email if you set it up). The official Docker installer in 2026 will let you skip SMTP and use Discourse ID login (email via id.discourse.com plus Google / Facebook / Apple / GitHub). That is a modern-default choice: get the forum up, add mail later. Traditional PHP forums almost never ship a first-party identity provider like that.
Mobile is no longer a Discourse exclusive — XenForo is responsive, phpBB can be — but Discourse was designed as a single-column reader with a timeline. Traditional styles that still assume a wide index plus a sidebar feel like a desktop app in a phone browser. If “works on a phone” is the actual complaint you are hearing, you might need a better traditional style, not a category change. If the complaint is “this still feels like a bulletin board,” you are in category territory.
6. Cost and who owns the box
Traditional PHP forums are cheap to host. phpBB is free software on a small VPS or on shared hosting that still offers PHP and MySQL. vBulletin is a license plus the same stack, often on a box that has not been rebuilt since the last successful upgrade. XenForo is a license plus a modest VPS. This category wins on “I already know cPanel.”
Discourse is free software with a heavier default self-host (official recommended 2 GB+ RAM, Docker, PostgreSQL, Redis, Rails) or a monthly hosted bill (discourse.org: Free / Pro / Business / Enterprise in 2026; Pro has been listed around $100/month). You are paying for not owning PHP, or you are paying in RAM and Docker skill.
There is a third traditional cost people hide: abandonware. An unmaintained vBulletin or a phpBB that cannot get a clean upgrade is not cheap. It is a security incident with a board index. Moving within the traditional category (phpBB/vBulletin → XenForo, official importer lists those sources) is often the rational 2026 move when you like trees but not the old code. Moving out of the category is a different project.
| Traditional (phpBB / vB / XF-shaped) | Discourse | |
|---|---|---|
| Software price | Free or a license | Free, or hosted monthly |
| Small host | PHP + MySQL, often tiny | Docker 2 GB+, or hosted |
| Who patches | You, or “nobody since 2018” | You + ./launcher rebuild, or Discourse |
| Abandoned-fork risk | High on old vB / neglected phpBB | Lower if you stay on official install / hosted |
7. Migration is a product change, not an upgrade
Switching phpBB 3.3 to XenForo 2.3 is an implementation change inside the traditional category. Official XenForo importers list phpBB 3.2–3.3, vBulletin 3.6–5.3, MyBB 1.8, SMF 2.0, IPS 4.x, Discourse 3.x. Members still have rooms. Staff still have groups. You will spend time on redirects and prefixes, not on explaining why the index is gone.
Switching phpBB or vBulletin or XenForo to Discourse is a category change. Meta has migration guides and community scripts; it is not a XenForo-style “Tools → Import data” button in the other direction. Even when the posts arrive, the IA will be wrong if you 1:1 the tree. Budget:
- A category/tag design workshop before the import.
- Redirects for every old
viewtopic.php//threads/URL you care about. - A veteran-moderator program so the people who knew the old rooms become the people who know the new tags.
- A period where Latest looks empty because you imported archives that nobody is bumping.
If you are not willing to redesign the map, you are not willing to change category. Stay traditional and modernize inside the family.
Three traditional-family moves that are not Discourse
- phpBB 3.2–3.3 → XenForo. Official importer lists the source. You keep rooms. You gain a maintained ACP, widgets, Analyze permissions. This is the default 2026 modernization if the tree is still loved.
- vBulletin 3.6–5.3 → XenForo. Same importer family, plus XenForo’s dedicated vBulletin redirect product when you need 301s from the old
showthreadworld. You are escaping abandonware, not the index. - Stay on XenForo and flatten. Archive ghost boards, stop adding a child for every mood, turn on friendly URLs. No import. This is the right move when the engine is already XF and the complaint is the maze.
Only after you have rejected those three should Discourse be in the room. A lot of “we need Discourse” tickets die on move 3.
8. When traditional is still the right category in 2026
Stay in (or move into) the traditional family when most of these are true:
- Members navigate by room, and the rooms match a real org chart or game world.
- You need deep private trees (staff children, application boards, region lockouts) more than you need Latest.
- Load-bearing features are forum-shaped add-ons: server lists, whitelist apps, credits, faction tools. Those live in the XenForo/IPS plugin cultures, not in Discourse’s default set.
- Staff already think in usergroups and board permissions, and you are not hiring a new team.
- The budget is a PHP VPS, not a Docker box or a $100/month hosted plan.
- You are escaping phpBB/vBulletin code, not the idea of a forum index. XenForo exists for that sentence.
Traditional is not “legacy.” It is the correct UI for a directory of communities.
9. When Discourse is the better category in 2026
Pick Discourse when most of these are true:
- You are starting greenfield, or the old tree is already ignored.
- New-user spam and cluelessness are the daily pain, and you want a sandbox that is on by default.
- The homepage should be what is happening, not a map of rooms.
- Tags are how you think about the work (versions, regions, statuses) and you do not want a board per combination.
- You want official hosted so community is not also a PHP job, or you already operate Docker comfortably.
- You want regulars (TL3) to take a slice of moderation without inventing a “Trusted” usergroup by hand.
- You do not need a gaming-economy plugin stack.
Discourse is not “forums are dead.” It is “the default forum of 2005 is the wrong default for this community.”
10. A decision you can explain to veterans
Veterans hear “we’re moving to Discourse” as “you are deleting my board.” They are not wrong if you planned a 1:1 import and a speech about modernity. Explain the category, not the brand.
Script that stays traditional: “The rooms stay. We are changing the engine under them so we can patch the site. Your Billing forum will still be Billing. URLs will redirect.”
Script that changes category: “We are going to fewer rooms and more tags. Billing becomes a category or a tag, not a third-level board. New accounts will read before they can do everything. Latest is the front door. I need three of you to own the tag list with me.”
If you cannot deliver the second speech without mumbling, you are not ready to leave the category. If you deliver the first speech and then install Discourse, you lied.
Use a two-week empty pilot. Traditional staff who light up when they see Latest and mute notifications per tag are convertible. Staff who keep asking where the last-post column went will make the launch a referendum. Listen to them. Sometimes they are the community.
A one-page checklist
Print this. Tick in ink.
Shape
- Members find threads by opening a named room, not by Latest or search
- We have private children that are really walls, not decorations
- We have a listing, shop, or application that is not “just a category”
- Veterans will treat “the index is gone” as a broken promise
If three of those four are ticked, you are traditional. Modernize inside the family.
Stream
- The current tree is already ignored
- Spam and clueless first posts are the daily fire
- Tags describe the work better than child boards
- We will pay hosted or we already run Docker
- We can give the “fewer rooms, more tags” speech without mumbling
If three of those five are ticked, Discourse is the category. Do not 1:1 the old forums.
Process
- We named the destination product, not just “away from phpBB”
- We mapped rooms to categories/tags (or decided to keep rooms)
- We counted permalinks we must 301
- We have a two-week empty pilot on the calendar
- Someone owns the freeze weekend
If process is empty, you are blogging, not migrating.
What this article will not do
It will not score phpBB against XenForo. Those are two traditional products; XenForo is the maintained one for most people who still want the shape. It will not reprint the XF/Discourse widget-versus-plugin matrix. It will not walk Docker install — that is the beginner guide. It will not tell you traditional forums are dying. Plenty of 2026 communities still are a directory of rooms. They should look like one.
Takeaways
- Discourse versus “a real forum” is a category choice: stream + tags + trust levels versus tree + usergroups + board index.
- phpBB, vBulletin, and XenForo sit in the traditional family when the question is navigation. XenForo is the modern engine inside that family.
- Deep rooms, private children, and gaming add-on stacks stay traditional. Greenfield public discussion, default sandboxes, and tag-shaped work go Discourse.
- Defaults differ on purpose. Discourse feels like a modern app; traditional feels like a map of rooms. Neither feeling is a moral victory.
- Hosting follows the category: cheap PHP versus Docker-or-hosted.
- Changing engine inside the family is an import. Changing category is a product redesign. Do not pretend they are the same Saturday.
- If your members already ignore the tree, you may already be Discourse-shaped. If they live in a specific room, they are not.
Choose the category that matches the map in your members’ heads. Then pick a maintained product inside it. Everything else is a reskin.