Title: Export Listings
Last modified: August 22, 2016

---

# Export Listings

 *  [demodave](https://wordpress.org/support/users/demodave/)
 * (@demodave)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/export-listings/)
 * I am moving my WP to a different website. I would like to easily transfer the
   listings in the calendar to the new site. Is there an export feature?
 * [https://wordpress.org/plugins/mf-gig-calendar/](https://wordpress.org/plugins/mf-gig-calendar/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Matthew Fries](https://wordpress.org/support/users/brewermfnyc/)
 * (@brewermfnyc)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/export-listings/#post-5879406)
 * Hey there. There’s no export capability built into the plugin. The data is just
   stored in a DB table with the WP tables. Just make sure you move the mfgigcal
   table along with everything else and you’ll be all set.
 * I usually use phpMyAdmin to do moves like this. Not sure that WP’s export function
   will include plugin tables.

Viewing 1 replies (of 1 total)

The topic ‘Export Listings’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/mf-gig-calendar.svg)
 * [MF Gig Calendar](https://wordpress.org/plugins/mf-gig-calendar/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/mf-gig-calendar/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/mf-gig-calendar/)
 * [Active Topics](https://wordpress.org/support/plugin/mf-gig-calendar/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/mf-gig-calendar/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/mf-gig-calendar/reviews/)

## Tags

 * [calendar](https://wordpress.org/support/topic-tag/calendar/)
 * [moving](https://wordpress.org/support/topic-tag/moving/)

 * 1 reply
 * 2 participants
 * Last reply from: [Matthew Fries](https://wordpress.org/support/users/brewermfnyc/)
 * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/export-listings/#post-5879406)
 * Status: not resolved