Question

I am using a highly patched version 8.0.1 SP1.

I have a lot of website sites to move from one hosting server and database to another. I have tried to use eSync but our version has a lot patches and I have spent days trying to work out a basic eSync. Not wanting the headache, I am going to attempt a manual move. I started a test run of the steps at http://documentation.ektron.com/cms400/v802/webhelp/Installation/Installing%20Ektron%20CMS400.Net/Moving_a_Site_to_Another.htm but that won’t set up all of the hooks into the Ektron Windows service and the notification service, etc. Am I assuming right?

Will this work?

1. Install new minsite on new server and create new database. (this should create all the bits and parts that the Ektron services need)
2. Copy website from old server and paste on top of new
3. Backup old database and restore to new
4. Copy asset folder from old site and paste into new

Will this give me all of the parts I need or am I missing something? Once we start this process, it is a one-way street and we have over 100 sites to move. I have to train a couple of people who will be living this process for a month or so I have to get it right.

Thanks, Zach

Answer 1

(Full disclosure: I work at Ektron)

Without being able to use eSync, your steps are on the right path, and you’re really close.
Only things that I see you missed were:

• root\uploadedimages
• root\uploadedfiles
• root\widgets (if any are custom)
• You mentioned assets, not sure if that includes root\privateassets as well

Things that are important:
Sitepath (in web.config) remains the same, eg:
http://www.mysite.com moved to something like sub.mysite.com or mysite.com/sub could potentially break any hard links within content or quicklinks/aliases depending how it’s setup.. so just make sure the architecture remains as close as possible (folder structure on server being the same will also be safest, eg all sites get installed to .