With Drupal and CiviCRM it is rather straight forward to bulk create Drupal users from CiviCRM individuals and connect them at the same time:

  1. Export the individuals from CiviCRM
  2. Import them into Drupal using the module User Import

It works really nice: Drupal accounts are created and at the same time connected with the CivicRM contacts. And the Drupal module gives you a lot of nice options such as sending out an email with a one-time login or defining user names.

If you try the same approach with CiviCRM organizations, it will create Drupal User records but wont connect them with the according CiviCRM contacts.

I made sure that the matching/dedupe rules should not be a problem (email only) and disabled CiviCRM profiles (the default name and address profile contains individual only fields) - but no success.

Any ideas on how to bulk create organizations? Preferably using Drupal user import or anything that is doable via the UI and/or not too complex?

2 Answers 2


That is indeed how the Drupal / CiviCRM user integration works: Users = Individuals.

We stick to this way of working so we're not restricting ourselves to having to maintain a customisation like this which would be business critical if it stopped working after an upgrade.

Having accounts linked to an individual is also good, as it shows who in the organisation did something, like apply for membership.

It also means things like event registrations work as expected as a person will be attending those.

Using webforms, you can easily expose information about a person and their related contacts so they can update their details as well as their organisation's at any time. Keeping contact 1 as the logged in user makes this easy.

There is also this blog from Whitefuse Media which explains a similar situation and how they handled it (see the section: Drupal Users Synced to CiviCRM Organisations)


  • Thanks for the feedback. However it is possible to link a CiviCRM Organization with a Drupal user account from within CiviCRM. I agree that in many cases it makes sense to have a dedicated contact person handling the login. But there are many other scenarios where you actually want the organization to have an user account (in our case: in addition to the contact persons that get an Drupal account as well...).
    – Fabian
    Jul 15, 2015 at 15:25
  • "it is possible to link a CiviCRM Organization with a Drupal user account from within CiviCRM" ? care to confirm how/where?
    – petednz - fuzion
    Jul 16, 2015 at 0:27
  • @pete: If you you view an organization simply choose "create user record" from the action menu.
    – Fabian
    Jul 16, 2015 at 6:53
  • There is no "out-of-the-box" solution for this. You would need to build something custom. Please see the link to the Whitefuse Media blog where they discuss making this customisation and where they have shared their code. It was written a few years ago now, so may not be compatible with your current versions.
    – Heather O.
    Jul 16, 2015 at 7:30
  • @Heather: Do you happen to have the link to the Repository of the moduel? As the CiviCRM UI already provides what we want, I will also look into doing it via the API... Other suggestions are still aprecciated :)
    – Fabian
    Jul 16, 2015 at 11:22

You can use the approach outlined here which uses Drupal Rules to create the User and send them a 'you have an account' email etc. The Rule can be triggered off a Civi Tag, ie you find your Orgs, you Tag them with a tag such as 'create drupal account' and Rules does the rest.


  • Thanks for this, I had seen you Blogpost but was hoping to avoid all the entity & rule setup as I only need to the whole user creation thing initially. Anyway, I will try a couple of approaches and let all of you know how it turned out (and mark one answer as the correct one ^^)
    – Fabian
    Jul 17, 2015 at 6:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.