Comments on: Migrate data from WordPress to Drupal 6

By: Nick

Nick — Fri, 12 Nov 2010 03:20:37 +0000

Hi, the value of ’50′ that you referred to is simple a default. You can change that in the admin settings for bulk alias updates.

By: Ahimsauzi

Ahimsauzi — Tue, 16 Mar 2010 15:27:33 +0000

What an amazing review! Thank you so much for all the tips! As of March 16th, the only change to the above was to update wp2drupal once I installed the one from the link you provided!

Thanks!

By: anonymous

anonymous — Thu, 07 Jan 2010 19:54:45 +0000

A million thanks for posting this. At least a million.

I have all my data in drupal now. I don’t know about nodes and paths yet (just starting out). Is it possible to do the pathauto module at some time in the future, or will that present a problem?

By: Steve

Steve — Thu, 19 Nov 2009 22:05:30 +0000

My current blog is at:

mysite.com/blog/

A typical blog post URL is (‘ugly’ WordPress URLs):

mysite.com/blog/?p=1234

I’m migrating to Drupal and, on a test site, have followed these steps but when I visit:

mysite.com/blog/?p=1234

It displays the landing page for all blog posts and the URL transforms to (the final slash is removed):

mysite.com/blog?p=1234

Any thoughts?

By: Mitchell

Mitchell — Thu, 03 Sep 2009 03:19:42 +0000

Thank you for helpful article.

FYI – according to WP users UTF converter truncates posts.

I am going to try WP2Drupal in a few minutes, and hope it works.
But I am going to start by removing all revisions in WP DB, which you did not mention.

Best wishes, Mitchell

By: mssmotorrd

mssmotorrd — Sun, 03 May 2009 12:51:40 +0000

It’s the first time I commented here and I must say you share us genuine, and quality information for bloggers! Good job.
p.s. You have a very good template for your blog. Where did you find it?

By: Damien McKenna

Damien McKenna — Sun, 12 Apr 2009 03:04:45 +0000

FYI, I’ve set up a project for the D6 version of WP2Drupal:
http://drupal.org/project/wp2drupal
I’ve stabilized it and will be adding features to solidify the data migration.

By: vivek

vivek — Mon, 19 Jan 2009 07:32:15 +0000

Thanks for your response! From what I understand, rewriterule doesn’t accommodate mysql requests on its own, hence the need for the rewritecond. I might be wrong about that, but this is how I got it to work:

Put the following in .htaccess:
RewriteCond %{QUERY_STRING} ^p=(.*)$
RewriteRule ^$ /node/%1? [R=301,L]

Obviously for this to work the WordPress post ID has to match the Drupal node ID.

These lines also assume that Drupal has replaced WordPress in the same directory.

Again, hats off to you for the wp2drupal hack. It’s a great way to redirect URLs for those of use who stuck with the default WordPress permalinks!

By: Webopius

Webopius — Sun, 18 Jan 2009 09:01:43 +0000

Thanks Vivek,

You’ll see I’ve made a slight change to the code in the post that makes sure the Drupal nodes match the WP posts IDs. I was missing the vid previously.

To answer your question, if you already have WordPress URLs with the post ID in, such as ‘/somepath/p=n’ and you want to redirect all of these to the equivalent node id based URL in Drupal, something like this should work in your .htaccess file:

RewriteRule ^(.*)p=(.*)$ node/$2

(I haven’t tested this so you may need to alter it slightly)

By: vivek

vivek — Sun, 18 Jan 2009 06:50:42 +0000

This is a great page, thanks.

I’d been messing around with wp2drupal for a while, and your instructions on getting post ID to match node ID is exactly what I needed. There’s one more step I need to make for post redirects, however, and I’m not sure how to do that.

In my .htaccess file, I know how to take a query to the old wordpress database (?p=900, for example) and redirect it to /node/900:

RewriteCond %{QUERY_STRING} ^p=900$
RewriteRule ^$ /new/node/900? [R=301,L]

Is there a way to tell .htaccess to redirect all queries ?p=n to /node/n?