Changing CMS from WordPress to Drupal

[robbrandt]

I have a client who has a failed launch of their CiviCRM site under WordPress, and I want to help them get it going under Drupal.  The WordPress installation got hosed and doesn't run, CiviCRM isn't accessible.  There were numerous custom fields and profiles, and an unknown number of extensions relating to the public side of WordPress.  Our focus will be to get the backend running under Drupal, not so concerned about public facing functions at the moment.

What do I need to do to get this running under Drupal?

[Erik Hommel]

That is a far too generic question on a fairly specific problem :-)

In general, I would install a clean Drupal and CiviCRM installation (same version), and then import the database back in?
http://wiki.civicrm.org/confluence/display/CRMDOC/Moving+an+Existing+Installation+to+a+New+Server+or+Location

[Coleman Watts]

I love drupal too, but just to play devil's advocate for a minute:

What's the rationale for changing CMSs midway through this project?
Since doing so will always cost time and money, hopefully the rationale is more compelling than just the preference/bias of the implementer.
Here's a quick bias-check: If a client had "hosed" their drupal site by installing a couple of incompatible modules, would you recommend they scrap the whole thing and switch to Joomla or Wordpress?

[robbrandt]

Thanks Coleman;

The client doesn't really have a preference, I do, and for some political (not economic) reasons it would be helpful to the organization to be able to say, clearly, that they aren't using the previous implementor's work (I did the Civi setup, she did the Wordpress integration).

That said, I might learn some Wordpress just to get the broken site operational, at least so that it's easier to see what was done where.  What I know so far is that there are old, unsupported commercial Wordpress extensions that are throwing fatal errors.