Switching from Jira to Resourcecloud: how the move works

When you change a project tool, you mainly fear one thing: losing data. Years of issues, comments and time entries shouldn't stay behind in the old system. That's why Resourcecloud has a Jira import that supports Jira Cloud and Jira Data Center. Here is the process in five steps.

What comes along

Projects, issues, subtasks, epics, sprints, comments (with the original author and date), time entries and attachments. Jira projects become a team (who sees the tasks) and a solution (what the work belongs to). An epic gets a story of the same name that contains its tasks. Story points are rounded to whole numbers, and worklogs become time entries for the person who recorded them.

The five steps

1. Export. Jira has no "export everything" button, so a script is included (tools/jira_export.py, Python 3.9 or newer). It only reads through the REST API and writes a zip. If it's interrupted, it resumes where it stopped.
2. Upload under Admin → Data import. Size doesn't matter, and an interrupted upload resumes too.
3. Map. Task types, statuses, projects and people, with suggestions from what you already have in Resourcecloud. People are matched by email address first, then by username. Jira statuses become stages of the team board.
4. Dry run. It shows what would be new, what would change and what stays untouched. Only then do you start. The import runs in the background.
5. Report. Afterwards you see what it did.

Why you can start without worry

• Repeatable. Every Jira object is recognised by its ID. The same export again changes nothing. A newer export updates what changed in Jira and adds new items. Nothing is created twice. So you can keep working in parallel and sync once more shortly before the cutover.
• Reversible. An import can be undone. It removes what it created and keeps what has been worked on since.
• Quiet. The import sends no emails and no notifications.
• Your data stays with you. It goes from Jira to the machine where you run the script, and from there into your own Resourcecloud, nowhere else.

What to prepare

An account with the RC Admin role, a team per Jira project (or the import creates it), the user accounts that should stay (missing ones can be created as inactive accounts), and Jira access that may see the projects: email address and API token for Jira Cloud, a personal access token for Data Center.

What isn't imported

Boards themselves aren't copied; they only decide which team a sprint belongs to. The guide has the full list of what isn't carried over.

Our tip: start small

Import one project first, look at the result, then add the rest. The detailed guide with all options is under Documentation → Switching from Jira.