Provisioner is, by far, the best option, but if you can't get it to work, there's a description of the old-fashioned method here:
http://bobsguides.com/migrating-revolution.html
Hi All,
I'm currently attempting to transfer an old Evolution site for a client over into Revolution [as a piece of a larger project], specifically the users. I'm using Provisioner, the Evolution version I'm transferring from is 1.0.6 and the transfer is happening in Revolution 2.1.5 because of the stated issues running Provisioner in 2.2+. I'm having success getting everything but the users transferred over. It appears that users within Provisioner need to be individually imported. Is that correct? I have over 1,000+ users that need to be transferred and having to import these individually will be a huge time suck. Is there something that I'm missing that would allow them to be mass imported? I've attempted using the "Site Import" feature in Provisioner, as well as simply checking out the "Users" tab in Provisioner to get the users imported and nothing has worked thus far. Should I just try and run a query within the database? If so, what would be the smartest way to approach that?
Any advice/assistance would be so greatly appreciated!!
I think 1.0.6 is old enough that the user passwords should be encrypted with MD5. You might be able to just export the modx_web_users table, manually edit it to remove the admin user, and import them into the modx_users table in Revo with PhpMyAdmin. Back up the Revo DB first!
There is a plugin that will convert the password hash to what Revo uses (PBKDf2) when each user logs in.
If that doesn't work, I think I have some code around her somewhere for importing Evo users into Revo.
-
☆ A M B ☆
- 24,524 Posts
You need to change the default password hash, I think. I did it once, changing the default hash and using the plugin to convert them all. It worked fine. It was two or three years ago, though, and I don't really remember the details.
Hi All,
Thanks for the feedback. So, I finally had an epiphany and was able to import the users into Revo 2.3 but for some reason it defaulted to the modx_web_users table instead of the modx_users table. To be clear all of the users that needed to be transferred were web user accounts for the frontend of the site. But, I can't see any of the users I've imported in the manager only the modx_users. Do I change this string in the database table from this:
CREATE TABLE IF NOT EXISTS `modx_web_users` (
`id` int(10) NOT NULL AUTO_INCREMENT,
`username` varchar(100) NOT NULL DEFAULT '',
`password` varchar(100) NOT NULL DEFAULT '',
`cachepwd` varchar(100) NOT NULL DEFAULT '' COMMENT 'Store new unconfirmed password',
PRIMARY KEY (`id`),
UNIQUE KEY `username` (`username`)
)
to this?
CREATE TABLE IF NOT EXISTS `modx_users` (
`id` int(10) NOT NULL AUTO_INCREMENT,
`username` varchar(100) NOT NULL DEFAULT '',
`password` varchar(100) NOT NULL DEFAULT '',
`cachepwd` varchar(100) NOT NULL DEFAULT '' COMMENT 'Store new unconfirmed password',
PRIMARY KEY (`id`),
UNIQUE KEY `username` (`username`)
)
in MODX Revo there isn't a modx_web_users table any more.
They are all in modx_users.
But you don't want to create a new modx_users table!
You want to merge the existing users (the admin for example) and the web-users into the modx_users and the modx_user_attributes - tables, which will not be an easy task, if you want to do it all by phpMyAdmin.
Users will get new autoincrementing ids.
This ids need to match with them in the modx_user_attributes - table.
Other tables might also be involved like modx_member_groups and more.
They might also be owners of other resources, where you would need to change user_ids.
You also have the problem that there will usually be duplicate users, where a manager user is also a web user. And you'll generally lose the user group memberships as well.
Add to that the fact that recent version of Evo have a variety of password hashing options that Revo knows nothing about. I've contemplated a plugin to handle this, but it's still in my head. I can face writing it, but when I think about testing it, I get a headache.