Skip to content
Book a demo

Moving from Jira

Leave Jira one team at a time, without losing the history

Agree which system does what, bring work across from Jira Cloud, Jira Data Center or a CSV export, and accept each transfer only once the comments, work logs and exceptions are checked.

Jira → Akollo

Jira

  • WEB-142Checkout times out on retry
  • WEB-157Add SSO to the admin area
  • WEB-163New pricing table
  • WEB-171Cookie banner in German
  • WEB-188Search results paging

Akollo

  • WEB-142Checkout times out on retry
  • WEB-157Add SSO to the admin area
  • WEB-163New pricing table
  • WEB-171Cookie banner in German
  • WEB-188Search results paging
Work items
1,284
Comments
6,930
Work logs
2,415

WEB moved · 3 items set aside for review

How a team moves from Jira to Akollo

No big-bang weekend. Each team moves when it is ready, and nothing is accepted until it has been checked.

  1. Planning the move

    Agree which system does what

    Decide project by project whether Jira or Akollo handles each activity, so teams mid-release can keep both tools for a while.

  2. Connections

    Connect Jira or bring a CSV

    Connect Jira Cloud with an email and API token, or Jira Data Center with a personal access token. A CSV export works too, with a dry run before anything is written.

  3. Field mapping

    Map each field once

    Pick the Akollo field for every Jira field and who owns it: Akollo, Jira or both ways. Changes are reviewed as a difference before they are published.

  4. Issues

    Check what did not fit

    Records that cannot be moved are set aside and grouped by cause, never dropped. Fix the mapping and retry. Custom fields, extensions, permissions and history get explicit checks.

  5. Transfer acceptance

    Accept the transfer, then move the next team

    The project owner accepts once coverage is confirmed and exceptions are resolved. The team switches over and the next one starts.

What your team works in after the move

Boards, backlogs and sprints feel familiar, and hours and cost sit on the same items without a plug-in.

  • Project board

    Work items as cards with key, priority, points, owner and due date, in columns that follow your workflow.

    • Tasks, stories, bugs and epics
    • Workflows with approvals
    • Timers on the card

  • Backlog and saved filters

    A ranked backlog, and search with a query language close to what Jira users already type.

    • owner = currentUser() works
    • Filters shared with a project or everyone
    • Subscribe to a filter

  • Active sprint

    Days left, committed, completed, added and removed work, with burndown and burnup, and velocity once sprints close.

    • Burndown and burnup
    • Sprint report with velocity
    • Unfinished work moved on close

  • Field mapping

    Every Akollo field next to its Jira field, its source of truth, its transform and what happens on a conflict or delete.

    • Draft, review, publish
    • Protected fields need a second admin
    • Older versions never overwrite newer

Let the assistant tidy up after the move

Akollo AI reads the projects you moved and suggests the clean-up. It asks before it changes anything.

Akollo AI

Which moved items have no owner or an owner who is no longer on the team?

41 open items in WEB have no active owner, 12 of them bugs. I can suggest owners based on who worked on similar items. Show the list?

Ask Akollo AI

Try asking

Run the assistant on our cloud, on your own model or switch it off. It only reads what the person asking is allowed to see.

See what the assistant can do

What you can check at every step

A migration you can stand behind is one you can count. These figures come from the transfer itself and from the work after it.

  • Records read, written and set aside

    For every sync run: how many records were read, written and set aside, how long it took and where it stopped reading.

    Where you see itConnections › Syncs

  • Open exceptions per cause

    Records waiting for a decision, grouped by cause with counts and first and last seen, so you know what blocks acceptance.

    Where you see itConnections › Issues

  • Sprint velocity after the move

    Committed against completed work per sprint, so you can see the team is back to its pace in the new tool.

    Where you see itSprints › Report

  • Hours and cost on each item

    Time logged on the same work items rolls up to the project's cost, without a separate timesheet tool.

    Where you see itTime tracking and Budgets

What you move into

Questions about leaving Jira

Do we have to move everything at once?

No. You choose the projects in scope and decide which system handles each activity. Teams move one at a time while the others stay on Jira.

Which Jira editions can we connect?

Jira Cloud, with an email and API token, and Jira Data Center, with a personal access token. You can also import a CSV export of up to 5 MB and 5,000 rows per file, with a dry run first.

Do comments, attachments and work logs come across?

Comments, attachments, work logs and history are part of a transfer's scope. Custom fields, extensions, permissions and history each need an explicit coverage check before you accept.

What happens to records that do not fit?

They are set aside and listed by cause while the rest goes on. You fix the mapping and retry, skip a record with a reason or resolve a conflict side by side. Nothing is dropped silently.

Will our Jira searches still work?

Not word for word, but advanced search uses a similar query language, for example owner = currentUser() AND statusCategory != "done", and results can be saved as shared filters.

Akollo vs Jira

Plan your move from Jira with us

We will look at your Jira projects and fields and agree which team moves first, then walk through the transfer on a call.

Book a demoRead the docs