So back in 2006 Drupal 5.x was introducing some cool new features to the open-source scene that had me wondering about the future of WordPress. Fast-forward to 2009, and WordPress has made some major changes since 2.5 that have made blogging fun again. Hooray! As trends continue to boom and bust, and creative masses are moving from technology to the next, the ability to take your content with you is invaluable. Here’s how I did it.
I debated whether I should post this because there are already at least five other guides at the time of this writing. But while D’Arcy’s was the most recent, a number of things had changed to where it still needed some tweaking to get right. I figured time is money and any time-saving tips are worthwhile. Hopefully this helps you at least for the next few versions of these platforms.
Note: While this gets you pretty darn close, you’ll still want to know a little about SQL, Drupal, and WordPress to customize this to fit your installation. Since Drupal was designed to be a CMS, not specific to blogging, there are multiple ways you could have configured the site to operate as a blog. Not knowing your setup ahead of time, I’m just going to show you mine. Here’s the SQL script to handle the import and conversion:
# Changelog # 02.06.2009 - Updated by Mike Smullin http://www.mikesmullin.com/development/migrate-convert-import-drupal-5-to-wordpress-27/ # 05.15.2007 - Updated by D’Arcy Norman http://www.darcynorman.net/2007/05/15/how-to-migrate-from-drupal-5-to-wordpress-2/ # 05.19.2006 - Created by Dave Dash http://spindrop.us/2006/05/19/migrating-from-drupal-47-to-wordpress/ # This assumes that both wordpress and drupal are in separate databases. The wordpress database is called "wordpress" and the Drupal database is called "drupal" # first, nuke previous content in wordpress database TRUNCATE TABLE wordpress.wp_comments; TRUNCATE TABLE wordpress.wp_links; TRUNCATE TABLE wordpress.wp_postmeta; TRUNCATE TABLE wordpress.wp_posts; TRUNCATE TABLE wordpress.wp_term_relationships; TRUNCATE TABLE wordpress.wp_term_taxonomy; TRUNCATE TABLE wordpress.wp_terms; # categories INSERT INTO wordpress.wp_terms (term_id, `name`, slug, term_group) SELECT d.tid, d.name, REPLACE(LOWER(d.name), ' ', '_'), 0 FROM drupal.term_data d INNER JOIN drupal.term_hierarchy h USING(tid) ; INSERT INTO wordpress.wp_term_taxonomy (term_id, taxonomy, description, parent) SELECT d.tid `term_id`, 'category' `taxonomy`, d.description `description`, h.parent `parent` FROM drupal.term_data d INNER JOIN drupal.term_hierarchy h USING(tid) ; # posts; keeping private posts hidden INSERT INTO wordpress.wp_posts (id, post_date, post_content, post_title, post_excerpt, post_name, post_modified, post_type, `post_status`) SELECT DISTINCT n.nid `id`, FROM_UNIXTIME(n.created) `post_date`, r.body `post_content`, n.title `post_title`, r.teaser `post_excerpt`, IF(SUBSTR(a.dst, 11, 1) = '/', SUBSTR(a.dst, 12), a.dst) `post_name`, FROM_UNIXTIME(n.changed) `post_modified`, n.type `post_type`, IF(n.status = 1, 'publish', 'private') `post_status` FROM drupal.node n INNER JOIN drupal.node_revisions r USING(vid) LEFT OUTER JOIN drupal.url_alias a ON a.src = CONCAT('node/', n.nid) WHERE n.type IN ('post', 'page') ; # post -> category relationships INSERT INTO wordpress.wp_term_relationships (object_id, term_taxonomy_id) SELECT nid, tid FROM drupal.term_node; # category count updating UPDATE wp_term_taxonomy tt SET `count` = ( SELECT COUNT(tr.object_id) FROM wp_term_relationships tr WHERE tr.term_taxonomy_id = tt.term_taxonomy_id ); # comments; keeping unapproved comments hidden INSERT INTO wordpress.wp_comments (comment_post_ID, comment_date, comment_content, comment_parent, comment_author, comment_author_email, comment_author_url, comment_approved) SELECT nid, FROM_UNIXTIME(timestamp), comment, thread, name, mail, homepage, status FROM drupal.comments; # update comments count on wp_posts table UPDATE `wp_posts` SET `comment_count` = (SELECT COUNT(`comment_post_id`) FROM `wp_comments` WHERE `wp_posts`.`id` = `wp_comments`.`comment_post_id`); # fix breaks in post content UPDATE wordpress.wp_posts SET post_content = REPLACE(post_content, '', ''); # fix images in post content UPDATE wordpress.wp_posts SET post_content = REPLACE(post_content, '"/files/', '"/wp-content/uploads/');
Things to be aware of:
- Always backup first, and don’t try this on a live server.
- Rename wordpress and drupal to the actual names of your databases.
- Remember to move your images from ./files into the ./wp-content/uploads directory. My Drupal ./files directory followed the same ./YYYY/MM/DD/filename URL structure for blog post images and attachments but yours may need to be manually renamed.
- You’ll likely need to use the WordPress Redirection plugin to preserve any link juice from your old permalink structure, where any changes occur.