CiviCRM Community Forums (archive)

I have inherited support for a Drupal 6.2 & CiviCRM 3.3.5 application and have been asked to migrate it to the latest version of WordPress & CiviCRM.

I have successfully upgraded through the following versions of CiviCRM (with Drupal 6.2): 3.3.5 -> 3.4 -> 4.1.0 -> 4.1.1 -> 4.1.2 -> 4.1.3 -> 4.1.4 -> 4.1.5 -> 4.1.6 -> 4.2.0.

All upgraded with success messages via CiviCRM interface.

I've followed http://wiki.civicrm.org/confluence/display/CRMDOC/Migrating+from+Drupal+to+WordPress instructions for my 4.2.0 CiviCRM db schema.

Following "Alternatively you can restore your CiviCRM database somewhere else and modify CIVICRM_DSN in <drupal_root>/sites/default/civicrm.settings.php to point to this new database." my application crashed.

I have subsequently compared each upgraded Drupal CiviCRM schema db dump file with the equivalent WordPress CiviCRM schema db  dump file with Vim and there are a lot of inconsistency between the same version schemas from the two environments.

"Alternatively you can restore your CiviCRM database somewhere else and modify CIVICRM_DSN in <drupal_root>/sites/default/civicrm.settings.php to point to this new database." implies that the database schemas will be the same.

I have ensured that "If you are going to be importing and overwriting your older CiviCRM database over the newly installed, blank CiviCRM database, adding IF NOT EXISTS clauses to the CREATE TABLE statements will help the import. DROP TABLE statements will fail because of foreign key restraints." has been employed when creating a db dump. I have also TRUNCATED all tables to see if it was an issue with the data but I still get the same error message in the log files when the application crashes.

Should I be able to point a Version X Wordpress CiviCRM application at an upgraded Drupal CiviCRM MySQL db of the same version?