Migrate your ZenPilot data

ZenPilot organizes ClickUp workspaces into three operational areas—Growth, Delivery, and Operations—mirroring the client's organizational structure. We preserve the space hierarchy and the naming conventions used in the Blueprint phase. We flag any non-standard space names that may indicate custom organizational logic that needs review.

Folders represent logical groupings within Spaces, often corresponding to client portfolios or service lines in agency contexts. We preserve folder names and nesting depth. ZenPilot's methodology typically creates a flat folder hierarchy with intentional naming conventions that we replicate exactly.

Lists are the primary task containers in ZenPilot-managed workspaces. We map List names, status schemes, task ordering, and recurring task configurations. ZenPilot often uses Lists to represent distinct workflow stages or client projects, so we preserve the List-to-status mapping carefully.

Tasks carry the core workload data. We preserve task names, descriptions, assignees, due dates, priorities, dependencies, subtasks, comments, and attachments. ZenPilot's discipline means task data is typically well-populated and consistently structured, which makes migration clean.

ClickUp Custom Fields support 30+ field types including text, number, date, dropdown, rating, and formula. ZenPilot frequently creates custom fields for client tracking, project metadata, and profitability tags. We map each custom field type to the destination equivalent and handle value transformations for dropdown, rating, and formula fields. Field IDs change between workspaces so all references are remapped.

ZenPilot builds automations using ClickUp's automation engine for task routing, status updates, and notifications. We map automation rules including triggers, conditions, and actions. Complex nested conditions or automations referencing custom fields may require manual review post-migration to confirm the logic fires as intended in the destination system.

ClickUp Docs store process documentation, meeting notes, and project briefs. ZenPilot creates extensive Docs as part of their methodology. We migrate Doc content, formatting, and internal links intact. Embedded task or list references are re-pointed to the corresponding objects in the destination workspace.

All standard views—List, Board, Box, Table, Calendar, and Map—are migrated with their current column configurations and filter states. ZenPilot often curates specific views for different team roles, and we preserve those view presets including hidden columns and grouping preferences.

ClickUp's built-in time tracking captures duration entries linked to tasks. We preserve time entries including the associated task, assignee, and timestamps. Time tracking data is particularly important for ZenPilot clients using the Profitability Reporting add-on, so we ensure no hours are dropped during migration.

ClickUp Goals link targets to tasks, numerical goals, or custom metrics. ZenPilot sometimes uses Goals for OKR-style tracking within Growth or Delivery areas. Goal structures vary between source and destination ClickUp workspaces so we map the Goal hierarchy and re-link associated tasks. Numerical targets and progress percentages are transferred but recalculated based on current task data.

Dashboards are the most migration-sensitive ZenPilot artifact. ZenPilot's custom dashboards—including their proprietary Profitability Reporting module—connect widget configurations to specific task data and custom fields. We migrate the underlying widget data but dashboard layouts must typically be rebuilt in the destination with attention to the specific metrics the client is tracking.

Tags provide cross-cutting classification across tasks and lists. ZenPilot uses tags to label work by type, priority, or client. We preserve tag names and all tag assignments across all tasks. Tag colors and group assignments are also migrated.

ZenPilot's library of process templates—including recurring workflow patterns for new client onboarding, sprint cycles, and project delivery—reside in ClickUp as List or Folder templates. We identify all templates in the workspace and migrate them with their full structure intact, including pre-populated tasks, status schemes, and automation rules.