Skip to main content
You can use an AI assistant as a migration bridge when Superthread does not have a built-in importer. The assistant reads your source through an official MCP server, a read-only API token, or an exported spreadsheet, then creates cards through the Superthread MCP server.
An AI-assisted import is not a transactional backup restore. Test with five cards first, review the field mapping, and keep the source data until you have checked the completed import. For Jira, Trello, and Shortcut, use Superthread’s built-in importer for the best fidelity.
This guide was verified against the providers’ official documentation on 27 August 2026. “Official MCP” means the source vendor publishes and supports the server. A route described as “compatible MCP” uses standards both products document, but may not have a source-vendor setup page for that exact assistant. Where authentication compatibility is not documented, this guide gives a file or local-client fallback instead. These routes were checked against current vendor documentation, but were not live-tested in every paid plan, tenant, and regional deployment. Rows marked as compatible rather than vendor-verified include a documented file, API, or local-client fallback.

Choose your assistant

The exact product surface matters because the four assistants do not expose the same tools.

Import methods at a glance

Before you import

  1. Create the destination space, board, and statuses in Superthread.
  2. Decide which source projects, boards, lists, or views are in scope.
  3. Decide whether completed and archived work should be included.
  4. Make sure assignees already belong to the Superthread workspace. Do not let the assistant guess user matches.
  5. Choose a stable source identifier, such as the original task ID or URL, for duplicate detection.

Connect Superthread

Connect Superthread before adding the source. The server URL is:
Full MCP write support currently requires ChatGPT Business or Enterprise/Edu on the web. On Business, an admin or owner creates and publishes the app. On Enterprise/Edu, an admin can authorize developers through role-based access control.
  1. Open Settings → Apps → Advanced settings and enable Developer mode. Business admins can also start from Workspace settings → Apps → Create.
  2. Open Settings → Apps → Create (or the equivalent Workspace settings page).
  3. Name the app Superthread, enter https://mcp.superthread.com/mcp, select OAuth, and scan the tools.
  4. Complete Superthread authorization, create the draft, and have an admin or owner publish it if other workspace members need it.
  5. In a new chat, select Superthread from the tools menu. For an MCP-to-MCP import, select both the source app and Superthread in the same message.
ChatGPT supports remote MCP servers only. It can invoke multiple apps in one prompt and may ask for confirmation before write actions. Pro users can use custom MCP apps only for read/fetch, so Pro cannot create the destination cards. See OpenAI’s Developer mode and MCP apps guide.

Run a controlled import

Use this prompt after both sides are connected. Replace every value in square brackets.
Keep the assistant’s confirmation requirement enabled. A prompt, task description, comment, or attachment from the source can contain instructions that were never intended for the assistant.

Jira

Recommended: use the built-in Jira importer. It preserves more Jira-specific structure than recreating issues through an assistant. For a selective AI-assisted migration instead, connect the Atlassian Rovo MCP endpoint https://mcp.atlassian.com/v1/mcp/authv2 and use the controlled-import prompt. The same connection can read Jira and Confluence. See Atlassian’s client guide.

Trello

Recommended: use the built-in Trello importer.

Shortcut

Recommended: use the built-in Shortcut importer. Shortcut tokens are created at https://app.shortcut.com/settings/account/api-tokens. See the Shortcut REST API authentication reference.

Linear

Source MCP URL: https://mcp.linear.app/mcp/readonly Linear’s endpoint supports OAuth 2.1 with dynamic client registration. The /readonly variant deliberately prevents changes to the source during migration. See the Linear MCP documentation.

Asana

Source MCP URL: https://mcp.asana.com/v2/mcp Asana’s V2 server uses Streamable HTTP and OAuth. Coding clients need a registered Asana MCP app with client credentials; Asana does not support Dynamic Client Registration on this endpoint. The old beta /sse endpoint is deprecated; do not configure a new import with it. See Asana’s MCP server guide, verified-client list, and coding-client setup. A CSV export remains the fallback when the assistant cannot register with Asana.

ClickUp

Source MCP URL: https://mcp.clickup.com/mcp ClickUp’s hosted MCP is currently public beta and supports OAuth only; an API key cannot authenticate this endpoint. ClickUp applies MCP-specific rate limits, so keep batches small and retry only failed items. See ClickUp’s MCP guide.

monday.com

Source MCP URL: https://mcp.monday.com/mcp The hosted server is Streamable HTTP and supports OAuth or a bearer API token. See the monday.com MCP client guide.

Confluence

Source MCP URL: https://mcp.atlassian.com/v1/mcp/authv2 Scope the prompt to a Confluence space or parent page. Ask the assistant whether each page should become a Superthread page, project, or card before it writes anything. Atlassian retired the old /v1/sse endpoint after 30 June 2026; use the URL above. See Atlassian’s official guide.

Notion

Source MCP URL: https://mcp.notion.com/mcp Scope the import to specific databases or parent pages. Notion’s hosted MCP requires interactive OAuth and does not accept bearer tokens. See Notion’s connection guide.

Wrike

Source MCP URL: https://mcp.wrike.com/v2 Do not use Wrike’s older /app/mcp/stream or /app/mcp/sse endpoints. See Wrike’s official guides for ChatGPT, Claude, and Copilot Studio.

Smartsheet

Source MCP URLs: US https://mcp.smartsheet.com · EU https://mcp.smartsheet.eu · Australia https://mcp.smartsheet.au Smartsheet MCP requires Business, Enterprise, or Advanced Work Management. Its official MCP documentation lists US, EU, and Australia production endpoints, but no Gov endpoint. For a token-based client, generate the token under Account → Personal Settings → API Access and keep it in an environment variable. See Smartsheet’s MCP installation guide, ChatGPT guide, and Claude guide. On an unsupported plan or Gov instance, export the sheet as .xlsx or .csv and use the spreadsheet workflow below.

Airtable

Source MCP URL: https://mcp.airtable.com/mcp Airtable MCP is available on all plans, uses OAuth, mirrors the connected user’s Airtable permissions, and can be restricted to selected bases after authorization. Enterprise integration restrictions may require an administrator to allowlist it. For a read-only PAT fallback, grant only data.records:read, schema.bases:read, data.recordComments:read, and workspacesAndBases:read, then restrict resources to the bases being migrated. Create PATs in Airtable’s Developer Hub; legacy API keys no longer work. See Airtable’s official MCP guide and PAT guide.

Todoist

Source MCP URL: https://ai.todoist.net/mcp See the Todoist MCP setup guide.

Azure DevOps

Hosted MCP URL: https://mcp.dev.azure.com/{organization} For a task import, restrict the source to the wit toolset where the client supports the X-MCP-Toolsets: wit header. The hosted server requires an Entra-backed Azure DevOps organization; standalone Microsoft accounts are not supported. See Microsoft’s remote Azure DevOps MCP guide and local-server overview.

Teamwork

Source MCP URL: https://mcp.ai.teamwork.com Teamwork MCP is available to paid customers after an administrator enables it in Teamwork settings. It uses OAuth and the connected user’s existing permissions, and supports reading, creating, and updating tasks and projects. See Teamwork’s MCP setup and capability guide and plan/enablement overview.

Basecamp

Recommended source: Basecamp’s official CLI and agent skill. macOS, Linux, and WSL2 installation:
The CLI stores OAuth credentials itself; never ask the assistant to print or read its credential file. See the official Basecamp CLI and Basecamp 4 API.

GitHub Projects

Source MCP URL: https://api.githubcopilot.com/mcp/ For a classic PAT or OAuth token, reading Projects requires the read:project scope; a fine-grained PAT instead needs the relevant Projects: read permission. The MCP projects_list operation returns only titles unless the assistant asks for field_names or field IDs. See the official GitHub MCP server and GitHub’s VS Code setup guide.

GitLab

Source MCP URL: https://gitlab.com/api/v4/mcp or https://<your-gitlab-instance>/api/v4/mcp GitLab’s MCP server is beta on Free, Premium, and Ultimate for GitLab.com, Self-Managed, and Dedicated. Before users can connect, an administrator must make GitLab Duo available, enable beta and experimental features, and allow MCP access. The server uses OAuth Dynamic Client Registration and Streamable HTTP. See GitLab’s official MCP guide. If the prerequisites cannot be enabled, use GitLab’s CSV export or a short-lived read_api PAT with the Issues API.

YouTrack

Source MCP URL: https://<your-instance>.youtrack.cloud/mcp The server is built into YouTrack 2025.3 and later. Its search_issues and get_issue tools are sufficient for a source-only migration; restrict the advertised tools with ?tools=search_issues,get_issue,get_issue_comments if comments are in scope. OAuth setup depends on whether the client supports Client ID Metadata Documents (CIMD); otherwise an administrator creates an OAuth client manually. See JetBrains’ remote MCP guide, OAuth client guide, and permanent-token guide.

Redmine

Source API: {Redmine URL}/issues.json An administrator must enable REST web services in Redmine. Each user finds their API key on My account, in the right-hand pane. See the Redmine REST API guide.

Google Sheets

  1. In Google Sheets, select File → Download → Microsoft Excel (.xlsx). Use Comma-separated values (.csv) only when the workbook has one relevant tab; CSV exports the current sheet only.
  2. Make sure the first row contains clear field names such as Title, Description, Status, Assignee email, Priority, Start date, Due date, Tags, and Source URL.
  3. Remove formulas or hidden columns that should not be sent to the assistant.
See Google’s spreadsheet export guide, OpenAI’s ChatGPT data-analysis guide, Anthropic’s file-upload guide, and Google’s Gemini file-upload guide.

Microsoft Excel

Prefer .xlsx because it preserves every worksheet. Use CSV only for a single active sheet and remember that CSV discards formatting, formulas, graphics, and other workbook features. If you need CSV, use File → Save As/Save a Copy → CSV and repeat for each worksheet. See Microsoft’s CSV export guide.

Verify the result

After the assistant reports completion:
  1. Compare the source count with created + skipped + failed.
  2. Open the five sample cards and at least five cards from later batches.
  3. Check status, assignee, priority, dates, tags, parent-child relationships, and source links.
  4. Search Superthread for two or three source IDs to confirm duplicate detection works.
  5. Review every failure before rerunning. Do not rerun the entire import without the source-ID duplicate check.
  6. Revoke temporary source tokens and disconnect source connectors that are no longer needed.

What AI-assisted imports may not preserve

Unlike a native importer, an assistant may not preserve every source-specific feature. Review these explicitly:
  • Original creator and original creation timestamp
  • Complete comment history and comment authorship
  • Attachments and inline images
  • Automation rules, formulas, dependencies, watchers, and notifications
  • Custom fields that do not have an agreed Superthread mapping
  • Historical state changes and audit logs
  • Permissions that differ between the source and Superthread
If any of these are essential, keep the source available as an archive and include the original item URL on every imported card.