Migrating from The Events Calendar
FreeSince 7.5Included in the free Events Manager plugin.
Events Manager can copy a whole site across from The Events Calendar: events, recurring events, venues, organizers, categories, tags, tickets and the attendees who hold them. It reads the data of The Events Calendar, Events Calendar Pro, Event Tickets and Event Tickets Plus straight from the database.
Nothing in The Events Calendar is changed or deleted. You can run the migration, look at the result, roll it back, and run it again, as many times as you like, before you switch the old plugin off.
- Back up your database. The migration can be rolled back, but a backup costs nothing.
- You need to be an administrator, on Events Manager 7.5 or later.
- The Events Calendar and its add-ons can be active or deactivated. Their data only has to still be in the database.
- Try it on a staging copy of the site first if the site sells tickets.
To bring in events from a spreadsheet instead, see Importing from a CSV File.
What is migrated
| In The Events Calendar | Becomes in Events Manager |
|---|---|
| Events that are published, scheduled, draft, pending or private | Events with the same title, description, excerpt, status, author, slug, publish date, password, featured image, dates, times, all-day setting and timezone. Comments on the event are copied too. |
| Recurring events (Events Calendar Pro) | Recurring events. The pattern is translated where Events Manager has the same kind of rule, so the event stays editable as a pattern. Where it has none, the event is saved with the exact list of dates instead. Either way the dates are checked against the ones The Events Calendar generated. |
| Venues | Locations, with address, city, state or province, postal code, country, coordinates, description and featured image. Phone and website become location attributes. |
| Organizers | Organizers, with email, phone, website and image. Enable organizers? is switched on for you. |
| Event categories | Event categories, keeping their hierarchy, descriptions and colors. |
| Tags used on events | Event tags. Tags used only on blog posts are left alone. |
| Cost, event website, additional fields, a status such as postponed and its reason | Event attributes, listed under the event's description along with its organizers. |
| A cancelled event | An event with the status Cancelled. |
| An event website on an event that has no venue | A URL location for the event. |
| A virtual event's stream link | An online location of the Custom Link type. With a venue as well, the event becomes a hybrid event. A stream shown only to ticket holders stays restricted to attendees. |
| Tickets and RSVPs (Event Tickets and Event Tickets Plus, including Tickets Commerce, WooCommerce and Easy Digital Downloads tickets) | Tickets on the event, with name, description, price, capacity and sale dates. An RSVP becomes a free ticket. Enable bookings? is switched on if it was off. |
| Attendees | Bookings: one booking for each order and event, holding one space for each attendee. Order statuses are mapped to booking statuses, so a completed order is an approved booking, a pending one is pending, and a refunded or cancelled one is cancelled. |
| TEC shortcodes and blocks in your posts and pages | The nearest Events Manager shortcode. For example [tribe_events view="list"] becomes [events_list] and a month view becomes [events_calendar]. |
No emails are sent while the migration runs. Attendees are not told about their migrated bookings.
The migration also switches on the Events Manager features the migrated data needs: categories, tags, attributes, and where the data calls for them organizers, recurrence, bookings and virtual locations. If Events Manager has no bookings of its own yet, its currency is set to the default currency of The Events Calendar. A rollback puts every one of these settings back.
What is not migrated, and other limits
- Attendee details need Pro to be seen. Attendee names, their answers to attendee fields and their check-in status are copied and kept with each ticket. Without Events Manager Pro they are not displayed, and you see each booking, its tickets and the person who booked.
- Settings, templates and styling of The Events Calendar are not carried over. Events use Events Manager's formats.
- Abandoned checkouts are skipped. Only orders that became real attendees are migrated.
- Unlimited tickets are given a size, because every Events Manager ticket has one: the event's shared capacity if it has one, otherwise well above the number sold.
- Series passes and tickets on recurring events: each date of the migrated event gets its own copy of the ticket, and a series pass order becomes one booking for each date. The amount paid is recorded on the first.
- A stream limited to logged-in users has no equivalent, so its link becomes public. The log names each event this applies to.
- Featured events and events hidden from listings keep that fact as an attribute, but are not treated differently in lists.
- The countdown shortcode has no equivalent and is removed from converted pages.
- A venue whose country isn't recognized is migrated with the country left blank, and the log says so.
- An event with no start date is skipped.
Run the migration
-
Open the migration screen. While The Events Calendar's events are on the site, there are three ways in:
- the Migrate to Events Manager button in the Moving from The Events Calendar? notice at the top of wp-admin
- Events then Migrate, a menu item that appears when data from another calendar plugin is found
- Events then Settings then General then Admin Tools (Advanced), under Import and Migrate, the Migrate from The Events Calendar button
-
Check the Found in The Events Calendar box. It counts the events, recurring events, venues, organizers, categories, tickets, attendees, and pages using TEC shortcodes or blocks that the migration will work through. Notices above it point out anything worth knowing first, such as tickets on recurring events.
What was found on the site, and the options for the run. The demo data has only events, venues, organizers and a category, so tickets, attendees and recurring events count zero.
-
Set the Options, described below. The defaults suit most sites.
-
Click Start migration. The Progress box lists the steps and ticks them off: Settings, Categories, Tags, Organizers, Venues, Events, Tickets, Attendees, Event and venue descriptions, Shortcodes and blocks, Finishing.
-
Keep the tab open until the status reads Finished. The work is done in short batches driven by this screen, so closing it pauses the run. Pause and Resume let you stop and continue on purpose.
A finished run. The counts beside each step show what was created, reused and skipped.
-
Read the Log. Lines marked with a warning sign are things the migration could not carry over exactly, each with the name of the event, venue or ticket.
Then look at the result: the events list in wp-admin, a few event pages on the front of the site, a recurring event, and the bookings of an event that had attendees.
Options
| Option | Default | What it does |
|---|---|---|
| Include past events | On | Off leaves out single events that have already ended. |
| Migrate tickets, RSVPs and attendees | On | Off migrates events only, with no tickets or bookings. |
| WooCommerce ticket orders become | Events Manager bookings | Shown only when the site has tickets sold through WooCommerce. Events Manager bookings creates ordinary bookings. Events Manager bookings linked to their WooCommerce orders is offered when the Events Manager for WooCommerce add-on is active, and keeps each booking attached to its original order. Nothing, migrate the tickets only creates the tickets and no bookings. |
| Replace TEC shortcodes and blocks in posts and pages with Events Manager equivalents | On | Rewrites those posts and pages. The original content of each is kept so a rollback can restore it. |
| Keep The Events Calendar's web addresses for events, venues, organizers, categories and tags | On | Changes Events Manager's permalink settings to match, see the next section. |
| Redirect any other old addresses, such as single dates of recurring events, series pages and calendar views, once The Events Calendar is deactivated | On | See the next section. |
What happens to your URLs
With Keep The Events Calendar's web addresses on, Events Manager's permalink slugs are changed so that every migrated item answers at the address it already had:
| Item | Address after migrating |
|---|---|
| Event | /event/your-event/ (or your own single event slug from The Events Calendar's settings) |
| Venue | /venue/your-venue/ |
| Organizer | /organizer/your-organizer/ |
| Event category | /events/category/your-category/ |
| Event tag | /events/tag/your-tag/ |
Links from search engines, emails and other sites keep working, with no redirect in between.
Some addresses have no direct counterpart, because Events Manager organizes things differently. With the redirect option on, a request for one of them is sent to the matching Events Manager page with a permanent (301) redirect:
- a single date of a recurring event, such as
/event/your-event/2026-12-01/, goes to the migrated event - a series page goes to the migrated recurring event
- calendar views, such as
/events/list/and/events/month/, go to your events page, and a month address such as/events/2026-12/goes to that month - the iCal export address goes to Events Manager's iCal feed
While both plugins are active they compete for the same addresses, and the redirects above stay off, since The Events Calendar still answers them. Once you have checked the result, deactivate The Events Calendar and its add-ons. You don't need to delete them or their data.
On a site that isn't in English, The Events Calendar may use translated slugs for venues, organizers, categories and tags. The migration uses the English ones (venue, organizer, category and tag), so those addresses change on such a site. A developer can supply the right slugs with the em_migrate_tec_permalink_slugs filter before the migration is run.
Run it again
After a migration the button reads Run again (sync changes). A second run:
- skips everything that was already migrated and has not changed in The Events Calendar since
- migrates anything new
- replaces an event that changed in The Events Calendar with a fresh copy, unless its Events Manager copy has bookings, in which case it is left as it is and named in the log
This lets you migrate early, keep taking bookings in The Events Calendar while you set up Events Manager, and sync once more before you switch.
Roll back
Roll back appears on the migration screen once something has been migrated. It asks you to confirm, then:
- deletes every event, location, ticket and booking the migration created
- deletes the categories, tags and organizers it created, but not ones that already existed and were reused
- restores the original content of every post and page whose shortcodes or blocks were converted
- puts back each Events Manager setting the migration changed, including the permalink slugs
The Events Calendar's data is not touched by a rollback either.
A rollback deletes migrated events along with any bookings made on them in Events Manager since. Roll back before you start taking bookings on the migrated events, not after.
From the command line
With WP-CLI the migration runs without a browser, which suits large sites. Run it as an administrator with --user.
# what was found, what has been migrated, and the state of the last run
wp em migrate status tec
# the options and their defaults
wp em migrate options tec
# run the migration to the end
wp em migrate run tec --user=admin
# the same, with options changed
wp em migrate run tec --past_events=false --woo_bookings=em-woocommerce --user=admin
# continue a run that stopped on an error
wp em migrate run tec --resume --user=admin
# roll back (add --yes to skip the confirmation)
wp em migrate rollback tec --user=admin
The option names are past_events, tickets, woo_bookings, content, urls and redirects. wp em migrate list shows every source Events Manager can migrate from.
Troubleshooting
There is no Migrate menu item or notice
The menu item and the notice appear only when events from The Events Calendar are found in the database, and the notice goes away once dismissed or once something has been migrated. The Migrate from The Events Calendar button in Admin Tools (Advanced) is always there.
The run stopped with "Stopped on an error"
The log's last line gives the error. Fix the cause if you can, then click Resume: the run continues from where it stopped and does not start over.
Event pages show The Events Calendar's layout, or the wrong page
Both plugins are active and are answering the same addresses. Deactivate The Events Calendar and its add-ons, then re-save your permalinks in Settings then Permalinks.
I can't see attendee names on migrated bookings
They were migrated, and are shown once Events Manager Pro is active. See What is not migrated.
A recurring event has "dates matched" in the log
Events Manager could not reproduce every date of that event. The log line gives the count. Open the event and compare its dates with the original before you deactivate The Events Calendar.