Moving from Jira, Monday, ClickUp, Notion & more

Three ways to move

• Jira: the built-in importer at Create project (Jira Cloud or CSV files) — https://www.boardmark.ai/docs/jira-import
• Every other tool: export from it (CSV, Excel, JSON or Markdown), then let your own AI agent (Claude, ChatGPT, Gemini, Cursor …) read the files, or the old tool's API / MCP server, and write into BoardMark over MCP with the mapping on this page
• Start fresh: create a project from a template and move only the open work; keep the old tool's export for reference
• There is no generic CSV importer today, and no built-in importer for any tool other than Jira. Where “automation” is listed as missing below, it means a rule builder: BoardMark has date reminders, webhooks and the GitHub / GitLab auto-move rules
• BoardMark does not have every feature of these tools — each section below says what is missing; check it before you decide
• Plans for what BoardMark adds: releases and the gate need a paid plan; Insights, automatic summaries, Agent accounts and editing columns / WIP limits need Premium; the rest is on every plan

Let your AI agent move it over MCP

The agent works with exactly the connected user's rights. People do these in the web app: create the project (company admin), change columns and fields (Premium), invite people and switch Releases on. Connect the agent as a project admin of that project (so it can write the brief and create sprints), following https://mcp.boardmark.ai/connect.md.

• 1. People: create the project from the closest template (see the mapping tables), invite everyone who will be an assignee, and set the columns to match the old statuses (Premium) or pick the closest columns
• 2. Agent: read get_project (status ids, fields, board type), get_docs_context and list_people
• 3. Agent: read the export or the old tool's API / MCP (read-only) and draft a mapping — statuses → status ids, people → user ids, types, fields — for the user to check and approve before writing anything
• 4. Agent: create epics / parents first, then children with create_issue (parent); put the old id in a label such as src:123 so a resumed run finds it and never creates a duplicate (search_issues label)
• 5. Agent: comments with add_comment, starting “Originally by <name> on <date>” (in the project's language); attachments with request_upload → PUT → attach_file (they count toward storage), or keep them as links
• 6. Agent: links (link_issues) once everything exists; wiki pages and docs with create_doc (the brief needs a project admin, notes any member; ≤ 1 MB per doc); upcoming sprints with create_sprint
• 7. Agent: compare counts with the export (issues, comments, files) and report what was skipped or could not move

What does not come across: original created dates and authors (they become the move date and the connected user — keep them in the text), status history (Insights starts counting from the move), closed sprints and automations. An agent has only a per-minute rate limit (429: wait retry_after), no daily quota.

Read the export in ./monday-export.xlsx and move board "Website" into BoardMark project WEB.
First read get_project WEB, get_docs_context WEB and list_people WEB, then show me the mapping
(groups → statuses, people → user ids, columns → fields or description) and wait for my OK.
Create parents before children, label every issue src:<monday item id>, add updates as comments
starting "Originally by <name> on <date>", then report the counts.

From Jira

• The same: Issues, descriptions, comments with their authors, attachments and images, links, parent / sub-task, sprints and the backlog, priority, status history (Jira Cloud) and a backdated burndown, search and saved filters (search_issues instead of JQL)
• What BoardMark adds: Everything is a Markdown file AI agents read and work on with the user's rights; card work context and warnings when agents overlap; a Delivery pipeline that shows each card's environment; a release gate computed by rules; business templates (Sales & Billing, Service desk, Budget, Roadmap, Feedback); Thai + English, and billing by the day with a Thai receipt / tax invoice for your BoardMark bill
• Not in BoardMark: Workflows with transition rules, custom issue types, JQL, Jira Automation, Jira Service Management, cross-team Plans (Jira Premium), worklogs, configurable dashboards, the calendar view, components as objects, and Marketplace apps
• How to move: The built-in importer: at Create project pick Import from Jira — Jira Cloud with a read-only API token (everything, attachments and history included), or CSV files from Filters → Export → Export Excel CSV (all fields) for Jira Data Center (no attachments, sprint dates or history). Full steps: https://www.boardmark.ai/docs/jira-import (Jira now calls issues “work items” and projects “spaces”). Confluence pages: your AI agent can read them with the Atlassian Rovo MCP server (https://mcp.atlassian.com/v2/mcp) and write project docs as in https://www.boardmark.ai/docs/migrate#agent

From Monday.com

• The same: Kanban boards, a list view, cards with comments and files, links between work, a Timeline (Roadmap & Goals; other templates on Premium), and OKRs built from boards (Roadmap & Goals here)
• What BoardMark adds: Scrum with sprints, points and burndown built in (Monday keeps sprints in its separate monday dev product), a Delivery pipeline, a release gate, AI agents working on the board over MCP with the user's rights, Thai + English quotation / billing note / receipt PDFs
• Not in BoardMark: Gantt with dependencies and critical path, automations, time tracking, WorkForms, dashboard widgets, Mirror columns, guests (a BoardMark viewer takes a seat), and views such as Calendar, Map and Workload
• How to move: Export: the board's three-dot menu → More actions → Export board to Excel (updates and subitems optional — subitem updates are not exported), or an account admin exports everything as a zip (Administration → General → Account → Export account data; no workdocs or dashboards). Then let your AI agent move it as in https://www.boardmark.ai/docs/migrate#agent — or let the agent read monday's MCP server (https://mcp.monday.com/mcp) or API directly

From ClickUp

• The same: Board and list views, sprints with points and a burndown, subtasks, blocking links, docs, goals, priority, comments and attachments
• What BoardMark adds: A Delivery pipeline and release gate, AI agents working with the user's rights plus card work context, every piece of work as a Markdown file, Sales & Billing with sales document PDFs, Thai + English
• Not in BoardMark: Time tracking, automations, several assignees, Gantt, Calendar, Mind map, Whiteboard, Chat and Form views, dashboards you build yourself, and guests
• How to move: Export: Settings → Imports / Exports → Export Items, pick Spaces / Folders / Lists, and get a CSV (comments, checklists and attachments as links; admins / owners only on several plans; the download link expires in 1 hour); Docs export as Markdown one by one. Then let your AI agent move it as in https://www.boardmark.ai/docs/migrate#agent — or read ClickUp's MCP server (https://mcp.clickup.com/mcp, OAuth) or API v2

From Notion

• The same: Markdown at the core on both sides (Notion's Markdown export maps straight to project docs), board and list views, sprints, sub-items, relations and rollups, docs next to the work
• What BoardMark adds: Boards with real rules (WIP limits, sprints a person starts, a test gate per environment), releases and a gate, Insights, automatic summaries, AI agents told to read the rules in the briefs first, which never see beyond the user's rights, Jira-style priority, an audit log
• Not in BoardMark: Free-form block pages and general databases, Gallery, Calendar and Chart views, database automations, Forms, complex formulas and guests — BoardMark never calls an AI itself; you bring yours over MCP
• How to move: Export: a page's ••• menu → Export as Markdown & CSV (a database becomes a CSV, every sub-page an .md file), or the whole workspace from Settings → General → Export all workspace content (can take hours; the link lasts 7 days) — comments come only with an HTML export. Then let your AI agent move it as in https://www.boardmark.ai/docs/migrate#agent — or read Notion's MCP server (https://mcp.notion.com/mcp)

From Trello

• The same: A Kanban board where you drag cards across columns, labels, checklists, comments, attachments, and MCP access for AI on both sides
• What BoardMark adds: Scrum (sprints, points, burndown), a Delivery pipeline, 5-level priority, epics and subtasks, releases with a gate, WIP limits, Insights, business templates, Thai + English
• Not in BoardMark: Butler-style automation, Power-Ups, Calendar, Map and Dashboard views (BoardMark has Columns, List and Timeline), an Inbox that captures from email or Slack, and guests
• How to move: Export: the board menu → Print, Export, and Share → JSON (any board member; only the latest 1,000 actions, comments included) or CSV (Trello Premium; no comments), or a Workspace admin exports everything from Workspace Settings → Export (Trello Premium; CSV + JSON, attachments optionally as a ZIP). Then let your AI agent move it as in https://www.boardmark.ai/docs/migrate#agent — or read Trello's MCP server (https://mcp.trello.com/v1) or REST API

From Asana

• The same: List and board views, sections as stages, subtasks, dependencies, goals, docs, comments and attachments, a Timeline (Roadmap & Goals; other templates on Premium)
• What BoardMark adds: Scrum with sprints, points and burndown, a Delivery pipeline and release gate, Jira-style priority built in, flags of the sales / service desk / budget templates, sales document PDFs, AI agents told to read the rules in the briefs first
• Not in BoardMark: Rules (automation), portfolios, time tracking, dashboards you build, one task in several projects at once, and multi-level subtasks
• How to move: Export: the drop-down next to the project title → Export/Print → CSV or JSON (every plan) — Asana's help does not say whether comments and attachments are in the file, so let the agent read them from Asana's MCP server (https://mcp.asana.com/v2/mcp) or API, then move everything as in https://www.boardmark.ai/docs/migrate#agent

From Linear

• The same: Issue keys, priority, labels, estimates, sub-issues, relations, sprints, board and list views, docs, and MCP on both sides
• What BoardMark adds: A Delivery pipeline with Testing / Passed per environment, a release gate, business templates and sales document PDFs, briefs that are rules for AI agents, card work context and overlap warnings, Thai + English
• Not in BoardMark: Triage with rules, nested initiatives and project updates, cycles that schedule themselves and roll work over automatically (in BoardMark a person closes a sprint and picks where unfinished work goes), T-shirt estimate scales, Asks / forms, and sub-teams
• How to move: Export: Settings → Administration → Import Export → Export data (admins; a CSV emailed as a link that lasts 12 hours) with ID, team, title, description, status, estimate, priority, assignee, labels, cycle and parent — no comments or attachments, so let the agent read those from Linear's MCP server (https://mcp.linear.app/mcp, read-only at /mcp/readonly) or GraphQL API, then move everything as in https://www.boardmark.ai/docs/migrate#agent

What to set up after moving

• What each column means — in Board columns (Premium) or in the project brief, for people and agents alike
• Working rules in the company / project brief (who moves cards where, what done means)
• Saved filters to replace your old filters / JQL (admins save them from Filters)
• Notifications: each person picks in Settings → Email notifications, LINE (Premium), Telegram (Pro, Premium) and devices; webhooks to Slack / Teams / Google Chat / Discord
• GitHub / GitLab (Pro, Premium), Releases (paid plans), automatic summaries and Insights (Premium)
• Access: teams, roles and company-wide access — check everyone sees the projects they should