Migrate VirtueMart 1.1 to 2.9.6

[PeterSwe]

Hi,
I need some advise regarding a big migrate.
Is it possible to migrate VM 1.1 to the comming 3.0 or is it easier to do it in 2 steps, 1.1 -> 2.6 and then 2.6 -> 3.0?
I can see that VM has change the table names from #__vm_xxxxx to #__virtuemart_xxxxx when I install the 2.9.6 version. Can I decide to keep vm instead of virtuemart in the table names?
Does somebode know a virtuemart template provider which had already done a Joomla 3.x template for VM 2.9.6?
Thanksful for answers.
Best regards,
Peter

[GJC Web Design]

VM 3 is not ready - as simple as that - when it is it will be announced

so the option is wait or do a J2.5/VM2.6

the update then to J3/VM3 will /should be painless as VM3 is aiming for backward compatibility with VM2

I can see that VM has change the table names from #__vm_xxxxx to #__virtuemart_xxxxx when I install the 2.9.6 version. Can I decide to keep vm instead of virtuemart in the table names?

definitely not - why would you want to? U need the different table names to do a migration/import to VM2

[PeterSwe]

Hi,
Thanks for the answer. I know that VM 3.0 is not ready but It's not so far away so we have decided to use our old VM site until the VM 3.0 is ready. We want to use the next LTS Joomla version 3.5.
My question regarding table names was because we don't do any updates in VM, everything is done in our ERP system and then updated to VM from the ERP system. So we just wanted to know if we have to change our scripts and APIs between the ERP system and VM.
So, we can migrate our VM 1.1.8 to VM 2.6.6 and then update VM 2.6.6 to 3.0 when it's ready (to save time)?
Regards,
Peter

[GJC Web Design]

migrate our VM 1.1.8 to VM 2.6.6 and then update VM 2.6.6 to 3.0

this is what I would recommend at the moment

table names - there are 100's of instances of __virtuemart  in the code .. really don't see the logic behind changing it even if u never update?

[PeterSwe]

Thanks,
The answers have been realy helpfull.
Peter