DB Migrate Pro Problems

Hi,

Not sure if anyone can help us with this.

We have a production site which is constantly being updates with new posts, events, event registrations, data collected via Gravity Forms etc.

We have a staging version on a separate server on which we have been adding new features including Peepso and LearnDash.

We’re at the point where we’re almost finished testing the staging version and ready to go live with the new features.

We were planning on doing a final data sync from production to staging using Migrate DB Pro and then cloning the entire staging site to production.

However, when we sync from production to staging using Migrate DB Pro we lose a lot of the custom pages and custom page elements created using Avia builder that we have set up on staging, so we have to immediately roll back. We also lose new menus etc on staging.

When running the sync, we leave out syncing wp_options table, we leave GUIDs alone and we don’t migrate active plugin settings.

Are there any other tables or post types we should not migrate so our new pages and layouts on staging don’t get overwritten?

With thanks

Regards

Phil