Migrate from Project Nucleus to Trello

Project Nucleus projects map to Trello boards with project name as board title, project description as board description, and project status (active, archived) mapped to Trello board visibility and archived-card inclusion. If a Project Nucleus workspace contains more than 10 projects and the destination is on Trello Free, we flag the workspace structure for restructure (split across multiple workspaces or upgrade to Standard) before migration begins.

Project Nucleus tasks map to Trello cards within the appropriate board. Task name becomes card title, description maps to card description, due date maps to card due date, and assignee maps to card member. Task ordering within its parent list is preserved. Project Nucleus status labels are mapped to Trello list names (e.g., To Do, In Progress, Done) or card labels depending on the customer's preferred workflow representation.

Project Nucleus sub-tasks map to Trello checklists within the parent card. Trello supports one level of checklists; deeply nested sub-task hierarchies (grandchild tasks and beyond) are flattened into a single checklist with indentation preserved as a prefix in the checklist item title (e.g., '-- [subtask name]'). Any checklist items exceeding Trello's 250-item per-checklist limit are split across multiple checklists on the same card.

Project Nucleus custom fields require the Trello Custom Fields Power-Up to be installed on each destination board before migration. Each project's custom field schema is extracted individually during scoping because fields are not globally standardized. Fields with unsupported Trello types (e.g., formula fields, multi-select with more than 100 options, date-range pickers) are flagged for manual mapping or simplification. We create the custom field definitions in Trello before card import and map values during the data transform phase.

Project Nucleus comments on tasks and projects migrate as Trello card comments with the original timestamp and author attribution preserved. Comment body migrates as plain text. Rich-text formatting (bold, links, code blocks) is simplified to plain text with URLs preserved as hyperlinks. Thread ordering is maintained by comment timestamp.

Project Nucleus attachments are stored as linked file references and migrate as Trello card attachments. Trello enforces a 10MB per-file limit. Any attachment exceeding 10MB is flagged for manual re-upload post-migration, and the card receives a comment indicating the pending re-upload with the original file name. All attachment URLs are re-validated post-migration to confirm accessible paths. We do not download and re-host files; we validate links and flag broken ones.

Project Nucleus team structures migrate as workspace members in Trello with board-level permission scoping. Project Nucleus team membership is preserved; team-level permissions are translated to board-level roles (Admin, Normal, Observer) based on the most permissive access the team member held. If a Project Nucleus team includes archived members, they are flagged for the customer admin to review rather than automatically added to the workspace.

Project Nucleus user records (name, email, role) map to Trello workspace members by email lookup. Duplicate or conflicting accounts in the destination workspace are flagged for the customer's admin to resolve. Inactive or archived Project Nucleus users are held in a review queue and not automatically provisioned in Trello.

Project Nucleus documents linked within projects are validated for accessibility post-migration. If documents are stored as URLs within Project Nucleus, they migrate as card attachments or links depending on accessibility. Documents stored as linked references without accessible paths are flagged for manual re-linkage in Trello.

Project Nucleus labels and tags migrate as Trello card labels with the original label name and color preserved where available. If the destination board has more labels than Trello's 50-label limit per board, labels exceeding the limit are merged or flagged for manual categorization.

Project Nucleus custom status labels vary by project and migrate as Trello list names (for workflow stages) or card labels (for categorical statuses). We capture the full status label set per project during scoping and decide with the customer whether statuses represent workflow stages or categorical flags. Complex status logic (conditional transitions, time-based status changes) is documented as a recommended Butler rule rather than migrated as code.

Time tracking in Project Nucleus maps to the Time Tracking Power-Up on Trello cards if installed, or to a custom field (e.g., Estimated Hours, Actual Hours) if no power-up is available. Project Nucleus configurations without time tracking are omitted from the mapping. Time entry data is migrated as numeric duration values rather than formatted time strings.