Tool Migration Services: Perforce, ClearCase, ClearQuest, DOORS, SVN and More
- Atlassian Gold Solution Partner
- GitLab partner
- Delivering since 1999
- Legacy ALM to modern platforms
Nobody migrates “their DevOps”. They move from one specific tool to another: Perforce to Git, ClearQuest to Jira, Bitbucket Server to GitLab. Each of those moves has its own data model, its own tooling, and its own list of things that do not survive the trip. ReleaseTEAM has been moving engineering teams between version control, issue tracking and requirements tools since 1999, and this page is the index to what we know about each one.
Pick the migration you are facing below. Every guide explains how the source concepts map to the destination, what the vendor tooling does and where it stops, what will not carry over, and when you should not migrate at all.
The short answer: a good tool migration is a decision first and a data move second. We start by confirming the destination is right for your teams, map every concept and field before anything moves, prove the approach on a pilot, and reconcile what arrived against what left before the old system is retired.
Source control migrations to Git and GitLab
Perforce to Git
Moving Helix Core depots and streams to any Git host, and how GitLab, GitHub, Bitbucket and Azure Repos differ on large files and locking.
Perforce to GitLab
The GitLab-specific deep dive: git-p4, p4-fusion, what breaks, repository splitting, and when not to migrate.
ClearCase to Git
VOBs, config specs, UCM streams and baselines, and how to decide how much history is worth bringing into Git or GitLab.
SVN to Git
Subversion to Git and GitLab: non-standard layouts, externals, author mapping, binaries and path-based permissions.
Bitbucket to GitLab
Bitbucket Server, Data Center and Cloud to GitLab, what GitLab’s importers bring across, and when staying on Bitbucket fits better.
Azure DevOps to GitLab
Repos, Boards, Pipelines and Artifacts are four separate moves. How each one maps to GitLab.
Issue tracking and requirements migrations to Jira
ClearQuest to Jira
Record types, state models, hooks and queries mapped to Jira projects, workflows and automation.
IBM RTC (EWM) to Jira
Work items, plans and iterations to Jira, and what happens to Jazz source control, builds and OSLC links.
IBM DOORS to Jira
Modules, attributes, link modules and baselines, and an honest look at when Jira is, and is not, the right requirements home.
ServiceNow to Jira Service Management
Moving IT service management from ServiceNow to JSM.
Legacy ITSM to Jira Service Management
Other service desk tools to JSM.
Platform and CI migrations
Atlassian Data Center to Cloud
Choosing a migration partner and planning the move to Atlassian Cloud. See the Data Center end-of-life guide for dates.
Jira and Confluence to GitLab
Consolidating planning and documentation into GitLab, or integrating the two platforms instead.
Jenkins to GitLab CI or CloudBees
Moving off self-hosted Jenkins, and how to choose between the two main destinations.
How every migration we run is structured
The tools change from one project to the next. The method does not, because the risks are the same every time: losing history people rely on, breaking the builds and integrations that hang off the old system, and a cutover weekend that turns into a month.
- Assessment. Inventory what exists: repositories or projects, customizations, triggers and hooks, integrations, users, and how much history actually matters. This is also where we tell you if the move is not worth making.
- Mapping. Every source concept gets a destination, agreed with the teams who use it, before any data moves: branches and labels, fields and states, links and attachments.
- Pilot. One team or one repository moves end to end. The pilot produces the real timings and the real list of surprises for the rest of the plan.
- Migration and reconciliation. Data moves in planned waves, and counts and spot checks prove what arrived matches what left.
- Cutover and parallel running. The old system goes read-only, not away, until your teams are confident. Integrations, builds and permissions are rewired and tested.
- Training and licensing. Teams learn the new tool’s way of working, not just its buttons, and licensing is sized to what you actually use.
“I needed to take the risk out of transitioning from one tool to another. ReleaseTEAM came up with an entire plan of action including addressing all the issues that I thought would be potential problems. They then did all the work without affecting anyone else on the team and with minimal interruption.”
Eric Wenger, Applied Research Associates
Frequently asked questions
Do you only migrate to GitLab and Atlassian?
Those are the platforms we sell and support, so most of our migrations land there. The guides above also cover other Git hosts where the destination is your choice, and we will tell you plainly when a different destination fits your teams better.
Our migration is not listed. Can you still help?
Probably. The pages above are the moves we are asked about most often, not the only ones we run. Tell us what you are moving from and to and we will say honestly whether it is something we do well.
Do we have to bring all of our history?
No, and often you should not. Full history, history from a chosen baseline, and a clean start with the old system kept read-only are all valid choices. The right one depends on audit needs and how often people really look back, and we settle it during assessment.
Can we run the old and new tools side by side?
Yes, and for anything beyond a small team we recommend it. A period of parallel running, with the old system read-only or synchronized, lets teams move in waves and gives you a rollback path.
ReleaseTEAM is an Atlassian Gold Solution Partner and a GitLab partner. Each migration guide lists the vendor documentation its facts were checked against and the date they were checked.
Planning a move between tools?
Tell us what you are migrating from and to. We will help you decide whether to move, then plan and deliver it with minimal disruption to your teams.
Speak With An Expert