https://youtu.be/wjZn5ql1HIc?si=qJ9CiWqKOwdrLzJb

Case Study: Community Migration Strategy for Disability Support Nonprofit

Transforming a 1,300-Member Facebook Group Into a Thriving Website Forum Through Strategic Migration Planning

Client Overview

<aside> 📸

Project Snapshot

</aside>

<aside> ⚠️

The Challenge

</aside>

<aside>

The Challenge

Iris and Alma came to the consultation with what seemed like a straightforward technical question: how do we move people from Facebook to our website forum? But within the first ten minutes of our screen-share session, it became clear they were sitting on a much more complex problem disguised as a platform migration.

"We want to move a large group of people from Facebook to an online forum that lives on our website," Iris explained at the start of our call. "We want to see if you can maybe help us migrate about 1,300 people from Facebook to the forum, making sure that they are motivated to move to a new platform and start the conversations that they used to do on the Facebook group."

This wasn't just about moving people from Point A to Point B. This was about convincing bereaved parents, exhausted caregivers, and overwhelmed families—people already stretched thin managing children with disabilities—to learn an entirely new platform when Facebook was their comfort zone.

The Facebook Algorithm Crisis:

The migration wasn't a nice-to-have upgrade. It was an urgent necessity driven by Facebook's increasing dysfunction.

"Facebook blocks our access to some of our people," Iris explained with visible frustration. "So let's say I have a group of 700 people, the most of those people that I could reach with one post was 400 and something, which is kind of still almost just a half of the population on the group."

Think about that math for a moment. An organization running support services for families of children with disabilities could only reach 57% of their own community members with critical event announcements, resource sharing, or time-sensitive support. The other 43% simply never saw the posts—not because they weren't active, but because Facebook's algorithm decided those posts weren't worth showing them.

"Usually, if I share a post, it reaches only 100 people in my group, which is fairly sad because we have events that could easily host all 700 people, but we can't tell them that there is that event," Iris continued.

The Security Compromise:

The reach problem was bad enough. But Facebook had also started auto-approving members without human oversight.

"Now the Facebook AI is taking over who they approved to join the group, you know, before I even get the chance to see who is that person, how they answered the questions, membership questions, etc.," Iris explained. "The Facebook AI already decided to let them in. So, I am feeling that the security is compromised and the reach of our post is compromised on that Facebook group."

For a community built on trust—where parents shared vulnerable stories about their children's disabilities, medical challenges, and family struggles—security wasn't a nice-to-have feature. It was foundational. Facebook's AI removing human verification meant anyone could potentially access private conversations without proper vetting.

The Funding Justification Requirement:

Unlike most community platforms, 1in6support needed detailed demographic data to justify continued funding.

"In terms of running the nonprofit, we need to know people's address, we need to know people's phone numbers, etc., just so we can justify funding later on and say, yeah, we have 700 people in Michigan and 700 people in New Jersey," Iris explained when I asked about their registration requirements.

This created tension between user experience (simple signup = more conversions) and organizational necessity (detailed information = funding proof). Any migration strategy had to balance both.

The Two-Population Problem:

The community had two distinct segments requiring different approaches.

"We have two populations online," Iris explained. "One is the people that we meet face-to-face with and then we have maybe a little bit more influence on their behavior because we can kind of convince them in person to move from the Facebook group to the forum. But the other people that only know us online—how do we kind of provide coherent messaging and help them help us by moving to the forum on the website?"

The face-to-face members could be engaged directly at in-person events. But the online-only population—potentially hundreds of families who'd never attended a physical gathering—would need pure digital persuasion. No handholding. No personal relationship leverage. Just messaging that had to be compelling enough to overcome inertia.

The Year-Long Platform Investment:

By the time Iris and Alma reached out for help, they'd already invested a full year building their forum solution.

"To be honest with you, Edd, this has been like a work in progress for a year now, like just to adapt the forum and put it on the website and all that," Iris admitted when I suggested they might want to consider alternative platforms. "And I don't know, you know, in terms of our webmaster, if this specific platform was the best choice or not, but she had to choose something with a bunch of different specifications that we gave her, so at this point in the game, I think now that it's all kind of ready to launch, it would be hard."

They'd selected their forum platform specifically because it supported SEO (making conversations searchable and discoverable) and because the company was willing to customize features for their anonymity requirements. Parents needed the option to post anonymously when discussing sensitive medical or family situations.

But a year of development meant they were deeply committed. This wasn't a situation where we could scrap everything and start over. We had to work with what existed—and make it dramatically better before launch.

The Scope Reality Check:

Early in the consultation, I had to level-set expectations.

"I don't think that is within my capacity right now," I said when Iris asked if I could execute the entire migration during our consultation. "I think if it was someone in the scope of a one-hour call, they would be able to do that, but it's going to take some intense work. I think we probably need someone who can come here, actually. It's a minimum of two to four weeks to this project, so I recommend you go back to Catchafire and you use the long-term project option versus the consultation."

But even though full execution was beyond our consultation scope, I could do something valuable: audit their current setup, identify critical friction points, and provide a tactical roadmap they could implement immediately or hand to a long-term contractor.

"Okay, we can do that and hand it over to someone else for a long-term project," Iris agreed. "But do you have any insights, any thoughts or suggestions for us? Just during this short call in terms of how to go about doing it and how to convince people."

That's when we got to work.

</aside>

<aside> 💡

The Solution

</aside>

<aside>

The Solution

I conducted a real-time forum audit via screen share, testing the registration experience on both desktop and mobile, identifying user experience failures, and providing tactical fixes across onboarding, content strategy, technical optimization, and phased rollout planning.

The Mobile Catastrophe: Fixing the 90% Traffic Problem

The first thing I did was test their forum on my mobile device—and immediately found critical problems.

"I took a look at your website and it seems to be a bit more towards Disqus. I don't know which software you're using, but a couple of things I noticed is, first of all, it's not very user-friendly," I began. "Because I took a look at it from my mobile device and the majority of the audience is going to be coming in from mobile."

I shared my phone screen during the consultation so Iris and Alma could see exactly what I was seeing.

The Registration Nightmare:

When I clicked through to register, I encountered a single, endless form requiring:

• First name, last name, email
• Username, display name, password
• Avatar upload
• Relationship to disability
• Specific disability type
• How they heard about the organization
• Code of conduct agreement
• CAPTCHA verification

All on one scrolling page. On a mobile device.

"This is extensively long to register. No offense to you guys, but this is really long," I said, scrolling through the form on screen share. "What I will do is I will split it into maybe three forms, so maybe have the first one get up until maybe the avatar, and then the next one you can be like, hey, these are some important questions for us to understand you better and customize the experience."

The Three-Step Registration Fix:

I walked them through the restructured flow:

Step 1 - Credentials (fits on one mobile screen, no scrolling):

• First name, last name, email
• Username, password
• "Next" button to Step 2

Step 2 - Personalization:

• Relationship to disability
• Specific disability
• How did you hear about us
• "Next" button to Step 3

Step 3 - Agreement:

• Welcome message: "Thank you for filling in the details, before you join the community, here's our code of conduct"
• Full code of conduct text
• "By participating, you agree to honor these guidelines" checkbox
• CAPTCHA verification
• "Register" button

"You want to make it fit within the frame of the screen," I explained. "So all the details should try and fit in here. So that there's no scrolling, because the moment somebody is scrolling, what they do is they associate it with being tiresome or they associate it with being annoying."

This wasn't about making registration "easier" in some abstract sense. It was about removing the psychological friction that makes people abandon halfway through. Each additional scroll increases abandonment rate exponentially.

The Username Placement Problem:

One detail caught my attention immediately: the username and password fields appeared at the bottom of the form, after all the demographic questions.

"You need to move this section over here that says username and password and it needs to be up after the last name and email because people are already acclimatized to creating a username and a password after they fill in their first name, last name, and email," I instructed. "So when you have it at the bottom it's like I thought I did this before, it can be a bit confusing."

This might seem minor—does it really matter if username comes before or after disability type?—but user behavior patterns are deeply ingrained. Every form people have ever filled out online conditions them to expect username/password immediately after email. Breaking that pattern creates cognitive friction, even if people can't articulate why the form "feels wrong."

The Avatar Upload Confusion:

During the form review, Iris paused at the avatar upload section.

"Now that I'm looking at the registration form, can you just tell me something here? It says display name, that's okay, but there was something about the avatar, the default avatar or URL. Is there a place there to drop a picture?" she asked.

"Yeah, I think you'll have to click on choose file," I confirmed.

This revealed another problem: features that weren't immediately obvious. The "choose file" button existed, but users had to hunt for it. On mobile, that button could easily be missed entirely or dismissed as non-functional.

The Onboarding Crisis: What Happens After Registration?

After examining the registration process, I tested what happened after someone successfully created an account—and found an even bigger problem.

When new members first accessed the forum, they saw a list of empty topic categories:

• Apraxia </aside>

<aside>

</aside>

<aside>

</aside>

<aside>

</aside>