- Migrate destination field handlers for commerce fields (reference fields, price field)
- Migrate destination plugin for commerce product types.
Commerce Migrate depends on Migrate Extras for Entity API and Address Field integration.
Commerce Migrate Ubercart, formerly a submodule, has moved to its own project. It can migrate 6.x and 7.x Ubercart stores from either the existing Drupal database or a remote database.
When should you use Migrate/Commerce Migrate vs Feeds/Commerce Feeds?
In general, you'll use Feeds and Commerce Feeds when there's a one to one mapping between the input data and the entities you're importing. So Feeds is fantastic for importing products from a CSV file, for example. For Commerce Feeds see this article/screencast. It's not very strong in transforming data on the way in though. Much of the time a feeds migration can be done without touching any code.
Migrate and Commerce Migrate, in general, know how to transform things mightily, with the full power of SQL and PHP, on the way in. So you *can* do something like an Ubercart to Commerce migration, and you can solve the problems of a specific migration. So Migrate is the solution for more complex migrations, and it's the home of Commerce Migrate Ubercart, which solves some of the Ubercart migration issues. There's an article/screencast on that here. Much of the time a *migrate* migration will require writing PHP code.
- Demonstration screencast
- Presentation from Drupalcon London 2011
- The Migrate handbook page
- The Migrate examples included in the Migrate module