Content migration, import, and export

Events happening in the community are now at Drupal community events on www.drupal.org.

Converting a web site from one content management system (or - ack! - raw HTML files) to another is always challenging. Going to Drupal is no exception. How does one go about it? What are the challenges and what's the best way to meet them? And what about exporting content from Drupal for use by other systems?

This group (formerly Data Import/Export, devoted to one solution) is for discussion of best practices in content migration. How do you manage the process? What are the things that are likely to trip you up? What tools are available?

In the short term, a major focus in this group is seeing if we can consolidate some of the myriad existing tools to aid in migration.

Jaza's picture

Direct database querying: pros and cons

Posted on behalf of dman@drupal.org:

From http://basement.greenash.net.au/soc2006/ImportExportApiModule?show_comments=1#comment_19:

Where is good for discussions? A Drupal.org thread, the issues register, or somewhere here? I'd rather keep it open than emails.

Granted you may not be ready for a code review yet :) I had a quick look and was surprised you are attacking the database directly. Wouldn't it be better to let Drupal continue to handle the serialization, and get (eg) user_load() or node_load() to instantiate the php object, and base your mappings to that structure? By digging directly at the database (clever though your structure mapping system is) you are bypassing a lot of Drupal goodness, especially once you come to node_load().

Read more
Subscribe with RSS Syndicate content

Content migration, import, and export

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week