ClickUp spreadsheet imports: reconcile tasks, subtask IDs and mappings

SOURCE-BASED ANALYSIS · NO HANDS-ON RATING

Prepare identities before uploading

ClickUp's spreadsheet preparation guide requires unique column headers and one task per row. Its documented hierarchy format uses task IDs and a column listing the IDs of subtasks. The importer maps source columns to task fields or Custom Fields, and its preview lets you review the proposed mappings.

Our recommendation is to keep stable source identifiers and an expected parent-child worksheet. Do not use visual indentation or matching titles as your only evidence of hierarchy.

A fictional launch plan

Assume the source contains four tasks: ID A is Launch site; IDs B and C are Design and Review; ID D is Prepare assets under Design. The intended pairs are A with children B and C, and B with child D. In the documented child-ID pattern, A's subtask cell lists B and C, while B's lists D.

These invented identifiers explain the relationship direction. They are not references to existing ClickUp tasks or a claim that an import was performed.

Review the source schema

• Task reference and task name: present for every intended task.
• Subtask references: use one consistent delimiter and resolve every referenced ID.
• Status and priority: map to the intended destination values.
• Owner: identify how source people will be reconciled.
• Dates: choose the source format deliberately.
• Custom Fields: identify required destination fields and their meanings.

Run a narrow rehearsal

1. Keep an unchanged copy of the spreadsheet.
2. Choose an authorized destination and a small synthetic hierarchy.
3. Review the selected date format and multi-value delimiter.
4. Inspect every mapping instead of accepting an automatic suggestion without review.
5. Resolve invalid or unmapped required information before import.
6. Open the import report from import history.
7. Compare the resulting task identities, parent-child pairs and representative values with the worksheet.

The current importer documentation says unmapped incoming fields are excluded. A correct task count alone therefore does not prove that all required information arrived.

Handle a partial outcome deliberately

Our migration advice is to pause before uploading the same file again. Record which source rows created usable tasks and which failed or need correction. Do not assume a repeated file is an update operation unless you have validated a supported update contract.

Inspect a nested subtask's own fields as well as its position. The target is a reconciled work graph with usable ownership and dates, not merely a tree that looks familiar.

Acceptance criteria

Approve the import when every in-scope source row has a matched destination or documented exception, all expected hierarchy pairs are correct and required values are present. This source-based checklist does not execute an import, certify a migration or promise preservation of unsupported fields.