Integrations & Import

The Integrations page

Open Sidebar → Admin → Integrations. Everyone can look; connecting usually needs an admin, and each card says what it needs.

Connect GitHub

Connect GitLab

Code on tickets and Git rules

• Git moves still follow the board's workflow rules: if one stops a move, the ticket gets a comment saying why. History says the move came from Git.
• Anyone who can see a ticket sees its Code tab; Git connections and Git rules are only for people with “Manage Git connections”.
• Code links never show in the client portal.

Slack: notifications and the app

Slack has one card on the Integrations page. Click Set up (or Manage once something is connected) to open its panel, which has two sections: Notifications and Slack app (commands). The card shows whether each one is on.

Work from Slack

API keys and webhooks

To connect a tool that isn't listed, use the API and webhooks in Sidebar → Company → Company Info → Developers. Standard and up.

A key can never do more than the person it acts as, nor more than whoever set it up, and only reaches your own company. Changes it makes show “via API key: <name>” in the history, and the account owner is told when a key is made, changed or revoked. Read the full details in the Company guide and the API docs.

AI tools

Let the AI tools your team already uses (chat apps, code editors and other AI tools that support MCP, the open standard for connecting AI tools) find, create and update tickets, boards, sprints, time and more in TeamTrackin. Open Sidebar → Company → Company Info → Developers → AI tools.

The link alone opens nothing, an AI tool never does more than the person it acts as, and it only ever reaches your own company. Read the full steps in the Company guide and the AI tools docs.

Import from another tool

Moving from ClickUp, Asana, Linear, Trello, monday.com, Notion, or Jira and Confluence? Bring boards, tickets, comments, files and people over. A CSV or Excel export works for any tool. Moving a wiki? Confluence spaces and pages (with their databases and whiteboards), and pages from Notion, ClickUp, Linear and monday.com, come into Docs (see Pages into Docs below).

The import step by step

1. Connect or upload

• If the tool is already connected on the Integrations page, click Use connected account.
• Or use the tool's own sign-in where offered (for Notion: Connect with Notion, pick the pages to share, and you come back).
• Or paste a personal token and click Connect; Where to find it explains each tool. The token is only used for this import and removed when it ends.
• For CSV or Excel (or a Trello JSON export), upload the file and click Read this file.

2. Columns (CSV and Excel only)

Each header shows with three sample values. Pick what it holds (title, key, status, priority, assignee, created, labels, comment, attachment and so on) or Ignore, pick the title column, then click Read again after changes.

3. Map

• Where it goes: the boards to bring and where each lands (a new Space or one you have, a group, a new board or an existing one).
• Statuses → columns: a column for each status (or a new column) and what it means (the nine column meanings). The meaning is guessed from the status name first (“Not started”, “To do”, “Backlog”, “New” and “Ready for dev” mean To do), so check any that look off.
• People: matched by e-mail to an active person here, kept as a name (not invited yet), or left out. Archived people are never offered; a row matched to someone archived since asks you to pick again.
• Fields, priorities and ticket types: map each to one here, a new field, or leave it out. Columns that match the ticket's own fields start there (Priority, Ticket type, Description, Estimate, Story points, Labels, Due date, Start date and Assignee); only columns that match nothing become new fields.
• What to bring (Jira & Confluence): tick Jira tickets, Confluence pages, Databases and Whiteboards, or untick what you'd rather leave behind. A company with only Confluence unticks Jira tickets; on a site without Jira it's unticked for you, with the reason.
• Docs and pages (when the tool has pages): Bring pages into Docs, and for each space a new Docs space (with its name) or one of yours.
• Also bring (comments, files, time…), who sees new boards, and optionally only tickets changed since a date.
• Pages only (Jira tickets unticked): the board, ticket and new-board sections aren't shown. Pick the spaces under Docs and pages and run the dry run.

Good guesses are filled in; fix only what's off. Click Save and run a dry run.

Some tools (Notion, for one) don't say how many tickets a board has. Then the map shows “—” for that board and Ticket counts appear after the dry run; the dry run shows the real numbers.

4. Dry run

See exactly what will happen before anything is written: per board, tickets New, Updated, Unchanged or Kept yours, what gets made, people not invited yet, files and their size, how long it takes, and what isn't brought over. Nothing is on any board yet. Click Change the mapping to go back, or Start import.

5. Import

A progress bar shows live counts. Pause, Resume or cancel. You can leave the page: it keeps running and you get one notification when it's done. If the other tool asks to slow down, it waits and carries on by itself. Only one import runs at a time.

6. Report

What came in, whether the counts match the dry run, what came in as text, notes and every problem with its reason. Download CSV gives the full list.

An extra the other tool refuses (comments, files or time) never stops the import: the tickets still come in and the import finishes. Left out this time lists each one with what to turn on, for example “Comments on 12 tickets in Income couldn't be read”. Files that didn't come in are named with their count (ticket files and page files on separate lines), with the fix. Turn it on in the other tool and import the same source again: tickets already in show as Unchanged and the missing extras come in. Files stored on another website are kept on the ticket as links; files and images uploaded to the tool itself (Notion included) are copied.

Pages into Docs

Notion, Confluence, ClickUp Docs, Linear documents and monday.com Docs come into Documents with their page tree and order, formatting, images, files, comments, authors and dates. Jira and Confluence are one card on the New import list, Jira & Confluence (Confluence is an import source, so it isn't on the Integrations page). One connection brings Jira tickets, Confluence pages, databases and whiteboards in one dry run, one report and one undo; a team with Confluence but no Jira unticks Jira tickets. Imports started from the old Confluence card still open from Imports.

• Links between imported pages open the Docs pages. In Notion, a ticket's “Page: <title>” line links to the imported page.
• Images and files are copied into Docs. Files kept on other websites stay as links.
• People not invited yet show as Written by <name> with a Not invited tag, and their comments are tagged Imported. Hand them over under Users → Imported people and their pages and comments move to that person.
• Importing again never makes copies: changed pages are updated, unchanged pages show Unchanged, and a page you edited in Docs is kept as yours.
• Confluence databases and whiteboards come in the same import, under the page they sat in, with a link back. Confluence shares only their names: a database comes in empty until you upload its CSV export on the report (⋯ → Export → CSV in Confluence, then Upload CSV), and a whiteboard comes in as an empty board with a note.
• From Notion, columns come in one after another, callouts, toggles, tables and synced blocks come in as their content, and a block Docs can't show (such as a button) leaves a short grey note. Importing again updates pages you haven't edited.
• From monday.com, check lists come in as task lists with their ticks, notice boxes as callouts, tables with their cells and a layout's columns one after another.
• Notion databases inside pages come in as boards in the same import: the page keeps a link to each board, and the report lists them under Databases inside pages.
• From Confluence, emoji, dates, status labels, panels, expand sections, task lists, tables and @mentions come in as the same things in Docs; SVG images come too, cleaned first.
• Undo removes the imported pages with their files and comments, and the databases and whiteboards the import made.
• Without Documents in your plan, pages are skipped and the dry run says why.

After an import

• An imported ticket shows its old key, for example “Was ABC-123”. Searching for the old key (Ctrl/⌘ + K, a ticket picker, or key = ABC-123 on the Search page) finds it. Export CSV has an Old key column.
• Created dates come from the other tool. Comments by people who aren't users here keep their name, tagged imported.
• Descriptions and comments keep their formatting (headings, lists, checkboxes, bold, links). Files the other tool stores itself are copied onto the ticket, and images on comments onto the comment; a comment that was only an image says “(image: name)”. Links that stop working after a while are never put on a ticket.
• Imported time says “Imported from <tool>” in the Worklogs and counts in Time vs estimate, but never in payroll, timesheets, invoices, summaries or insights.
• Importing writes quietly: no automations, e-mails or notifications fire for imported tickets.
• Import the same source again and nothing doubles: unchanged tickets are skipped, changed ones are updated, and tickets your team changed since are Kept yours and listed in the report.

Imported people

People from the other tool who aren't users here come in as names. They don't take a seat and don't show in payroll or timesheets. Their tickets show a dim avatar marked not invited and count as Unassigned.

What each tool brings