Facebook's algorithm was quietly locking 1in6support out of its own community.

Iris and Alma run 1in6support, a nonprofit supporting families of children with disabilities. Facebook's algorithm limited their reach to just 57% of a 700-person group, and its AI had started auto-approving new members without human vetting — a real security risk for a community where parents share vulnerable medical and family details.

The reach and security crisis

Posts about events that could host all 700 members often reached only ~100 people, while Facebook's AI approved new joiners before Iris could vet them against membership questions.

A mobile registration nightmare

The new forum's signup was a single endless scrolling form — name, username, password, avatar, disability details, and a CAPTCHA all on one mobile screen — a guaranteed abandonment trap.

The "ghost town" launch risk

Every topic category on the new forum was empty. A new member landing on zero conversations makes an instant judgment: nobody's here, so why bother.

A year already invested

The forum platform was chosen for its SEO support and custom anonymity features after a full year of development — starting over wasn't an option, so the fix had to work within what already existed.

A real-time mobile audit, then a phased migration blueprint.

I tested the forum live on my own phone during the screen-share, found the critical failures immediately, and built a tactical roadmap covering registration, onboarding, navigation, content seeding, and a phased ambassador-first rollout — while pointing them toward bringing in dedicated outside help for full execution.

Three-step mobile registration

Split the single endless form into credentials, personalization, and agreement screens, each fitting on one mobile view with no scrolling — and moved username/password back to where users expect it, right after email.

Welcome video + content seeding

A sub-3-minute welcome video popup mapping Facebook features to their forum equivalents, paired with seeded posts in every empty topic category to eliminate the "ghost town" first impression.

Single-menu navigation & memorable URL

Consolidated two competing nav menus into one, with the community forum highlighted in brand blue during migration, plus a clean bit.ly link replacing an unmemorable subdirectory path.

Phased ambassador rollout

Starting with the 10–15 most active Facebook members via Loom walkthroughs before mass-migrating, so bugs and confusion surface with forgiving ambassadors instead of all 1,300 members at once.

From launch anxiety to a controlled, data-driven rollout.

A complete tactical roadmap

Registration UX, onboarding, navigation, mobile fixes, phased rollout, and a 30-day messaging campaign — a full implementation plan instead of vague migration advice.

De-risked launch strategy

Iris and Alma left planning to test with 10–15 ambassadors first, replacing "launch to everyone and hope" with controlled, private failure before public scale.

Realistic conversion expectations

Set honest 50–80% conversion projections upfront, so the team wouldn't read a lower-than-hoped migration rate as failure.

A confident, positive client response

"You've been really helpful. You know what you're talking about," Iris said — with enthusiastic five-star feedback on the consultation to follow.

Test First, Then Strategize

Iris and Alma came asking how to convince people to migrate. The real need was an audit identifying exactly where the friction lived — then tactical fixes for each point.

Scope honesty over overpromising.

Full execution needed a two-to-four-week engagement with dedicated outside help, not a one-hour call — so the consultation delivered the audit and roadmap, then pointed to the right next step.

Tools and Platforms I Applied

Every tool matched a specific migration risk — mobile failure, empty content, or unrealistic launch expectations.

MT
Real-time mobile device testing

Loaded the forum on my own phone during the screen-share to make abstract UX problems concrete and immediately visible.

AR
Phased ambassador rollout plan

A three-phase migration structure (10–15 core, 20–30 extended beta, then full launch) enabling controlled testing before scale.

ChatGPT
ChatGPT content-strategy prompting sequence

A step-by-step method for feeding organizational context to AI and generating an initial migration messaging strategy for free.

CS
Content seeding framework

Pre-populating every empty forum topic with transferred Facebook posts and starter questions to remove the "ghost town" first impression.

Certifications That Informed This Strategy

Six certifications, chosen for direct relevance to the friction-removal, growth-testing, and content work behind this migration blueprint.

HubSpot Inbound

Directly informed the three-step registration redesign and welcome video — removing friction between interest and participation.

Meta Blueprint: Facebook and Instagram

Informed the social-proof and urgency tactics recommended for the 30-day migration messaging campaign.

HubSpot Growth-Driven Design Agency

Shaped the phased ambassador rollout — test with a small group, fix privately, scale only once proven.

HubSpot Content Marketing

Informed the content-seeding recommendation — populated forums feel inviting, empty ones feel intimidating.

Google Ads Mobile Certification

This mobile-optimization training is what reinforced the mobile-first prioritization behind the registration redesign — most real traffic arrives on mobile, not desktop.

LinkedIn Learning: Create a Brand Strategy

Guided the positioning framing — presenting the new forum as an upgrade to embrace, not a loss to mourn.

Most migrations fail from being backwards, not from bad platforms.

If your nonprofit manages a large Facebook community and feels the algorithm actively working against you — suppressed reach, auto-approved unvetted members, no ownership of your own audience — 1in6support's situation should feel familiar. The instinct is usually to build the new platform, announce it, and hope people follow, which is exactly backwards.

The real barriers are almost always the same: a broken mobile experience where 90% of your traffic actually lands, an empty platform that reads as abandoned, and no controlled way to catch problems before your whole community sees them. Fix those first, and the messaging campaign becomes the easy part.

Built a community platform nobody's using yet?

I can audit the real migration pathway — mobile experience, onboarding, and a phased rollout plan that turns passive Facebook lurkers into active contributors.

A year of forum development, one launch away from becoming a ghost town.

Without Edd

  • An endless single-scroll signup form keeps losing mobile users before they ever join
  • Every empty topic category tells new members "nobody's here" the moment they arrive
  • The whole 1,300-member community migrates at once, with no forgiving group to catch bugs first
  • Facebook's algorithm keeps auto-approving unvetted members into a community sharing sensitive family details

What Actually Happened

  • A three-step mobile registration flow replaced the endless scrolling form
  • Seeded posts and a welcome video eliminated the ghost-town first impression
  • A phased ambassador rollout with 10-15 members surfaced bugs before the full community saw them
  • Iris and Alma left with a full tactical roadmap and honest 50-80% conversion expectations