tag:help-archives.hannonhill.com,2010-02-09:/discussions/installation/2728-site-migration-from-706-to-7102Cascade CMS: Discussion 2014-06-19T13:38:37Ztag:help-archives.hannonhill.com,2010-02-09:Comment/332947532014-06-06T13:01:17Z2014-06-06T13:01:17ZSite migration from 7.0.6 to 7.10.2<div><p>Hi Jim,</p>
<p>You should not run into any major issues with the version jump
and imports. I would recommend importing any shared/common Sites
first help avoid cross-Site reference issues with your
administrative assets.</p>
<p>That being said, if you don't mind me asking, is there a reason
why you would want to perform the upgrade this way? It would be
much quicker, and simpler, to dump your current production database
(just to be safe), perform the upgrade using either <a href=
"http://help.hannonhill.com/kb/installation-and-upgrades">an
installer</a> or the <a href=
"http://help.hannonhill.com/kb/installation-and-upgrades/upgrading-in-place-with-rootwar">
ROOT.war method</a>, and start up your instance against your
current database to perform the upgrade.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffithtag:help-archives.hannonhill.com,2010-02-09:Comment/332947532014-06-06T18:41:22Z2014-06-06T18:41:22ZSite migration from 7.0.6 to 7.10.2<div><p>Ryan,</p>
<p>The main reason we are considering this is that we have a number
of people who have refused to migrate their sites out of the
"Global" area. They either don't have the resources or the time to
do so.</p>
<p>Our original setup had individuals with the "Manager" role in
order to manage their sites. We have been trying to eliminate all
the old vestiges of this way of running things.</p>
<p>By doing a fresh install and migrating sites, I would be able to
force people to plan ahead for the migration.</p>
<p>There is also the"house cleaning" idea. We have a large number
of legacy sites that probably need to be deleted, but people are
not sure if they want to keep them. It may be easier at this point
to just start with what is currently being used and get rid of the
rest.</p>
<p>Chances are we will do the standard migration. I just wanted to
know if there are any real issue that I would run into if the
decision was made to do this.</p>
<p>Thanks!</p>
<p>Jim</p></div>jkreuzigtag:help-archives.hannonhill.com,2010-02-09:Comment/332947532014-06-06T19:49:20Z2014-06-06T19:49:20ZSite migration from 7.0.6 to 7.10.2<div><p>Thank you for the clarification, Jim.</p>
<p>What you describe does make sense and I do not foresee any
issues with exporting/importing the Sites from your older version
into the latest version. Generally, issues arise when you go the
other way; that is, export from a newer version of Cascade Server
into an older version.</p>
<p>Please let me know if you have any questions.</p>
<p>Thanks!</p></div>Ryan Griffith