Importing guidance

If you track issues in another service, Pulse can create a copy of them in a team. The only importer Pulse ships is Jira (CSV).

Workspace managers open Settings → Administration → Import & export (/settings/import-export). There is no general workspace export on this page.

Concepts

A workspace holds teams. Issues belong to a team. Jira epics become Pulse projects when at least one imported issue belongs to them. Read more on Concepts.

The importer does not change issue data in Jira. Pulse applies a removable Migrated label so you can filter imported issues.

Pre-import best practices

Plan the destination team and who will map before you upload a file.

Which data is worth importing?

Bring open work you still need, plus completed issues if you want them searchable in the archive. Skip columns Pulse lists as ignored after it reads the file. Strategic objects that never lived in Jira (North Stars, Objectives, Key Results) are not created by this importer.

Choose an import method

Use a Jira CSV with all fields exported. Optional Jira hostname, email, and API token import images and add link-backs — you can run without them. There is no GitHub Issues, Asana, Shortcut, or CLI importer.

Understand the import process

To run an import:

1. Open Import & export and choose Import from Jira (/settings/import-export/jira).
2. Upload the CSV and pick a top-level Pulse team (or create one).
3. Choose open issues, completed issues, or both, then map people.
4. Confirm the summary and Start import. You can leave the page; the run continues.

Previous imports lists runs. Open a row or View import history (/settings/import-export/history).

Troubleshooting

Re-importing the same source into the same team skips duplicates. You can delete a completed import in full within 14 days — that removes what the import created in Pulse, not the Jira project. See Jira.

FAQ