Illustration of an innkeeper showing her regulars a sketch of their new inn by the fire, with a stack of addressed letters ready on the bar.

How to Prepare Members for a Migration

How to prepare members for a community migration: what to tell them, who to tell first and when to email, plus an announcement post, three email templates and an FAQ you can copy.

By Founder, Jatra Updated
Talk through your move See plans

In 2011, I moved CrazyEngineers from vBulletin to XenForo. Google took it badly. Our traffic dropped about 40% and stayed down for six to seven months.

Our members took it well. We didn't lose a single active member. The regulars carried straight on in the new platform as if nothing had happened.

The difference was simple: Google had to work out the move on its own. Our members didn't. We told them why we were moving, what they'd get and what they'd lose.

Once members understand the need for a migration, they support it. That's the whole lesson of this guide. The rest is how to say it, when to say it and who to say it to first.

If you're still deciding whether to move at all, start with the community migration guide. This one assumes you've decided.

Most members won't follow you at first

Let me set your expectations, because this is the part that scares owners.

In my experience, when a community moves, typically about 10% of the active members show up on the new platform in the first few days. Sometimes it's 50 to 70%, but that's rare.

My own moves went better than most. When we moved from phpBB to vBulletin, about 70 to 80% of our active members came across, and the rest followed within a few months. They felt left out, because almost everyone was already on the new platform.

Don't let the 10% stop you. Stay on a platform that isn't working and you get 0%.

People don't skip your move because they disagree with it. They just don't see it. The biggest problem is discovery, and everything below is about solving it.

What to tell them

Four things, in plain words.

Why you're moving. The real reason, not a press release. "Our old platform hides everything behind a login, so nobody can find our answers on Google" is a reason. "We're excited to bring you a better experience" isn't.

What they'll get. Name the things they'll notice: faster pages, search that works, threads that show up on Google, no more lost answers.

What they'll lose. Be honest. If private messages, signatures or a feature they love won't come across, say so before the move, not after. People handle a known loss far better than a surprise.

What they need to do, and when. If they'll have to set a new password, tell them now, and tell them it takes a minute. Give them the date.

Tip: Don't dress it up as exciting news if it isn't exciting for them. Members can smell a marketing email from a mile away.

Tell your regulars first

Every community has a handful of people who answer most of the questions. You know their usernames by heart.

Tell them before anyone else, privately. Explain the why, show them the new place and ask what worries them. Their questions are the questions everyone else will ask, so they'll write half your FAQ for you.

Then give them early access. Nobody likes to be the first one in an empty room. I learned that in 2005, when I had to log in with five different accounts to get CrazyEngineers' first discussions going. When the rest of your members arrive, they should find their regulars already there, already posting.

Where to say it

Everywhere your members already look: a pinned post in the old community, a banner on every page, your newsletter, your product dashboard if you have one, and an email to every member.

The email matters most. The people most likely to drift away are the ones who've stopped logging in, and they'll never see your banner.

When to say it

Here's the order I'd follow.

A few weeks before: tell your regulars privately, then announce it publicly with a date. A few weeks, not a few days. People need time to ask questions.

A week before: a reminder email, and the FAQ pinned in both places.

Moving day: make the old community read-only, put a clear notice at the top that points to the new home, and send the "we're live" email with one simple first step.

Once the new community has life: email everyone who hasn't come back yet. This is the email most owners never send, and it's the one that works best.

The email most owners forget

DMTWorld moved from Discord to Jatra. In the first three or four months, only about 10% of their members came across, which is exactly what I'd expect.

Then the community found its feet. Members were posting and answering each other, and new people were finding it through Google. That's when the owners emailed their old member base again. About 20 to 25% of those old members became active.

The first email announced a move. The second email showed people a place that was already alive. That's what brought them back.

So don't send your last email on moving day. Wait until there's something to show: answered questions, busy threads, usernames people recognise. Then write to everyone who hasn't returned and show them what they're missing.

Templates you can copy

Change the words to sound like you. These are a starting point, not a script.

The announcement post

We're moving to a new home on [date]

After [X years] on [old platform], we're moving the community to [new platform].

Why: [the real reason, in one or two sentences].

What you'll get: [two or three things members will notice].

What you'll lose: [be honest; "nothing you've posted" if that's true].

What you need to do: nothing until [date]. On that day you'll get an email with a link. [If passwords don't carry over: you'll set a new password the first time you log in. It takes a minute.]

Questions? Ask them in this thread. I'll answer every one.

Email 1: we're moving

Subject: [Community name] is moving on [date]

Hi [first name],

Quick heads-up: on [date], [community name] moves to [new platform]. All the discussions, including yours, are coming with us.

We're moving because [the real reason].

You don't need to do anything yet. I'll email you on moving day with a link.

If you have questions, reply to this email or ask in [link to announcement thread].

[Your name]

Email 2: we're live

Subject: We're live. Here's the new [community name]

Hi [first name],

The new [community name] is live at [link].

Your account is ready. [Set a new password here: link. It takes a minute.]

Start here: [one thing to do, e.g. "say hi in the introductions thread" or "check the answer to the question everyone asked last month"].

The old community is now read-only, so nothing you posted is lost.

[Your name]

Email 3: look what's been happening

Send this one weeks later, only to members who haven't logged in yet.

Subject: [Name of a regular] answered [a real question] last week

Hi [first name],

It's been [X weeks] since we moved, and the new community is busy. A few things you might have missed:

  • [A real thread with a great answer]
  • [A new discussion in their area of interest]
  • [A name they know, and what that person has been posting]

Your account is waiting for you: [link].

[Your name]

The FAQ to pin

Your regulars will tell you the real questions. These come up every time:

  • Will I lose my posts? Say exactly what's coming across and what isn't.
  • Do I need a new password? If yes, say so plainly and link to the reset page.
  • Will my old links still work? If you've set up redirects, say yes. If you're not sure, find out before you answer. See forum URL mapping and 301 redirects.
  • What happens to the old community? Read-only, archived or deleted, and when.
  • Where do I report a problem? One thread, and someone who answers it the same day.

If you're moving to Jatra

We handle the migration with you, including the redirect plan and the member transition. Passwords carry over only when the old platform allows it. If they can't, we plan the sign-in and reset step so members know what to expect before moving day.

Plan the move with the free community migration planner, or talk to me about your migration.

Frequently asked questions

How far in advance should you announce a community migration?

A few weeks. Enough time for members to ask questions and for you to answer them, and not so long that people forget. Tell your regulars privately before the public announcement.

Should you email every member about a migration?

Yes, including the ones who haven't logged in for months. A banner only reaches people who still visit. Send a second email weeks later, once the new community is active, to everyone who hasn't come back.

How many members follow a community to a new platform?

In my experience, typically about 10% of active members in the first few days. More follow once the new community has visible activity and you email them again.

What should a migration announcement say?

Why you're moving, what members will get, what they'll lose, and what they need to do and when. Keep it plain and honest.

Planning a move? Plan your community migration with Jatra.

Plan your migration

Community builder since 2005.

Kaustubh Katdare

Founder, Jatra

A note from the founder

I write from the work, not the sidelines.

I'm Kaustubh Katdare. I've been building online communities since 2005, from growing CrazyEngineers to hundreds of thousands of members to creating Jatra. These articles draw on the work I still do myself: auditing platforms, planning migrations, protecting years of searchable knowledge, and helping community teams build something people want to return to.