xpntl
SIGN IN GET STARTED
§ SWSWITCH TO XPNTL

bring the backlog.
keep the agents.

See every row before anything is written. Decide who each person becomes. Keep the agents you already use.

READ THE MIGRATION GUIDE START A FREE TRIAL

Importing is included in Pro and Ultra. Both start with a 30-day trial, no card. Pricing

§ SW.1THREE REASONS NOT TO · ANSWERED

the three things
everyone says first.

You half want to move, and you have reasons not to. They are good reasons. Here is what is true about each one.

01"What we have works fine."

it works for people.
agents are doing the work now.

Once an agent does part of the work, it needs a board it can read and write. In xpntl an agent is a member of the workspace with a role. Every tool it calls is checked against that role, and every change carries its name. An agent's part ends at Review. Whether the work ships is still a person's call.

  • A SEATEach agent is its own member, not a shared login
  • THE RULESThe same role checks a person gets
  • APPROVALLoops only propose. A person approves or vetoes
  • THE RECORDWho did what is kept, person or agent

What an agent can do → How loops work →

02"Moving is disruptive."

you see every row
before anything is written.

Connect the old tracker with a read token and the importer lists what it found. Everything starts selected. Filter by title, untick rows, or drop a whole status in one click. Nothing is written until you press Import, and nothing in the old tracker is changed.

  • THE PREVIEWTitle, status and source for every row it found
  • PEOPLEMatched on email or name. The rest are yours to place: pick a teammate, or leave the work unassigned
  • THE SOURCERead only. The import never edits or deletes there
  • YOUR TOKENUsed for the run. It is not saved with the import
The preview, step by step →

03"We have years in the old tool."

your work moves.
the old tracker stays.

Titles, descriptions, states and assignees come across from every source. Labels, dates and comments depend on where you are coming from.

Nothing in your old tracker is changed. It stays as your archive.

What your tracker brings ↓
§ SW.2WHAT YOU KEEP

you change the board.
the rest stays yours.

You bring the agents you already use, over MCP, and they run on the plans you already pay for. No AI credits. Nothing sits between you and your model bill.

Pricing → Security → Request the source →

Your agent
Claude Code, Codex, Cursor, Copilot, Gemini CLI, OpenCode, Aider, Grok Build, or anything else that speaks MCP
Your model bill
No AI credits. We never meter tokens or mark them up
Your compute
Your agent keeps running on your machine, on the plan you already pay for
Your sign-in
SSO with Google, GitHub or Microsoft, on every plan
The source
Yours to read on request. Self-hosting is included with paid plans
The way out
Export the whole workspace as JSON, with an attachments archive
§ SW.3COMING FROM

what each importer brings.

One block per source. Each list is read out of the importer itself.

Jira Cloud

One Jira project into an xpntl project you choose.

Carries

  • Summary
  • Description
  • Status, by category
  • Priority
  • Labels
  • Assignee
  • Comments
  • Created and updated dates
  • PEOPLEYour mapping of display names first, then a matching email.

GitHub Issues

One repository's issues into an xpntl project you choose.

Carries

  • Title
  • Body
  • Open or closed
  • Labels
  • Assignee
  • Created and updated dates
  • PEOPLEYou map each login to a teammate. A login that matches a teammate's display name, or the first part of their email, is filled in for you.

ClickUp

One Space becomes an xpntl project of the same name. Its lists become lists.

Carries

  • Name
  • Description
  • Status, by name or type
  • Priority
  • Tags, with colors
  • Assignees
  • Sub-tasks
  • Comments
  • Attachments
  • Start and due dates
  • Created and updated dates
  • Custom fields, in the description
  • PEOPLEMatched to your teammates by email, with nothing for you to map.
  • ALSOAn agent can run this one over MCP.

Azure DevOps

One project's work items into an xpntl project you choose.

Carries

  • Title
  • Description, as Markdown
  • Work item type
  • State, by category
  • Priority
  • Tags
  • Assignee
  • Parent links
  • Comments
  • Created and changed dates
  • PEOPLEYour mapping of display names first, then a matching email.
  • ALSORun it again and it brings over what is new.

Asana

One project's tasks into an xpntl project you choose.

Carries

  • Name
  • Notes
  • Open or completed
  • Tags
  • Assignee
  • Created and modified dates
  • PEOPLEMapped by name or email. Matches are filled in for you.

Trello

One board's cards into an xpntl project you choose.

Carries

  • Name
  • Description
  • Open or done, from the list
  • Labels
  • First member, as assignee
  • PEOPLEMapped by member name. Matches are filled in for you.
  • ALSOArchived cards, and cards on a list named Done, Complete, Closed, Shipped or Resolved, land in Done.

A CSV file

One file into an xpntl project you choose. You map the columns.

Carries

  • Title
  • Description
  • Priority
  • State, by name
  • Assignee
  • PEOPLEYour mapping first, then a cell that is a teammate's email.
§ SW.4HOW SWITCHING WORKS

three moves.
the guide has the rest.

  1. Preview

    Open Settings, then Import. Pick your source, paste a read token, and look at what it found.

  2. Map and import

    Say who each person becomes, untick what you do not want, and press Import.

  3. Connect

    GitHub for pull requests, Slack or Teams for the channel, and your agents over MCP.

READ THE MIGRATION GUIDE → START A FREE TRIAL

30-day trial on Pro and Ultra · No card · SSO on every plan