> ## Documentation Index > Fetch the complete documentation index at: https://help.zarms.cloud/llms.txt > Use this file to discover all available pages before exploring further. # Move from another tool > How to move work you tracked in Jooto, Backlog, Trello, Asana, or another tool into ZARMS: import exported data with a spreadsheet, or have an AI agent move it for you, plus what to decide before you start. You can move work from another task management tool into ZARMS using the data you export from that tool. There are two ways to do it. | Method | Good for | | - | - | | [Import with a spreadsheet](#import-with-a-spreadsheet) | Many cards, or when you want to check each row before creating it | | [Have an AI agent move it](#have-an-ai-agent-move-it) | When you don't want to rearrange the exported file yourself | Both methods can move card names, statuses, priorities, dates, and assignees, as well as descriptions, steps, and parent-child relationships. ## Decide before you move ### What becomes a board A [board](https://help.zarms.cloud/en/boards/create.md) in ZARMS is where a team or a type of work keeps its cards. The simplest approach is to turn each project or board in your old tool into one ZARMS board. ### Which status each item gets ZARMS cards have six fixed statuses: **Draft, Not started, In progress, In review, Done, and Cancelled** (see [Why there are exactly six statuses](https://help.zarms.cloud/en/concepts/fixed-statuses.md)). Decide first which of the six each status or list in your old tool maps to. | Common names in other tools | ZARMS status | | - | - | | Open, To do, Backlog | Not started | | In progress, Doing | In progress | | Resolved, Review, Waiting | In review | | Closed, Done | Done | In the import sheet, write a status as its standard Japanese name (`下書き`, `未着手`, `進行中`, `確認中`, `完了`, `中止`) or as its key (`DRAFT`, `TODO`, `IN_PROGRESS`, `IN_REVIEW`, `DONE`, `CANCELLED`). Use the standard names even if a board shows renamed labels. ### Invite assignees first Only members who have signed in to ZARMS can be assignees (Processor, Reviewer, or Receiver). Before you import cards, [invite your members](https://help.zarms.cloud/en/team/invite.md) and have them join. ### What doesn't move A spreadsheet import can't move comments, attachments, or change history. Copy anything you need into the description, or use [an AI agent](#have-an-ai-agent-move-it) to add it as comments. Labels and tags can be imported as columns if you first create matching [custom fields](https://help.zarms.cloud/en/admin/custom-fields.md). ## Export data from your old tool Here's how to export from common tools. Menu names may change when those tools are updated. | Tool | How to export | | - | - | | Jooto | Export a CSV from **Export project** in the project menu. Which plans and people can do this is decided by Jooto. | | Backlog | On the issue search screen, export the result list as CSV. The Excel format can cut off long text, so choose CSV. | | Trello | Export from **Print, export, and share** in the board menu. CSV is only on paid plans; on the free plan you get JSON. | | Asana | Export a CSV from the project menu. | | Excel | Use it as is. Upload it to Google Drive and open it with Google Sheets. | JSON is hard to work with in a spreadsheet, so it's better to [have an AI agent move it](#have-an-ai-agent-move-it). ## Import with a spreadsheet **1. Create an import sheet** On the **Bulk import** tab of the card create dialog, click **Duplicate template**. An import sheet is created in your Google Drive. **2. Paste in the exported data** Open the exported file with Google Sheets and paste each column into the template. See the table below for which column goes where. **3. Fix statuses and assignees** Replace the values in the `状態` (status) column with one of the six statuses. For assignees, the email address of a member who has joined ZARMS is the safest choice. **4. Import** Click **Import sheet**, choose the sheet, check that there are no errors, and click **Create**. For details, see [Import and export with spreadsheets](https://help.zarms.cloud/en/boards/spreadsheets.md#import-cards). You can import up to 500 rows at a time. If you have more, split them across several sheets. ### Column mapping | ZARMS column | Example name in Backlog | Example name in Asana | What to enter | | - | - | - | - | | `ボード名` (board name) | — | — | The board for the card. Use the old project name | | `カード名` (card name) | 件名 (Subject) | Name | Required | | `状態` (status) | 状態 (Status) | Section/Column | One of the six statuses | | `優先度` (priority) | 優先度 (Priority) | (custom field) | `低`, `中`, or `高` (Low, Medium, High) | | `進行開始` (start) | 開始日 (Start date) | Start Date | A date | | `完了期限` (due) | 期限日 (Due date) | Due Date | A date | | `進行者` (Processor) | 担当者 (Assignee) | Assignee Email | An email address or display name | | `説明` (description) | 詳細 (Description) | Notes | The card description. Up to 4,000 characters | | `チェックリスト` (checklist) | — | — | Steps, one per line | | `親カード` (parent card) | 親課題 (Parent issue) | Parent task | The card name of the parent card | For Jooto and Trello CSVs, paste the task name (card name), list (status), description, due date, and checklist (steps) into the matching columns the same way. ### Move parent-child relationships In the `親カード` (parent card) column, write the card name of the row you want as the parent. The parent row must be in the same sheet and on the same board. Parent rows are created first, then their child cards. If your old tool exported the parent as an issue key (such as `PROJ-12`) or an ID, replace it with the parent row's card name. To use a card that's already in ZARMS as the parent, write its card number, such as `#123`. A parent must be on the same board as its child. ## Have an AI agent move it If you connect an AI agent such as Claude or ChatGPT to ZARMS, you can give it the exported file and ask it to "turn this data into ZARMS cards." You don't need to rearrange the file's columns, and it can move descriptions, steps, and comments too. **1. Connect the AI agent to ZARMS** Follow [Use ZARMS from AI agents (MCP)](https://help.zarms.cloud/en/mcp/overview.md). The agent will create cards, so choose **Read and write**. **2. Try a few first** Give it the exported file, tell it which board to use and how to map statuses, and have it create just a few cards. Check the result in ZARMS. **3. Move the rest** If everything looks right, ask it to do the rest. With many cards, working in smaller batches, such as one board at a time, makes the result easier to check. Here's an example request. ```text theme={null} The attached CSV is a task list exported from my previous tool. Create one ZARMS card per row on the "Sales" board. Map statuses like this: Open → Not started, In progress → In progress, Resolved → In review, Closed → Done. Put the description in the card description and the comments in card comments. Create just 5 cards first and show me the result. ``` Comments written by an AI agent are posted under the name of the person who connected it. To keep the original author and date, ask the agent to include them in the comment text. Actions from AI agents don't use ZARMS credits. ## If something goes wrong * **The assignee column shows an error**: That person hasn't joined ZARMS yet. Invite them, wait for them to join, and import again. * **The status column shows an error**: It contains something other than the six standard statuses. Use the standard names even on boards with renamed labels. * **The parent card column shows an error**: The parent row is on a different board, or several rows have the same card name. Put them on the same board and make the card names distinct. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.