Re:StackOverflow for your Intranet
by ridruejo on Tuesday October 25, 2011 @10:11AM
(#3154092)
The problem is that you need to move the content, user accounts, ratings, etc. from one system to another. The existing system has to had an API to export that information in a format that the new system can understand. If you have that, then it is easy, the problem is most systems out there do not have that :) Situation is a bit better with extremely popular projects for blogs or forums, like Wordpress or phpBB, which have an ecosystem of exporter/importer tools.
[ Parent
| on HN ]
Re:StackOverflow for your Intranet
by icebraining on Tuesday October 25, 2011 @10:31AM
(#3154175)
in a format that the new system can understand
Or you can write your own converter - it probably takes ~30m to whip up something in Python.
Something - yes. Something which implements everything required and is tested - not likely.
There's a huge difference between converting data from your little hobby and converting the vital knowledge of your company. It's different because it's more mission critical - you don't want to screw it up.
It's also different because the bigger dataset is likely to have some customizations and other "small" stuff which tends to matter in big perspective. You might be okay for losing e.g. votes if it's a small data set, but you really want it in with a big one.
Sorry, that's nonsense. Each one of the systems is going to have a different schema and constraints for users, posts, comments, votes, that most likely will not have a one-to-one mapping.
Re:StackOverflow for your Intranet
by mrgoldenbrown on Tuesday October 25, 2011 @10:41AM
(#3154213)
depends on the system - 30 minutes is not enough to convert users, groups, permissions, threaded conversations, voting, keywords, etc, especially if both systems do not use the same data model.