Hi POP,
Unfortunately, I’ve not seen an easy solution for this problem. Typically, I see web developers typically take a strategy like this:
1. Take a snapshot of the production database.
2. Work on the new stuff for the site for a while.
3. Take another snapshot of the production database and manually merge those changes in.
4. Take the website offline in preparation for the launch of the new stuff.
5. Take another snapshot of the production database and merge the remaining changes in.
6. Push the local database with the most recent changes and new site features to the production database.
That’s the rough framework. It’s different for every site, and obviously more complex the large the site is.
I’d be glad to move this over to Community Help where others can toss in their strategies. Would you like me to do that?