Skip to content
Migration

Import from Jira (guide)

A migration approach for agencies: keep the ticket-first mental model, drop the field/workflow sprawl, and roll out the portal.

The goal of a Jira migration isn’t recreating Jira.

It’s keeping the ticket-first mental model and dropping the sprawl.

Ticket view
Keep the nouns, cut the overhead.

Import flow (what it looks like)

1) Connect Jira

Enter your Jira base URL and API token.

  • If your Jira is on atlassian.net, you’ll also need your Atlassian account email.
  • Timelint stores tokens encrypted after a successful test so re-imports are fast.
Connect Jira
Base URL + token (and email for Jira Cloud).

2) Select a Jira project (and optional JQL)

Load projects, pick which one to import, and optionally add a JQL filter to narrow the scope.

Select Jira project
Pick the Jira project key and (optionally) add a JQL filter.

3) Choose the destination project

Import into a new project, or re-import into an existing project to pull over new/changed work.

Destination project
Import into a new project or re-import into an existing one.

4) Map statuses and users

Keep the workflow readable by mapping Jira statuses to a smaller, clearer set.

Mapping
Map statuses and users before importing.

5) Review the preview (then run the import)

Timelint shows a preview so you can confirm totals and mappings before starting the run.

Review
Confirm preview totals and mapping before import.

A calm migration path

  1. Import active projects first
  2. Trim unused fields
  3. Standardise statuses
  4. Roll out the portal to clients

Use the checklists and guides

If you want a structured plan, use the resources linked on the Import page:

  • Jira import checklist
  • field mapping guide
  • workflow simplification guide
  • client portal rollout checklist

See:

Want a calmer workflow?

Timelint is ticket-first project management for agencies.

Start free Service desk