There’s a pretty odd fight happening among customer community platforms. Gainsight wants Khoros customers to leave, while Khoros wants Classic customers moving internally to Aurora AI.
Khoros Communities 26.5 finished rolling out on September 23–24, adding new Aurora capabilities, although some headline features remain in Early Access. Khoros is also offering Classic customers free migration services to Aurora AI through the end of 2026.
Then there’s Atlassian. On September 22, Atlassian Forums moved from Khoros to Higher Logic Vanilla after its previous platform contract ended. Atlassian called it a platform migration, “not a feature-for-feature upgrade.”
Technically, the move went well. Atlassian says more than 99.5% of topics and replies migrated and were validated. Yet redirects, image permissions, profile statistics, and follows still needed attention.
Atlassian summed it up, saying:
“We moved houses, not renovated.”
That’s the warning for buyers. Strong data migration doesn’t guarantee a familiar member experience.
PTC’s Khoros-to-Gainsight move had already shown how subscriptions, messages, and media can change during migration. Atlassian adds another enterprise example. Its forums spent at least 10 days in read-only mode, and a September 29 update still listed follows to rebuild, profile-stat fixes, Loom issues, and missing search alerts.
That isn’t evidence of a failed migration. It shows how member routines, and even familiar community metrics, can change after the archive arrives.
Why Are Companies Migrating From Khoros to Gainsight?
The answer to that will depend on who you ask, but it seems like most Companies are moving from Khoros to Gainsight mainly because they want community tied more closely to customer success, retention, and product adoption. Khoros’s acquisition by IgniteTech in May 2025 has also prompted some enterprises to reassess their platform strategy.
Gainsight says it has completed more than 25 Khoros migrations. That’s vendor-reported, but it’s demonstrative of the wider replatforming trend, as is the fact that Atlassian recently chose Higher Logic Vanilla for its community strategy instead of Khoros.
Interest in customer communities is picking up. Gainsight recently pointed to Gartner data showing inquiries rose 33% between April 2025 and March 2026. As communities take on more support work and influence more buying decisions, buyers aren’t only looking at what happens inside the platform. They want to know where all that customer context goes next.
That’s where Gainsight has the best pitch. Its September 24 release added automatic community-role assignment from customer-success data, while mapped profile fields can sync every four hours.
FeverBee’s Richard Millington describes Gainsight CC as built to run community “as a customer success engine rather than a marketing channel.” For teams measuring community against retention or adoption, that tighter connection may matter more than recreating every legacy feature.
None of this means Khoros is giving up. In April, we covered the launch of Aurora and Iris AI, where Eric Vaughan argued:
“AI answer engines are rapidly widening the gap between market leaders and those failing to understand the changes required to keep up.”
So the choice isn’t between an active platform and a dead one. It’s between different ideas of what community should become next.
The destination market is broader, too. Millington says Gainsight, Higher Logic Vanilla, and Discourse are the Khoros alternatives he sees most often. It’s practitioner observation, not market-share data, but it reinforces the wider replatforming story.
What Does a Community Platform Migration Cost?
We talk a lot about community ROI, but migration costs deserve just as much attention. The obvious ones are licensing, technical work, and staff time. PTC’s Khoros-to-Gainsight move exposed the less visible bill: the habits, signals, and routines members expect to survive.
After reopening, PTC temporarily used pre-moderation. Private messages didn’t transfer, hosted videos had to move onto PTC servers, and some subscriptions needed rebuilding. Existing badges came across, but some kudos badges disappeared, and changes to the ranking system meant individual ranks could shift.
PTC preserved old thread links with permanent redirects, but it’s worth remembering data can migrate while the experience around it changes. That doesn’t mean the migration itself went badly. PTC moved 15 years of community history and launched on its three-month timeline. Technical lead Andy Kenefick said:
“It was a really pleasant surprise how smoothly everything went.”
So, that tells us a well-run technical migration can still leave members adjusting to changed subscriptions, rankings, or routines.
There’s also the question of what should move at all. Gainsight’s September guidance says, “The goal is to migrate as little as possible.” It’s vendor advice, but the principle holds. Stale or duplicate material can make search worse and leave AI answer tools working from noisier source content.
Gainsight calls the member friction around a move the “migration tax” and argues that teams should plan the first 90 days before they plan the migration itself. Its September 9 guidance treats recovery as a workstream, with an owner, measurement plan, and extra launch capacity ready before members arrive.
What Should Be on a Community Platform Migration Checklist?
A migration checklist can get very technical very quickly. Posts, permissions, redirects, integrations. All important. But the better starting question is simpler: what are members used to having today that they’d complain about losing tomorrow?
PTC’s move makes that pretty clear. The archive is only one part of the job. Before signing anything off, somebody needs to own each of these:
-
Export: Do posts, DMs, attachments, subscriptions, reactions, and audit records actually leave the old platform?
-
URLs: Which links will change, and who’s checking redirects after launch?
-
Identity: What happens to profiles, ranks, badges, and accepted answers?
-
Media: Will videos and embeds survive intact?
-
Search: Can members still find the same answers afterward?
-
Operations: Does anything go read-only or move behind pre-moderation during cutover?
-
Connections: Will CRM, support, SSO, education and analytics keep behaving as expected?
-
Recovery: If traffic or participation drops, who spots it and what happens next?
There’s another AI consideration now too. Migrated content may end up feeding answer engines, which means broken permissions, stale material and dead citations become more than housekeeping problems.
Regulation belongs on the same list. Discord changed its age-assurance model on September 22 while Brazil’s ANPD kept its live-video suspension in place. Access and moderation rules can change underneath the platform.
One last question is worth asking: can the team test member-facing changes before launch? Gainsight’s September 30 newsletter says Feature Previews can trial selected structural, CSS, and layout changes in sandbox first.
How Should You Judge the Destination Platform?
Migration due diligence shouldn’t stop at whether the data fits; the destination has to suit the community you actually run, and the one you plan to build next.
Start with the operating model. Richard Millington’s FeverBee review says Gainsight CC’s place inside the wider Gainsight ecosystem “cuts both ways.” For B2B teams tying community to customer success, that connection can be valuable. Gainsight reinforced it on September 24 by adding automatic community-role assignment from CS data, followed on September 25 by multiple SSO options and automatic image moderation.
But integration depth usually comes with trade-offs. As Millington puts it:
