Project

General

Profile

Forums » Help »

Migrating to Redmine from in-house issue tracker

Added by Vitor Py over 14 years ago

I have an in house issue tracker, now deprecated. I would like to migrate the current issues on it, open and closed, to Redmine. I thought about writing a little script to do it. Where can I find a reference on the database schema used by Redmine? There's any issue I should be aware before doing it? I'm running 1.0.2 Stable on MySQL with CentOS 5.5.

Thanks in advance,


Replies (2)

RE: Migrating to Redmine from in-house issue tracker - Added by Eric Davis over 14 years ago

The database schema is built from the files in db/migrate. What I would recommend is:

  1. Setup a test Redmine server on your desktop or local development environment (use RedmineInstall).
  2. Once you have run the rake db:migrate command, you should have a db/schema.rb file.
  3. If you read through this file you can see the exact database schema for your Redmine version. It's in Ruby but it's pretty easy to read.
  4. As part of the install, you will also have an actual database setup so you can use your database tools to view the schema there too.

If you know a bit of Ruby, I'd also recommend reading through some of the existing import scripts to get an idea of how they work. They are lib/tasks/migrate_from_trac.rake and lib/tasks/migrate_from_mantis.rake.

Hope this gets you started.

Eric Davis

RE: Migrating to Redmine from in-house issue tracker - Added by Terence Mill about 14 years ago

Vitor Py wrote:

I have an in house issue tracker, now deprecated. I would like to migrate the current issues on it, open and closed, to Redmine. I thought about writing a little script to do it. Where can I find a reference on the database schema used by Redmine? There's any issue I should be aware before doing it? I'm running 1.0.2 Stable on MySQL with CentOS 5.5.

Thanks in advance,

We used the cvs import plugin successfully to migrate from sharepoint lists.

    (1-2/2)