Pike
  • Pricing
  • Contact us
Log in
  1. Home/
  2. Migration guide/
  3. Jira
Jira logoPike logo

Migration guide

Move from Jira to Pike

Connect Jira Cloud, map each space to a Pike project, and run Import once to bring work items and worklogs. Budget five weeks from connection to cutover, then one month-end in Pike.

Available now

Pike reads Jira Cloud through the Jira API. Work items, epics and worklogs import into the Pike projects you map them to, with worklogs matched to members by email.

  1. 1In Pike, go to Workspace settings → Integrations → Jira, click Add integration, and authorize Pike for your Atlassian Cloud site in the popup.
  2. 2Map each Jira space, or a saved JQL filter, to one Pike project. Turn on Map epics to phases if your epics follow client deliverables.
  3. 3While teams move one at a time, click Import data. Work items sync in real time through Jira webhooks. Worklogs import only through Import once.
  4. 4When the last team moves, choose Import once. It copies the mapped spaces, epics as phases, work items and subtasks as tasks, comments as text and worklogs as time entries, then disconnects.

Pike does not write to Jira during the import. The one write Pike offers is Send worklogs, off by default, which posts Pike time to Jira as the member who logged it.

Available now

Use CSV for Jira Server or Data Center, which the Pike integration does not support, or when you bring over open work items without their worklogs.

  1. 1Open the space’s List, set the filter, then choose More actions → Export → Export CSV (all fields). Jira Cloud exports up to 10,000 work items per file.
  2. 2Over 10,000 work items, split the JQL by created date and export each batch. Atlassian recommends created because it never changes, so batches do not overlap.
  3. 3Map Summary, Description, Assignee, Due date and Status to the Tasks template. The CSV records Time Spent per work item as one total, so it does not map to dated time entries.
  4. 4Upload projects, members, then tasks under Workspace settings → Integrations → CSV, using the Pike template columns.

The CSV is UTF-8. Atlassian notes older Excel versions garble it, so open it in a UTF-8 aware editor before you map columns.

Entity map

What each Jira record becomes in Pike

Column one uses Jira Cloud’s own labels. Jira has no client, rate or invoice records, so your team sets billing in Pike. Pike matches assignees and worklog authors on the email of each Atlassian account.

Spaces (projects) or a saved JQL filter

Pike: Projects

Carries over: The work items you map into each Pike project.

You set in Pike: Customer, project number, billing type, budget, hourly rate and team. A Jira space stores none of these.

Template columns: projectNumber, title

Epics

Pike: Phases

Carries over: Epic name and the work items under it, with Map epics to phases on.

You set in Pike: Phase start and end dates.

Template columns: projectNumber, phase

Work items and subtasks

Pike: Tasks

Carries over: Summary, description, assignee, due date, work type and labels as labels, status through the status mapping.

You set in Pike: Billable status. Jira custom fields do not import, except Original estimate.

Template columns: title, projectNumber, description, status, assigneeEmail, dueDate

Original estimate

Pike: Hours allocated on the assignee

Carries over: The estimate on each work item.

You set in Pike: Allocations for work with no estimate.

Worklogs

Pike: Time entries

Carries over: Duration, date and comment for each worklog, matched to the member by email, through Import once.

You set in Pike: Billable status and approval. Jira worklogs record neither.

Comments

Pike: Task comments

Carries over: Comment text, through Import once.

You set in Pike: Nothing.

Jira entityPike entityWhat carries overWhat you set in PikeTemplate columns
Spaces (projects) or a saved JQL filterProjectsThe work items you map into each Pike project.Customer, project number, billing type, budget, hourly rate and team. A Jira space stores none of these.projectNumber, title
EpicsPhasesEpic name and the work items under it, with Map epics to phases on.Phase start and end dates.projectNumber, phase
Work items and subtasksTasksSummary, description, assignee, due date, work type and labels as labels, status through the status mapping.Billable status. Jira custom fields do not import, except Original estimate.title, projectNumber, description, status, assigneeEmail, dueDate
Original estimateHours allocated on the assigneeThe estimate on each work item.Allocations for work with no estimate.
WorklogsTime entriesDuration, date and comment for each worklog, matched to the member by email, through Import once.Billable status and approval. Jira worklogs record neither.
CommentsTask commentsComment text, through Import once.Nothing.

Jira stores no bill rates, cost rates or money budgets. Set billing type, budget and hourly rate on each Pike project before you run Import once, so imported worklogs show revenue from day one.

Imported worklogs have no billable flag in Jira. Decide per project whether past hours were billable and set it in Time admin after the import.

Original estimate becomes hours allocated on the assignee. Jira converts estimates at 1w = 5d and 1d = 8h by default, so check your site’s time tracking settings if it uses other values.

The plan

Seven steps out of Jira

The same steps as the main migration guide, with this tool's screens and settings.

  1. Week 1

    Migration owner, finance

    1

    1Week 1 · Migration owner, finance

    Freeze scope and export

    Pike reads Jira directly. The export in week one is your archive copy of the spaces you close.

    • Pick a cutover Friday and list the Jira spaces or JQL filters that move, with the client each one bills.
    • Run Export CSV (all fields) for each space and save the files. Split by created date above 10,000 work items.
    • List the spaces that log billable time as worklogs. You check their hours after the import.
    exports / rawdo not edit
    • customers.csvraw
    • projects.csvraw
    • tasks.csvraw
    • time-entries.csvraw
    • invoices.csvraw
    Cutover: Friday, week 5

    Done when: Archive exports in one folder, a cutover Friday on the calendar, and a Jira site admin named to authorize Pike.

  2. Week 1 to 2

    Operations lead

    2

    2Week 1 to 2 · Operations lead

    Clean the data in Jira

    Pike imports what Jira stores, so fix statuses and worklog authors in Jira before you connect.

    • List every status in the spaces that move. Each one maps to a Pike task status in the status mapping table.
    • Check every person with worklogs has the email they will sign in to Pike with on their Atlassian account.
    • Close or move work items that belong to no client. Pike imports every work item in a mapped space or filter.
    customers.csvbefore / after
    • Acme
    • ACME Ltd
    • Acme retainer

    Acme

    C-104 · T&M · 1,250/h

    Done when: Every status has a Pike status. Every worklog author has a Pike email.

  3. Week 2

    Workspace admin

    3

    3Week 2 · Workspace admin

    Build the workspace shell

    Jira has no clients or rates, so admins set up every commercial detail in Pike before the first import.

    • Connect your accounting system and run its Import data, so customers come from the ledger.
    • Create one Pike project per Jira space or filter, with customer, billing type, budget and hourly rate.
    • Set a cost profile for everyone who logs worklogs, so imported time shows margin.
    Workspace setup
    • Teams and roles
    • Templates and labels
    • Cost profiles12 of 12
    • Accounting connected
    • Invite everyoneweek 4

    Done when: Every Jira space has a Pike project with a customer, billing type and budget.

  4. Week 2 to 3

    Workspace admin

    4

    4Week 2 to 3 · Workspace admin

    Connect and import

    Map spaces, edit the status mapping, then import. The stepper imports epics as phases before the work items under them.

    • Add the Jira integration, map every space or filter, and turn on Map epics to phases where it fits.
    • Click Import data and retry anything listed under Sync issues.
    • Compare work item counts on three spaces with Jira, and check each synced task shows its Jira key.
    Import datain order
    • Customers48
    • Projects112
    • Members19
    • Tasks1,430
    • Time entries
    • Deals

    Done when: Work item counts on every mapped space match Jira.

  5. Week 3 to 4

    Delivery lead, finance

    5

    5Week 3 to 4 · Delivery lead, finance

    One team in Pike, the rest in Jira

    Move one team with a live client project and an invoice due. Jira work items sync in real time while the others finish the sprint.

    • The pilot team logs time in Pike only. Turn on Send worklogs and have each pilot member connect their Jira account under Settings → Connections, so Jira reports still show their hours.
    • Finance approves the pilot team’s time in Time admin and sends one invoice from Pike.
    • Compare the pilot project’s hours in Pike with the worklogs on the same Jira space. A gap means a member without a personal Jira connection.

    Old tool

    Rest of team

    logs as before

    keep syncing

    Pike

    Pilot team

    approved, invoiced

    Done when: One invoice sent from Pike. Pilot hours in Pike match the worklogs in Jira.

  6. Week 4 to 5

    Migration owner

    6

    6Week 4 to 5 · Migration owner

    Cutover weekend

    Close Jira time tracking on Friday evening with Import once, which brings every worklog logged before cutover.

    • Friday: everyone logs their last worklogs, then an admin runs Import once and checks last week’s hours per person in Pike.
    • On Premium or Enterprise, archive the spaces that moved. On Standard, a Jira admin removes edit permissions on those spaces and leaves browse access.
    • Monday: everyone logs time in Pike. Pin one message with links to log time, find tasks and ask for help.

    Fri

    Approve. Sync. Read-only.

    Sat, Sun

    Rest.

    Mon

    All in Pike. Demo at 10:00.

    Done when: Time admin shows every active member by Monday afternoon. Last week’s hours in Pike match Jira worklogs.

  7. Week 5 to 8

    Finance

    7

    7Week 5 to 8 · Finance

    First month-end in Pike

    Done when finance closes a month without opening Jira.

    • Approve all time, invoice every billable project from Pike and send the invoices to accounting.
    • Set the billable status on imported worklogs for the current month before you invoice. Jira recorded no billable flag.
    • Remove Jira app access for people who no longer need it. Atlassian counts a user toward billing until they are deactivated, deleted or removed.
    Baselinebefore / Pike
    Days to invoice
    Unbilled hours at close
    Margin by project

    Done when: Month closed in Pike. Jira exports saved with two owners. Jira user count lowered.

Rebuild

Set these up in Pike by hand

  • Clients and billingSet customer, billing type, budget and rate on each project.Pike docs
  • Billable status on imported timeReview imported worklogs and set billable status in Time admin.Pike docs
  • Jira custom fieldsRecreate the fields you report on as task properties.Pike docs
  • Cost ratesSet a cost profile for every member who logs time.Pike docs

Questions

Moving from Jira: common questions

Do our developers have to leave Jira?

No. Leave the integration connected and Jira work items sync into Pike tasks in real time. With Send worklogs on, time logged in Pike posts back to Jira as a worklog, so developers see hours where they work.

Does Pike import Jira worklogs?

Yes, through Import once. Each worklog becomes a time entry with its duration, date and comment, matched to the member by the email on their Atlassian account.

We run Jira Data Center. Does the integration work?

No. The Pike integration works with Jira Cloud only. Use the CSV route for Server and Data Center, and plan time history separately because the CSV records one Time Spent total per work item.

Why does the Jira CSV show two time columns?

Time Spent shows the time logged on that work item, and Σ Time Spent adds the time on its subtasks. Use one of them for checks, never both, or you count subtask hours twice.

Can we archive Jira spaces after cutover?

Space archiving is available on Jira Premium and Enterprise. On Standard, a Jira admin removes edit permissions on those spaces and leaves browse access, so the team can still read the history.

Support through the move and after it

Migration support comes with every plan: we map your exports, run the imports with you and check the counts before cutover. After go-live, hypercare until the first month-end closes in Pike. Then we hand over to your admins and stay close for as long as you use Pike. Email hello@usepike.com with your source tool and we will say which route fits.

  • Switch playbook
  • Jira integration
  • Migration guide for every tool

Jira documentation used for this guide

  • Jira: How to export work items from Jira Cloud in CSV format
  • Jira: Export over 10,000 work items in Jira Cloud
  • Jira: Time spent rollup from subtasks in the CSV export
  • Jira: Log time on a work item
  • Jira: Archive a space
  • Atlassian: Cloud licensing
  • Jira Cloud REST API v3

Your business runs better on Pike.

Contact sales
  • ISO 27001 CertifiedISO 27001
  • GDPR CompliantGDPR
  • AICPA SOC 2 Type IISOC 2 Type II

Built to keep sensitive client data secure and private.

Pike box logoPike
Features
ProjectsResourcing & capacityFinance & invoicingDashboardsCustomers & salesTime & absencePike MCPIntegrations
Company
BlogOur storySwitch playbookMigration guideGet in touch
Industries
Creative agenciesMarketing agenciesDigital agenciesConsulting firmsIT consultanciesArchitecture firms
Resources
DocsChangelogPrivacy policyTerms and conditionsGlossaryFree toolsFAQ
All systems operational

Engineered around the 🌎

© 2026 Pike. All rights reserved.