Okay, I've decided I'd like to start fresh...eh...well, almost.  I'm going to create a new 3.1 site to replace my existing (v 2.12) site. This is to prevent the upgrade issues I've read about as well as give me a fresh palete to work from. (This has been a long time coming and my files are simply all over the place and this will give me a chance to reorganize.)

The only data I want to migrate is my user data. I've got over 1100 members on my site and I don't want to inconvenience them. Does anyone have an SQL or utility to migrate my existing users?

Thanks!

I would also be interested in a solution like that. I have a couple of sites I would like to start fresh with but maintain the user base.

I have a similar requirement too! I want to export my DNN users to Community Server to test that out!

It will be easy to get a list of the users but is there a way to unhash their passwords?

Regards,

Matt

Well, I only saw one listing for moving users but it does not move roles. Maybe someone could simply tell me if the data structure has changed. If not, this shouldn't be a very difficult task and I'll write something myself and publish it.

I always enjoy it when I get a chance to give a little back to this community (I can't afford the shirt so this will have to do):

I have just finished importing all of my DNN 3.1.1 users and roles into DNN 4.0.2. The process I used follows, but let me say upfront that I'm sharing this information with no warranties or guarantees whatsoever. If this makes sense to you and you are confident about checking it over for potential problems with respect to your particular situation give it a go and be sure to test it in a development environment thoroughly (otherwise, don't).

* First, do everything you would normally do to setup a new website with DNN 4.0.2 from the install package. Please note that I used SQL 2005 Express and SQL Server Management Studio for the database storage and manipulation. 

*When you come to editing the web.config file...
- Change web.config SQL connection keys to suit your circumstances
- Change validation and decryption keys in Web.config to the keys from your previous installation
- Add the following to the appSettings section so that the installation does not replace your keys: <add key="InstallationDate" value="12/31/2005" />

* Proceed with the DNN installation by browsing to the site. When you try to browse to the newly installed site you may see an error page, copy SiteURLs.config from the Config folder to the root folder to correct it (we used the upgrade process to do a full install).

* Manipulate the database tables (in this order):
- Backup DB (as always)
- Delete all rows from aspnet_Membership
- Delete all rows from aspnet_Profile
- Delete all rows from aspnet_UsersInRoles
- Delete all rows from aspnet_Roles
- Delete all rows from aspnet_Users
- Delete all rows from aspnet_Applications
- Delete all rows from aspnet_SchemaVersions
- Delete all rows from UserPortals (NOTE: if you have multiple portals you may need to consider the Portals table).
- Delete all rows from UserRoles
- Delete all rows from Roles
- Delete all rows from Users
- Import aspnet_SchemaVersions from old DB
- Import aspnet_Applications from old DB
- Import aspnet_Users from old DB
- Import aspnet_Roles from old DB
- Import aspnet_UsersInRoles from old DB
- Import aspnet_Profile from old DB
- Import aspnet_Membership from old DB
- Import Users  from old DB (Use "Enable identity insert")
- Import Roles  from old DB (Use "Enable identity insert")
- Import UserRoles  from old DB (Use "Enable identity insert")
- Import UserPortals  from old DB (Use "Enable identity insert")

Good luck.

I used a tool called MZNS.UserImport.

Essentially you have to extract your 2.x data into an Access database, which should be relatively easy. Make sure you have the passwords in clear format before extracting.

Then re-create roles in 3.x installation. Copy access database to website, and use module to create users/passwords based on queries from your access database.

http://www.mikez.com/Home/Default.aspx?tabid=90

Bear in mind in 2.x passwords are not case sensitive, whilst in 3.x they are.

Hope this helps
Roger

Roger,

Thanks for pointing users to our module.

We are about to post a new module for managing users that incorporates all the code we have laying around into a complete user management module.

Our intent is to turn this into a shared project so we can all benefit by the tools that are surely out there.  The module is not done, but will be posted as an ongoing project.  Our goal is to get the help and support of the community.

Look for something in the next few days.

mikez 

Mikez,

Don't know if my post triggered it, but that page seems to have disappeared, as well as the rest of your site!! Apart from a server uptime indicator. :-(

Roger

Roger,

I am rebuilding the whole site.  Should have most of it done by Monday.

I will have a development site where the demo will be running.

mikez