Drupal to WordPress migration technical FAQ

How can we send you the database dump file?

The best way would be either:

  • as a downloadable file on an FTP or SFTP server;
  • via a private link to the file using a file sharing service like DropBox.
  • through a file-sending service like DropSend.

Do not place the file in a publicly accessible location on your web server.

The dump file should be a compressed .sql file in UTF-8 character set.

Do you need my entire Drupal database?

Having access to your entire Drupal installation database is useful for troubleshooting and analysis but not necessary for most content-only migrations. At a minimum, I’ll need the following Drupal tables:

  • comments
  • node
  • node_revisions
  • node_type
  • system
  • term_data
  • term_hierarchy
  • term_node
  • url_alias
  • users_roles
  • users
  • variable
  • vocabulary
  • vocabulary_node_types
  • Any table pre-fixed with ‘content_’
  • Any table pre-fixed with ‘field_’

Can you run a migration while we’re developing the WordPress site?

An empty WordPress installation would make migration easier but theme and plugin development can often be done concurrently with content migration. The migration should be simple if whatever you’re doing can be deactivated via the WordPress Dashboard and then re-activated at the end of the project.

Things get more complicated if your development involves significant configuration, adding content or users. Because of the way WordPress stores configuration information in the database, we’ll almost certainly overwrite settings and possibly corrupt the site. Migrating content into WordPress installation with pre-existing content requires extra steps. It’s possible but involves more work.

Which WordPress tables will you write to?

A typical Drupal to WordPress migration involves writing to the following WordPress tables:

  • wp_comments
  • wp_posts
  • wp_postmeta
  • wp_terms
  • wp_term_relationships
  • wp_term_taxonomy
  • wp_usermeta
  • wp_users