Content Importer

JUNE 6th, 2009: I plan on spending a week or two examining both migrate and content importer to see if this project fills a need or simply duplicates a solution. Have an opinion? Put it in the issue queue, or email. I'd love to hear it.

The content importer is designed to be a framework which can be used to easily import content from other systems. It is designed for the group that has already got a blog somewhere, but doesn't understand any of the inner workings of the software.

For users that have a degree of understanding of Drupal, I would suggest the migrate module.

To put it simply, if the migrate module were a swiss army knife, the content importer would be safety scissors: the main goal is to let users import data with cutting their fingers off. For users that have a degree of understanding and confidence about the way that data is stored or have a unique migration need, migrate would undoubtably be the way to go. For users that understand that the submit button somehow saves "what I typed" to the internet, the content importer would be the module that they might prefer.

At the moment, this is still in the earliest stages of development. Do not expect this project to work yet. (However, if you'd like to change that, you are more than welcomed to contribute code.)