--- title: Migration Overview description: "Eventixa includes a guided migration system for moving events and supported related data from another event plugin into Eventixa. The current built-in migration source is **The Events Calendar**, with support for compatible Event Tickets data where available. Eventixa reads the…" url: "https://eventixawp.com/docs/migration-overview/" updated: "2026-09-26" category: Migration --- # Migration Overview Eventixa includes a guided migration system for moving events and supported related data from another event plugin into Eventixa. The current built-in migration source is **The Events Calendar**, with support for compatible Event Tickets data where available. Eventixa reads the source data, lets you choose which events to migrate, processes them through a persistent migration run, and provides statuses, warnings, retry controls, and a final migration report. > **Admin Location:** Eventixa → Migration > **Current Source:** The Events Calendar > **Source Safety:** Migration reads from the source and does not modify the original source data. ## What Is Eventixa Migration? Eventixa Migration is designed to help you move existing event data into Eventixa without manually recreating every event, venue, organizer, ticket, attendee field, or supported registration record. The process is selective rather than all-or-nothing. You first fetch available source events, choose the events you want, decide whether historical transactional data should also be included, and then start the migration. ![Eventixa Migration screen showing The Events Calendar source detection and Fetch Events action](https://eventixawp.com/wp-content/uploads/2026/09/eventixa-migration-overview.jpg) Eventixa detects supported migration sources and lets you fetch source events without modifying the original event data. ## Current Supported Migration Source The current built-in migration source is **The Events Calendar**. Eventixa detects whether the supported source plugin is available on the WordPress site. When the source is detected and its migration adapter is ready, the **Fetch Events** action becomes available. If the source plugin is not available, Eventixa displays **Not detected** and disables migration from that source. ## Source Data Remains Unchanged Eventixa treats the source plugin as read-only during migration. The Migration screen explicitly indicates that source data remains unchanged and that fetching and migration read from the original source. This means migration creates or updates corresponding Eventixa records without intentionally deleting or modifying the original events in the source plugin. ## Open the Migration Screen Go to: **Eventixa → Migration** The Migration screen displays available migration sources. Each source card shows: - Source name - Description - Detection status - Migration availability - Fetch Events action ## Detected and Not Detected Sources A migration source can appear as either **Detected** or **Not detected**. **Detected** means Eventixa has found the corresponding source plugin or data provider. **Not detected** means the required source is not currently available. A detected source must also implement the complete Eventixa migration contract before the migration controls are enabled. ## Fetch Source Events When The Events Calendar is detected, click **Fetch Events**. Eventixa retrieves the source events and opens the event browser. Fetching events does not immediately migrate anything. It gives you an opportunity to inspect, search, filter, and select the events you want to move. ![Eventixa Migration Scope showing Bookings and Orders Attendees and Responses and Historical Check-In options](https://eventixawp.com/wp-content/uploads/2026/09/eventixa-migration-scope.jpg) Historical bookings, attendees, responses, and check-in state can be included separately when you need to preserve existing transactional records. ## Migration Event Browser The event browser displays source events in a table. The current columns include: - Event - Date - Source Status - Type - Migration Status A checkbox lets you select individual events for migration. ## Search Events Use the search field to find source events by title. This is useful on sites with a large number of existing events. ## Filter by Source Status You can filter source events by their current WordPress status. Available filters include: - All Status - Published - Draft - Pending - Private - Scheduled This lets you migrate only the event states relevant to your site. ## Filter by Event Type The Migration screen also lets you filter by: - All Types - Single Events - Recurring Events Recurring-event support depends on the migration capabilities available on the destination Eventixa installation. ## Select Events Select the individual source events you want to migrate. You can also use **Select loaded events** to select the events currently loaded in the browser. Eventixa displays the number of selected events before migration begins. ## Load More Events Large source libraries can be loaded progressively. Use **Load More Events** when additional source events are available. This avoids forcing the Migration screen to load an entire large event database at once. ## Migration Status Each source event has a migration status. The current Eventixa migration states include: - Not Migrated - Queued - Migrating - Migrated - Migrated with Warnings - Skipped - Failed - Requires Pro - Unsupported These statuses help you understand what happened to each source event. ## Not Migrated **Not Migrated** means Eventixa has discovered the source event but it has not yet been processed successfully. ## Queued **Queued** means the event has been added to a migration run and is waiting to be processed. ## Migrating **Migrating** indicates that Eventixa is currently processing the event. ## Migrated **Migrated** means the supported migration pipeline completed successfully for the event. ## Migrated with Warnings **Migrated with Warnings** means the event was created or updated in Eventixa, but one or more pieces of source data could not be migrated exactly. The event can still be usable, but the warnings should be reviewed. ## Skipped **Skipped** means Eventixa intentionally did not migrate the event or a migration stage determined that the source record should not be processed. ## Failed **Failed** means the migration could not complete for that event. Failed events can be reviewed and retried. ## Requires Pro **Requires Pro** indicates that the source event needs an Eventixa Pro migration capability that is not available on the current installation. An example can be source data that depends on a Pro-only destination feature. ## Unsupported **Unsupported** means the source contains a structure or feature that the current Eventixa migration adapter cannot safely convert. Eventixa reports unsupported data instead of silently pretending it migrated correctly. ## Migration Scope Before starting migration, use **Migration Scope** to decide whether you want only event configuration or also historical transactional data. Some data is always included in the base migration. Historical data is optional. ## Data Included by Default The standard migration scope always includes supported: - Event details and dependencies - Tickets - Attendee field definitions - Event and ticket reconciliation You do not need to enable historical migration options for these items. ## Event Details and Dependencies Eventixa can migrate the core event record together with supported dependencies required by the event. Depending on the source event, dependencies can include data such as: - Categories - Tags - Venues - Organizers - Featured image - Supported virtual-event information The exact migrated data depends on what exists in the source and what Eventixa supports. ## Tickets Supported ticket definitions can be migrated into Eventixa. The migration system also reconciles the migrated Eventixa ticket with its corresponding source ticket so the mapping remains consistent. ## Attendee Field Definitions Supported registration or attendee-field definitions can be migrated as part of the normal migration scope. If a source advanced field cannot be represented by the available Eventixa destination capability, Eventixa can report a warning rather than failing the entire event migration unnecessarily. ## Event and Ticket Reconciliation After importing the supported event and ticket configuration, Eventixa performs reconciliation checks. These checks help confirm that important migrated records correspond correctly with their source equivalents. ## Historical Data Is Optional Historical transactional data is not enabled by default. The available historical options are: - Bookings & orders - Attendees & responses - Historical check-in state Leaving these options disabled provides the fastest and safest configuration-focused migration. ## Bookings & Orders Enable **Bookings & orders** when you want Eventixa to preserve supported historical registration, order, payment, and booking information. This is intended for existing records rather than new live transactions. ## Attendees & Responses Enable **Attendees & responses** when historical attendees and RSVP-related response records should also be migrated. Because an Eventixa attendee requires a booking relationship, enabling attendees automatically requires historical bookings. ## Historical Check-In State Enable **Historical check-in state** when supported previous attendee check-in information should be preserved. Historical check-in requires attendee records, and attendees require their booking parent. Therefore, enabling historical check-in also enables the required attendee and booking scope. ## Historical Migration Does Not Trigger Live Check-In Actions Migrating historical check-in state is a data-preservation operation. Eventixa does not treat the imported historical check-in as a new live attendee check-in action. This avoids unintentionally triggering current check-in workflows while importing old data. ## Eventixa Core Migration Capabilities The current migration framework registers the following destination capabilities in Eventixa Core: - Events - Event Categories & Tags - Venues - Organizers - Tickets - Attendee Fields - Bookings - Attendees - Virtual Events Whether each capability is used for a specific event depends on the data available from the migration source. ## Eventixa Pro Migration Capabilities Eventixa Pro adds destination migration capabilities for: - Recurring Events - Advanced Event Fields - Attendee Check-In Pro also extends The Events Calendar migration for supported recurrence, additional fields, historical check-in information, and virtual-event behavior. ## Recurring Events When Eventixa Pro is active, the migration system can process supported recurring-event data from The Events Calendar. Not every source recurrence structure can necessarily be represented exactly in Eventixa. Unsupported recurrence rules are identified rather than silently converted into incorrect schedules. ## Virtual Events Eventixa Migration includes support for compatible virtual-event information. For supported source data, virtual event configuration can be transferred into Eventixa. Managed providers such as Zoom or Google Meet are only adopted when the destination configuration can safely represent them. When direct provider mapping is not appropriate, migration can preserve usable meeting access through supported fallback behavior. ## Start the Migration After selecting the events and migration scope, click **Migrate Selected Events**. Eventixa creates a persistent migration run and begins processing the selected events. ## Persistent Migration Progress Migration progress is persistent. The Migration screen states that closing the page does not discard the migration run. This is particularly useful for larger migration jobs that take longer than a normal admin-page interaction. ## Migration Progress Panel While a migration is running, Eventixa displays a progress panel. The panel tracks values such as: - Processed - Total - Migrated - Warnings - Failed - Pending A progress bar shows the overall state of the run. ## Pause Migration Select **Pause Migration** when you want the migration run to stop processing additional events. The current event is allowed to reach a safe stopping point before the run pauses. ## Resume Migration A paused migration can be continued using **Resume Migration**. You do not need to create a new migration run simply because processing was paused. ## Recover an Unfinished Migration Eventixa can recover an unfinished migration run. If an existing run was interrupted, the Migration screen can restore its progress rather than discarding the run. ## Failed Events If one or more events fail, the progress area records the failures. Eventixa does not require successful events to be migrated again just because another event in the run failed. ## Retry Failed Events Use **Retry Failed** to retry events that failed during the migration run. This is useful after fixing a temporary source, environment, or configuration problem. ## Retry an Individual Event The migration framework also supports retrying an individual failed event. This lets you focus on one problematic source event instead of rerunning an entire migration. ## Reimport an Event Eventixa supports reimporting source events that already have migration records. This can be useful when the source event has changed or when a previously created Eventixa destination event no longer exists. The migration mapping helps Eventixa determine whether it should update, retry, or recreate destination data instead of blindly producing duplicates. ## Avoiding Duplicate Migration Records Eventixa maintains source-to-destination mappings for migrated entities. These mappings help the migration system recognize previously imported events, tickets, attendees, and related records. The goal is to allow retries and updates without creating unnecessary duplicate destination records. ## What Happens if the Migrated Event Was Deleted? If an Eventixa event created by migration is later deleted, the migration system can detect that the previous destination record no longer exists. The source event can then be migrated again instead of being permanently blocked by an old migration mapping. ## Migration Warnings A warning does not always mean that the whole event failed. Warnings are used when Eventixa can migrate the main event successfully but cannot safely reproduce a particular source detail. Examples can include: - Unsupported recurrence details - Unsupported custom fields - Virtual-event data that requires fallback handling - Source records that cannot be mapped exactly Review warnings before removing the original source plugin. ## Migration Errors A migration error means Eventixa could not complete the required migration workflow for the affected event. The Migration Report provides additional information to help identify what failed. ## Migration Report After processing, select **View Report**. The Migration Report provides a summary of the migration run together with event-level results. Use the report to review successful migrations, warnings, skipped events, and failures. ## Reconciliation Eventixa performs reconciliation checks after supported data is imported. Depending on the selected scope, reconciliation can verify information such as: - Event relationships - Ticket mappings - Historical booking relationships - Booking statuses - Payment statuses - Ticket quantities - Historical financial snapshots - Currency - Attendee relationships This helps detect data that was copied but does not accurately match its source relationship. ## Historical Booking Validation When historical bookings are included, Eventixa can validate that the migrated booking corresponds with the source order or registration record. This includes supported booking and payment status information. ## Historical Ticket Quantity Validation Eventixa can verify that the ticket quantities in a migrated historical booking match the source order. ## Historical Financial Validation When the source provides supported financial data, reconciliation can compare the migrated booking snapshot with the original source financial information. ## Currency Validation Supported historical migration also validates the booking currency against the source where applicable. ## Historical Attendee Validation Historical attendees must resolve to the correct migrated Eventixa booking and ticket. If those required relationships cannot be established, Eventixa does not silently create a disconnected attendee record. ## Recommended Migration Workflow A safe migration process is: 1. Back up your WordPress site and database. 2. Keep the source plugin active. 3. Activate the required Eventixa features. 4. Go to **Eventixa → Migration**. 5. Confirm the source is detected. 6. Click **Fetch Events**. 7. Search or filter the source event list if necessary. 8. Select a small group of test events first. 9. Leave historical options disabled for the first configuration test. 10. Click **Migrate Selected Events**. 11. Review migrated events, tickets, venues, organizers, and other supported data. 12. Review all migration warnings. 13. Test frontend event and ticket behavior. 14. If required, run migration with historical bookings, attendees, or check-in state. 15. Review the final Migration Report. 16. Only consider removing the source plugin after migration has been fully verified. ## Start with a Small Test Migration For a large production site, avoid selecting every event on the first run. Begin with a representative group that includes the event types you actually use. For example, test: - One simple event - One event with tickets - One event with registration fields - One virtual event - One recurring event if Eventixa Pro is active - One event with historical data if you plan to migrate history This makes it easier to verify mappings before migrating the complete source library. ## Keep the Source Plugin During Verification Do not immediately uninstall the original event plugin after Eventixa reports a successful migration. First compare the source data with the migrated Eventixa records. Check event dates, recurrence, tickets, registrations, virtual-event access, and other important workflows before making the migration permanent. ## Migration Is Not the Same as Live Synchronization Eventixa Migration is an import and reconciliation system. It does not create permanent two-way synchronization between Eventixa and The Events Calendar. After migration, future edits made independently in one plugin should not be assumed to automatically synchronize with the other. ## Common Questions ### Does Eventixa Delete My Original Events? No. The current migration workflow reads from the source and leaves the source data unchanged. ### Does Clicking Fetch Events Start Migration? No. Fetch Events only loads source events into the Migration browser. You must select events and explicitly click **Migrate Selected Events**. ### Do I Have to Migrate Every Event? No. You can select only the events you want. ### Can I Search the Event List? Yes. The Migration screen includes event-title search. ### Can I Filter Draft or Published Events? Yes. Source-status filters include Published, Draft, Pending, Private, and Scheduled. ### Can I Filter Recurring Events? Yes. You can filter the browser by Single Events or Recurring Events. ### Are Historical Bookings Migrated Automatically? No. Historical bookings are optional and disabled by default. ### Are Historical Attendees Migrated Automatically? No. Enable **Attendees & responses** when you want supported historical attendees migrated. ### Why Did Enabling Attendees Also Enable Bookings? Every Eventixa attendee requires a booking relationship. Eventixa therefore includes the necessary historical booking data when attendee history is requested. ### Why Did Enabling Historical Check-In Also Include Attendees and Bookings? Historical check-in belongs to an attendee, and an attendee belongs to a booking. Those parent records are required to preserve the relationship correctly. ### Does Migrating Old Check-In Data Trigger New Check-In Actions? No. Historical check-in import does not trigger the live Eventixa check-in workflow. ### Can I Pause a Migration? Yes. Migration runs can be paused and resumed. ### Will Closing the Migration Page Cancel the Run? No. The migration uses persistent run progress so the run is not discarded simply because you leave the page. ### Can Failed Events Be Retried? Yes. You can retry failed migration items. ### Can an Already Migrated Event Be Imported Again? The migration framework supports reimport and source-to-destination mapping rather than blindly creating duplicates. ### What Does Migrated with Warnings Mean? The primary event was migrated, but Eventixa detected one or more source details that could not be reproduced exactly. Review the warning details before considering the migration complete. ### What Does Requires Pro Mean? The event contains a migration requirement that depends on a destination capability supplied by Eventixa Pro. ### What Does Unsupported Mean? The current destination or migration adapter cannot safely represent the particular source data. ### Does Eventixa Migrate Recurring Events? Supported recurring-event migration is available through Eventixa Pro. Some source recurrence rules can still be reported as unsupported if they cannot be represented safely. ### Does Eventixa Migrate Virtual Events? Supported virtual-event data can be migrated. Provider-specific data is only mapped when Eventixa can safely represent it. ### Can I Remove The Events Calendar Immediately After Migration? It is better to fully verify the migrated data and frontend workflows first. Keep a backup and confirm all important events and related records before removing your source plugin. ## Important Notes - The current built-in migration source is The Events Calendar. - Migration is available from **Eventixa → Migration**. - Source data is read-only during the migration workflow. - Fetch Events does not start migration. - You choose which events are migrated. - Search and status/type filters are available. - Event configuration, dependencies, tickets, attendee-field definitions, and reconciliation are part of the base migration scope. - Historical bookings, attendees, and check-in state are optional. - Historical attendees require bookings. - Historical check-in requires attendees and bookings. - Migration runs use persistent progress. - Runs can be paused and resumed. - Failed events can be retried. - Eventixa maintains source-to-destination mappings to support retries and reimports. - Eventixa Core provides the base migration framework and standard destination capabilities. - Eventixa Pro adds recurring-event, advanced-field, and historical check-in migration capabilities. - Warnings should be reviewed even when an event is successfully migrated. - Always verify migrated data before removing the original source plugin. ## Related Documentation - [Migration from The Events Calendar](https://eventixawp.com/docs/migration-from-the-events-calendar/) - [Supported Migration Data](https://eventixawp.com/docs/supported-migration-data/) - [Recurring Event Migration](https://eventixawp.com/docs/recurring-event-migration/) - [Migration Warnings & Troubleshooting](https://eventixawp.com/docs/migration-warnings-troubleshooting/) - [Recurring Events Overview](https://eventixawp.com/docs/recurring-events-overview/) - [Creating Event Tickets](https://eventixawp.com/docs/creating-event-tickets/) - [Attendee Registration Fields](https://eventixawp.com/docs/attendee-registration-fields/) - [In-Person, Virtual & Hybrid Events](https://eventixawp.com/docs/in-person-virtual-hybrid-events/)