FeverBee – Community Consultancy

Khoros in 2026: An Honest Review (And Why I’d Leave)

Richard Millington — Wed, 01 Jul 2026 13:48:30 +0000

Khoros is the platform I get asked about more than any other, and the one that has caused the most upheaval in our space over the last few years. So let me give you an honest review of where it stands in 2026, and whether you should stay or go.

This one is different from every other platform I review. The product is strong. In some areas it is still the best on the market. And I would still tell most teams on it to leave as soon as they reasonably can.

One thing you should know going in: Khoros has sent me legal threats over my past commentary about them. So I am going to be careful, frame this as my opinion, and stick to what I can stand behind. Two things are true at once. The product is good, and I would leave. The gap between those two things is the whole story.

How Khoros got here

For most of the last fifteen years, Khoros was the premium community platform in our space. If you were a big brand running a big support community, you were probably on Khoros, or on Lithium before it. It earned that. The feature set was deep, and it ran at a scale almost nobody else could touch. A lot of us still carry that version of Khoros around in our heads.

The product still deserves a fair amount of that respect. The company around it, in my view, no longer does.

Khoros came out of Lithium, one of the original enterprise community platforms, which merged with Spredfast in 2019 and rebranded as Khoros. In my experience, that merger started a rough stretch. The attention drifted toward social media management, the community product did not move forward the way it should have, and the cost and service charges came up again and again as a real source of frustration. Then in May 2025, Khoros was acquired by IgniteTech. That is the moment everything else here hangs on.

What Khoros still does well

Before the rest, the product deserves its due, because the scorecard is genuinely good. On discussions and Q&A it scores an 8: deep threaded forums, a proper question-and-answer format with accepted answers, and strong enterprise admin tools. Moderation is an 8, with a mature suite, AI models for spam and abuse, and support for dozens of languages. Analytics is an 8, with deep Adobe and Google Analytics integration. Gamification, ideation, and content all sit at 7. The one real hole is events, which I score a 1.

Two things stand out. The first is scale. Khoros has run some of the largest brand communities on the planet, with enormous traffic, deep permissioning, and complex multi-board structures, for years and reliably. The second is gamification and reputation. Lithium, and then Khoros, with Michael Wu, Joe Cothrel and the team, wrote the playbook for it. A lot of platforms are still copying the model.

So none of what follows is that the product is bad. On its own terms, it is strong. The problem is that you do not buy a community platform on its own terms.

You are not buying a product, you are buying a company

You buy the company behind the platform, and you commit to it for three to five years. Over that window you are not betting on the feature list, you are betting on the vendor: will they support you, keep the lights on, invest in the product, and treat you fairly when something goes wrong. That is where, in my opinion, Khoros has become a bad bet.

Khoros is owned by IgniteTech, part of ESW Capital, which has bought well over a hundred software companies. As best I can tell, the model is consistent: acquire enterprise software with customers locked into longer contracts, cut costs hard, and run it for cash. This is not only my read. IgniteTech’s own CEO has spoken about laying off close to 80% of the company after staff resisted an AI-first mandate.

Within weeks of the acquisition, almost the entire Khoros team was let go. That matters, because the feature set I just praised was built and maintained by people, and much of the work is now done by contractors with far less knowledge of community or the clients. In my experience, that kind of gap shows up slowly, then all at once, usually at the worst possible moment.

All-in on AI, and the Aurora question

What has replaced those people, in the messaging at least, is AI. In April 2026, Khoros launched Aurora AI, described not as an upgrade but as a brand-new, AI-native platform, with a suite of tools the parent company rolls out across its acquisitions. I am not anti-AI; we do a lot of work helping clients get AI ready. The open question is whether this is AI that helps a team do more, or AI positioned to replace the team. Judge it on what it actually does in your community, not on the launch copy.

If you are a current customer, pay close attention here. You are probably on the older platform, Khoros Communities Classic. Khoros is offering free migrations from Classic to Aurora through the end of 2026. Aurora may turn out to be good, but it is a relatively new platform, it does not have anywhere near the feature set of Classic, and any migration is a real risk. As far as I can tell, there is no published end-of-life date for Classic. You would be migrating either way, so if you are going to take on the cost and risk, at least look at what else is out there before defaulting to Aurora.

What customers are telling me

I get messages almost every week from Khoros customers describing real pain, and most of the ones I have spoken to are actively planning to leave. The first theme is support: account managers and commercial teams going quiet for weeks, issues left unanswered, and how hard it is to get anyone on the phone. The second is reliability: outages and platform issues, with some clients left running their own analysis to work out what went wrong. I cannot independently verify every incident, so take it as what customers report, but I am hearing it from enough of them that, in my opinion, it is a trend rather than bad luck.

Then there is getting your data out. From what I have heard, a full, usable export of your content, members, and structure can be more of a fight than it should be, and some customers say they have been charged for additional exports. And there are the invoices: large, unexpected overage bills, sometimes into the hundreds of thousands of dollars. It has become a common story that bot traffic has surged on a community and the customer is then charged for it, with customers telling me they believe much of that billed traffic is bots and automated crawlers, not the human visitors their contracts were written around.

The verdict: should you stay on Khoros?

This is why I score platforms on nine capabilities but tell you to weigh a tenth thing that is not on the sheet: the vendor. Khoros still scores like a top-tier platform, and on product it nearly is. But the scorecard measures what the software can do, not whether the company behind it will still be supporting you fairly in three years. On that question, in my opinion, Khoros is now one of the riskiest choices in the market.

My answer is no. If you are on Khoros today, start planning your exit now, not in a panic, but deliberately. The worst position to be in is deciding to leave the day a surprise invoice lands or your support stops responding, because that is when you have no room to negotiate and no time. Almost everyone I know on the platform is already looking, and many have moved.

Where to go instead

The right alternative depends on what your community is for. If product feedback or Gainsight CRM integration is the point, look at Gainsight. For a general-purpose enterprise community built around Q&A and knowledge, Higher Logic Vanilla is one of the strongest all-rounders. For a daily, social, members-hanging-out community, look at Higher Logic Thrive or Bettermode. Discourse is where a lot of Khoros communities are already migrating and is hard to beat on discussion depth. And if you are built around events or want a vendor investing heavily in AI, look at Bevy.

Map your must-have capabilities first, then test these against your list, not against a demo. If you do move, do it properly: get your data out early, and test that you can export your content, members, and the SEO value tied to your URLs cleanly.

You can see the full nine-capability scorecard and platform comparison at feverbee.com/communityplatforms. And if you want help getting off Khoros or choosing what comes next, you will find me at feverbee.com or richard@feverbee.com.

The post Khoros in 2026: An Honest Review (And Why I’d Leave) first appeared on FeverBee - Community Consultancy.

Higher Logic Vanilla: An Honest Review

Richard Millington — Wed, 24 Jun 2026 15:55:07 +0000

Higher Logic Vanilla: An Honest Review

This is the first in a new series, Enterprise Community Platform Reviews 2026. I’m reviewing the major enterprise community platforms one at a time, using the same nine-capability scorecard each time so you can compare them like for like. First up is Higher Logic Vanilla.

Before we get into it, the context matters, because the ground has shifted under this whole decision. Choosing a platform used to be a five-year bet you could get slightly wrong and survive. That has changed, and the reason is Khoros.

Khoros was, for years, the default heavyweight for enterprise communities. Now it has faded. They wound down Khoros Care, customers are migrating off, and when your platform vendor is in trouble, your roadmap is too. At the same time, AI has raised the stakes on getting the choice right, because your platform is now feeding answers to your members and to their AI tools. Pick the wrong one and you feel it faster than you used to. So the pressure to choose well is higher than it has been in years.

That is also why Vanilla is interesting: it nearly missed its moment. Vanilla started in 2006 as forums that looked good and were easy to stand up, a small team winning enterprise logos it had no business winning. Then Higher Logic acquired it in 2021, which made sense on paper. Higher Logic was strong in associations and weak in the enterprise. Vanilla was the opposite.

Then it drifted. For a couple of years after the acquisition it felt like Higher Logic had taken its eye off the ball. When we ran our Buzz Report a couple of years ago, Vanilla was one of the platforms starting to look left behind. The product wasn’t keeping pace.

That is no longer the case. Vanilla is shipping again, and shipping the things that matter for where the market is going. That turnaround is why, for a general-purpose enterprise community, I now put Vanilla in the top two all-round platforms you can pick. Here’s the evidence, and I’ll be honest about what’s still missing.

Vanilla, not Thrive

One thing to clear up first, because it constantly confuses buyers: Higher Logic sells two community platforms, not one.

Higher Logic Vanilla is the one I’m reviewing today. It’s the B2B and B2C product, built for support, knowledge, and product feedback, with Q&A at its heart.

Higher Logic Thrive is different. Thrive started out aimed at associations and now goes after the enterprise market too. It’s a different experience: the platform you pick if you want members hanging out and chatting every day, rather than the more focused Q&A experience that defines Vanilla.

They’re also run quite separately inside the company. They don’t even share a support team, and they’re marketed and sold separately. So if a daily, social, members-hanging-out community is what you’re after, Thrive is probably your conversation, and I’ll review it on its own. Everything from here is about Vanilla.

So, should you buy Vanilla? You should if you recognise this: you’re running an enterprise B2B community for support, knowledge, and product feedback; you need deep permissioning, with different members seeing different things; you want a real path from a question to an answer to a knowledge base article; and you may need multiple brands or languages on one platform.

Look elsewhere if your community is built around events, or if most of your members live on their phones. Those are the two places Vanilla is genuinely weak, and I’ll show you the numbers rather than bury them at the end.

Discussions & Q&A

Let’s start with the core. Discussions and Q&A. I score Vanilla a very solid eight out of ten here.

The standout is the Q&A. Vanilla has the cleanest separation between an open discussion and a question that needs an answer of almost any platform I reviewed. You get accepted answers, AI-suggested answers, and a genuine route from a resolved question into a knowledge base article. If your community exists to deflect support tickets, that loop is the whole game, and Vanilla runs it well.

It also has the best Zendesk integration of the group, which matters more than it sounds if your support team lives in Zendesk. You can see this working on the Smartsheet community, which runs on Vanilla: 80% of questions there are answered by other members, only 20% by moderators. That ratio is what good Q&A design buys you.

Here’s the honest counterweight. On raw forum depth, Vanilla is a notch behind Discourse, which I’d put at a nine. Discourse has the read-position tracking, the wiki mode, the code blocks, the real-time touches. If a pure, forum-only experience is what you want, Vanilla probably isn’t the best option. But if you want that integrated support experience, Vanilla is fantastic, and for most enterprise teams this isn’t the deciding factor.

AI & the MCP

Second, and the most forward-looking one: AI. I rate it a seven for Vanilla.

At the time of writing, Vanilla is one of only four platforms with a live MCP, the Model Context Protocol. It’s a connection that lets your AI tools read and act inside your community. Vanilla’s is the only one of the four that’s free on every tier and can take member-facing actions, not just answer questions. It can send a DM, award a badge, and tag content. That’s a different category of useful.

Two honest caveats, because I haven’t been able to test it hands-on yet. It’s still in beta, and access is gated behind a beta agreement, so the rollout is phased.

When I spoke to Higher Logic’s own team about this, it’s clear they’re rebuilding around it. They’re rebuilding their moderation tooling to fill the gap enterprises felt when Khoros wound down Khoros Care. They’re adding automated demographics, so the platform can segment members by tenure, role, or activity and then act on those groups. And they’re building what they call data shipping, so enterprise customers can get all of their data out. That’s a credible roadmap. It’s also a roadmap, so judge it on what actually ships.

Other strengths

Vanilla has some other strengths worth considering.

First, customisation. You get more here than on most platforms, more than on Gainsight and others. The layout editor lets you drop in and target widgets by role without a developer. The Widget Builder goes further, syncing files to your local environment and giving an AI coding tool the guardrails and data types it needs to build a custom widget for you. The ceiling is high, though reaching it still rewards someone with design and technical skill.

Second, permissioning. Vanilla goes deep: specific roles, private areas, category-level access, beta groups, and more. If different members should see different things, this is one of the best in the market.

Third, scale. It handles multiple brands, sub-communities, and languages from one instance about as well as anything out there.

Fourth, analytics. You can build your own dashboards, filter deep by category, and pull everything out through the API, which Higher Logic’s own team will tell you is one of the strongest parts of the product. There’s an ROI calculation tool for case deflection, and analytics that flag advocates in the making and accounts drifting toward churn. The limit is manual export: getting data out by API is easy, a clean manual export less so. The MCP tackles a lot of this.

Fifth, support. Like the better platforms in this market, Vanilla has a strong support team. Customers consistently rate the people they deal with very highly, and that matters more over a multi-year contract than any single feature.

The gaps

Now the holes, the places Vanilla doesn’t score well.

The first is events. I’d score Vanilla a 3 out of 10. If your community runs on meetups, webinars, and an events calendar, this is not your platform. Bevy and Gradual are far better suited to that.

The second is mobile, also a three. The experience is desktop-first. If your members live on their phones, you’ll feel it. Mighty Networks and Hivebrite are best in class here; Vanilla is not.

Neither of these is fatal for a classic enterprise support community sitting on the desktop. But both are dealbreakers if they’re central to how your members behave. Know which you are before you sign.

Ideation

One more, smaller, thing to know about: ideation.

I don’t think ideation is as important to most companies as it used to be, but if it is for you, I score it a five out of ten. You get ideation boards with voting, but the workflow is less sophisticated than the best-in-class platforms. For a B2B SaaS community where product feedback is the point, Gainsight is well ahead here, with idea scoring weighted by account value. If your community’s main job is feeding the product roadmap, weigh that hard.

Worth flagging too: Vanilla finally offers email digests, which corrects a long-standing gap.

The verdict

Put it all together. For a general-purpose enterprise community, I think Vanilla is in the top two, probably alongside Gainsight. The specialists beat it on their one thing: Discourse on the depth and quality of discussions, Gainsight on product feedback, Bevy and Gradual on events. But across everything an enterprise community needs at once, Vanilla doesn’t have an obvious weakness, and that breadth is what most teams really need.

So is it for you? For most enterprise B2B community teams, yes. At the very least, put it on your shortlist and get to know the team, particularly if you’ve already ruled out the heavier legacy platforms and you want a vendor shipping toward the AI era rather than away from it.

Say no if events or mobile are core to your community, or if you have one overriding need that a specialist serves better and you’re willing to give up breadth to get it. The real trade-off with Vanilla has always been the same: ease of use versus customisation. It strikes a better balance between the two than almost anyone, but if you sit hard at either extreme, you’ll feel the pull.

On commercials, a couple of things to know. Vanilla is enterprise-priced and sold on multi-year contracts. I’m not going to quote a number, because what you pay depends on your size and your negotiation, and anything I put here would be out of date by the time you read it.

Honestly, I find it striking that if you’d gone back five years and said Vanilla and inSided, now Gainsight, would be the top two all-round platforms, most of us would have been surprised. But that’s how it has played out. Vanilla is exceptional at the Q&A-to-knowledge loop, strong across the middle, forward-leaning on the AI connection, and held back mainly by events and mobile, neither of which I think is a severe issue. More than any other platform right now, Vanilla has momentum, and it’s winning a lot of the major clients out there today, especially those moving off Khoros.

Before you go

Next in the series, I’ll take the same nine-capability scorecard to the next platform so you can compare them like for like.

The full scorecard behind this video is free. Download it, check it against your own shortlist, and tell me in the comments where you think I’ve got Vanilla wrong. I read them, and I change my scores when the evidence says I should.

And if you want help choosing a platform or getting a community ready for what’s coming, you can find me at feverbee.com.

The post Higher Logic Vanilla: An Honest Review first appeared on FeverBee - Community Consultancy.

Is Community a Dead-End Career?

Richard Millington — Mon, 08 Jun 2026 17:04:23 +0000

Is working in community a dead-end career?

It is one of those questions that matters to everyone working in this space, which is exactly why so much bias creeps into the answer.

What we want to be true and what is actually true can be many different things.

So I want to explore what the data actually says. We can all think of people who worked in community and then climbed to a really high level. But that runs into survivorship bias. For every person who made it, how many didn’t? How many people are stuck in the same job year after year? How many haven’t made any progress?

I will give the answer first, then explain how we got there.

Is community a dead-end career?

For many people, somewhat. For some people, absolutely not. And for a few, the answer doesn’t really matter.

Let’s go into the data.

Why This Question Is Coming Up Now

I spent some time pulling together all the CMX industry reports from the last four or five years. The picture is consistent: the community industry is contracting. I personally think we have been in a community recession for a couple of years now, and it only seems to be getting worse, especially for the B2B enterprise communities we typically work with.

Fewer people answering these surveys are working full-time on community than before. And a lot of the career advice in our space is now out of date. What we used to share from 2018 to 2022 doesn’t apply the same way today. It was written before AI changed the entry rung, before the contraction, before the big tech layoffs.

When you look at the CMX data, three trends stand out:

The number of full-time community roles is down.
Confidence in increased investment is significantly down from the post-pandemic peak.
Interest in community from other departments has dropped dramatically in recent years.

I really wish CMX still published the interest-from-other-departments number, because it is the one I find most worrying. None of these three measures point to anything positive about our space.

The Three Data Sources

For this analysis we drew on three sources.

One, the CMX industry reports. Their 2026 report is due soon and I’ll take a look at it when it lands.

Two, an 11-year cohort study. More on that in a moment.

Three, the broader labour market data: public salary numbers, layoff trackers, and what is happening at the company level for community pros.

The Community Pyramid Is Unusually Flat at the Top

The first finding is structural. If you look at community job titles, the pyramid is far flatter at the top than in most professional fields.

Roughly 21 managers for every one VP.

I need to caveat that. “Manager” means different things in community from elsewhere, so the comparison is not perfectly clean. But 21 to 1 is still a very big number. There just aren’t that many senior roles to climb into.

Where 86 Community Pros from 2015 Ended Up

The problem with all CMX survey data is that it is a snapshot. You are measuring the people who took the survey that year, not following the same people over time. Different respondents in different years, so what looks like a trend might just be sampling variation.

So we did something different. Back in 2015 we hosted an event called FeverBee Sprint, 11 years ago. We had all the attendee information: their job titles, the companies they worked for. We selected a sample from that list and tracked what happened to them.

Of the 86 we could verify on LinkedIn:

8% climbed within community to a Sr Director or VP role
1% became senior at a community-as-product company
24% are still in the same role today (this one absolutely shocked me)
41% moved laterally out of community into a different function
20% went independent or founded their own thing
6% left the field entirely

The 24% is the number that stayed with me. I will caveat it: this is based on LinkedIn, and if someone hasn’t updated their profile in years they would still be counted. But as best we can tell, those people are in the same job today as they were 11 years ago.

I would love to do this with a bigger sample. We could include all the attendees from all our events over the years. But it takes a serious amount of time and energy. Maybe at some point.

The Single Most Useful Number: Stay Versus Leave

What happens to people’s careers when they leave community compared to staying in it?

This is the most definitive metric we have for the original question.

If you stayed in community, there is a 28% chance you reached Director or VP level after 11 years. If you moved out to another function, there is a 60% chance you did. Twice as likely to climb if you leave.

You could argue that more ambitious people are also more likely to switch roles, so this is not a clean causal story. Fair point. But the difference is striking.

What we found is that community seems to be a 3 to 7 year window of doing the core work. Either you get stuck in it, or you need to leave community after that time if you want to progress.

Only 8% climb within community itself. Only 8%. Despite all the articles written about VP of Community roles, there really aren’t that many roles to climb into.

The Three Paths That Actually Work

If community is your career, three paths genuinely work.

Path One. Big Org, Manage a Team by Year Four

If you want to reach VP level, you need direct profit-line responsibility and you need to be managing a team. You won’t get there without that. Position yourself to work within a team if you want to manage a team one day. If you are solo or part of a team of two, the progression prospects are limited. We’ve written more about the strategic options for enterprise communities here.

Path Two. Work Where Community Is the Business

Some of the people doing very well are at organisations where community itself is the product or central to the business. Stack Overflow, Reddit, Discord, Discourse. Senior community roles exist there because the company depends on them.

Path Three. Consultancy, Agency, or Fractional CCO

FeverBee is one example. There are plenty of other consultants in this space. I’ll say this having watched around 100 people try to transition into consulting over the last 15 years: it isn’t easy. Very few make it. Part of the reason is that there aren’t many clients to go around, and it’s hard to differentiate from people who have been doing this for a long time. Not impossible, but you need a clear answer to why you are the best option and how you will attract clients. Do you have unique relationships or a reputation no one else has? Most people believe they can do the work. That is a separate topic. Attracting clients is the harder problem. If you make it work, brilliant. The overwhelming majority of people I have seen try haven’t been successful.

Five Takeaways for Anyone Doing the Work

Treat community as a 3 to 7 year career window. You are probably not going to be in this for 20 years unless you want to be. Some people enjoy the core work and stay in it forever. No shame in that.
If you want to grow, move to an org with a real community team. You need to be in a place that invests in community: good platforms, dedicated headcount, room to climb.
Pick a community type that maps to a revenue function. Customer marketing, product, advocacy, customer experience. Support is fine, but I noticed that people doing pure online support communities tend to progress less.
Own a metric the business actually cares about. Pipeline influenced, expansion revenue, deflection. Not engagement.
If you are five years in and nothing has changed, the data is telling you something. You are probably in the situation many people are in: there is nowhere to go from where you are. If you want to grow, you will probably need to make a lateral move.

The exceptions exist. Big org with a real team. Community as the product. Going independent. There are opportunities. But if you stay in the role and hope to progress through doing community work alone, the data says you will most likely be disappointed.

The Picture in One View

The headline numbers, the industry pyramid, the climb rate, and the career outcome breakdown:

So, Is Community a Dead-End Career?

It can be. It definitely can be.

But if you want to progress, you have to align yourself with a function where progression is possible. Either work within a larger team where you can climb, or make a lateral move out of community where you can take the connections, experience, and expertise you’ve built into the next level.

Good luck.

The post Is Community a Dead-End Career? first appeared on FeverBee - Community Consultancy.

The Way We Compare Community Platforms Is Broken (new tool)

Richard Millington — Wed, 03 Jun 2026 15:52:31 +0000

TL:DR – We’ve launched a new platform feature selection tool – you can find it here.

Tell me if this sounds like a familiar story.

You decide to migrate your community. You speak to stakeholders, create a list of requirements, and compile them into a weighted RFP. This may run from 20 to over 200 rows.

You send the RFPs to platform vendors and get responses within a week.

As you review the list, you soon discover that nearly every community platform vendor claims to do everything you want. What luck!

So you select a platform based on price or other nebulous attributes and get started.

And that’s when problems begin. Suddenly, the features don’t quite work as planned. Some aren’t quite as ‘out of the box’ as you were led to believe. Others just look a little ugly and outdated. Sometimes the functionality is atrocious. The problems begin to accumulate as does the cost.

The brutal reality begins to dawn on you…you’ve picked the wrong platform, and now you’re stuck on it for the duration of a 3-year contract.

The lesson is that there’s a gaping void between a platform vendor saying, “Yes, we definitely have that feature,” and that feature being any good.

And the problem right now is that it’s very difficult to tell the two apart because people aren’t even sure what to ask for.

How Do You Compare Platforms That Offer Similar Feature Sets?

This confusion has existed for decades. The difference today is that the new breed of platforms is nipping away at the old guard, promising an equivalent feature set at a fraction of the price.

Which leads many organizations to ask: can a platform a few years old really have the feature set of one that’s decades old?

The RFPs we’re using do a terrible job of distinguishing between features and functionality. They ask about features instead of going granular with functionality.

This lets any platform, regardless of how new or lightweight it may be, claim near-feature parity with the old guard.

This creates a lot of confusion, not only about what separates the legacy platform vendors from one another, but also about what separates them from the newcomers.

And this problem is particularly acute when the project is being run by a non-community stakeholder (i.e., IT, marketing, or customer support). Their platform requirements are often aligned with their goals rather than with the best community experience.

To Help You Navigate This, We’re Publishing Our Platform Feature Selection Tool

To help you select the features that you need and have the tricky internal discussions that you need to have, we’re introducing our new platform feature selection tool.

It’s a tool that will help you clarify the difference between vendors who seemingly offer feature parity. And explain why sometimes it might be worth paying more for one platform than another, even though the feature set is the same, the functionality is completely different.

You can either use this to guide your thinking on the functionality you want or use it to select the right functionality for your use case.

Click here to explore it.

Tell me if this sounds like a familiar story.

You decide to migrate your community. You speak to stakeholders, create a list of requirements, and compile them into a weighted RFP. This may run from 20 to over 200 rows.

You send the RFPs to platform vendors and get responses within a week.

As you review the list, you soon discover that nearly every community platform vendor claims to do everything you want. What luck!

So you select a platform based on price or other nebulous attributes and get started.

The brutal reality begins to dawn on you…you’ve picked the wrong platform, and now you’re stuck on it for the duration of a 3-year contract.

The lesson is that there’s a gaping void between a platform vendor saying, “Yes, we definitely have that feature,” and that feature being any good.

And the problem right now is that it’s very difficult to tell the two apart because people aren’t even sure what to ask for.

FeverBee's Community Platform Feature Comparison Tool

Discover the difference between good and great platforms

Click Here

The post The Way We Compare Community Platforms Is Broken (new tool) first appeared on FeverBee - Community Consultancy.

You Can’t Fight The Tide: Why Sephora Closed The Most Totemic Brand Community Of The 2010s

Richard Millington — Tue, 12 May 2026 06:45:21 +0000

There’s been plenty of chatter the past week about Sephora closing its community.

This is sad news for anyone who’s been in the community space for a while.

For many years, Sephora was held up as the totemic example of a thriving brand community that wasn’t centered on customer support.

It’s genuinely hard to think of others (not impossible, mind, but certainly difficult).

Which is why its closure is worth considering.

After all, if the best-in-class example can’t thrive in the modern era, which community can? Does the past approach to building brand communities work in the new era?

Why The Sephora Forums Are Closing

While plenty of folks have mourned the loss of Sephora’s forums, surprisingly few have reflected on why they are closing.

(Note: FeverBee has consulted with Sephora several times over the years, and we were among those who recommended closure for the forums.)

Closing a community is almost always a last resort. You want to fix the problem first.

But there are some problems you simply can’t fix. And that’s what makes the Sephora community a totemic case for a different reason today.

Sephora Forums Should Be Thriving

If you look at sales figures alone, the Sephora community should be on a tear. Revenues are at record highs. There should be more people eager to discuss Sephora products than ever before.

And yet, it’s no secret that engagement in the forums has declined over the past five years.

Which raises one of two possibilities:

Customers don’t want to talk about Sephora products anymore.
Customers want to have those discussions elsewhere.

The first is possible, but unlikely. It’s hard to think of a reason why customers would stop wanting to talk about beauty products en masse.

This makes problem two far more likely.

The Rise Of Reddit

Whenever we face an enticing community mystery (p.s. I love this talk), it’s always helpful to look at some data. And the data in this case puts the smoking gun very clearly in the hands of third parties, notably Reddit.

Let’s examine the growth of the Sephora subreddit over the past few years. Archive.org isn’t a perfect tool, but it lets us compare snapshots of the community at different times (alas, not at identical times of year).

But taking snapshots of Reddit by year and comparing membership growth shows some rather startling results.

That’s a staggering level of growth, especially between May 2023 and Oct 2, 2024 (approximately the time when Google began diverting large amounts of traffic from other channels to Reddit).

But you can argue that figure pales in comparison to the 5m+ members the Sephora community might have. What we need isn’t just membership growth, but the level of engagement.

Let’s begin with the official community.

I can’t share the data Sephora has provided, but we can create a ‘back of the napkin’ estimate by looking at the total number of posts in the Sephora approximately a year ago (3,216,003) and subtracting that from the number today (3,184,561) and then averaging out the difference between the two dates (31442/354 days).

This gives us a post-moderated average of 89 posts per day …or approximately 621 posts per week.

As of today, May 11, 2026, the Sephora subreddit attracts 6,400 posts per week…

That’s 10x higher than the official community volume!!

That’s about as strong a smoking gun as you’re likely to see in data terms.

And this is before we factor in the post-pandemic rise of influencers, Facebook groups, and the plethora of other places where people can discuss Sephora outside of the official community.

The problem isn’t that people didn’t want to talk about Sephora; it’s that they wanted to do it in places Sephora didn’t control.

Why Are External Channels Preferred?

It’s worth looking at feedback on the closure announcement on Reddit to understand why external channels are preferred.

A (Claude) analysis put the responses into a few clear categories.

You can read this and think well, if more people knew it existed, then more people would use it.

And that’s a valid argument, but it lacks nuance. The reality is, Reddit has become the de facto place for people to discuss topics that interest them.

It overcomes the single biggest problem all non-support-centric communities face: finding a trigger to get people to visit. People are already there, and they get alerts, notifications, and prompts to visit the other subreddits they are a part of. It has a built-in trigger.

The Sephora community offered a range of unique customizations, benefits, and rewards for engagement. But ultimately, none of that came close to matching the one that members valued most: ease of use.

As I’ve written before, members are like water. They follow the path of least resistance to achieve their goals. Reddit is the path of least resistance. It’s one of those rare 5 to 7 websites people visit every day to see what’s new. Most brand communities are not.

And that’s a killer when members don’t need to visit your site to solve a problem.

Five Strategic Options

It’s good to reflect on the five strategies available to enterprise community pros right now.

Double down on AI and focus on the community being part of the AI tools your organisation is developing?
Focus on building a sense of belonging that AI can’t compete with?
Optimise what you’re already doing and ignore the noise?
Embrace ‘Community Everywhere’ and engage across multiple platforms?
Five Strategic Exit.

Of the five, I’d much prefer that Sephora pursue option four rather than a strategic exit. But that’s easier to recommend from the outside than to implement from the inside.

That path forward isn’t always viable within unique organizational structures and constraints.

So rather than renew for another three years on an increasingly abysmal community platform, a strategic exit makes sense.

Strategies From 2010 Flounder In 2026

The reality is, times have changed. Case in point, back in 2021, a former Sephora exec moved to Athleta and tried to replicate the same Sephora template there by launching a near-identical community.

I predicted at the time it would fail, which it did.

The reason is that the strategies that succeeded in the 2010s don’t work as well in the 2020s.

Times and technology have moved on – and we need to move with them.

The Crest Of The Community Everywhere Wave

A few years ago, I gave this talk about Community Everywhere.

Essentially, members’ preferences have changed, and we now prefer to meet the majority of our engagement needs on platforms outside a brand’s direct control. For many brands, especially those with non-support goals (loyalty, sales, retention, etc.), the new game was to engage in and support ecosystems comprising different groups, platforms, leaders, and more.

This approach is harder to measure and organize (it doesn’t fit neatly into most departments), but also the most aligned with current audience preferences.

And as strategists, it’s always critical to go with the tide vs. fight against it.

Now, the crest of the community everywhere is beginning to crash against some of the larger rocks in the community industry, and Sephora shutting down its forums is the result.

The Blockbuster Problem

There have been and will be some folks who cling to a purist idea of community – a place which a brand controls and where you (theoretically) own your data.

And there will be a few who will look at this Sephora news with a thought of;

“Why didn’t you try [x]?”

And, I’ll bet pretty good money. Whatever X is, it has already been considered, tried, and/or incorporated. The problem isn’t the engagement activities the Sephora team was or wasn’t doing. The problem is quite simply that the forums are on the wrong side of trends.

I remember reading an article many years ago about him closing his Blockbuster video store. Everyone had some advice about how to save the store. Video clubs, membership schemes, social media advertising, etc., and yet, if it were that easy, there would be more than one Blockbuster store in the world.

The only thing that would’ve saved Blockbuster was to acquire Netflix and change the entire business model.

There are some trends you simply can’t fight. You can either completely revamp your approach to incorporate them or admit it’s a losing battle.

The same is true here. No brand community will last forever. They rise and fall like the tide over years, potentially decades. The best run lasts for decades. And Sephora lasted for decades. That’s an incredible achievement.

Can Forum-Centric Communities Survive?

I made similar comments about forums during a debate with Marius at Higher Logic’s Superforum in Washington, DC, a few weeks ago.

I noticed in the poll responses, one skeptical attendee said

“People have been predicting the death of forums for over a decade!”

Which is valid, but also misses the point.

It’s not that binary. It’s not about death (non-existence of forums) vs. life (existence of forums).

There will always be forums in some capacity (people still use videotapes, too!), and there are plenty of degrees of nuance along the continuum between the two extremes.

It’s about the increase or decrease in their popularity and, subsequently, when and where they are the best tool to achieve our goals.

And over the past decade, we’ve seen a sharp decline in the popularity of forums for most engagement-related activities.

For customer support, forums are fantastic. They may even see an AI-driven revival as authoritative and useful sources of information.

But for almost any other needs, the Community Everywhere wave is about to crash upon them and carry the remnants out to sea.

The Community Everywhere Era Is Here To Stay

If you want a simple takeaway from all of this, it’s this.

You need to keep your community fully aligned with your audience’s needs and preferences. And when those needs and preferences shift, so does your approach. That often means changing the technology, goals, or approach. But the moment you try to cling to what you have, seek control, or try to fight against the changing tide is the moment your community begins its long journey towards irrelevance.

And if you want help knowing if your community is aligned with your audience’s needs and preferences, drop us a line.

Good luck!

The post You Can’t Fight The Tide: Why Sephora Closed The Most Totemic Brand Community Of The 2010s first appeared on FeverBee - Community Consultancy.

Stop Letting Defaults Dictate Your Community’s Design

Richard Millington — Mon, 04 May 2026 20:54:17 +0000

I’ve now sat through hundreds of UX sessions watching members navigate enterprise communities. The same pattern surfaces every time.

There’s a wide gap between how members say they want to engage in a community and how the homepage is actually set up to let them. The community team isn’t usually at fault. The platform vendor’s professional services team configured a template, the homepage went live, and no one has questioned the defaults since.

So to save some time, I mocked up what a modern enterprise community homepage should look like:

Notice the seven things on this page. Each one replaces a default that’s quietly costing communities their members.

1. A powerful, value-based message

Most homepages open with “Welcome to the [Brand] Community” or some variation of “Connect, share, learn.” This tells the member nothing about why they should be here rather than on Reddit, Stack Overflow, or a Slack group their colleague set up.

The message should make the unique value of this specific community obvious in one line. What can a member do here that they can’t do anywhere else?

The homepage messaging should generally answer these community positioning questions.

2. Task-based search

A typical community search returns 25 to 50 threads sorted by recency. The member then has to read through them to find the one answer they need. Half the time, they give up and post a duplicate question.

Modern RAG-based search should be doing the work the member is doing manually.

It should synthesize the answer from the best threads, surface the source posts underneath, weight recent and authoritative content above stale ones, and let the member ask a question in natural language.

The technology has been available for two years. It’s about time it was embedded in your community.

3. A small number of trending topics

On most community homepages, there’s no navigation help at all. The member lands on the page and has to figure out where to click to find anything relevant.

The category tree is buried, the topics are alphabetical, and the discovery experience is “scroll until something catches your eye.”

A small, curated set of trending topics solves this. You ideally want five to seven topics, refreshed daily, surfaced prominently.

It guides 80% of members to the location they want to go to most. It tells the member what the community is talking about right now and gives them an obvious entry point.

4. Value-based engagement stats

Plenty of community homepages display vanity metrics. “47,000 members. 380,000 posts. 1.2 million replies.”

These numbers mean nothing to a member trying to decide whether this is the best place to solve their problem and achieve their goals.

Replace them with stats that signal value. This includes questions answered in the last 24 hours, average response time, active superusers online right now, problems solved this week etc. The member is asking, “Will I get help if I post here?” The homepage should answer that question in the data it shows.

5. An AI summary of the past 24 hours

This isn’t a radical idea, but it hasn’t been executed well yet.

Regulars are the engine of every healthy community. They want to know what they missed since their last visit without scrolling through 80 threads to find out.

A short AI-generated digest of the most important discussions from the past 24 hours, with links to the full threads, gives them exactly that. It takes ten seconds to read and pulls them straight back into the activity that matters. Every platform has the technology to build this. Almost none of them have shipped it.

6. A clear path to becoming a superuser

Superuser programs exist in most enterprise communities, but the path to becoming one is not visible on the homepage. It’s buried in a help doc, gated behind an internal nomination process, or restricted to people the community manager already knows.

The homepage should make the path visible. “Here’s what superusers do, here’s how you become one, here’s what you get.” Communities that surface this generate a self-selecting pipeline of high-intent members who want more responsibility.

Communities that hide it rely on the community manager’s personal knowledge of who’s been active lately.

7. A clear list of what members can actually do here

Almost every community offer the following actions: ask a question, share work, find an expert, and join an event. The actions just aren’t visible on the homepage. They’re tucked into a navigation menu or surfaced through a “+New Post” button that doesn’t tell the member what kinds of posts they could make.

The homepage should make the available actions explicit. For example, a short panel with three or four primary actions, each with a one-line description.

It removes ambiguity and gives the member permission to participate in a specific way.

Stop Relying on Defaults For Your Community Design

Too many enterprise community homepages are designed by the platform vendor’s professional services team. That’s not a design discipline. It’s an implementation discipline.

The result is a homepage that reflects what the platform does by default rather than what the community needs. The vendor has no incentive to question whether the design is right for the audience, because their job is to launch the platform on time and on spec. Once it’s live, the community team inherits a homepage that nobody really designed, and the defaults stay in place for years.

This is why we keep having poorly designed community homepages.

Get a community design that actually works

If you’re staring at a homepage you didn’t design, that doesn’t reflect how your members want to engage, and that your platform vendor isn’t going to fix, that’s the kind of problem FeverBee solves.

We can undertake a community design project (est. cost $20k to $30k) that includes:

Community Experience Diagnostic: a scored audit of your current experience against 40+ design principles, benchmarked against the top quartile of enterprise communities we’ve assessed.
Member Behaviour Analysis: analytics, session recordings, and structured interviews with newcomers, regulars, and lapsed members to surface the gap between how members say they engage and how they actually do.
Vendor Capability Assessment: an objective evaluation of what your platform can and can’t deliver, separating platform limits from configuration choices your vendor hasn’t surfaced.
Community Design Index Score: a proprietary score against our benchmark of enterprise communities, giving you a number you can take to leadership.
RAG search architecture spec: the technical specification for how your search should be configured, weighted, and integrated with your knowledge sources.
Information architecture for the full member journey: wireframes for the homepage plus 4 to 5 key templates, mapped against newcomer, regular, and superuser behaviour.
Onboarding flow design: the sequence of prompts, notifications, and CTAs that turn newcomers into regulars across their first session, first week, and first month.
Implementation brief: a document your platform team or vendor can build from directly, removing the ambiguity that lets implementations stall.

If you’re interested, contact us or reply to this email.

Good luck!

The post Stop Letting Defaults Dictate Your Community’s Design first appeared on FeverBee - Community Consultancy.

Read This Before Your Next Community Migration

Richard Millington — Mon, 27 Apr 2026 14:47:13 +0000

TL;DR: Six processes decide whether your migration succeeds or disappoints: the right team, selecting the right problem, the right migration strategy, the right data decisions, the right field mapping, and early testing. Don’t skip any of them.

Over the past few months, I’ve spoken with several organizations that haven’t been happy with their recent community migration.

The common complaints include:

The platform doesn’t have the features they thought it did.
The platform’s features aren’t working as well as they thought.
They’ve lost data in the process.
It wasn’t the right platform for their use-case.

It’s genuinely painful to hear about organizations that invest hundreds of thousands of dollars, as well as countless hours and emotional labor, for an experience that turns out badly.

Each time I hear this story, I try to dig deeper into what happened. Typically, one of two things happened.

A tiny community team with limited experience in complex platform migrations tried to shepherd the process through themselves. They weren’t given the support or guidance they needed. So they go down the journey alone and tackle each platform as it arises without the experience to avoid common mistakes.
The majority of the process was outsourced to a third party (typically a vendor/implementing partner). This avoids most technical problems but not the strategic ones. Once the migration is complete, they find the platform works – but doesn’t always do what they wanted.

The real problem is almost always a variation of the same problem: poor processes.

Migrations Are Poorly Executed Because They’re Misunderstood

From the outside, a platform migration probably resembles a process of:

Select the vendor we will migrate to.
Migrate all the data across.
Launch it with a good communications program to members.

What it actually looks like in practice is a six-to-twelve-month program involving:

Difficult decisions about data you’d rather not deal with.
Stakeholders who appear late with strong opinions.
Integrations that don’t map cleanly.
Data that doesn’t map at all.
A vendor whose priorities don’t perfectly align with yours.
Content that nobody wants to take responsibility for cleaning up.
And a launch date that keeps moving.

…all while still running the community you’re supposed to be migrating.

How FeverBee Helps Implement Successful Migrations

Our role is to embed the right practices right at the beginning of the project to guide clients to the right outcome.

1) Build and Run The Right Community Migration Team

Two people from the community team shouldn’t be liaising with the vendor and trying to tackle this alone.

We first need to create the right working group (or steering committee).

This group needs to involve the executive sponsor (who is proactively involved), IT representatives, members of the community team, a project manager (if not ourselves), and potentially folks from customer support, marketing, or other interested departments.

If you don’t bring the right people together at the beginning, you’ll regret it for the rest of the project.

Once you have the team, you need to implement best practices for managing it. This means proper:

Project management. An up-to-date timeline with clear milestones and moments when people will need to be involved so they can plan their availability in advance.
Roles and responsibilities. Use a RACI chart. You will need folks for data quality control, integration testers, clear sign-off moments and more.
Regular bi-weekly meetings (weekly tends to be too frequent).
Weekly updates. Keep everyone on the same page.

2) Ensure You’re Solving The Real Problem(s)

Migrating a community incurs a huge opportunity cost.

The time, resources, and goodwill you expend on the migration is time you can’t spend on a dozen other programs that might improve your community.

This is why you should migrate only when it’s the next phase of your community strategy.

You shouldn’t do it just because you’re tired of the platform or it feels outdated — but because it solves a specific challenge that your community needs to overcome to achieve its goals. And you should be able to articulate the challenge clearly.

If you don’t clearly define the problem, it’s easy to get swept up in scope creep, add new features that someone likes, experience delays, and end up with a bloated mess.

The first step then, is to ensure our clients have a clear problem statement to work from. This typically includes:

Deciding which of the five strategies they’re pursuing.
Gathering stakeholder needs through workflow-specific questions.
Evaluating the technology environment to understand key trends for the years ahead.
Deciding which audiences your community will serve in the future (and which it won’t).
Deciding where your community adds unique value, and align the process accordingly.

It helps to use external consultants to work through these problems with you — it eliminates internal bias and ensures best practices are followed.

By the end, you should be able to articulate a very clear, specific problem statement.

A bad problem statement looks like:

“Our current platform feels dated and the new one has better features and a more modern look that the team prefers.”

A good problem statement is specific, member-facing, and tied to a measurable outcome. It names the audience, identifies the friction or gap, and connects it to a business or community goal. For example:

“Our enterprise customers can’t find peer-validated answers to technical implementation questions, which is increasing support ticket volume and reducing product adoption. Our current platform’s search and taxonomy limitations mean we can’t surface the right content to the right people at the right time. We need a platform that can support structured knowledge management at scale.”

Don’t move forward until everyone is aligned on the problem you’re solving.

The critical thing this step achieves is that it forces through most of the critical decisions as early as possible.

3) Select The Right Migration Strategy

Right at the beginning, we need clients to decide which of the four major migration approaches they’ll use. You have four options here:

Hard cutover. This is where you close the old platform and launch the new one on the same date. This is the simplest to manage; it forces adoption, but it also entails a huge risk if something doesn’t work, and it can be tough on search traffic. There’s no fallback if something breaks.
Parallel running. This is where both platforms run simultaneously. If there’s any issue, can you quickly switch back to the old one? You might have an old one running at a different URL or the new one running at a new URL for a short time. The downside of this is that it can create confusion, double the maintenance burden, and take longer. It also simply costs more. This is quite rare in practice.
Phased Migration. This is where you migrate the community in stages. This gives you a way to test out the new community before making the big change. In this case, you might migrate specific content categories, audiences, geographic areas, or use cases first. This reduces the risk but often increases the cost and timeline.
Soft launch/beta migration. This is where you roll out the new platform launches to a small group of members first (often power users or volunteers) before a full rollout, allowing you to test and refine the experience before the wider community transitions across. This tends to happen only when moving to a new platform category (e.g., Slack to forums).

Here’s how to pick. Option 1 (hard cutover) is what most teams default to because it’s simplest — just accept that it carries the most risk if something breaks. Option 3 (phased migration) is what we usually recommend: the added time and cost buy you real protection against a bad outcome. Option 4 (soft launch) is a niche fit when you’re changing platform category — for example, moving from Slack to a forum. Option 2 (parallel running) is rare in practice; reserve it for regulated environments or cases where the ability to roll back has to stay on the table. Whatever you pick, commit to it early. The choice cascades through every other decision in the project plan.

Also, decide what needs to be migrated on day 1 vs. what can be migrated over time.

The common mistake in a migration is trying to get everything perfect and in place on day one. This tends to cause significant stress, delays, and overruns.

A far better approach is to draw a clear line between what’s a “must have” on day one and what can be improved post-migration. It’s incredibly important not to get stuck on the inverse 80/20 rule (i.e., spending 80% of your time on the least important 20% of the project).

You need to separate the critical work that can get done today from the roadmap improvements that can be implemented over the following months. This means planning very clearly what is a must-have and what is a nice-to-have.

4) Force Yourself To Make The Critical Data Decisions

Data is too often considered an IT task. And IT can usually successfully migrate data from one system to another by mapping fields, running scripts, and loading records.

The problem here is that the IT team often makes the critical decisions you should be making in the process.

I know one IT team that recently migrated 1.8m threads from one platform to another and declared the migration a success because the record count matched.

Yet six months later, the community team is seeing that outdated content is surfacing in search results more frequently than ever before.

The IT team can migrate data, but they can’t tell you which discussions are no longer accurate and should be archived, or whether your taxonomy reflects member behaviors, or even whether a piece of content is still relevant.

Your goal isn’t to perform a simple lift-and-shift. It’s time to take this rare moment to decide what data should be part of your community knowledge going forward.

The more you cut at this stage, the better the community will be for everyone.

In practice, this means we usually ensure clients:

Set a minimum quality threshold for what gets migrated. Any content that attracts no traffic, is more than two years old, falls into categories of products that are no longer supported, and/or isn’t included in the Google Search Index can be noindexed, archived, or simply deleted entirely. But agree on the rules early. Often, content related to products the company no longer sells is ripe for removal. You might also zero in on unanswered questions — does it make sense to you to migrate questions that never received a response?
Undertake a community data audit. Based on these rules, undertake a community data audit. Begin at the category level and decide which categories of discussion you won’t migrate across. Then filter the remaining discussions into the relevant groups (deleted, archived, noindexed). At this point, you might have saved yourself the effort of migrating a vast amount of content.
Review the remaining discussions. Undertake an audit of the remaining discussions to identify discussions that fail data quality standards. This might include duplicate, contradicting, or decayed answers. It might include answers with missing responses or simply those lacking the right freshness signals. Zero in on the discussions where the community provides the most value. At this stage, you can typically archive/merge/update many discussions and reduce the number being migrated across.
Decide on the new taxonomy. Review the existing taxonomy structure and make sure you’re clear on the category structure, tags, content types, resolution status, and any custom fields you might use.
Decide which members you will migrate across. Don’t migrate dormant accounts. Decide what “dormant” means for you, then send an email asking people to log in if they wish to retain their account access. You might also wish to review your member retention policy going forward with regards to GDPR (how long will you keep member data?).
Assign business owners. Community owners need to be assigned to specific data domains; someone owns content, someone owns member data, and someone owns taxonomy and navigation. They’re the ones who define what “good” looks like: which content is worth migrating, what gets archived, and what gets deleted entirely. They also need to sign off on test migrations, not just confirming that the data moved, but that the content is correct, findable, and still relevant.

This should ideally result in a clear data decision document that IT can use when migrating the data and ensuring no unnecessary data is migrated.

Again, make these decisions as early as possible.

5) Lead The Data-Field Mapping

Generally speaking, community folks should typically take the lead on matching data fields between platforms. And you should be fully aware of what does and doesn’t match.

You might find that some data fields can’t easily carry across. Passwords, for example, are encrypted and never transferred; hence, resetting passwords is always required after a platform change. Private messages also don’t typically migrate well.

Our steps here usually include:

Building a complete data field inventory. Before any mapping begins, we list every data field on the current platform: content, member profiles, roles, permissions, gamification, tags, metadata, and engagement data. Don’t rely on the vendor or IT to produce this list. You’re more likely to know what exists and what matters.
Identifying what maps cleanly to your new platform, what maps loosely, and what doesn’t map at all. Here we go field by field and categorize each one. Clean maps require no decisions. Loose maps require a judgment call about where the data should land on the new platform. Non-maps require a decision about whether to drop the data, transform it, or find a workaround. Pay special attention to gamification data.
Making an explicit decision for every non-mapping field. Don’t let gaps get deferred. For each field that doesn’t map (e.g. private messages, member photos, gamification elements, custom tags, etc.), we decide whether to: migrate with transformation, archive, communicate to members, or drop entirely. Then we document the decision and who made it.
Building a member communications plan around the gaps. Be mindful that members might complain about anything they lose, so we build a communications plan that flags what they will lose and advises them on how to retain/export the data (if possible). Anything related to member photos, gamification, and private messages is worth flagging.
Getting formal sign-off on the mapping document. Before full migration begins, we need a named business owner to sign off on the complete field mapping. This protects you if decisions get questioned later and ensures accountability sits in the right place.

Sometimes tags and labels for discussions don’t easily transfer across either. This is important from both a communication perspective (preparing members) and a knowledge perspective — you need to be aware of what does and doesn’t map.

6) Run Early Data and Integration Testing

If you’re not hands-on with the early data and integration testing, mistakes can easily slip in.

We need to check that all the data fields have been matched accurately and that there are no obvious issues. LLM tools can help here, but nothing beats the human eye and good judgment.

Request a data sample as early as possible. Different platform vendors have different rules about providing you with a full export of your data. Some will be good vendors and help you. Others will give you just one big data dump and charge you excessively for any additional requests. But you need to request a data sample as early as possible. Not all vendors have a good track record of providing you with data access.
Run multiple small test migrations before the full migration. Don’t wait until you’re ready to migrate everything. Transfer batches of data early, review the output, fix any issues, and rerun. Do this as early as you possibly can. Problems caught in a test batch cost a fraction of what they cost post-launch.
Use random sampling to review migrated content. Randomly sample across content categories, member types, and date ranges to catch issues that only appear in specific conditions. LLMs can certainly help with a review here and flag issues, but nothing really beats the human eye for checking that all of this is accurate and as it should be. And don’t rely on the IT team to do this — the IT team can confirm the record counts match, but only the community team can check it looks right, reads correctly, and makes sense in your new platform’s architecture.
Test every integration independently and end-to-end. The same principle from above applies to integrations, too. Test every connection your community has with other systems (e.g., CRM, SSO, ticketing, analytics, email, etc.). These should be tested in isolation and as part of the full system. As with the records, assign a named person to do this and check it.
Log every issue found and track it to resolution. Every single problem identified needs to be logged and tracked with your vendor or implementing partner to resolution. And every problem needs to be retested before going live.

Don’t Go Through This Process Alone

My advice is that if you don’t have migration experience, don’t go through the process alone.

Get help to ensure you select the right platform (we’ll cover this separately), solve the right problems, and achieve the most seamless, beneficial outcome possible.

The result should never be just a lift-and-shift. It should be a community experience that’s set within your modern realities but designed for the future. It should be clearly better than what came before, and a decision you can live with for the next few years.

If you’re about to migrate, or you’re in the middle of one that isn’t going well, drop us a line. We can take on most of the heavy lifting to ensure your migration is a success.

The post Read This Before Your Next Community Migration first appeared on FeverBee - Community Consultancy.

Moving From Slack/Discord To A Forum: Don’t Make The Most Common Mistake

Richard Millington — Mon, 13 Apr 2026 06:29:07 +0000

I can’t stress enough the difference between shifting from a chat platform to a forum (or question-and-answer) platform.

Sometimes the shift is natural. Members were primarily using the chat platform as a question-and-answer platform anyway. In which case, it was the wrong platform to begin with, and the shift to a forum is correcting the initial error.

At other times, though, it’s asking members to change both their behavior and their perception of the community’s value. It’s a little like asking a group of friends, used to a free-flowing nature of discussions, to suddenly have to come up with precise questions and receive precise answers in a facilitated environment.

It can happen, but it’s a very different kind of experience.

And that can be a problem.

Are The Costs of Change Experiences Quicker Than The Benefits?

The worst thing to do is to try to copy the existing Slack/Discord experience.

The most common approach is to replicate the channels on Slack/Discord, send a series of messages asking members to use the new forum experience with a countdown, and then close down the Slack/Discord channels.

This runs into one obvious problem: the costs of the change to members (more friction in the user experience) are recognised much faster than the benefits.

In a chat experience, you skim what people have been saying, type a comment, and hit ‘enter’. That’s it, your comment appears (and it is soon buried by other comments – both part of the charm and cost of chat).

But in a forum, you have to type a subject line, write out a post, categorise it, possibly tag it, and then hit enter. This additional friction may lead to higher-quality debate, but it feels burdensome to members used to a chat experience.

This is often the result of a misalignment between what the organisation wants to offer (gamification, easier-to-follow discussions, better integration with internal systems) and members’ desires (an easy-to-use experience).

As a rule, you risk member backlash and declining engagement.

The solution is to recognise that you can’t offer a forum experience to replace a chat experience. The comparisons members will make will work against you.

Moving from one experience to another isn’t just a technology change; it’s a change in behavior and in the community’s value perception.

Create A New Thing…A Much Better Thing

Instead of simply replicating the old thing – i.e., ‘here’s a new place for you to chat’ – you have to create a different value proposition.

And that value proposition has to be immediate and obvious, not something which will only be realised over the long term. “Gamification” and “easier to follow discussions” are examples of value that will only be clearly visible over a longer period of time.

And this value proposition should embrace the unique advantages of a forum over chat. I.e., What kind of activity would make sense to have in a forum that you wouldn’t be able to have in chat?

This might include:

“Solve This Once And For All” Threads. Members collaborate to produce the definitive answers to a recurring issue, then it’s pinned and updated over time.
“Solve My [x].” Members post a full write-up (problem → process → outcome) and receive threaded feedback, not just emoji reactions.
Peer Review Threads. Members upload work (slides, code, docs) and receive threaded, topic-specific feedback.
Ask for a Review” Sections. Members request feedback on a product setup, campaign, or configuration, replies stay tied to the request forever.
Monthly Expert Clinics. One topic per month, members submit questions in advance, expert replies in depth, all stored + indexed forever.
Template / Playbook Exchanges. Members upload files, screenshots, workflows – future members can find, reuse, and iterate.
Research Collaborations. Structured threads where members contribute data, screenshots, survey inputs, etc., and the findings are summarised at the top.
“Show Your Setup” Galleries. Members post photos, configs, dashboards, and code blocks, which are impossible to scroll through and retain in chat.
Multi-Week Challenges (progress tracked per member). e.g. “30-Day Implementation Sprint” — each person replies weekly with screenshots/progress.
Structured Debates. 2–3 side arguments, moderated, with citations and threaded counter-replies, not real-time chaos.
Beta Feature Feedback Hubs. One thread per feature, tagged by status (Planned, In Review, Released), linked to release notes.
Crowdsourced “Glossary of Terms” Thread. Members supply definitions, vote, and refine. Searchable, linkable, not buried like Slack messages.
“Hall of Fame” Knowledge Threads. e.g. “The Best Automation Scripts Ever Written”, curated, updated, forever referenced.
Persona-Based Rooms. Instead of channels, you have structured categories (Developers, Marketers, Admins) with pinned guides and FAQs.
Idea Tournaments. Members submit proposals, others vote & comment, moderator advances the top 8 → final winner.
Post-Event Knowledge Drops. After webinars, conferences, or workshops, slides, takeaways, recordings Q&A captured and archived.
“Lessons Learned” Retrospectives. One thread per major mistake, members add similar experiences – becomes a collective safety net of insights.

You can come up with plenty of your own examples, I’m sure.

But now you’re using a forum in a way you couldn’t (or wouldn’t) use Slack/Discord.

You’re not letting members compare friction levels across community platforms (which is a losing battle).

You’re instead pioneering a new way to build and engage with a community. One that is less about the ephemeral nature of chat and more about building a structured knowledge database, a database that will prove eternally useful.

Run Both (At Least For A While)

Don’t close down chat when the community is launched. Run both – at least for a while. Use the chat to promote community activities.

Set up an automation to post new forum discussions to Slack/Discord channels to drive activity back to the forum. Remind members who post support-related questions in chat that the forum is the best place to continue their support requests.

Over a relatively short period, activity will naturally shift. That’s because member preferences will shift. You won’t be forced to deal with the blowback from members resistant to the forum. They will simply find the activities published in the forum more valuable and engaging than those in chat.

After a few months, you should be able to close down the previous channels and rely solely on the forum (although it’s worth noting that many have both running for a period of time).

Good luck!

The post Moving From Slack/Discord To A Forum: Don’t Make The Most Common Mistake first appeared on FeverBee - Community Consultancy.

It’s Time To Add Friction (And What Happened When We Did)

Richard Millington — Sat, 28 Mar 2026 17:01:13 +0000

What Are We Optimising For Anymore?

For the best part of twenty years, we’ve been optimising enterprise communities for engagement; more posts, more replies, more members, more activity, more deflection.

If the graphs went up – the majority of people didn’t think too deeply beyond that.

There are generally two ways to increase engagement;

Increase people’s motivation to engage.
Reduce the friction to engage.

The former is much harder than the latter, so over the course of twenty years, we’ve been on a relentless mission to lower the friction to engaging.

This meant:

Single sign-on. Removing the separate login so members could access the community with their existing credentials.
Gamification. Giving points and badges for every post, reply, login etc..
One-click reactions. Adding likes, upvotes, and emoji reactions so people could participate without writing anything.
Email notification triggers. Sending digest emails, “you haven’t visited in a while” reminders, and reply notifications to pull people back in.
Removing onboarding steps. Cutting profile completion, interest selection, and community guidelines from the sign-up flow to get people posting faster.
Auto-suggested content. Showing trending topics, recommended threads, and “people also asked” to reduce the effort of finding something to engage with.
Lowering moderation barriers. Pre-approving new members, reducing content review queues, and letting posts go live instantly rather than holding them for approval.

The more members, content, and activity we had, the better. The graphs went up!

There are obvious benefits of more engagement, too. You get a greater diversity of responses, more people to connect with, and a lower response time.

But these are now outweighed by bigger factors

A greater volume of content makes it harder for people to find the answer they’re looking for.
More content confuses the knowledge-retrieval AI and leads to greater cleanup effort later.
More people discourage people from feeling a sense of connection with one another.

None of the five possible futures for enterprise communities depends on driving as much engagement as possible.

Having a big party doesn’t mean everyone had a meaningful conversation. You just have a big cleanup afterwards.

So what if we begin adding friction?

Two Big Changes We Made To A Client’s Community

We’ve been trying exactly this with a mid-tier SaaS community over the past two months.

We made two specific changes:

We began approving members. We asked members to complete a short form to be approved for membership. This asked for some basic details about them and what they could contribute to the community. We also asked them to agree to two specific things. First, to take the effort to respond to the answers they received without disappearing, and two to take the time to construct questions people could answer.
We required people to complete a different process to ask a question. Instead of letting members ask a question in a box, we created a question wizard. Essentially, we would ask THEM questions to describe the issue (product type, what they have already tried, ideal outcome, any constraints, etc.).

(Our first attempt let members bypass the wizard and write a question as normal. Almost everyone did exactly that. So we removed it).

These weren’t random interventions. We spent time analysing this community’s data to understand where the quality breakdown was actually happening.

The question wizard was designed around the five most common reasons questions went unanswered in this particular community: missing product version, no description of what the member had already tried, vague problem descriptions, duplicate questions that had already been answered, and questions posted in the wrong category.

The approval form was shaped by patterns we’ve seen across dozens of client projects about what separates members who contribute long-term from those who post once and disappear.

The two commitments we asked for (respond to your answers, take time to construct your question) weren’t arbitrary. They mirror the behaviours we’ve consistently seen in the most valuable community members.

The bypass lesson was also worth noting. If you offer the easy path alongside the hard path, people will always take the easy path. You have to commit to the friction. Half-measures don’t work.

The Results

We’ve only been running this for two months, but comparing March 2025 to March 2026 gives us the cleanest year-on-year comparison.

The results have been genuinely interesting.

Total post volume dropped by around 20%. Probably due to the following, and the increased difficulty of asking a question.
New member registrations declined, too. The approval filters deterred some people from even trying to get through them, which filter out those who aren’t willing to invest even a small amount of effort.

But here’s what went up:

Average question length increased by 87%. Members were providing more context, more detail about what they’d already tried, and clearer descriptions of their situation. This turned out to be a surprisingly insightful thing to measure.
The answer rate improved by 23%. A higher percentage of threads received at least one response.
The accepted solution rate increased by 73%. More threads ended with a marked solution, meaning the answers given actually resolved the problem (or the new members were simply more inclined to mark them as accepted solutions).
Member retention improved by 60%. A significantly higher percentage of approved members went on to make a second post, with no further increase in email prompts.
Community’s content started being retrieved more frequently in the organisation’s internal RAG search as citations, up roughly 55% compared to the pre-friction* average. The AI tools were pulling from community threads more often.

* Community content was being retrieved roughly 55% more frequently in RAG search, though other RAG improvements were happening simultaneously, so this one is harder to isolate.

Your mileage will vary depending on your community model, your audience, and how much friction you can introduce without losing critical mass. There’s a balance to find, and it’s different for every organisation.

But the broader point stands. For twenty years, the default assumption has been that making it easier to participate makes a community better. That assumption is probably wrong, and it’s been wrong for longer than most of us have been willing to admit.

The communities that will matter most over the next five years won’t be the biggest ones. They’ll be the ones where the quality of what’s shared is high enough that both humans and AI systems treat it as a trusted source.

If you’re rethinking what your community should be optimising for, or you want to explore what adding friction could look like in practice, that’s exactly the kind of work we do at FeverBee.

The post It’s Time To Add Friction (And What Happened When We Did) first appeared on FeverBee - Community Consultancy.