Migrating from Bugtracker.net
Added by Jon Lumpkin over 14 years ago
We are moving to redmine from bugtracker.net, and wanted to know if anyone had made this migration before. There doesn't seem to be an automatic way to do this.
Could we write a SQL script to export from the MSSQL install and import into the Redmine MySQL install?
Replies (6)
RE: Migrating from Bugtracker.net
-
Added by Douglas Dallas over 14 years ago
Did you ever manage this? We are looking to do the same?
Thanks,
Doug
RE: Migrating from Bugtracker.net
-
Added by Jon Lumpkin over 14 years ago
It looks like ours is going to be a manual process. The way some of our BT.net installs are set up, it would take just as much time manually moving things over as it would to generate scripts to put them in the right place. I searched all around but never found anything that could do this.
There was an importer for redmine, but when I last checked, it had not been checked against .9.x yet, which is what we are running. That, and again, ours wouldn't map just right.
Still open to suggestions though, since we haven't started the full migration yet.
RE: Migrating from Bugtracker.net
-
Added by Corey Trager over 14 years ago
Guys - If it were me, I'd dump the SQL db into individual flat files, write some ruby or whatever to read/adjust/insert them into Redmine's schema. A few hours work maybe? Mostly tedious work, but pretty straight forward. But, then there are the attachments (screenshots, etc). BugTracker.NET has the option of storing these either as blobs in the database or as plain old files in the file system. I don't know how Redmine stores them, but either way, this is an area where you might be spending more time.
Question: Why are you guys moving from BugTracker.NET, specifically? I'm asking because I'm the author of BugTracker.NET, and I'd just like to know what specifically you wanted from Redmine that BugTracker.NET doesn't have. I've tried Redmine, and I like it a lot, and it has a lot of features that BugTracker.NET doesn't have, but I'm curious which of those features specifically were the important ones to you?
RE: Migrating from Bugtracker.net
-
Added by Douglas Dallas over 14 years ago
For us it looks like being a manual process as well, like Jon mentioned.
The reason for migrating for us is to allow us to use the Wiki (mainly for developer information and support) and Roadmap (visibility of release dates etc..) features. We want all everything in one place. Visibility of the SVN integration is useful as well. Basically we are needing a bit more than a just a bug tracker.
BugTracker.NET is a good application and we have used it for years - keep up the good work!! It has it's place for sure.
RE: Migrating from Bugtracker.net
-
Added by Jon Lumpkin over 14 years ago
I agree with Douglas. The other reason why we are moving is for the project management side of things. We really like BugTracker.net, but we also were using an in house PM system, and this let us merge those two together. We are also very interested in the SVN integration, some CI and other plugin integration, and the roadmap.
RE: Migrating from Bugtracker.net
-
Added by Corey Trager over 14 years ago
Thanks for the info. I understand.
I debated about integrating, say, Screwturn wiki, with BugTracker.NET, after seeing wiki integration in Trac and FogBugz, but, actually, nobody has ever requested it. And I mean, I have gotten thousands of requests for changes, and never once for a wiki.
And just for the record, BugTracker.NET has svn integration: http://ifdefined.com/doc_bug_tracker_subversion.html. (And git, mercurial integration too). But it's not as complete as Redmine's. It's not a full featured svn client. But here also, nobody has asked for more than I've implemented.
( These days, most requests are related to fine grained control of permissions - more and more permissions - and some email improvements. )