Events Manager, or a newer plugin built on blocks?

What Events Manager is, and who it suits

Events Manager is one of the older events plugins in the WordPress repository. Its free version lists recurring events with exclusion dates, bookings with approvals and a CSV export, physical and online locations, Google Maps, front-end submission for guests and members, BuddyPress group events, multisite support, a REST API and GDPR tools. The vendor sells a Pro tier on top.

It suits site owners who want a deep feature set and are happy to configure it. Many sites have run it for years without trouble, and that stability is real.

The case for looking elsewhere is not that it is bad. It is that a plugin with this much history carries its history: shortcodes and templates beside blocks, post types beside custom tables, and a Pro tier that holds several things people expect to be basic. If those do not bother you, you may not need to move.

The real difference: age and architecture

Think of the two as different generations. Events Manager grew feature by feature over many years and is dense with options. Eventonomy started recently with a smaller scope and built the structure first: events and RSVPs in their own tables, every action through a REST API, and a front end made of blocks.

That structure shows up in three places you can feel.

• Front end. Calendar, list, RSVP and dashboard pieces are blocks you place in the editor. Most also work as shortcodes, though the RSVP and attendee-management blocks are block-only.
• Data. Events are not posts, so event lookups do not share a table with your articles.
• Integration. The REST API covers the plugin and is described in a machine-readable spec, so an app or a script can use it without scraping.

Density goes the other way. Events Manager exposes more settings, more booking-form options and more automation. We would rather say that than pretend a younger plugin has caught up.

What the free plugins each hold

On the Events Manager side, we read the wordpress.org listing and the vendor’s site. The free plugin lists recurring and multi-day events, bookings (attendee lists, approvals and rejections, CSV export, confirmation emails), locations, maps, front-end submission, multisite sharing, calendars, lists, grids, widgets, blocks, iCal and RSS feeds, a REST API and statistics. The listing marks payments, PDF tickets, QR check-in, waitlists, custom booking forms, coupons and automation as Pro.

On the Eventonomy side, the free plugin holds recurring events, RSVPs with guest counts, capacity and a waitlist, custom questions, the Manage Events dashboard, member submission with optional approval, an ICS feed, reminders and the importers.

The overlap is large. The deciding items are the waitlist, which is free here, and multisite, which is stronger there.

What changes for your editors

Editors who know the Events Manager screens will notice that settings are grouped differently. Eventonomy keeps views and the default view under Appearance, registration rules under Registration, and payments under Payments once Pro is active. Most people find their way in an afternoon, but plan a short walkthrough for anyone who edits events daily.

The other change is where events appear. Because events are not posts, they will not show up in a standard post query, in a post-based search plugin or in an archive you built around a post type. Check any custom loop, widget or SEO plugin rule that assumed they were. If you are unsure, list them on a sheet and test each on staging.

If you run more than one site

Events Manager lists network-wide sharing and booking management. If your project is one network of subsites that publish into a shared calendar, that is its strongest ground and ours is weakest. If instead you run several unrelated sites that each need their own calendar, Eventonomy is a fine fit, because each site simply has its own events.

Running an event in Eventonomy, step by step

For someone coming from Events Manager, here is the same job in the new plugin.

1. Add an event from the front-end editor or the admin, with a venue and organizer picked from a shared catalog. Free.
2. Make it repeat if needed. Daily, weekly and monthly rules are free; yearly and ordinal rules such as the second Saturday are Pro.
3. Pick the registration mode: RSVP here, an external link, or none. Free.
4. Set a capacity. Overflow goes to the waitlist, and a free RSVP event promotes the next person automatically. A paid, ticketed event is different: the waitlist collects names, and the organizer admits people by hand. Free for the waitlist, Pro for tickets.
5. Reminders go out a day and an hour before by default. Free. Email all registrants from the attendee panel and export the list to CSV, also free.
6. At the door, check people in by QR link, scanner, pasted code or search. Pro.

One limit to know before you migrate a series: you can cancel or restore a date, but you cannot move a date to a different day.

Selling tickets: gateways and fees

Events Manager’s Pro tier lists several gateways, including PayPal, Stripe, Authorize.net, Square and offline payment, with WooCommerce sold separately. Eventonomy Pro offers Stripe, PayPal and a WooCommerce bridge that uses whatever gateways your store already has. If you need a gateway outside that set, look at the WooCommerce route or stay where you are.

Neither product takes a cut of ticket sales. You pay your payment provider and the license for the plugin. Eventonomy Pro adds coupons, early-bird tiers, tax and booking fees, and full-order refunds from the order screen. A partial refund has to be made in the gateway’s own dashboard, and Eventonomy reconciles it back without reversing the ticket.

If you only take free bookings today, none of this applies and you can leave Pro out of the plan entirely. Many Events Manager sites never turn on payments, and they can move without buying anything. Add Pro later, on the day you first want to charge for a seat, and the existing events and RSVPs stay exactly where they are.

Site owners who run a marketplace can also set a platform fee and pay organizers out through a ledger, either by hand or through an opt-in Stripe Connect flow.

Letting visitors and members submit events

Both plugins let outsiders add events without the admin screen, and Events Manager’s version is free and covers guests too. In Eventonomy, the Manage Events page is the home for members: they create events, see attendees, email registrants and export a list. A role setting decides who may create events, and approval mode holds new submissions as pending until you publish them.

How guests are handled comes down to one setting, “Do attendees need an account?”, with three choices: create an account automatically (the default), guest only, or must log in. Choose it once and every event follows it.

If anonymous event submission from a public form is your main use, compare carefully. That is a strength of Events Manager, and you should test the Eventonomy flow on staging before committing.

What it costs to run each, and what happens to your data

Neither is hosted for you. Both run on your own server, so hosting, updates and backups are yours.

Upkeep

Events Manager is a single plugin with a Pro layer. Eventonomy is a free plugin with a Pro layer. In practice the upkeep is similar. What differs is how much custom template work you have done: if your Events Manager setup uses overridden templates or placeholders, count the time to rebuild that as blocks.

Attendee data and privacy

Eventonomy stores RSVPs and orders in its own tables and connects to the WordPress export and erase tools. Export returns a person’s RSVPs and orders. Erase anonymizes RSVPs and keeps the seat and keeps order financial records. Event emails carry a one-click unsubscribe, and uninstall can remove all data if you switch that on.

Check how your Events Manager data is handled today and plan to keep its booking records for as long as your accounting requires.

Moving over from Events Manager

Eventonomy ships a free importer for Events Manager. It reads the plugin’s own event and location tables from your database, so the plugin can be inactive, and it never changes the source.

1. Open Tools in Eventonomy and choose Events Manager. It reports how many events it found.
2. Run the scan. The report flags series it cannot translate, such as positional monthly rules, exclusion dates and multiple rule sets. Those arrive as single events.
3. Import. It works in the background in batches.
4. Confirm the 301 redirects from old event pages.
5. Undo if needed. The undo removes what that run created.

What you rebuild by hand: booking forms and any custom fields, payment settings, email templates, and every page that used an Events Manager shortcode. Bookings and payment records do not come across, so export those first.

Launch checklist

Before you switch

1. Back up the site and clone it to staging.
2. Install Eventonomy and choose your account policy.
3. Run the scan, read every call-out, then import.
4. Replace shortcode pages with calendar and events-list blocks; check them at 390 pixels wide.
5. Recreate your booking questions under the registration settings and switch them on.

Test, then clean up

1. If you sell tickets, add Pro, connect a gateway and buy and refund a test ticket.
2. Send a test reminder and a confirmation to a real inbox.
3. Run a data export and an erase request on a test person.
4. Export old bookings to CSV and store them.
5. Turn off Events Manager only after the redirects check out.

For a busy booking site, add one more habit. Move during a quiet week, not the week before a popular event, and keep Events Manager installed but inactive for a few weeks. That gives you a way back if a booking record turns out to matter.

How it sits with the rest of your stack

Eventonomy is one of several separate plugins from the same team. They are optional, they install on one WordPress site, and they share one login.

The real connections are narrow and on different sides. Eventonomy Pro ships the BuddyPress integration, with an events tab in groups and profiles, activity posts and notifications. The BuddyNext link is built and shipped by BuddyNext Pro and needs only the free Eventonomy plugin. If you already use Events Manager with BuddyPress groups, the group tab is the piece to test.

Jetonomy for forums, Learnomy for courses, Listora for directories, WP Career Board for jobs, WP Sell Services for a services marketplace and WB Gamification for points and badges all run on the same site. We make no integration claim for them. BuddyX Pro and Reign are community themes the plugin works under.

The trade against a hosted platform is simple. A hosted tool is one bill and takes a fee per ticket. These plugins are ones you install, host and update, with no per-ticket cut.

What Eventonomy does not do for you

• No network-wide event sharing on multisite.
• No Square or Authorize.net gateway of our own; payments go through Stripe, PayPal or WooCommerce.
• No custom booking-form builder with file uploads; custom questions come with ten answer types.
• No moving a single occurrence to another day.
• No Meetup sync.
• No bundled mobile app.

Other alternatives worth a look

• The Events Calendar wins on ecosystem size and add-on range.
• Modern Events Calendar wins when you want a large choice of calendar layouts.
• EventON is for sites that want its compact calendar look.
• WP Event Manager suits listing-style event directories.
• Event Espresso is built around registration and ticket workflows.
• Amelia is the better fit if your real need is appointment booking.

The side-by-side table is at Eventonomy vs Events Manager.

Who should stay with Events Manager

Stay if you run multisite with shared events, if you depend on its gateways or booking forms, or if your current setup works and nobody is asking for changes. A working site is a good reason not to migrate.

Think about who else touches the site. A developer who has built custom templates around Events Manager has an investment to weigh, and an editor who lives in its booking screens will need a walkthrough. Neither is a reason to avoid moving, but both belong in the plan and the schedule.

Move if you want blocks, a documented API and a waitlist without paying for Pro. Run the importer on staging first and read the features and the Free vs Pro line before deciding.