MEC – Advanced Importer Addon

MEC – Advanced Importer Addon is an import utility for WordPress sites running Modern Events Calendar. It brings events, posts and other custom post types into the site from CSV and XML files, while also connecting to services such as Facebook, Google, Meetup and Eventbrite. The focus is broader than a one-off event transfer: field mapping, scheduled imports and logs give administrators a way to organise recurring data work.

Import scope

The addon covers the main content types an event site is likely to handle. Its stated support for bulk imports includes events, standard posts and custom post types, which gives it relevance beyond the calendar itself. CSV and XML support also suits sites receiving structured data from different systems or editorial workflows.

• Bulk importing for events, posts and custom post types.
• CSV and XML file support.
• Automatic field mapping to match incoming data with WordPress fields.
• Scheduled imports for recurring updates.
• Detailed logs showing import status and issues.
• Page-builder integration for imported content layouts.

Automatic mapping is the practical centre of the feature set. It reduces the amount of manual field matching during a large import, while the logs provide a place to review whether the operation completed cleanly or raised problems.

Connected services

The addon also handles imports from named third-party services, including Facebook, Google, Meetup and Eventbrite. The vendor describes these connections as ongoing rather than limited to a single transfer. Account authentication and import planning are part of the workflow, so the usefulness of each connection rests on how clearly the source data maps to the fields used by MEC and the rest of the site.

For an events team collecting listings in several places, this is more practical than maintaining separate manual entry routines. The value is strongest when the site already has a regular flow of external event data and needs that information brought into one WordPress calendar.

Automation and layout

Scheduled imports are intended to keep site content current with less repeated administration. That makes the addon suitable for recurring feeds rather than only a migration at launch. Import logs add accountability to the process by recording status and highlighting issues for review.

Its page-builder integrations address the next stage after data arrives. Imported content can be used within layouts supported by the site’s page builder, rather than stopping at raw records in the WordPress database. The vendor also positions the addon as compatible with major WordPress themes and plugins, though the concrete layout result will still depend on the builder and templates already in use.

What to weigh

The first limitation is structural: this is an addon for a site that has MEC installed, not a standalone event platform. Sites without that underlying calendar system have less reason to choose it. The second trade-off is configuration responsibility. Automatic mapping and scheduled jobs shorten repetitive work, but they do not remove the need to decide which source fields belong in which WordPress fields or how often imports should run.

The feature description also does not specify duplicate handling, conflict resolution, data transformations or recovery behaviour when a source changes its format. Those details matter for untidy feeds and long-running synchronisation. The named services and file formats give the addon a clear starting point, but teams with unusual data structures should confirm those edge cases before making it central to their publishing process.

Who it suits

MEC – Advanced Importer Addon suits event sites that combine MEC with recurring imports from files and external event services. It is a sensible fit for administrators who need bulk entry, repeatable schedules, field mapping and a record of import results in one workflow. Page-builder users also gain a route from imported records to designed content layouts.

It is less compelling for a site handling occasional manual event entry, or for a project that needs a general-purpose migration tool independent of MEC. Its strongest case is a structured, ongoing import process where the saved administrative work justifies the extra configuration.