Import

You can import tasks from popular project management tools into Hule. Imports create new spaces and lists in your workspace — your existing data is never overwritten.

Supported sources

Source	Format	What's imported
ClickUp	CSV export	Tasks (with subtasks), statuses, priorities, assignees (by name), due dates, tags, descriptions
Trello	CSV/JSON export	Cards, lists (become Hule lists), labels (become tags), members, due dates, descriptions
Todoist	CSV export	Tasks, subtasks, priorities, due dates, labels (become tags), projects (become spaces)
Notion	CSV/JSON export	Database items, status/property columns
Kaiten	CSV export	Tasks, statuses, priorities
Weeek	CSV export	Tasks, statuses
Yandex Tracker	CSV export	Issues, statuses, priorities, assignees
Hule	Account export (JSON)	Folders, lists, tasks (with subtasks), status templates (groups preserved exactly), priorities, dates, tags, plain-text descriptions, comments, time logs, saved views

Importing a Hule account export

The Hule source re-imports the JSON file produced by Settings → Export — for example to copy every workspace you own into another workspace, or to seed a fresh account.

• Status templates are preserved exactly. Unlike the heuristic sources (which guess a status's group from its name), a Hule export carries each list's real status template, so custom statuses keep their exact group and order. Lists that used a built-in template are rebuilt from the statuses their tasks actually use.
• Every workspace in the file is merged into the target workspace. Nested folders are flattened to the top level; lists that sat at a workspace's root get a folder named after that workspace.
• Members are not carried across. Assignees, @mentions and task references point at the source workspace's members, which don't exist in the target — so imported tasks are assigned to you, and descriptions come in as plain text (formatting and mentions are flattened).
• Comments and time logs come across, attached to their task. You become the author/logger; comment bodies are plain text, and time-log dates/durations are preserved. Comment attachments and reactions are not carried over.
• Saved views come across — each list's default view plus any extra list/folder/workspace views, with their layout, mode, sort, grouping, display config and icon. View filters are not carried (their rules point at statuses/tags/members that don't survive the move), and personal views are skipped.

How to import

1. Export your data from the source tool (usually as CSV).
2. In Hule, go to the workspace where you want the data.
3. Click Import in the top bar.
4. Select the source tool.
5. Upload the exported file.
6. Review the mapping preview (statuses, users).
7. Click Import.

Import runs in the background. Depending on the file size, it can take a few seconds to a minute.

What happens during import

The import process:

1. Parses your file and normalises the data.
2. Maps statuses — source statuses are matched to Hule status groups (Open / In Progress / Closed). Unmatched statuses are created as new statuses.
3. Creates structure — spaces and lists are created matching your source organisation.
4. Creates tags — labels/tags from the source are created in Hule.
5. Inserts tasks — tasks are sorted by their parent-child relationships so subtasks end up under the right parent.
6. Preserves metadata — due dates, priorities, descriptions, and assignees (matched by name) are carried over.

What's not imported

• Comments (coming in a future update).
• Attachments.
• Recurring task definitions.
• Views and filters — you'll need to set those up in Hule after import.
• User accounts — assignees are recorded by name; they need to accept their workspace invitation separately.

Rollback

If an import creates data you don't want, you can manually delete the created spaces. There's no automatic rollback — review the preview carefully before confirming.

Related

• Quick start — getting started with Hule.
• Tasks — working with imported tasks.