Skip to main content
jocelyn92
Contributor ⭐️⭐️
October 7, 2026

Has anyone kept their legacy community live during a platform migration?

We're migrating to Gainsight Community platform and are considering keeping our current community live during the migration rather than making it read-only. The plan would be to let customers continue posting, communicate that some content may not immediately appear in the new platform, and then run a smaller follow-up migration after go-live to capture anything created during that window.

We were curious if anyone here has done something similar.

If so, how did it work out? Were there any unexpected challenges or lessons learned that you'd be willing to share? 

We would love to hear your experiences. Thanks in advance!

6 replies

spieri
Contributor ⭐️
October 7, 2026
  • Hi ​@jocelyn92 - we did :) 

    We migrated from Khoros and while it introduced a bit more complexity, it was the right decision for us given the volume we are seeing on people relying on our community. 

    We informed our users that change is coming and that not all content will be available from the get-go, but will be coming later. Here is the post we posted on Khoros back then: https://community.adobe.com/questions-712/we-re-upgrading-adobe-community-for-you-1619121

    A few things we made sure:
    * We have as little as possible threads unanswered in the gap period
    * Transparency throughout to members 

    DM me if you have more questions - happy to help.
Translate
    jocelyn92Author
    Contributor ⭐️⭐️
    October 19, 2026

    ​@spieri Thanks for sharing your insights. Were points recalculated after the launch to reflect the missing data?

    Translate
    Linsey M
    Linsey M
    Helper ⭐️
    October 7, 2026

    Hi ​@jocelyn92 

    We’ve supported quite a few community migrations, and there’s definitely a case for keeping the legacy community live, especially if it’s large and active. It means users can continue to interact, ask questions, and help each other during the migration.

    The downside is that it adds quite a bit of work afterwards. You’ll need to analyse what happened on the old community during the migration window and then run a follow-up migration to bring that content across. That can get fairly complex and requires the right skills and capacity.

    If it’s possible to keep the community read-only for a couple of days, we usually recommend that instead. With good communication and some alternative way for users to reach you (email or chat for critical topics), users generally accept it.
    So yes, keeping it live is definitely possible, but it’s worth weighing the benefit of uninterrupted activity against the additional work it creates for the migration and community teams.

    Translate
      jocelyn92Author
      Contributor ⭐️⭐️
      October 19, 2026

      That makes sense ​@Linsey M Read-only is definitely better in terms of less complexity. Thanks for sharing your insights, this really helps. 

      Translate
      mitchell.gordon
      mitchell.gordon
      Expert ⭐️
      October 7, 2026

      I did this during our transition. 

      We communicated to our super users that x amount of days the community wouldnt transfer over. We manually moved over some content or double posted on 2 platforms until we went fully live on GS. 

      (We did manually move over solutions and any corporate communication during that timeframe*
       

      It did rub some new contributors the wrong way (their contributions didnt make it over) but as a whole, the community understood.

       

      Happy to expand on anything if youd like!

      Translate
        jocelyn92Author
        Contributor ⭐️⭐️
        October 19, 2026

        Thanks ​@mitchell.gordon for sharing your experience. 

        Translate
        Terms & ConditionsAccessibility statement