Converting to Drupal

Hi everyone,

Here is my trouble.
I would like to import around 60000 records from my old MS access table to drupal site. I spent few days searching different ways to do this, installed dozen of modules, but still haven't find a good way. Note I am not php coder and still dont know much about Drupal, but I can do anything with database. So my question is if I can create nodes directly with database import to MySQL using MySQL import instead of Import modules.

Hi all,
I hope I haven't shot myself in the foot, I've set up Drupal using a test domain name and got it how I want thinking that it will be easy to copy the files over to the correct directory on the live server but I think there are references to the test domain name in paths in the sql database, am I right and is there an easy way to correct this please?

Thanks,

Wayne.

I'm looking for some advice on if I should upgrade our existing Drupal system and custom modules, use a new Drupal system with a specific non-custom module that gives us the same functionality, or should I consider not using Drupal at all.

Basically, instead of the expensive user-licensing fees of the nightmarish ERP software used company-wide, we have a user-access controlled intranet site providing reporting and searching capabilities on the SQL Server 2000 DB used by the ERP software (pull only, not push). Drupal was chosen by my predecessors predecessor, installed, and multiple custom modules were created over the last 3.5 years to extend this functionality.

Hello! I used the joomla to drupal module to convert joomla users to drupal. That module maps the user ids and give the users new id's on the drupal installation. Then I used the migrate module to migrate an image gallery. The problem is that the image gallery had stored the joomla user ids as author. Since the joomla to drupal module had changed the id's the wrong author is shown.

I am looking for suggestions for how I might persuade a large University's IT department to support Drupal. I am a Drupal developer and have 'sold' a client on using Drupal to develop their web site, but the client (a research group within the university) has learned that their IT department does not support Drupal. I suspect they are short-staffed and fear the additional burden of supporting 'new' technologies (e.g. individual MySQL databases, which they do not currently support).