It's a rare thing, the web project that starts with a perfectly clean slate. Almost every organization has some kind of history, represented in database tables, spreadsheets, even raw HTML if you're particularly unlucky. The Feeds module can be great for bringing that kind of data into Drupal, when the source is relatively simple and the mapping is straightforward. But when you find yourself needing to impose some custom logic onto your import process, it may be time to use Migrate.
In this session, we'll learn about some of the key features of Migrate and discuss the main advantages and disadvantages of a Migrate-based import solution over one using Feeds. We'll go through the process of creating a Migration class, exploring its various components and their use. Finally, we'll demonstrate the migration process itself and open up the floor for questions. Prior knowledge of Migrate or Feeds is unnecessary, but we will be examining PHP code in some detail.
Collaborative notes link: http://bit.ly/18iKgLV
Presentation slides: http://ten7.com/drupal-camp-2013-migrate
All attendees should leave in a better position to evaluate whether a Migrate-based solution is appropriate for a given import task. Developers will leave with a basic understanding of how to implement their own custom Migrations, and where to find the documentation and reference material to continue along.