Author Topic: Migration civicrm db from drupal to joomla (Read 1649 times)

dirkvds · March 11, 2013, 12:34:19 am

I've setup a civicrm in drupal some time ago. At that time it seemed to me that the functionality/integration in drupal was better (and it probably still is) even though our organisation's website is in joomla (2.5). I was thinking about moving the website to drupal if needed. By now, I do have a stable civicrm database, but still would prefer to keep the website in joomla. I know there are lots of reasons to choose for drupal or to stay with joomla - but this question is not intended to start this discussion - as it is already being discussed in many other threads.
As for integration reasons and towards my site user's ease of use, it would make more sense to move my civicrm installation to joomla. I have been trying to get this done based on the material that I could find in the documentation and on the forum. So far I have not succeeded. Setting up a fresh install of civicrm in joomla is easy enough, but when I try to migrate my existing data, the civicrm becomes useless, giving me an error that some database table or field is missing (without specifying which table of field actually is missing). It appears that I run into problems because of two reasons: either because I enable the multilingual features of civicrm or because of custom fields that were added. In both cases the database structure seems to be different from the standard core installation, so that after moving the existing tables to the joomla installation, there are inconsistencies.

As I am kind of swimming against the usual flow and wanting to go from drupal to joomla, I am not finding a lot of useful tips here. Anyone had experience in doing this migration? Or can anyone tell me how I can see in the error message what table of field exactly is missing, so that hopefully would give me a hint there.

Version info about my current installation:

CiviCRM version:4.1.3
CMS version:Drupal 7
MySQL version:5.1.66
PHP version:5.3

Trying to go to a joomla 2.5 installation (same MySQL and PHP).

lcdweb · March 11, 2013, 05:12:27 am

civicrm works great in joomla, and at this point, there really is no significant benefit to using drupal over joomla. it's a matter of preference.

I suspect the problem you're running into is that you're transferring your 4.1 database into a 4.2 installation. here are the steps I would follow:

1) drop all civicrm tables from your joomla installation
2) import the civicrm tables from your drupal installation into the main joomla database
3) truncate the uf_match table. that table links the CMS user id to the CiviCRM contact id. because you are moving to a different CMS, those values will no longer match. truncating the table clears out those connections and will cause CiviCRM to recreate the link as the system is used (you can also for a resynchronization if desired).
4) install civicrm 4.2 using the standard method (upload the package to the /tmp directory, unpack, and use the joomla extension manager install-by-directory method)

after the extension is installed, you will receive an upgrade screen prompting you to upgrade from v4.1 to v4.2. click the link to trigger the DB upgrade.

dirkvds · March 16, 2013, 02:06:55 am

I will try the steps you descibed, but there was no attempt to transfer the data from a 4.1 to a 4.2 installation. I have a running civicrm 4.1.3 installation in Drupal with my data on a hosted machine and a joomla with a 4.1.3 installation that works without any data in it yet on a local virtual machine running ubuntu. I dropped the joomla tables and then imported the civicrm tables from the drupal installation (with some exceptions as was indicated in the civicrm documentation - like the civicrm_domain and some cache tables - cfr wiki.civicrm.org/confluence/display/CRMDOC41/Moving+an+Existing+Installation+to+a+New+Server+or+Location). When that is done civicrm fails because of missing database structures...

But I'll give it another try and post the exact message that I get.

lcdweb · March 16, 2013, 04:40:29 am

you still have to transfer those tables. you just can truncate them.
in the civicrm_domain table, you only need to empty the backend_settings field for the single record that exists there. for the cache tables, they can be completely truncated.

CiviCRM Community Forums (archive)

News:

Author Topic: Migration civicrm db from drupal to joomla (Read 1649 times)

dirkvds

Migration civicrm db from drupal to joomla

lcdweb

Re: Migration civicrm db from drupal to joomla

dirkvds

Re: Migration civicrm db from drupal to joomla

lcdweb

Re: Migration civicrm db from drupal to joomla