1

I am in the process of upgrading my Magento website. I have started with a clean slate and done a fresh install of Magento 1.9.1 on a dev URL.

I imported my current LIVE database and performed the upgrade, and then began site development on the DEV site.

The LIVE site is still taking new orders, and having new products uploaded to it, as business must continue, of course.

When I am ready to launch the new site, how do I go about making sure the DEV site contains all of the LIVE sites products, customers and sales history, and anything else that is required along those lines.

There are a number of threads out there talking about dropping the DEV database and rerunning the upgrade on the LIVE database (once restored to the DEV database) and then launching - but all my site modifications stored in my DEV database would be lost if I did this!

I imagine there is a way to just copy the relevant data from the LIVE database to the DEV database to bring it up to date, and then I would be able to launch the new site. That being the case, can someone provide a list of the relevant tables that would need to be copied from the old LIVE to the new DEV database.

Sub-question... how do you get around the problem of any differences between the old (1.6.2) database and the new (1.9.1) database tables to be copied?

I hope someone can help.

Cheers,

Rob

2
  • You need to make list of the changes you are doing in the dev database and has to manually feed into new database that is the possible way. Apr 23, 2015 at 5:01
  • There has to be an easier/better way than doing that. That makes no sense.
    – robgt
    Apr 23, 2015 at 9:00

1 Answer 1

1

You will want to backup and restore you LIVE database to your DEV site often as thing will change. Documenting the procedure will help you when you finally do go live.

The easiest way to make sure you CMS and Static blocks are available is to create them in LIVE and restore that site to dev. You would then document the procedure to GO-LIVE by making sure all the necessary changes happen in Config, CMS and static blocks

11
  • Thanks. I already know this though. WhatI was looking for is a solution to moving product/sales/customer data from the LIVE db to the DEV db, as changes to the LIVE db will continue on during the development of the DEV site.
    – robgt
    Apr 24, 2015 at 13:27
  • Why don't you just backup live and restore to dev? Apr 24, 2015 at 22:16
  • As stated, the Dev site has been further developed, so dumping the database is not an option.
    – robgt
    Apr 25, 2015 at 22:54
  • But the dev site would have to some day turn into the live site so why wouldn't you use your most recent data? Apr 25, 2015 at 23:54
  • Just in case you missed them... here's the 2nd to 4th paragraphs of my question again :-) I imported my current LIVE database and performed the upgrade, and then began site development on the DEV site. The LIVE site is still taking new orders, and having new products uploaded to it, as business must continue, of course. When I am ready to launch the new site, how do I go about making sure the DEV site contains all of the LIVE sites products, customers and sales history, and anything else that is required along those lines.
    – robgt
    Apr 27, 2015 at 8:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.