I’m trying to convert site http://www.mircscripts.org to Drupal, and researching more and more about migration I’ve been getting more and more confused.
There are various modules that supposidly will help with the migration process, but these are nothing but confusing and all lack in either a. documentation (listen up Migrate module!) or b. only support Drupal 6.
The Migration Module you seem to have to dive into PHP code and create some “mappings” to your old table data and Drupal. First off, I would ideally like a GUI (Table Wizard only supports Drupal 6 it seems, and the superseded Data module only Drupal 6 too). I also want to import data into Drupal and not use “mappings.” I want to be able to disable the Migrate module after all the data has been “converted” to be Drupal node compatible.
If you take a look at the site above, you can pretty much see the scale of data, forum, comments, etc and get an idea of how the database tables look, just your usual stuff; users, comments, and more custom stuff like “files” which stores all the different scripts uploaded by users.
Any suggestions on how I would I go about converting the site?
Cheers
Gary
edit: I forgot to mention the site is almost entirely custom made. The code for it looks like my nan on her way to bingo — a complete mess. There is an interesting bit of code available at http://drupal.org/node/261066 if you scroll down, although I don’t feel like doing node_save() 60,000 times for every record, for just one table. It sounds evil.
Take a look at feeds. It’s a GUI importer thing that allows you to map fields in a file to objects like nodes.
http://drupal.org/project/feeds
There’s nothing evil about node_save over all the rows in your table. That’s essentially what any import module should do anyway. I worked on a huge d5 project where we imported millions of nodes that way. It works fine.
Some people have recommended saving to the database directly. Never do that. It’s just not the right way to create nodes. Use the Drupal API!