- Yes, with hosting matched to the job. WordPress runs sites far larger than that; the work is in the setup, which means object caching, a properly indexed database and a host that expects the traffic. It is a real engineering task rather than a checkbox, and it is the honest cost of leaving a managed platform.
- Implementation services, an account manager, a contractual SLA and single sign-on integrations built for enterprise IT. Those are services, not features, and they are most of what the contract price buys. If your organisation needs a vendor to hold accountable, that gap is the whole decision.
- Hivebrite exports members and events as CSV, which imports into WordPress cleanly. Check your contract for the data clause before you start, because notice periods and export windows tend to govern the schedule far more than the technical work does.
- BuddyNext for the community and member profiles, Listora for the directory, Eventonomy for events, WP Career Board for the job board and Learnomy for courses. All five install free, and each has a paid plan you take only when that specific part of the site earns it.
- Yes, and it is mostly operational rather than technical. You take on responsibility for uptime, updates, backups and security that the contract used to cover. Budget for someone to own that, whether in-house or on retainer, and the saving is still substantial. Skip it and the saving is an illusion.
- WordPress supports SAML and OAuth through established plugins, so university or corporate SSO is achievable. It is configuration work rather than a checkbox, and it is worth scoping properly with your IT team before you commit to a timeline, because this is usually the longest technical item.
- WordPress custom fields handle arbitrary member data, and BuddyNext exposes extended profile fields for the community side. The care goes into mapping your existing Hivebrite fields before importing rather than after, because cleaning up a bad import of 50,000 records is considerably worse than planning it.
- You do, or a partner you retain. That is the honest difference from an enterprise contract and it should be budgeted rather than assumed away. Wbcom offers support on the products, but it is product support, not a managed service with an SLA attached.
- Hosting is the running cost people forget to budget. A small community runs comfortably on shared or entry-level managed WordPress hosting for a few hundred dollars a year. Past a few thousand active members you want managed hosting with object caching, which is more like $50 to $100 a month. That is still an order of magnitude below a $15,000 to $50,000 annual contract, and unlike a subscription it buys you infrastructure you control rather than access you rent.
- With the three-year total and an honest account of what you are taking on. The licence and hosting against the contract is the easy half. The harder half is naming who owns uptime, updates and security afterwards, and budgeting for them. A proposal that shows the saving and ignores the operational transfer will not survive scrutiny, and should not.