What we'd *like* is for Commerce Migrate Ubercart to handle converting an Ubercart site to Drupal Commerce as almost an upgrade process. It would be great if you could go through a simple process with your working Ubercart store and end up with a Commerce store with equivalent features. We have a ways to go for this, and it may not be achievable, but this issue is to describe a roadmap.
Here's a list of wanted features in (possible) priority order:
| Feature | Level of Effort | Issue | Description |
|---|---|---|---|
| Attributes | 3-5 days | #1210280: Support attributes on products and mutivalue product reference fields | Doing attributes means
|
| Taxonomy/Catalog | 2 days | #1212172: Bring Ubercart Taxonomy/Catalog into Commerce | We should recreate the catalog on the Ubercart side on the Commerce side |
| Consolidate customer profiles | 1 day | #1212174: Consolidate identical Customer Profiles | Currently each Ubercart order is turned into a profile. We should at least try to consolidate like profiles. However, it's possible this should be done outside/after migrate. |
| Customer purchase history | 1 day | #1211024: Capture customer purchase/payment history | Currently there is no purchase history. |
| Customer payment history | 1 day | #1211024: Capture customer purchase/payment history | Currently there is no payment history |
| Migrating Ubercart as opposed to upgrading | 1 day | #1206348: Ubercart: Use Cross-database import in addition to self-importing ubercart database | Currently, commerce_migrate_ubercart assumes that the source database is the site where Migrate is running. This is quite messy, as it means all the ubercart modules, tables, nodes, etc. are in there, and there's no good way to clean them up. It would be far better to bring in the Ubercart store from a remote database. |
Things we should probably not do at this point:
- Taxes and the like
- Any support for most Ubercart contrib modules
Comments
Comment #0.0
rfayImproved roadmap
Comment #0.1
rfayAdded Taxonomy
Comment #1
recrit commenteddisplay node comments should be added to the roadmap since they provides valuable user feedback
#1324448: Migrate product comments?
Comment #2
btmash commentedFiguring out a way to migrate product kits would be great (though I guess I'm not entirely sure how it all fits into commerce; I understand multiple products can be referenced though I am unsure on what else is necessary.
Comment #3
rfayComment #4
CraigBertrand commentedAny idea how recurring fees would come over?
Comment #5
rickmanelius commented@CraigBetrand considering the functionality is a bit different, I don't know if there is a clear upgrade path for that... particularly since it's not part of the standard ubercart/drupal commerce packages.
Comment #6
nightlife2008 commentedHey rfay, if you're interested in enabling some exotic stuff like taxes and discounts, the following could be an option. I have figured out that the easiest way to properly have your orders contain the correct discounts and taxes, is to resave an order in the commerce site.
This actually requires someone to manually setup the "corresponding" discounts and tax rules as the ubercart, which is the easiest way as there are different possibilities (coupons, discounts, taxes, vat, etc).
Once these rules are set up in the Commerce website, the saving of an order object will trigger the necessary actions to add discounts and taxes.
The following 2 lines of code actually do the job quite well:
I have created the batch functions which actually do this:
Comment #6.0
nightlife2008 commentedAdd issues to each item in table
Comment #7
Anonymous (not verified) commentedMost of these items are now in the 7.x-2.x branch or can be achieved by using the latest migrate_d2d in the UI.
Attributes is the only item that stands out as might be needing some work so please take any patches over to that issue and roll against 7.x-2.x.