VirtueMart Forum

VirtueMart 2 + 3 + 4 => Installation, Migration & Upgrade => Topic started by: Hammerhead on September 09, 2011, 03:47:01 AM

Title: 'Selective' Migration
Post by: Hammerhead on September 09, 2011, 03:47:01 AM
I would like to migrate to J1.7 and VM2.x, but do NOT wish to take the former catalog with me because we are changing our store strategy so dramatically for this year that none of the old catalog information pertains.  The only thing I wish to migrate are users, order history/invoices (etc.) and some settings if possible.  How would one go about doing this?

Thanks in advance for your help!
Title: Re: 'Selective' Migration
Post by: Milbo on September 09, 2011, 09:14:23 AM
There are different tasks. We want to add even some more options, like port flypages to layout and things like this.

But afaik you can do that.
Title: Re: 'Selective' Migration
Post by: PRO on September 09, 2011, 17:03:02 PM
Milbo, the flypages use different php variables etc. I dont think its worth the trouble.

Title: Re: 'Selective' Migration
Post by: Milbo on September 09, 2011, 20:51:27 PM
You misunderstood me Banquet, when people already heavily used different flypges in vm1.1 then they should port them to layouts, give them the same name and when they import their products then, the products use the old "flypages".
Title: Re: 'Selective' Migration
Post by: Hammerhead on September 10, 2011, 15:57:26 PM
Mibo, thanks for the reply.

I'm presently running VM 1.1.5 - not sure which current version of VM is recommended - do I want 1.9?  2.0?  In either case, where would I find the migration script to upgrade and bring my data to a new installation?  Not seeing it in the downloads area.

Thanks!
Title: Re: 'Selective' Migration
Post by: Milbo on September 10, 2011, 18:48:14 PM
You dont need that, just wait for the next release. We enhanced the migrator again. The migrator is IN vm2, you don't need to uninstall vm, just unistall the old modules /plugins for vm1.1
Title: Re: 'Selective' Migration
Post by: Hammerhead on September 16, 2011, 18:49:44 PM
Sounds good... when's the new release due?  I'm rather anxious to relaunch my store soon, so that we can capture the opportunity in this upcoming holiday season.  Is it not possible to start the migration now?  Remember - all I really need are customer/users , order history and the other components/modules are already available.

IOW, could I not use Akeeba to create a 'migrate' installation, upgrade that VM install, then bring the result to a new fresh Joomla/VM installation to begin rebuilding my catalog?

Just not really sure what the 'order of operations' should be, here.  Would appreciate some guidance... I'm a bit lost in the woods.

Thanks!!!
Title: Re: 'Selective' Migration
Post by: Milbo on September 18, 2011, 11:20:37 AM
You can of course use the svn.

I hope that helps http://dev.virtuemart.net/projects/virtuemart/wiki/Upgrading_VM1_to_VM2_with_provided_packages

just updated
Title: Re: 'Selective' Migration
Post by: Hammerhead on September 19, 2011, 18:01:24 PM
Mibo, thanks for your reply, that information helps.

I think what I want to do is still not clear.

I want to start with a new fresh installation.  But I do want to bring over only users and orders from the existing store.

Here's what I plan to do.  Let me know if you see anything wrong?

1) Use Akeeba to backup and install old store to a temporary folder and temporary DB
2) Disable all VM plugins on temporary site.
3) Install VM2 and use migration tool on temporary site.
4) ?  - Not sure what to do about getting the old users/orders to the new fresh install.

To clarify, I will NOT be needing any old templates, store settings, manufacturers, items, images or anything.

My objective is to start over, as though I were beginning "from scratch", but with the benefit of having legacy customer information only.
Title: Re: 'Selective' Migration
Post by: Milbo on September 19, 2011, 22:48:17 PM
I could do a file for you, doing this.
Title: Re: 'Selective' Migration
Post by: Hammerhead on September 19, 2011, 22:59:29 PM
That's a possibility, but it would help me to go through the exercise to understand more about VM and how it works.  I'm still learning.

So, if I follow the above procedures, what table(s) would I need from the temporary DB?  I presume I'd need some Joomla tables also, yes?  Is it safe to just import those tables directly into the target DB after changing the prefix accordingly?
Title: Re: 'Selective' Migration
Post by: Milbo on September 20, 2011, 00:36:43 AM
oh, for exampel for the orders you need the products, I would write it in your case so, that the products are not published
of course you can migrate them without products, but I may have todo some extra work.
Title: Re: 'Selective' Migration
Post by: Hammerhead on September 20, 2011, 16:46:16 PM
Is there no way to import legacy data without having the corresponding product?  What if the items are no longer made or carried in the store, but we still want to know what a customer ordered, when, and how much they spent with us?

Again, all I really want is to bring forward legacy order and customer information.  I presume I'll need both VM and Joomla user information, but I need to understand what data is required and how to get it over to a new (vanilla) install.

Thanks!
Title: Re: 'Selective' Migration
Post by: Hammerhead on September 23, 2011, 16:55:23 PM
Quote from: Hammerhead on September 20, 2011, 16:46:16 PM
Is there no way to import legacy data without having the corresponding product?  What if the items are no longer made or carried in the store, but we still want to know what a customer ordered, when, and how much they spent with us?

Again, all I really want is to bring forward legacy order and customer information.  I presume I'll need both VM and Joomla user information, but I need to understand what data is required and how to get it over to a new (vanilla) install.

Thanks!
Bump.
Title: Re: 'Selective' Migration
Post by: PRO on September 23, 2011, 17:02:56 PM
hammerhead. YOU can bring the whole site over. THEN, change the order items to a new products called. "Former Product etc."

THEN, delete all the products from the database.

That will save the price they paid. BUT not the product
Title: Re: 'Selective' Migration
Post by: Hammerhead on September 23, 2011, 19:06:21 PM
Quote from: BanquetTables.pro on September 23, 2011, 17:02:56 PM
hammerhead. YOU can bring the whole site over. THEN, change the order items to a new products called. "Former Product etc."

THEN, delete all the products from the database.

That will save the price they paid. BUT not the product

The more I think about this, the more I realize it's going to be too much hassle to carry over legacy orders.  How would you go about bringing over only users?  I presume that I'd need both the Joomla and VM user tables, yes?  Anything else?
Title: Re: 'Selective' Migration
Post by: PRO on September 23, 2011, 19:22:55 PM
i would use jupgrade, and then empty all database tables you do not want
Title: Re: 'Selective' Migration
Post by: Hammerhead on September 23, 2011, 19:40:40 PM
Quote from: BanquetTables.pro on September 23, 2011, 19:22:55 PM
i would use jupgrade, and then empty all database tables you do not want
Sounds good.  Though I think I'd feel better about a completely new install of J/VM.  If I were to use 'jupgrade', leaving aside other components (like ACYmailing) that have their own upgrade mechanism, what tables would you say I'd need to copy over to the new (vanilla) installation?
Title: Re: 'Selective' Migration
Post by: PRO on September 23, 2011, 20:15:16 PM
To just move users over?
http://extensions.joomla.org/extensions/migration-a-conversion/users-import-a-export/12607
THEN, import the 1.1 table into the 2.0

Vmart 1.1 connects vmart users to their corresponding Joomla user info. (username & password)

So to get the address etc, U will need both.




Title: Re: 'Selective' Migration
Post by: Hammerhead on September 23, 2011, 22:10:37 PM
Quote from: BanquetTables.pro on September 23, 2011, 20:15:16 PM
To just move users over?
http://extensions.joomla.org/extensions/migration-a-conversion/users-import-a-export/12607
THEN, import the 1.1 table into the 2.0

Vmart 1.1 connects vmart users to their corresponding Joomla user info. (username & password)

So to get the address etc, U will need both.


I guess we could do it that way, but it seems overcomplicated.  Let me revisit this again, because my thinking has changed and I fear some things got lost in the sauce.  Just want to be sure I'm not missing anything.

1) Duplicate current J/VM installation to a temporary folder and db
2) Upgrade J to 1.7 and VM to 2.0 when released
3) Export user tables for both J and VM (it would be helpful if someone could advise which ones, specifically, are needed)
4) Import user tables to NEW target installation of J and VM

Correct?
Title: Re: 'Selective' Migration
Post by: Milbo on September 23, 2011, 22:22:27 PM
you should not work with import/export tables, the layouts changed so I dont think it will work. it is easier for you to take a look on the migrator yourself
Title: Re: 'Selective' Migration
Post by: Hammerhead on September 23, 2011, 22:58:09 PM
Quote from: Milbo on September 23, 2011, 22:22:27 PM
you should not work with import/export tables, the layouts changed so I dont think it will work. it is easier for you to take a look on the migrator yourself
Milbo, if I've migrated an existing site to Joomla 1.7 and then upgraded that same installation of VM to 2.0, then why wouldn't the tables be the same?
Title: Re: 'Selective' Migration
Post by: jeorcal on September 24, 2011, 07:46:02 AM
I am using VirtueMart 1.1.5 stable on J1.5.23
I don't understand how it works ? how can I select the old database  to upgrade to VM2 on J1.7 ?  there is no place where to indicate the old DB name
Title: Re: 'Selective' Migration
Post by: Milbo on September 26, 2011, 19:19:11 PM
I think you both overestimate the difficulty :-)

The process itself is described here http://dev.virtuemart.net/projects/virtuemart/wiki/Upgrading_VM1_to_VM2_with_provided_packages

When you dont want the product importet, I just can say look on the migrator itsef, the code is seperated in two parts, one part is just firing the commands and the other parts are these commands. So when you want to change it, you should play around for yourself.