Last post Dec 29, 2005 01:08 PM by staffanberger
Dec 29, 2005 10:47 AM|wylie|LINK
Dec 29, 2005 01:08 PM|staffanberger|LINK
I don't think there is an easy way.
I just moved one portal from 3.2.1 on one server to 3.2.2 on another server. The 3.2.1 was a multi portal and the portal I moved had to be alone (#0) on the new server.
The design and structure on the 3.2.2 is completely different from the old one (another forum, another news handler and so on) but we had to keep all the members and their posts, articles etc.
Problem #1 was to isolate the members corresponding to the portal and port them to the right tables in the database (and there is a bunch of affected member tables - some of them using GUIDs as UserId - hard to read...).
Problem #2 was to avoid writing over host and admin, but keep their passwords.
Problem #3 was to map the old posts and threads and articles to the old members, which on the new server have complete new UserIds.
I also changed from Microsoft SQL Server 2000 to Microsoft SQL Server 2005 Express Edition, but this was the easiest thing...
Problems #1 and #2 can, in a future DNN version, be solved by separating the data corresponding to the portal's "hard contents" (that is the design, module lay out and portal settings) from the member data more efficient (take the table aspnet_Profile for
I think that the 3rd party module BulkReg 3.6 can do a very good job, but it wasn't fully suitable for my needs.