A very common DNN scenario:

1) The production website's database is frequently updated with new information from content editors, registered users, e-shop customers, scheduled jobs, etc. In other words, the database is constantly changing state.

2) New functionality (modules) and/or a UI design (Theme) is required that cannot added to the running/live site because it is technically not possible and/or it is too risky to attempt. Therefore, the production site is taken down for 30 minutes to make a full backup (instance-files and database) after which the site is restarted.

3) The backup from step 2 is used to create a clone on a localhost development machine where the changes are made in a zero-risk environment.

4) After one-week of hard work the modified clone is deployed to a staging area on the webserver to complete the testing process via the Internet.

5) Two days later the modified clone now in the staging area meets the new requirements and is authorized to go live.

6) The production site is taken offline to prevent database changes.

7) *** The redesigned website (in the staging area) is merged with the current state of the production website to create the new & improved live website. IN PRACTICE HOW DOES THIS WORK?

8) The website is restarted with the new features and/or theme and everyone is happy.

Question: How exactly is step 7 accomplished? Tools, Process?

Thanks in advance for your reply.
Daniel

Sorry Daniel but no simple solution here. The changes will have to be manually retrofitted into the new site.

I recommend making a copy of the current old site and keep it running for a bit until the retrofitting process is finished.

Sincerely,
Andy

I find it helpful to use the page and module export/import features.

If the site has user registrations and/or user contributed content, there will be times when you need to take the site offline, make a copy, do your updates, and then move the copy to production and turn it back on.