The work’s definition.
Title, description, acceptance criteria, type, complexity, status or stage key, due date, and blocked state with a reason.
titledescriptionacceptance_criteriastage_keyMove existing work
Bring the useful work.
Keep the context clear.
Choose a manageable task list, prepare its destination and check how the fields map. The CSV import uses a spreadsheet-style file to create new work and keep a reference to its source.
- Source list
- Reviewed mapping
- New work
The supported path is CSV. Direct importers for providers such as Jira, Asana and Trello remain Coming soon. Their catalogue cards cannot connect or transfer work yet.
- File size
- 2 MB
- Data rows
- 500
- Columns
- 100
- Per confirmed batch
- 50 rows
Prepare a small first destination
Give the list a place to belong.
An active administrator needs permission to create work in the destination Project or Team. The import follows existing access rules and any Required Context reading requirements. It does not invite people or make them members.
- 01 · Owner
Choose a Project or Team.
Agree who owns the outcomes and who should have access. Create the destination through the normal workspace controls before importing.
- 02 · Working rules
Prepare the workflow.
Check stages, enabled work types, the estimation scale, existing members and labels. Map the imported fields to those choices.
- 03 · Small sample
Try a small sample.
Include a parent and child, an item with a date and a completed item if relevant. Check the result before importing the rest.
What CSV can carry
A useful task list.
A clear field mapping.
Download the template in Admin → Integrations → Imports → CSV file. Map only supported fields; extra headers do not create custom fields.
Links between items.
Source IDs that stay the same across uploads, links to parent items, and assignees and labels matched to existing destination values.
source_idparent_idassigneeslabelsRelevant source history.
Source creation and completion dates and a completion summary. Depending on the work type, you can also import timebox, severity, impact, cost and benefit-period details.
created_atcompleted_atcompletion_summarySOURCE NAMESPACE · receipt-work
Use another row’s source ID to link a child to its parent. Tellenze assigns new destination IDs after import.
| source_id | parent_id | title | Destination after import |
|---|---|---|---|
source-41 | — | Customers can download a receipt | LAUNCH-41New parent work item |
source-42 | source-41 | Explain a failed receipt download | LAUNCH-42New child of LAUNCH-41 |
Your IDs will differ. Import history keeps the source IDs. It records the importing member and import time separately from the original source dates.
Make a plan for the rest
Check what moves.
Plan for what stays.
Decide what stays in the source system, what you need to recreate and what needs another agreed way to move. Keep the original export and source records for reference.
No provider credentials are needed. The CSV path does not contact or modify your source system.
CSV does not import
- Comments and activity history
- Attachments and external links
- Memberships and original authors
- Focus groups and milestones
- Linked documents and their contents
Check these separately before treating the transition as complete.
Preview before creating work
Map it. Review it.
Then confirm.
Uploading and previewing prepare the import. New work is created only after you confirm the reviewed preview, in batches of up to 50 rows.
- 01
Check the file format.
Check the text encoding, the separator between fields and whether the file has a header row. Give every column a unique name and map the Title field.
- 02
Match the destination values.
Map source stages, assignees and labels. Decide how to handle unknown or unclear values. Check dates, estimates and parent links too.
- 03
Resolve preview issues.
Correct the source or mapping and preview again, or explicitly skip invalid rows. Inspect warnings before confirming.
- 04
Confirm and inspect results.
Process up to 50 rows per request. Check how many were created, skipped or failed, then continue or resume the saved import.
Source stage ReadyDestination stage Backlog
Source assignee [email protected]Existing member Jordan
Source label EscalationExplicit choice Needs mapping
Match an unknown value before confirming, or choose to skip that row. Importing does not invite an unknown assignee.
Keep the same source IDs
Upload again carefully.
Check what happened.
Choose a source namespace: a name for the source list. Reuse it on later uploads. Keep source IDs the same so the importer can recognize work already imported into that destination and namespace.
Import history keeps each row’s result and links to the new tasks, so you can see what was created and what still needs attention.
Read retry and history detailsKeep later edits to imported work.
Reusing a source ID detects an already imported item. It does not overwrite the item’s current title, assignments or later manual edits.
Use IDs when the file may change.
Without source IDs, the importer recognizes duplicates only when the file and row position are identical. Editing or reordering that file can create new items when you upload it again.
Cancellation stops the remaining rows.
Already created items stay in the destination, and import history remains. Cancellation does not remove work already created.
Inspect a failed row before resuming.
Read its reason, correct the source or mapping and keep the same source namespace and IDs when uploading a corrected list.
After the sample checks out
Turn the imported list into a working habit.
Read a parent and its children, check assignments and stages, and verify the original dates. Add any missing context, then agree how the team will review the results of new work.
Give people a clear start.
Confirm membership and access to the Project or Team. Help each teammate find the work they now own.
Start with TellenzeReuse a good definition.
Templates help the next item carry the right structure, guidance and checks.
Read the templates guideChoose a small focus.
Agree a useful outcome and how often you will review the work that matters next.
Try a first focusA few useful details
Know what comes across.
Can CSV bring over my whole source workspace?
CSV imports supported work-item fields into one prepared Project or Team. Comments, files, memberships, original authors, source activity, Focus groups, milestones and document links need their own plan. Check what is included before moving a list.
Will importing invite assignees or change access?
No. Map assignees to existing eligible destination members. An active administrator still needs creation permission, and the import follows any Required Context reading requirements.
What happens to completed source work?
It records historical completion and keeps the original completion date if you supply one. It does not make a new completion decision or award fresh Points or XP. Historical imports do not send assignment notifications or trigger creation automations.
Can I update imported work by uploading it again?
The importer recognizes a source ID already used in the same destination and namespace. It keeps the existing item’s current fields. Make later work changes through the normal workspace workflow.
Is there a direct importer for my current provider?
Direct provider importer cards currently remain Coming soon. Use Product availability to see what is supported, or discuss your transition requirements with Tellenze.
Keep your next step clear
Find the guide for your next step.
COME TAKE A LOOK
A little less busy.
A lot more together.
Curious? Join the waitlist and see how we welcome your team.
Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace.
Join waitlist Start with your email. No payment needed to join.