Hule Docs

Appearance

Import from another tool ​

Import when you move to Hule from another task tracker and want your projects and tasks to come with you. You export a file from the old tool, upload it in Hule, and Hule builds folders, lists and tasks from it in your workspace.

Before you start ​

You need the Import data permission and an export file from your old tool.

You need the Import data permission

Your permission set must include Import data. The Admin and Super Admin sets include it, and the workspace owner always has it.

Files up to 25 MB, 1,000 new tasks a day

Imported tasks, subtasks included, count toward the daily limit of 1,000 new tasks per member, so a bigger export has to be split.

Export files by tool ​

ToolFileWhat you export there
ClickUpCSVa List or Table view: Customize → Export → CSV
TrelloJSONa board: Show menu → More → Print and Export → Export as JSON
TodoistCSVa project: ⋯ → Export as CSV (completed tasks are not included)
NotionCSVa database: ⋯ → Export, format Markdown & CSV, content Current view; unzip the archive
Yandex TrackerJSONthe response of the Tracker API issue search (for technical users)
KaitenJSONspaces, boards, columns and cards from the Kaiten API, in one file (for technical users)
WEEEKJSONprojects, boards and tasks from the WEEEK API, in one file (for technical users)
HuleJSONanother Hule account's export: User settings → Export → Download my data (see Download your data)

Advanced tools: export through the API

The tools marked "for technical users" are marked Advanced in Hule: they have no export button, so you call their API and save the answer. Hule shows the exact requests when you pick one.

Import a file ​

  1. Export your data from the old tool: Export files by tool gives the file and the menu path for each one.

  2. Click your name at the bottom of the sidebar and choose Workspace settings. With several workspaces, pick the one to import into: the file goes into the workspace whose settings you open. The settings open for that workspace.

  3. In the Data section, open Import. You see a card for each tool.

  4. Click the tool you are moving from. The page shows How to export with the steps for that tool, and an upload area.

  5. Drag the file onto the upload area, or click it and choose the file. Its name and size appear.

    "File is too large (max 25 MB)"?

    Export a smaller part — one board, project or view at a time — and import each file.

  6. Click Start import. The button shows Importing… until the import finishes. Then the message "Imported … tasks from …" appears, and What was imported counts what was created, kind by kind.

    Workspace settings, Import from Trello after the import: 1 folder, 3 lists, 37 tasks and 2 tags created, with two warnings about created tagsWorkspace settings, Import from Trello after the import: 1 folder, 3 lists, 37 tasks and 2 tags created, with two warnings about created tags

    "Import failed (429)"?

    The file has more tasks than you can still create today, and nothing was imported. Split the file, or import it again after midnight UTC.

  7. Click Open workspace. The settings close. The new folders are already in the sidebar.

Imported structure and data ​

For example, a Trello board Website with the lists Ideas, Doing and Done becomes:

text
📁 Website            a new folder at the end of the workspace
├── 📋 Ideas          one list per Trello list
├── 📋 Doing
└── 📋 Done

Cards keep their Trello list, not a status: a card is in the Done stage only if its due date was marked complete, otherwise it is Not started. Archived lists and cards are not imported.

Folders and lists follow the old tool's structure. Each import adds new folders at the end of the workspace; move them afterwards.

Old toolBecomes in Hule
ClickUpa space becomes a folder, and a list a list
Trelloa board becomes a folder
Todoista project becomes a folder Todoist with one list, Imported from Todoist
Notiona database becomes a folder Notion with one list, Imported from Notion
Yandex Trackera queue becomes a folder with one list, Issues
Kaitena space becomes a folder, and a board a list
WEEEKa project becomes a folder, and a board a list

What else comes across:

  • Tasks keep these, where the old tool had them:

    • title and description;
    • status and priority;
    • dates, which become all-day dates;
    • tags.

    Subtasks and checklist items become subtasks.

    What Subtasks counts

    In What was imported, Subtasks counts the subtasks made from checklist items. Subtasks that were already subtasks in the old tool are counted under Tasks.

  • Statuses: each imported list gets its own status template, and each status goes to a stage by its name. A status Hule can't place becomes Not started, with a warning. If none of a list's statuses lands in Not started, Hule adds to do to its template. A Hule export keeps its own status templates as they were.

  • People are not carried over. Every imported task is assigned to you (subtasks made from checklist items are left unassigned), and imported comments and time logs are credited to you. Reassign tasks after the import.

  • Attachments are not imported.

Importing a Hule export copies each workspace you owned into this one, with comments, time logs and shared views; nested folders become top-level folders, and lists at the top of a workspace go into a folder named after that workspace.

If it doesn't work ​

A failed import leaves nothing behind

If an import fails, Hule removes everything it created in that attempt, so you can fix the file and try again.

  • There is no Import page in Workspace settings. You don't have the Import data permission. Ask an admin or the owner to grant a permission set that has it; see Permissions and access.

  • "File is too large (max 25 MB)". Export a smaller part — one board, project or view at a time — and import each file; see Limits.

  • "Import failed (429)". Nothing from this file was imported: it has more tasks than you can still create today (1,000 a day per member, subtasks included; see Limits). A file with more than 1,000 tasks never fits: split it. Otherwise import it again after midnight UTC, when your daily count resets.

  • "Could not parse the file." or a message about the file's format. The file is not the export Hule expects for that tool. Check that you picked the right tool and followed its How to export steps; see Export files by tool.

  • Warnings after the import. Hule lists what it created or had to guess:

    • each new tag;
    • a status it placed in Not started;
    • a subtask it moved to the top level.

    Fix those statuses by hand; see Change statuses. A warning that comments or time logs could not be imported means those were not copied; the tasks themselves were.