Migrate from Redmine to Gitlab

Migrate Redmine projects to Gitlab.

Enjoy.

Does

Per-project migrations
Migration of issues, keeping as much metadata as possible:
- redmine trackers become tags
- an extra Redmine tag is added on each issue
- issues comments are kept and assigned to the right users
- issues final status (open/closed) are kept along with open/close date (not detailed status history)
- issues assignments are kept
- issues numbers (ex: #123)
- issues/notes authors
- issue/notes original dates, but as comments
- issue/attachments
- relations (although gitlab model for relations is simpler)
Migration of Versions/Roadmaps keeping:
- issues composing the version
- statuses & due dates

Does not

Migrate users, groups, and permissions (redmine ACL model is complex and cannot be transposed 1-1 to gitlab ACL)
Migrate repositories (piece of cake to do by hand, + redmine allows multiple repositories per project where gitlab does not)
Migrate wiki
Archive the redmine project for you
Keep creation/edit dates as metadata
Keep “watchers” on tickets (gitlab API v3 does not expose it)
Keep dates/times as metadata
Keep track of issue relations orientation (no such notion on gitlab)
Remember who closed the issue
Migrate tags (redmine_tags plugin), as they are not exposed in gitlab API

Requires

Python >= 3.5
gitlab >= 7.0
redmine >= 1.3
curl
Admin token on redmine
Admin token on gitlab
No preexisting issues on gitlab project
Already synced users (those required in the project you are migrating)

(It was developed/tested around redmine 3.3, gitlab 8.2.0, python 3.4)

Credits

Many thanks to the @oasiswork team for the good work they have done with the project redmine-gitlab-migrator on which this project is based on.

Install

You can or can not use virtualenvs, that’s up to you.

Install it:

pip install migrate-redmine-to-gitlab

(or if you cloned the git: python setup.py install)

migrate-redmine-to-gitlab --help

Migrate a project

This process is for each project, order matters.

For the example we will migrate project observe from Code Lutin Redmine to Ultreia.io Gitlab.

Create the gitlab project

It does not need to be named the same, you just have to record it’s URL.

Add users to your project (we will se later how to map redmine users to them).

Note that if a redmine user can’t be found in gitlab, the issue/comment will be assigned to the gitlab admin user.

Import git repository.

Important note: The project must have NO milestone and NO issue.

Init migration

Create a directory, go in it.

mkdir observe
cd observe

Create a config.json file with this content (adapt content with your credentials):

 {
  "redmine": { "host":"https://forge.codelutin.com", "path":"projects/observe", "key": "XXX" },
  "gitlab": { "host":"https://gitlab.com", "path":"ultreia.io/ird-observe", "key": "XXX" }
}

Launch command

migrate-redmine-to-gitlab init

This will download all the redmine project stuff in directory redmine

You should have then a such directory layout:

observe
├── config.json
└── redmine
    ├── attachments
    ├── issues
    ├── project.json
    ├── users
    └── versions

Adapt users

The directory redmine/users contains all users from the Redmine project.

To match a gitlab user, you need to set the login attribute in each file to the gitlab login.

Note that you won’t be able to continue migration process until all redmine users match any of one gitlab user.