Thread

Hi,

I’ve upgraded a customers site from 1.6 to 2.1.3. While getting the new site working, third party and custom plug-ins etc, the customer has continued entering data into the old 1.6 site. We are now ready to make the switch but as you can imagine, new members and posts have been added to the 1.6 db.

I’ve seen the installer/updates/up_213.php file and it has given me the idea that there must be a routine somewhere to just update, or re-sync the 2.1.3 db with the latest data from the old 1.6 db just before, or after making the switch.

Hopefully this makes sense.

Any ideas?

Bruce

Bruce,

I’ve seen the installer/updates/up_213.php file and it has given me the idea that there must be a routine somewhere to just update, or re-sync the 2.1.3 db with the latest data from the old 1.6 db just before, or after making the switch.

That wouldn’t be the best route.

What I would do is replicate their EE1.6 site locally and perform an upgrade to that there. Then make any updates you made to the dev site here too. Add any new add-ons etc. When it is a replica. You can export the database from your local and import it to your dev site.

Alternatively you could spit out all recent data in an EE XML template in your EE1.6x site and import it into your EE2 site with something like DataGrab

If its not an awful lot of info that has been added then personally I would quickly create it by hand in the dev site