Just looking for some expert advice here. I am new to Magento (I have done a Zen Cart website from scratch), and I have a client requesting upgrade from 1.3.2.4 to the latest version (on my recommendation). After spending hours perusing posts about the upgrade path options, it appears to be down to the choice between incremental upgrading (via 1.6 and with themes and extensions discarded) and a fresh installation and dbase migration via cart2cart.
So, some questions:
These caveats on Cart2Cart’s webpage (for Magento-Magento migration) seem like they could matter (especially the last one):
- Customers’ credit card information is not migrated. Though, the information about customers’ billing, shipping addresses will be successfully migrated.
- When the migration process is completed all registered customers will have to use password recovery form on the target shopping cart to use their profiles, due to the fact that various shopping carts use different password encryption algorithm.
- The migration result may be unpredictable in case the attribute set ‘default’ was modified.
Would doing the upgrade path avoid these issues in the upgraded database?
This is my plan for incremental upgrade. Please comment or advise, including my time estimates):
-----
1) Investigate current installation (1 hr)
2) Upgrade
2a) Create copy of current installation (2 hr)
- verify that webserver meets minimum Magento requirements
- back up current dbase and website
- copy website to subdirectory on webserver (not “live")
- create copy of live dbase
- tweak config files for subdirectory installation
- configure for upgrade:
- disable theme
- disable extensions
2b) Upgrade to v 1.6 (2 hr)
- perform upgrade
- verify & test data
2c) Upgrade to v1.7 (2 hr)
- perform upgrade
- verify & test data
3) Configure new site (4 hr)
- theme installation & customization
- extension installation
- custom pages (quotes, etc)
4) Go live when satisfied with new installation (1 hr)
- back-up and re-copy live dbase and replace copy on new Magento installation
- move live website aside
- move new installation to live directory (or link)
- enter interim orders into database manually
-----
These caveats on Cart2Cart’s webpage (for Magento-Magento migration) seem like they could matter (especially the last one):
- Customers’ credit card information is not migrated. Though, the information about customers’ billing, shipping addresses will be successfully migrated.
- When the migration process is completed all registered customers will have to use password recovery form on the target shopping cart to use their profiles, due to the fact that various shopping carts use different password encryption algorithm.
- The migration result may be unpredictable in case the attribute set ‘default’ was modified.
Thank you for your interest in Cart2Cart. That is right, customers’ credit card information, as well as customers’ passwords will not be migrated due to the specificities of different carts.
However,
As for the last statement, if your database configurations differ from the default ones, you can still perform successful migration. In this case an extra customization service can be applied. Cart2Cart techies will perform all the necessary modifications so that the data is migrated correctly.
Moreover, before all the data is migrated to your store, you can perform free Demo Migration of a limited number of entities. This will let you check how the migration result is gonna look like on your store.
If you have any other questions, please let us know,
Thank you
It is a long way to upgrade Magento from 1.3.2.1 to 1.7.0.2. Errors are almost always happen. You didn’t mentioned the way how you plan to upgrade, it plays a vital role in this question. Definitely, it is safer to move step by step 1.3 to 1.4 to 1.5 to 1.6 to 1.7.
Have you made a backup for you data? If yes, it is better to start it all from the very beginning.
Minor problems here are inevitable, especially, if you have really old version of Magento that you would like to upgrade.
Here is the standard procedure when getting Magento up to date. It is just for you to see, because you can select another way to update the store.
1) Know what are you facing with:
Check google if there is something special about upgrading your specific version of Magento to the newest one. If nothing else, you will be prepared with issues that you will need to solve.
2) Backup your files
We usually do it from CLI like this: tar -cvvzf your_site_directory.tar.gz your_site_directory/ 2>error.log
In case you need to move files between 2 servers, easiest way I can think of in CLI would be this:
scp /path_to_some_file/your_site_directory.tar.gz user@REMOTE_SERVER_ADDRESS:/some_dir_on_remote_server You can do the same with your backup-ed database
5) Now it is time to import database into new created one:
a) Extract my_database_name.sql.gz
b) mysql –verbose –user=THIS_IS_YOUR_USERNAME –password=THIS_IS_YOUR_PASSWORD newly_created_db < my_database_name.sql
6) Now extract the files this way:
tar -xvvzf your_site_directory.tar.gz This will extract all files to the current directory
7) Edit db table core_config_data and set new secure/unsecure URLs of your site
8) Disable cache from admin.
9) Delete cache and session directories located here: /var/cache /var/session
10) Execute “clean” bash script located in /downloader/pearlib directory
a) Run chmod +x clean to be able to execute this script b) ./clean to execute script
11) Finally go to Magento connect manager from your Magento admin Paste this extension to upgrade Magento: magento-core/Mage_All_Latest After this is done, you should have new Magento, however if there was some custom coding, you should really know what is going on with your code.
12) All that left is to test it and move those files on production server.
