Agent skill · software engineering · jeremylongshore
clickup-migration-deep-dive
Plan and execute resumable migrations into or between ClickUp Workspaces with explicit mapping, stable source IDs, bounded writes, and reconciliation. Use when moving Jira, Asana, Trello, or ClickUp data. Trigger with "migrate to ClickUp", "ClickUp migration", or "clone ClickUp Workspace".
Why this skill is useful
Adds a comprehensive migration script for ClickUp that automates data transfer from multiple project management tools, which the AI cannot generate on its own.
What it needs
Requires npm installed locally. Requires clickup account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
ClickUp Migration and Reconciliation Overview Treat migration as a versioned data program rather than a one-shot task-creation loop. Make each batch resumable, reconcilable, and safe to stop. Prerequisites Source export/API ownership and a destination Workspace/List allow-list Approved field, user, status, date, attachment, comment, and dependency mappings A durable reconciliation database, pilot cohort, rate budget, and rollback policy Tool Discipline Use Read, Glob, and Grep to inspect the repository, adapters, configuration names, tests, and evidence. Use WebFetch only for current official ClickUp documentation. Use Write or Edit after confirming the target file, Workspace boundary, and requested mode. Current Contract Get Tasks returns 100 records per zero-based page; decide explicitly about closed tasks, subtasks, and Tasks in Multiple Lists. Task priorities and dates require ClickUp's documented values and millisecond timestamps. Custom Field definitions/options must be resolved first; existing task fields use their separate value endpoints. ClickUp does not document a general transactional bulk-create endpoint, so partial progress must be durable and resumable. Authentication Use a personal token only for accountable individual/testing work or OAuth Authorization Code for a user-facing integration. Inject the token server-side through a governed secret reference, send it in Authorization, verify authorized Workspace IDs, and never print the token, OAuth client secret, or webhook secret. Instructions 1. Inventory source entities, destination hierarchy, volume, sensitivity, identities, and unsupported concepts. 2. Define mapping versions and validate status, assignee, priority, Custom Field, relationship, and attachment rules. 3. Extract with complete pagination and persist immutable source IDs plus content hashes. 4. Run a no-write transform report, then migrate a representative pilot with strict ceilings. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clickup-migration-deep-dive