How to upgrade a large Evo site (4500 docs) to Revo

So I've got a large MODx Evo site (0.9.6.3-RC2) that has 4500 MODx Resources. I need to do a few things:

• Transfer all the values for each MODx Resource from Evo to Revo
• Keep the tree structure intact (parent/child relationship) at all levels
• Transfer all TV values for each Resource from Evo to Revo

Not sure if anyone has pulled this off or seen any docs online to this end. I know the rest of the code will have to be rewritten, but before diving into the project, wanted to see if anyone has successfully moved the content, tree structure and TV's from an Evo to Revo site. I haven't started the project yet, but plan on using the newest version of MODx Revo (which at this writing is 2.2-pl2) [ed. note: flinx777 last edited this post 14 years, 8 months ago.]

So I've begun the process today of transferring the old db from Evo to Revo and so far so good. Without any available scripts that I'm aware of to pull this off, I'm simply going into the each Evo table in the database (a backed up copy of course) and updating that table DB to have all the same columns (and in the same exact order with all the same settings and default values) as the Revo table. I started with modx_site_content and it all transferred over just fine. Next I did the modx_site_templates and the only problem I ran into was that I hadn't done the modx_categories table transfer, so none of the templates showed up. Once I moved over the categories table (updated to match Revo of course), the templates showed up. Once I completely pull this off (about 1/2 way through), I'll try and do a write up.

I looked at Bob Ray's guide which is a good starting point: http://bobsguides.com/migrating-revolution.html. The only challenge I had with this info was that I have 4500 MODx Resources which I don't have time to copy/paste as he suggested (this obviously will work on a much smaller site).

I'll update this thread once I successfully move this large Evo site to Revo in the hopes that other people have better suggestions or that it will help someone else.

The biggest challenge may be TVs. The TV table is very different and you won't be able to just add fields.

Also, you can't migrate the table with the resource-specific values of TVs unless the resources and TVs all have the same IDs. The same is true for the table that attaches TVs to templates.

And, of course, forget about anything related to user security permissions.


---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone: http://bobsguides.com/modx.html

Hey Bob,

Thanks for the head's up on TV's. I plan on crossing that bridge in the next day or two. Yeh, fortunately there's a small group of manager users, so permissions for them shouldn't be a big issue.

I'll post back here once I've migrated the entire site over in the hope that the community can get a little insight or show me a better way.

I've written the code in my head to migrate Templates (with their page connections), and TVs (with their page values and template connections) in my head after dumping the Evo DB to a .SQL file. It would require every resource to have a unique alias, and I don't know if it would work.

If only there were more hours in the day.

---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone: http://bobsguides.com/modx.html

@Bob ... seriously. We all need more time! I've got 2 kids under 4 years of age, so I have very little time

Currently each Resource does have it's own unique Alias fortunately. I'm really surprised nothing has come out of the community that handles this yet...if only I could write a script. I thought there would have been a big demand in the community for something like this. Once the project actually starts (should be within a week) and I document my steps, I'll post them up in the hopes that it will help someone else down the road. It won't be sexy, but it will hopefully get the job done.

Sorry if this is too late, but I hope it can help:

A few months ago, I managed to import about 3500 resources from a site made in Evolution, to Revolution with the help of Shamblett's Provisoner https://github.com/shamblett/provisoner

I think that it was in MODX Revolution 2.1.3-pl and Provisoner 1.00 pl, where I subsequently updated Revolution to the latest version ...

Though of course there were some adjustments, that made ​​the workflow much easier!

But do it for safety's sake on a copy of the existing website, and on a copy of the new site ...

wow...thanks for providing this info. the project is going to start in the next week, so this will be perfect.

Thanks!

Note that Provisioner does not work with the current version of Revolution. You'll have to install an earlier version and then upgrade after you import the data.

I also don't think it works with the current version of Evolution either, but I'm not sure.


---------------------------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using . . . PLEASE!
MODx info for everyone: http://bobsguides.com/modx.html

Quote from: BobRay at Feb 14, 2012, 08:46 PM

Note that Provisioner does not work with the current version of Revolution. You'll have to install an earlier version and then upgrade after you import the data.

I also don't think it works with the current version of Evolution either, but I'm not sure.

You have an idea what versions of Revo and Evo it works with or is that in the docs?