How this WordPress alumni management plugin actually works
AlumniCore stores alumni records in a custom indexed database table, not repurposed WordPress posts or a generic directory plugin’s schema. That distinction matters the moment an institute has a real alumni base: a few hundred records will run fine on almost anything, but a searchable, filterable directory of 5,000 or 10,000+ profiles needs a database actually built for that scale, or search and filtering slow to a crawl exactly when the institute needs it most — homecoming, a reunion announcement, an admissions campaign referencing past graduates.
Alumni self-register through a front-end form, and every new registration sits in an admin approval queue until someone at the institute confirms it — so the public directory only ever shows records the institute has actually reviewed, not anything anyone typed into a form.
The three ways institutes currently solve this — and where each one breaks
Before AlumniCore, institutes generally end up in one of three places. Stitching together generic WordPress plugins — a business directory plugin, a user-frontend plugin, a membership plugin for gating access — works at first, until a migration of thousands of legacy records is needed, or the directory plugin’s database (built for a handful of business listings, not a searchable alumni base) starts timing out under real load. A standalone alumni application outside WordPress — a separate Laravel or CodeIgniter script bolted onto the main site — solves the scale problem but creates a new one: separate login, separate database, separate hosting considerations, separate everything. The website and the alumni portal stop being one thing an institute actually manages as a single system. Paying an agency for a fully custom build gets exactly what was asked for, once — but every feature added afterward, a new field, a new filter, an events add-on, is a fresh invoice and a fresh wait.
AlumniCore is a WordPress alumni management plugin built to avoid all three failure modes at once: it runs inside the existing WordPress site (one login, one theme, one hosting bill), it’s built for alumni data specifically rather than repurposed from a generic directory tool, and new capability arrives as an upgrade, not a fresh development invoice.
Migrating from a legacy system without months of manual re-entry
Why a custom indexed database actually matters at this scale
A generic WordPress directory plugin, or an alumni list built on standard WordPress posts, is built to hold dozens or a few hundred entries comfortably. An alumni directory plugin for WordPress needs to hold thousands, sometimes tens of thousands, and still return a filtered search — by batch, by year, by department, by city — in the time a visitor is willing to wait. AlumniCore’s database is indexed specifically for this: batch, year, department, and location are indexed columns, not custom fields buried inside a generic post-meta table that was never designed for filtered search at volume. The difference is invisible on a 200-record test site and very visible the day an institute’s real alumni base goes live.
Most institutes adopting a real alumni CRM for WordPress aren’t starting from zero — they’re migrating years of records out of a legacy spreadsheet, an old standalone system, or a platform like AlmaShine. AlumniCore’s CSV import includes an AlmaShine-mapped template specifically so that migration is a mapped import, not a manual re-entry project spanning weeks. A department or institute that has been maintaining alumni records in whatever system was available five or ten years ago doesn’t need to choose between keeping that history and adopting something better.
Privacy controls that don’t require a separate plugin
A public alumni directory raises an obvious question immediately: how much of an individual’s information should actually be visible to the public internet, versus visible only to fellow alumni, versus not shown publicly at all? Alumni management plugins built by repurposing a generic directory tool typically need an additional plugin bolted on just to answer this. AlumniCore includes privacy-controlled profile visibility as a core part of the plugin itself — alumni decide what’s visible to the public directory versus visible to fellow alumni only, without the institute needing to configure or maintain a second, separate privacy plugin alongside it.
Free, Pro, and Pro Max: what’s actually in each tier
Free: a real directory for a small department or single batch
AlumniCore’s free tier — available on WordPress.org — is not a crippled trial. It’s a genuinely usable alumni database and searchable directory, capped at 200 records, aimed at a small department or a single graduating batch that wants a real system before an institute-wide rollout. The custom indexed database, self-registration, and admin approval workflow are all present in the free version, not held back to force an upgrade.
Pro: the full system of record
Pro removes the record cap entirely and is the tier most institutes running this as their actual alumni system of record land on. Full batch, year, and department filtering, privacy-controlled visibility, CSV migration with the AlmaShine-mapped template, unlimited admin exports, and portal publications for announcements and newsletters — everything an institute needs to treat this as the real alumni database, not a small pilot.
Pro Max: events, jobs, chapters, and fundraising
Pro Max is built for institutes ready to run more than a directory — event RSVPs, a job board connecting alumni with opportunities, WhatsApp and email campaign tools for reaching alumni directly, city and regional chapter grouping for institutes with alumni spread across multiple cities, and donation or fundraising tracking alongside reunion and multi-batch tooling. This is the tier built for the mid-size and large institutes running full alumni-relations programs, not just a directory page.
Built for the way institutes actually roll this out
Most institutes don’t launch with the full feature list on day one — and AlumniCore ships in the same phased shape real institutes actually use it in. Start with the directory, migration, registration, and privacy controls. Add events, the job board, and campaign tools when the institute is ready for them. Add chapters, fundraising, and reunion tooling once the alumni base is engaged enough to need them. Same install throughout — no re-platforming, no migrating to a different system when the institute’s needs grow.
Where the alumni data actually lives
AlumniCore does not receive, store, or have any access to an institute’s alumni records — nothing about the database is ever transmitted to PolyBright’s servers. Every record lives inside the institute’s own WordPress database, on the institute’s own hosting, under the institute’s own control. The plugin’s only outbound connection at all is a small, periodic license check — the license key, the site’s domain, and the plugin version, used purely to confirm the license is valid and check for updates. For alumni data specifically, where an institute is responsible for genuinely personal information about thousands of real people, keeping that data on infrastructure the institute already controls — rather than a third-party alumni-management SaaS platform — is not a minor technical detail; it’s the difference between the institute owning its own alumni relationships and renting access to them.
Who this alumni portal plugin for WordPress is actually built for
A single department or a small school with a few hundred alumni gets a real directory on the Free tier without committing to anything. An institute running this as its actual system of record — the case most colleges and universities land in — belongs on Pro, with unlimited records and full migration support. An institute running a genuine alumni-relations program, with events, fundraising, and multiple regional chapters, is what Pro Max is built for.
Common situations this actually solves
An institute has alumni records scattered across a decade of spreadsheets, a discontinued platform export, and a stack of physical forms nobody digitized: CSV import consolidates what’s digital, and the admin approval workflow means self-registered alumni fill in the rest over time rather than requiring a single massive data-entry project before launch. A department wants to pilot an alumni directory before asking the wider institute to commit budget: the Free tier runs a genuine 200-record pilot with the real database and real search, not a stripped demo that has to be rebuilt later. An institute is planning its first reunion in years and doesn’t know how many alumni from a given batch are even reachable: batch and year filtering surfaces exactly that group, and — on Pro Max — the reunion tooling and campaign features reach them directly. An alumnus reports their profile shows a phone number they’d rather keep private: privacy-controlled visibility lets them adjust what’s public versus fellow-alumni-only themselves, without a support ticket to the institute’s IT department.
Frequently asked questions
Does this replace our existing website theme? No. AlumniCore is theme-independent — it works alongside whatever design the institute’s site already has.
Can we migrate from our current system? Yes — CSV import is built to handle exports from legacy platforms, including an AlmaShine-mapped template specifically for that migration.
Is our alumni data hosted separately from our website? No. Everything lives inside the institute’s own WordPress database — no separate app, no separate hosting bill, no separate login system.
What happens after the update period ends? The plugin keeps working. Updates simply stop arriving until the institute renews.
Is this a subscription? No. Pro and Pro Max are one-time payments with 12 months of updates included.
How many sites does a licence cover? One WordPress installation per licence.
