CiviCRM Community Forums (archive)

Dear "CiviCRM specialists",

I need to export all of my Joomla CiviCRM 3.4.8. users with their referring memberships, custom fields AND their login name and password.
Then I need to import this csv file into my Drupal 7 CiviCRM 4.2.2 installation.

The needed result is that our users can login with their existing "Joomla /CiviCRM" login credentials (username & password) in our new Drupal 7 / CiviCRM 4.2.2 site.

Is there a standard procedure for this?

I am aware of how to export users in CiviCRM but not sure if and how the username/password issue must be correctly handled for working with Drupal's standard user authentication later on.

Thx for any info or where I might find suitable documentation on this (I read through the manuals but no luck here)
Gerhard

Dear Hershel,

thx a lot for your prompt and helpful reply. I am already following the steps of the docs you've recommended.

Before deleting anything I am wondering if this in my case is also the right way to use my old Joomla users ("Migrating from Joomla to Drupal") mapped to contacts in Civi:

"Empty the civicrm_uf_match table

This table is used for mapping your CMS users with CiviCRM contacts. At this stage those mappings will be according to users from your Joomla site. You will need to delete these mappings so that Drupal can then automatically rebuild them from the new users table."

Does that mean I delete these mappings from Joomla/Civi -> import the old Joomla users with the Joomla to Drupal Module and sync Users and Contacts with the Civi
"Synchronize Users to Contacts" tool?

But what happens to our different Membership associations , our custom fields the contacts have filled out etc.? Are these lost then?

Thx a again for the helpful support.

Viele Gruesse from Germany - Gerhard

Great, thx again. Just struggling with the version Civi 3.4.8 coming from the old Joomla site which is Drupal 6 only, changing MyISAM to InnoDB, then upgrading the 3.4.8 to 4.2.4, using Drupal 7 and then the user import...
But with your help/info above I am optmistic to get it done somehow... :-)

Thx and viele Gruesse
Gerhard

 

5) I followed the steps there but at step 7 I have no clue what is meant there:

You are done. You don't need to proceed past where it says "Now the new database is ready for upgrade to next higher version." Just try the upgrade again there. If it fails, then post for us exactly what steps you are taking to fix the schema.

where does these version numbers are coming from anyway (ancient times when it was civicrm 1.x?)? Confusing!

Yes, CiviCRM was 1.x in ancient times. There are even a few elders still left on the team who remember those days.

@lobo: :-)

Dear Hershel,

thx for the reply & help.  Since I still didn't succeed here is a short wrap-up of what I have tried so far (only the last attempt of my 5 complete "run-throughs"):

1) I edited the sql file of the joomla and civicrm 3.4.8 in an editor, deleted all the joomla tables, changed all the civi Tables from MyIsam to InnoDB, deactivated forreign keys (SET foreign_key_checks = 0;) and added to the last line this again (SET foreign_key_checks = 1;).

2) Imported this file via SSH (mysql command) in an empty mysql db and changed everything according to the documentation (Joomla to Drupal) with my Drupal 6 domain for this purpose:
TRUNCATE TABLE `<civicrm_database>`.`civicrm_uf_match`;
Update the Directory Path and URL
Update the Resource URLs
TRUNCATE TABLE `<civicrm_database>`.`civicrm_menu`;
UPDATE `<civicrm_database>`.`civicrm_domain` SET `config_backend` = NULL
WHERE `civicrm_domain`.`id` = 1 LIMIT 1;

after this last step, the CiviCRM Menu shows up in Drupal but also "1 meter civi error messages" ("warning: array_key_exists() [function.array-key-exists]: .../civicrm/CRM/Core/BAO/Setting.php on line 175").

I managed to succeed here with pasting the drupal 4.2.4 ingredients from the clean Drupal 7 install and civicrm 4.2.4 into the field `civicrm_domain` `config_backend' (instead of NULL, which always lead to the horrible 100+ error messages, deleting the templates_c folder/en-US didn't help neither before...! (I read through nearly all of these issues before :-)

Now I can use civiCRM 3.4.8 on my Drupal 6 test site and can search for contacts etc..
I dumped this "working" mysql (SSH) again.

3) D7 / CiviCRM 4.2.4
I imported this dump in an empty new mysql on my live server, connected this 3.4.8 civicrm mysql db to my Drupal 7 CiviCRM 4.2.4 (via editing civicrm.settings.php)

Then I tried to run the upgrade script (http://<your_drupal_home>/civicrm/upgrade?reset=1) - but without success:

"Sorry but we are not able to provide this at the moment.
The upgrade has identified some schema integrity issues in the database. It seems some of your constraints are missing. You will have to rebuild your schema before re-trying the upgrade. Please refer Ensuring Schema Integrity on Upgrades"

Then I followed all the steps from here: http://wiki.civicrm.org/confluence/display/CRMDOC42/Ensuring+Schema+Integrity+on+Upgrades
with a clean mysql (not the one which I attempted to upgrade in the step before (Itook again the initial dump that came from step 2 (D6, civicrm 3.4..

I used the 4.2.4 sql scheme only from .../sites/all/modules/civicrm/sql/civicrm.mysql (without data, imported one custom field table structure only from 3.4.8, imported the dump (with data) again (SSH) in this 4.2.4 structure only db and connected this to my Drupal 7 / CiviCRM 4.2.4.
It shows civiCRM 4.2.4 environment, civi menu, etc.  but when I try to search e.g. for a contact (or a member) I get the following error:

"Sorry but we are not able to provide this at the moment.
DB Error: no such field

Return to home page."

When I try to upgrade this db I still get the same error as before (see above):

""Sorry but we are not able to provide this at the moment.
The upgrade has identified some schema integrity issues in the database. It seems some of your constraints are missing. You will have to rebuild your schema before re-trying the upgrade. Please refer Ensuring Schema Integrity on Upgrades"

So I assume I have done a very decent job but unfortunately without a working civiCRM on my Drupal 7 / CiviCRM Live Server :-(

Thx again and viele Gruesse aus dem super sonnigen Köln (schwitz!) -Gerhard

Hallo,

one day later (and following your steps 1. - 4.) still no change:

"Sorry but we are not able to provide this at the moment.
The upgrade has identified some schema integrity issues in the database. It seems some of your constraints are missing. You will have to rebuild your schema before re-trying the upgrade. Please refer Ensuring Schema Integrity on Upgrades

Return to home page."

I used the clean scheme from 3.4.8 this time in a fresh new mysql and imported the working dump data from D6 / CiviCRM 3.4.8 in it (changed from MyISAM to InnoDB this time with VI (Shell) which helped me to keep the correct UTF-8 encoding (every Windows Editor destroys this and so German Umlaute are destroyed as well ...)

So I guess this upgrade is just not ppossible?

What if I manually import all the Users into the empty 4.2.4? How do I keep all activities or at least memeberships and custom fields existing in the 3.4.8 civiCRM mysql.

Thx -G

I don't follow you. If it's a data-ONLY dump then there are no tables, so MyISAM and InnoDB should be in that dump.

I use the "mysqldump" command to dump the working mysql (I only know that with a -d command inserted the result is a structure only dump with no output data exported)
Is there a command to only dump the data without tables?

The documentation "Ensuring Schema Integrity on Upgrades" suggests to

mysqldump -u username -p -c -e -n -t databasename > datafile.sql

I don't what the -c -n -t stands for.  Maybe this is the solution?

:-)

(Puh)
Thx -G