How to Keep Your First 100 Users When the Community You Depend On Moves

When the forum you have been answering in disappears, your advantage travels with the people. The old comment history is a receipt. The list is the asset.

You have spent months doing the unscalable work: reading threads, replying in private, learning which questions signal a buyer. Now the community is moving platforms. If you treat that as a loss, you will start over. If you treat it as a migration, you keep the early users.

The people are the asset

The members who asked you questions, replied to your follow-up, and showed up in the right channel at the right time are still there. User engagement examples begin from observed user behavior, are timed to the moment, and use the appropriate channel.

67% of members say shared identity or values is why they join or stay. The group you built is a set of people who recognize each other. When the platform changes, the identity does not.

39% of builders are de-prioritizing raw member growth in 2026 to chase quality over quantity. Your job is to keep the people who already know your work.

Build the list before the move

Do not wait for the new workspace to be perfect. The archive is the thing to protect. Slack's free tier restricts message history, and Superpath risked losing 800,000+ messages from 23,000 members unless it upgraded to a $26,000-per-month enterprise plan. Export the old threads that prove your value. List the people now.

Salesforce announced at Dreamforce 2026 that its reimagined Trailblazer Community on Slack is planned for November 2026. The current online forums for the Trailblazer Community will shift into the Trailblazer Community on Slack. During onboarding, Trailblazers will choose interests and receive a customized set of Slack channels.

Slackbot is described as a guide for locating answers, channels, and Trailhead learning. An Answers Agent will let users ask questions and receive AI responses generated from the community's trusted knowledge. Salesforce is offering a virtual demo and feedback submission window that runs through September 30, 2026.

After the move, the channel is the product

The early days will feel noisy. That is normal. Use them to prove you still know the people. Answer the questions that used to come to you in the old forum. Routine questions can go to the automated answer. Questions about your product, your edge case, or your user's workflow need a person.

Do not send a mass message saying you are here. That kind of growth tactic needs scale to work. Your early users do not need a campaign. They need a reason to trust that you still understand their problem. Start with the people who have already shown you that problem.

When you re-introduce yourself, keep it short. Name the question you helped with. Point to the channel where the work is happening. Offer a next step. A person who already asked for help can get a reply. A person who has not can get a question about their current setup.

Keep the checklist portable

Use this before and after the move. Each item is a quick test, and each reason is the failure it prevents.

• Name the people who have asked you a question. Without names, outreach becomes a broadcast.
• Mark the 20% of free members who show consistent engagement and visible results. They are the ones worth re-contacting.
• Write down the forum-to-channel mapping. For a question that used to live in a category, note where it will land in the new channel set.
• Decide which questions get a human answer and which get an AI answer. Your early users expect a person.
• Draft a re-introduction message. It should name the question, the channel, and the next step.
• Check the archive risk. When the old history is capped, save the threads that prove your value.
• Set a reminder to re-run the list after the move. The new workspace will have new questions.