Fluent Community Migration — Viability Assessment
Status: Research complete. WPManageNinja response received 2026-05-14. All gaps confirmed. Phase 1 viable; Phase 2 blocked pending FC roadmap delivery. Scope: practice.baseworks.com — community, courses, forums, video delivery Initiated: 2026-05-14 (Patrick + Claude Code, Patrick’s Mac)
What We Are Evaluating
Section titled “What We Are Evaluating”A migration from the current practice.baseworks.com stack to Fluent Community as the primary platform, with Bricks Builder replacing Elementor for page customization.
Current stack:
- LearnDash — course delivery
- BuddyBoss Platform + BuddyPress — community (groups, activity feeds, profiles, DMs)
- bbPress — forum/discussion layer
- Presto Player + Bunny Stream — video hosting and delivery
- WP Fusion — tag-based access control for courses and groups
- FluentCRM (on crm.baseworks.com) — CRM, connected via WP Fusion
- Uncanny Automator — cross-plugin automation
- Elementor — page customization inside BuddyBoss
Proposed stack:
- Fluent Community — community (spaces, feeds, DMs, group chat) + courses (Phase 2)
- LearnDash — courses (Phase 1 only, then phased out when FC course feature is viable)
- Bricks Builder — page customization for everything outside the FC portal
- Presto Player + Bunny Stream — retained for video delivery (Phase 1); FluentPlayer (Phase 2, pending launch)
- WP Fusion — retained, FC integration confirmed
- FluentCRM — retained, native FC integration (first-party)
- Uncanny Automator — retained, FC integration confirmed (10 triggers, 7 actions)
- Fluent Forms — replaces Formidable Forms (stronger fit for Fluent ecosystem)
Related active plans:
- buddyboss-forum-cli-notification-fixes — recently implemented BuddyBoss forum CLI fixes; these become irrelevant post-migration
- buddyboss-mention-notifications-via-wp-cli — same; partially resolved but moot if we migrate
- community-forums-consolidation-plan — executed 2026-04-14; consolidation decisions will inform which forums/groups are worth migrating
Architecture Note: FC is a React SPA
Section titled “Architecture Note: FC is a React SPA”Fluent Community’s portal (/portal URL) is a Vue.js 3 single-page application — not a collection of WordPress pages. This has three practical consequences:
- Bricks Builder cannot design the portal interior. Bricks handles the chrome around the portal (header, footer, landing pages, marketing pages) in “classic mode.” The feeds, spaces, courses, member profiles inside the portal are owned by Vue.
- Standard WP-CLI post commands are blind to FC content. FC stores all community posts, space posts, and course lessons in custom
wp_fcom_*tables, notwp_posts. Any existing CLI scripts targetingwp post list,wp bbp, orwp buddybossneed to be rewritten against FC’s PHP classes (wp eval) or direct SQL on the custom tables. - Standard translation plugins (TranslatePress, WPML, Polylang) may not work cleanly. See Multilingual section below.
Phase 1 — Community Migration (Viable Now)
Section titled “Phase 1 — Community Migration (Viable Now)”What migrates via the official BuddyBoss migration tool (WP-CLI)
Section titled “What migrates via the official BuddyBoss migration tool (WP-CLI)”| Data | Status |
|---|---|
| BuddyBoss groups → FC Spaces | Migrates (Public/Private/Secret tiers preserved) |
| Member accounts | Migrates |
| Activity feed posts, comments, reactions | Migrates |
| Media attachments | Migrates (added FC v1.8.0) |
| Followers | Migrates (bug fixed in FC v2.3.0) |
What does NOT migrate via the official tool
Section titled “What does NOT migrate via the official tool”| Data | Status |
|---|---|
| Direct/private messages | Not migrated — confirmed absent from migration docs |
| bbPress forum content (topics, replies, tags) | Not migrated — no official tool exists |
| Profile pictures / space images | Not migrated — explicitly excluded |
| Profile field data beyond basic account info | Not addressed |
Phase 1 course presentation
Section titled “Phase 1 course presentation”LearnDash courses stay at their own URLs, built with Bricks Builder as currently done on practice.baseworks.com. FC’s course module is disabled or unused. The FC navigation menu (supports custom links) gets a “Courses” item pointing to the existing custom Bricks-built course index page. FluentCRM tags + Uncanny Automator bridge the two: completing a LearnDash course → tag applied → grants access to the corresponding FC space.
bbPress Forum Migration — Manual Path
Section titled “bbPress Forum Migration — Manual Path”No official bbPress → FC migration tool exists. The official tool covers BuddyPress/BuddyBoss only. A manual migration is feasible but is custom scripting work (~200–400 lines PHP/WP-CLI).
Data model mapping:
| bbPress | Fluent Community | Notes |
|---|---|---|
forum post type | wp_fcom_spaces | One forum = one Space; nested subforums must be flattened |
topic post type | wp_fcom_posts | Title, content, author ID, date map directly |
reply post type | wp_fcom_post_comments | Content, author, date, parent ID map directly |
topic-tag taxonomy | wp_fcom_terms (taxonomy = post_topic) + wp_fcom_term_feed | Each tag → FC term; each topic-tag relationship → term_feed row |
| Sticky topics | wp_fcom_posts.is_sticky = 1 | Mappable |
| Topic subscriptions | wp_fcom_notification_users | Complex; most teams drop these |
| Closed/locked topics | No equivalent | Must be stored in meta JSON blob or excluded |
What would be lost even with a well-built script:
- Closed/locked topic state
- Subforum hierarchy (FC has no sub-spaces — must flatten or use Space Groups)
- Topic subscriptions (complex to reconstruct)
- Voting data (if using a bbPress voting plugin)
- Revision history
- User favourites
- Author IPs
Decision needed before scripting: How to handle subforums (flatten vs. archive) and closed topics (import as open posts vs. exclude). These choices drive the script structure.
Since bbPress is on the same WordPress install as FC, user IDs map directly — no user remapping required.
Blocking Gaps for Full Course Migration (Phase 2)
Section titled “Blocking Gaps for Full Course Migration (Phase 2)”These features are absent from Fluent Community’s current course module. Phase 2 is not viable until they ship.
| Requirement | FC Status | Notes |
|---|---|---|
| Video completion gating (must watch before “Complete” activates) | Not supported | Feature requested; no roadmap ETA |
| Sequential/linear lesson progression (completion-gated) | Not supported | Drip is time-based only, not completion-gated |
| Assignment submission + instructor grading | Not supported | Feature requested July 2025; no response |
| FluentPlayer public launch | Not yet released | Still waitlist-only as of 2026-05-14 |
Feature Comparison
Section titled “Feature Comparison”| Feature | Current Stack | Fluent Community | Verdict |
|---|---|---|---|
| Linear course progression | LearnDash — yes | Not available | Keep LearnDash |
| Free/self-paced progression | LearnDash — yes | Yes | Migrates (if course moves to FC) |
| Video completion gate | Presto Player + LearnDash | Not available | Keep LearnDash |
| Quiz with pass-gate | LearnDash — yes | Yes (FC v1.7.0+) | Migrates |
| Assignment grading | LearnDash — yes | Not supported | Keep LearnDash |
| Public/hidden/secret groups | BuddyBoss — yes | Yes (3 tiers) | Migrates cleanly |
| Group/activity feeds | BuddyBoss — yes | Yes | Migrates cleanly |
| Threaded forums (bbPress) | bbPress — yes | No equivalent | Content archived; see above |
| Forum shortcodes in lessons | bbPress — yes | No shortcodes | No equivalent |
| 1-to-1 direct messaging | BuddyBoss — yes | Yes | Migrates (content doesn’t transfer) |
| Group messaging | BuddyBoss — yes | Yes (FC v2.4.0) | Migrates |
| On-site notifications | BuddyBoss — yes | Yes, real-time, granular | Migrates |
| Email notifications + digest | BuddyBoss — yes | Yes | Migrates |
| Tag-based group access (WP Fusion) | BuddyBoss — yes | Yes — confirmed | Migrates cleanly |
| Lesson-level WP Fusion gating | LearnDash — yes | Not supported in FC | Keep LearnDash |
| FluentCRM automation | Via WP Fusion | Native, first-party | Improves |
| Uncanny Automator | Partial | 10 triggers, 7 actions | Improves |
Plugin Stack
Section titled “Plugin Stack”| Plugin | Status |
|---|---|
| Fluent Community | Core platform — replaces BuddyBoss + bbPress |
| LearnDash | Keep for Phase 1 — FC cannot replace it yet |
| Bricks Builder | Compatible with FC (CSS fix required — see below) |
| FluentCRM | Native FC integration, first-party |
| Fluent SMTP | No conflict |
| WP Fusion | Confirmed FC integration — space/course level only (not per-lesson) |
| Uncanny Automator | Confirmed — 10 FC triggers, 7 actions |
| Presto Player | Keep for Phase 1; no native FC integration; no path to native integration (FC’s strategic direction is FluentPlayer) |
| Fluent Forms | Strong fit — replaces Formidable Forms; native FluentCRM + FC integration; Bricks element via BricksExtras |
| Formidable Forms | Weak fit for this stack — no native Fluent ecosystem connections; replace with Fluent Forms |
Bricks Builder + FC CSS fix: FC uses CSS cascade layers internally. Bricks 2.0 also uses @layer bricks. These conflict on portal-adjacent pages. Install “Plus for FluentCommunity” (Jeff Brigman) to resolve. Bricks cannot design the portal interior — only the chrome around it (header, footer, landing pages).
Video and CDN
Section titled “Video and CDN”Recommendation: keep Bunny Stream and Presto Player for Phase 1.
- Presto Player has a confirmed native Bunny Stream integration (Pro)
presto.playerEndedJS hook fires on every video completion — the correct primitive for gating- Uncanny Automator “A user completes a video” trigger (Unlimited runs) → “Mark FC lesson complete” is a documented, working recipe
- Bunny Stream is significantly cheaper than Cloudflare Stream at any meaningful library size (Cloudflare charges per minute stored — punishing for large libraries)
- Neither Bunny nor Cloudflare provide server-side “user watched to 100%” webhooks — both require client-side JS event listeners
FluentPlayer: Still waitlist-only. Video completion gating is a community feature request, not a shipped capability. Revisit when it launches publicly and hooks are documented.
Tagging and Search
Section titled “Tagging and Search”FC has two separate systems — neither fully matches bbPress’s taxonomy archive behaviour:
| bbPress topic tags | FC Topics (Pro only) | FC Hashtags (free) | |
|---|---|---|---|
| Type | WordPress taxonomy | Admin-curated per space | Freeform user-typed |
| Scope | Site-wide archive pages | Per-space filter only | Search bar (scope unclear) |
| Cross-space browsing | Yes — archive URLs | No | Not confirmed |
| Clickable filter | Archive page | Filters current space feed | Not confirmed |
bbPress tag archive pages (standard WP taxonomy, SEO-indexed, REST API) do not have a direct equivalent in FC. FC Topics (Pro) are in-space filter tabs inside the SPA. A meaningful reduction in cross-space discoverability — worth raising with WPManageNinja.
Multilingual
Section titled “Multilingual”FC is translation-ready (standard WordPress i18n, 11 locales on WordPress.org) but has no built-in language switcher and no per-user account language preference.
GTranslate (confirmed working approach):
- Free tier: full language switcher widget (flags, dropdown, globe — embeddable via
[gtranslate]shortcode, in menus, or via CSS selector; also injectable into the FC portal header viafluent_community/before_header_menu_itemsPHP hook) - Free tier: machine translation only — no editing of strings
- Pro (~$9.99/month): neural translation + in-context editing of specific strings
- Language preference: stored in browser cookie/localStorage — not tied to a WordPress user account. A user switching language on one device will revert to default on another device.
- One community member confirmed it works on the FC React SPA (DOM scanning approach catches dynamically rendered content)
Limitations: No clean per-user-account language switching (profile-level, cross-device) without Multisite. TranslatePress/WPML/Polylang are unconfirmed with FC’s React SPA. This is the weakest area of the platform for Baseworks’s multilingual requirements.
WP-CLI Impact Post-Migration
Section titled “WP-CLI Impact Post-Migration”| Command type | After FC migration |
|---|---|
wp user list, wp user get | Still works — users stay in wp_users |
wp post list, wp post get | Blind to FC content — FC uses wp_fcom_posts, not wp_posts |
wp bbp * | Irrelevant — bbPress removed |
wp buddyboss * | Irrelevant — BuddyBoss removed |
wp db query "SELECT * FROM wp_fcom_posts ..." | Full access — direct SQL on custom tables |
wp eval "..." | Full access via FC’s PHP classes |
wp fluent-community * | Likely exists (FC registers WP-CLI for migration tool) — full command surface unclear |
Existing CLI scripts from buddyboss-forum-cli-notification-fixes and buddyboss-mention-notifications-via-wp-cli will need to be rewritten against FC’s data model if similar automation is needed on the new platform.
Recommended Phases
Section titled “Recommended Phases”Phase 1 — Community migration (viable now)
Section titled “Phase 1 — Community migration (viable now)”- Deploy FC alongside the existing stack on staging (
staging.baseworks.com) - Run BuddyBoss migration via WP-CLI → validate spaces, members, posts, media
- Archive bbPress forums (export to static HTML or read-only format) — no migration path
- Wire WP Fusion tag rules to FC spaces, replacing BuddyBoss group access rules
- Replace Elementor with Bricks Builder on portal-adjacent pages; install “Plus for FluentCommunity”
- Switch Formidable Forms → Fluent Forms
- Push to production once validated on staging
LearnDash, Presto Player, and Bunny Stream stay exactly as they are. FC’s course module stays off. FC and LearnDash run in parallel on the same install without conflict.
Phase 2 — Course migration (blocked)
Section titled “Phase 2 — Course migration (blocked)”Requires FC to ship: video completion gating, sequential lesson progression, assignment grading, and FluentPlayer in a production-ready state with documented hooks. Not on a confirmed near-term roadmap. Revisit based on WPManageNinja’s response to the support inquiry.
Support Ticket Sent to WPManageNinja — 2026-05-14
Section titled “Support Ticket Sent to WPManageNinja — 2026-05-14”Two messages sent on the same day. Response received same day.
Message 1
Section titled “Message 1”We’re evaluating a migration from BuddyBoss Platform, bbPress, and LearnDash to FluentCommunity, and we have a set of specific questions before committing to a timeline. We’ve done a thorough stack analysis on our end and want to confirm a few things directly with you.
About our current setup: Our platform runs LearnDash for course delivery, BuddyBoss Platform + bbPress for community and forums, Presto Player with Bunny Stream video hosting, and WP Fusion + FluentCRM + Uncanny Automator for access control and automation. We’re planning to move to Bricks Builder as our page builder. Video completion tracking is a core requirement — specifically, a user must watch a video fully before being able to mark a lesson as complete.
Q1. FluentPlayer — launch and video gating What is the current status of FluentPlayer, and when is a general public release expected? We’ve seen it in waitlist mode for some time. More specifically: is video completion gating — where a user must watch a video to completion before the “Mark Lesson Complete” button activates — on the roadmap? If so, what is the expected timeline?
Q2. Course progression Does FluentCommunity have a sequential/linear lesson progression mode — where completing one lesson unlocks the next — or is that also planned? The current drip mode is time-based, which doesn’t satisfy our requirement.
Q3. Assignment grading Is assignment submission with instructor grading (both graded and ungraded, with the option to require grading before progression) planned for FluentCommunity courses?
Q4. LearnDash coexistence and integration Our plan for an initial phase is to run FluentCommunity for community only, with LearnDash handling all course delivery. The two would connect via FluentCRM tags and Uncanny Automator. Is there anything in FluentCommunity’s architecture that would conflict with LearnDash running in parallel on the same install? And is a native LearnDash ↔ FluentCommunity bridge — beyond tag-based automation — on your roadmap?
Q5. bbPress forum content migration The official BuddyBoss migration tool covers groups, members, and activity feeds. It does not appear to cover bbPress forum content — topics, replies, and topic tags. Is there an official path for migrating bbPress content into FluentCommunity? If not, what would a manual migration look like at the database level? We want to understand whether this is a scripted export/import exercise or something that requires custom development.
Q6. WP Fusion — lesson-level access control WP Fusion’s FluentCommunity integration currently controls access at the space and course level, but not at the individual lesson level. Is lesson-level tag gating something you expect WP Fusion to support, or would that require a FluentCommunity-side change?
Q7. Presto Player We currently use Presto Player for video delivery and its LearnDash integration for video progression gating. We understand a native Presto Player ↔ FluentCommunity integration is not currently supported. Is that integration planned, or is the expectation that FluentPlayer replaces this use case entirely once it launches?
Q8. Multilingual — per-user language switching We serve participants in multiple languages and need users to be able to choose their language preference without running WordPress Multisite. GTranslate appears to be the only community-confirmed workaround, operating via a client-side JS overlay. Is per-user language preference (saved to a user profile, consistent across devices) on your roadmap for FluentCommunity?
We’re genuinely interested in the platform. These are the specific gaps between what FluentCommunity offers now and what our platform requires to complete a full migration.
Patrick
Message 2
Section titled “Message 2”Hi again — a few additional questions that came up as we were mapping out the migration in more detail:
Q9. WP-CLI command surface for FC content
We currently use WP-CLI extensively for community management on the practice site (querying posts, managing group memberships, running automation scripts). Since Fluent Community stores its content in custom wp_fcom_* tables rather than wp_posts, standard post commands won’t apply. Does Fluent Community have a documented wp fluent-community command suite beyond the migration tool? And what is the recommended approach for scripting things like bulk space membership changes or querying course enrollment data via CLI — wp eval against FC’s PHP classes, or direct SQL on the custom tables?
Q10. Topic tags — cross-space filtering We noticed that the Topics feature (Pro) filters posts within a single space only. Is there a plan to support cross-space topic browsing — where clicking a topic shows all posts with that topic across the full community, similar to how bbPress tag archive pages work across all forums? And separately, do hashtags (#tag style) produce any clickable cross-space feed, or are they search-only?
WPManageNinja Response — 2026-05-14
Section titled “WPManageNinja Response — 2026-05-14”Hello Patrick,
Thank you for the detailed breakdown.
Based on the current FluentCommunity supported feature set, here is the clearest picture we can confirm at this time:
Q1 — FluentPlayer: The plugin is currently in beta, and an official release date will be announced soon. However, there is no video-completion gating workflow where a learner must watch the full video before the “Mark Lesson Complete” action becomes available.
Q2 — Course progression: FluentCommunity courses currently support Self-Paced, Structured, and Scheduled modes. Structured mode is drip-based. There is no strict sequential prerequisite progression (e.g., complete Lesson A before Lesson B unlocks). Docs: https://fluentcommunity.co/docs/creating-and-managing-course/
Q3 — Assignment grading: No full assignment submission and instructor grading workflow comparable to LearnDash-style graded progression at this time.
Q4 — LearnDash coexistence: Running FluentCommunity and LearnDash on the same WordPress installation is generally possible with no known conflicts. There is no native LearnDash ↔ FluentCommunity bridge beyond external automation, CRM, or tag-based workflows.
Q5 — bbPress content migration: The official migration covers BuddyBoss-related data (groups, members, posts, comments) only. No official bbPress migration path. Docs: https://fluentcommunity.co/docs/fluentcommunity-buddyboss-migration/
Q6 — WP Fusion lesson-level access: No built-in lesson-level tag gating confirmed. If WP Fusion supports only Space and Course-level access, lesson-level restriction would require custom development or additional integration support.
Q7 — Presto Player: No native Presto Player ↔ FluentCommunity integration. Community workaround: https://community.wpmanageninja.com/portal/space/community-meta/post/how-we-used-presto-player-on-fluent-community
Q8 — Multilingual / per-user language preference: No built-in per-user language preference system across devices.
Q9 — WP-CLI command surface: The only clearly documented WP-CLI command is wp fluent_community migrate_from_bb. No publicly documented full CLI suite. Recommended approach for automation and scripting: developer APIs and hooks at https://dev.fluentcommunity.co/getting-started
Q10 — Topics / cross-space filtering: Topics are currently space-scoped. No global cross-space topic archive/feed (comparable to bbPress tag archives) is currently available. Docs: https://fluentcommunity.co/docs/manage-topic/
In summary, FluentCommunity already covers a significant part of the community/course stack, but several LMS-grade progression, grading, migration, and global discovery features you listed are not currently available as built-in functionality.
For roadmap-specific commitments, we recommend confirming directly with the product team via the official roadmap: https://community.wpmanageninja.com/fluentcommunity-roadmp/#/24/
Assessment After Response
Section titled “Assessment After Response”The response confirms all gaps identified in the stack analysis above. No answers changed the Phase 1 / Phase 2 split. Key takeaways:
- Phase 1 (community migration) remains viable — LearnDash coexistence confirmed, no architectural conflicts
- Phase 2 (course migration) remains blocked — video completion gating, sequential progression, and assignment grading all unconfirmed as roadmap items with ETAs
- bbPress migration — no official path confirmed; manual scripting remains the only option
- FluentPlayer — still beta, no release date, no video gating; Presto Player + LearnDash stays for Phase 1
- WP-CLI — only the migration command is documented; all automation will require
wp evalagainst FC PHP classes or direct SQL - Cross-space topic browsing — not available; a meaningful reduction in forum discoverability vs. the current bbPress setup
Related
Section titled “Related”- Practice Platform — practice.baseworks.com overview
- Community Forums & Groups — current forum/group structure
- buddyboss-forum-cli-notification-fixes — recently implemented BuddyBoss CLI fixes (become irrelevant post-migration)
- buddyboss-mention-notifications-via-wp-cli — partially resolved; moot post-migration
- community-forums-consolidation-plan — executed 2026-04-14; informs which content is worth migrating