Mike Jolley on "[Plugin: WooCommerce] Move Woocommerce to a new site"

I currently have a wordpress site with woocommerce. I would like to create a new site, but I don't want to loose my existing or any new woocommerce data that happen on my old site while I build my new site. I want to start with a new clean instal of wordpress, because my old site is cluttered with unneeded tables from old plugins. I want to start clean with everything except woocommerce which I want to migrate over.

Can I create my new website and when I am ready to launch it just copy all of the woocommerce table contents to the new database? If so exactly which tables would need to be copied?

Thank you!
Mariah

https://wordpress.org/plugins/woocommerce/

WooCommerce shares the DB with WordPress; products and orders are both post types for example, so migrating specific tables isn't really an option here without getting conflicts..

Thanks for the info.

Is there anyway to work on a wordpress site without working on the actual live site or loosing everything that happens on the old site while you build a new site?

I guess I just need to put up a maintenance page for a month or two while I revamp my site. Very frustrating.

You could make a duplicate from your live-site with duplicator... install it local @home (use xampp e.g)

or you could install the duplicated page in a subdirectory @your hoster

The only problem with that is I will loose any orders or new site registrations that happen after the site is duplicated.

I might end up doing it anyways, but I wish there was a better method for working on wordpress sites.

sorry, maybe i misunderstood.... do you want to build a new frontend or do you want to change the backend too?

for point one: build it on the duplicate and then, when its ready activate it on your live site.

another way (needs much documentation of the steps you made) .... make any customisation on the duplicate, when you're ready and satisfied take the live site off for a day or two and redo on the live site (hope you understand what i mean)

anyway, it's always good to have a duplicate running in an test environment. this way you're able to check updates or new functions.

You can do your dev changes on a duplicate install (plugins, theming etc), then do the actual data changes and product updates on live when you're ready to reduce downtime.