Migration

Switch from Jira.Your history comes too.

FlowX imports your Jira CSV export directly — projects, tasks, statuses, people, and dates arrive mapped and traceable, with a dry run before anything is written.

Free trial · no cardUp to 5,000 items per fileRe-imports update — never duplicate

How it works

From export to imported, in three steps

A wizard in Settings → Import, run by a workspace admin. Upload the file your tool already exports — or connect with an API token to bring comments and attachments too; the token is used for the one pull and never stored.

1

Export from Jira

In Jira: Filters → Export → CSV (all fields). One file per 1,000 issues is fine — the import is safe to run in parts.

2

Map, then dry-run

Match source projects, statuses, and people to FlowX — statuses come pre-suggested, people match by email. The dry run shows exactly what will be created, updated, and skipped, plus the plan-quota math, before anything is written.

3

Import, with a report

One transaction writes it all and ends in a report of what happened. Zero notifications are sent, finished work arrives Closed instead of entering review queues, and every item keeps its source key — searchable, and shown on the record.

No surprises

What arrives — and what doesn't

The wizard states this before you commit, not after. Approval history is never reconstructed from a source workflow — a guessed chain is worse than none.

Imported

  • Projects and their issues, as FlowX projects and tasks
  • Titles, descriptions, priorities (Highest → Critical)
  • Statuses — mapped your way, pre-suggested from Jira's status categories
  • Assignees, matched by email against your workspace
  • Created, due, and resolved dates — history keeps its dates
  • Issue type as the task category
  • The issue key on every item (PHX-102), searchable in FlowX

Not imported

  • Sprints and story points
  • Custom fields
  • Workflows and automations
  • Epic and sub-task hierarchy — everything arrives as flat tasks
  • Comments and attachments — from a file export; connect with an API token instead and they come along

After the move

What your imported work plugs into

FlowX is a system of record for operations: every item has an owner, a deadline, and an audit trail. Imported history lands inside that — it doesn't sit in a separate archive.

Multi-level approvals

Sequential and parallel approval chains with delegation, escalation, and a no-self-approval rule — attached to requests and projects, not bolted on.

A weekend-aware SLA clock

Deadlines follow the workspace's weekend calendar and timezone. Overdue is a flag with an audit trail, not a status someone edits away.

Arabic, all the way down

A full right-to-left interface and Arabic notifications — set per workspace, overridable per person and per device.

An audit trail you don't configure

Creates, edits, approvals, and sign-ins are recorded automatically — including what the import itself did.

Questions

Before you export

Bring your history. Start today.

Create a workspace in 2 minutes, run the import, and your projects are in FlowX the same morning — with a report of exactly what moved.