CiviCRM Community Forums (archive)

Looking at the latest version of that migrate doc, I don't see where it says to disable the CiviCRM module
http://wiki.civicrm.org/confluence/display/CRMDOC33/Moving+an+Existing+Installation+to+a+New+Server+or+Location

You definitely need to have it enabled in order to do step 8 (rebuild menus).

Hmm - missed that, and surprised others didn't catch that the instruction to re-enable the module was missing :-(  I added that step to the latest doc version:
http://wiki.civicrm.org/confluence/display/CRMDOC40/Moving+an+Existing+Installation+to+a+New+Server+or+Location

I used this guide as a reference and I wanted to offer up some additional suggestions worth note.

It does not describe migration from unlike Drupal installs.  I used this method to migrate CiviCRM from production into a clean Drupal install on a dev server to work with different modules.

There were a few issues that I encountered. First rule is to migrate only like versions of CiviCRM.  I tried moving from different sub version to a newer subversion (i.e. 4.0.3 to 4.0. and it actually dropped some of my setup (localization settings with countries and states available).  Need to move to same version and subversion then use the upgrade method to move upward in versions. I did have to check all the checklist again and go back and compare the production to the dev server.  I was then able to upgrade civicrm after I got all my settings corrected.

Just a few extra notes in case anyone else is trying to do the same thing.  Don't forget to check DB integration setup if doing what I did. Drupal was fresh install.