Migrate from Project Nucleus to Asana

Project Nucleus Projects map directly to Asana Projects as the top-level container. We preserve project metadata including name, description, status, start and due dates, and owner assignment. Project Nucleus does not have a documented Asana Portfolios equivalent; we create Asana Projects within a Team workspace and note the absence of portfolio-level rollup data for manual recreation post-migration.

Project Nucleus Tasks map to Asana Tasks with direct field mapping for name, description (migrated as Notes in Asana), assignee (resolved via User email mapping), due date, start date, and completion status. Task status in Project Nucleus uses custom labels per project; we preserve the original label as a text value in Asana Notes and flag any tasks where the Project Nucleus status has no direct Asana equivalent.

Project Nucleus Subtasks map to Asana Subtasks as child tasks within the parent Task. Project Nucleus allows flexible nesting depth per project configuration; Asana supports one level of subtasks natively. We flatten any deeply nested hierarchies (grandchild tasks and beyond) into sibling tasks under the parent and flag any that exceed Asana's nesting depth for the customer's admin to restructure as linked independent tasks.

Custom fields in Project Nucleus are defined per project, not globally. We extract the full custom field definition for each project during scoping, including field type, options list, and default value. Each distinct custom field schema becomes a separate Asana Custom Field created at the workspace level or project level depending on whether the customer wants it shared across projects. Fields with unsupported types (complex formulas, calculations) are flagged for manual handling; dropdown and text fields map directly.

Project Nucleus Teams map to Asana Teams as workspace containers for organizing members and projects. We preserve team membership by resolving Project Nucleus user references to Asana user accounts by email. Archived or inactive memberships in Project Nucleus are flagged for the customer's admin to review before migration, as Asana Teams do not support an archived membership status equivalent.

Project Nucleus User records map to Asana user accounts by email address as the dedupe key. We extract name, email, and role for each user. Any Project Nucleus users without matching Asana accounts go into a reconciliation queue for the customer's admin to provision before record import. Duplicate or conflicting accounts in the destination are flagged for resolution before migration begins.

Project Nucleus Comments on Tasks and Projects map to Asana Stories on the Task object. We preserve the full comment body, timestamp, and author attribution. Thread ordering is maintained by setting the Story created_at timestamp to the original Project Nucleus comment timestamp. Asana Stories do not support rich text formatting beyond basic markdown; we convert any rich text from Project Nucleus to plain text and flag any comments with embedded media for manual re-upload.

Project Nucleus Documents linked within projects require path re-validation after migration. We extract all document URLs during scoping, validate each URL resolves, and flag any that return 404 or access-denied responses for the customer's admin to re-upload or update. Valid document URLs are re-attached as links in the corresponding Asana Task description or as Attachments if the document is stored in a compatible cloud location.

Project Nucleus Attachments are stored as linked references with URLs. We validate all attachment URLs post-migration to confirm they resolve. Broken links are flagged for manual re-upload or re-linkage. Attachments that resolve successfully are re-attached to the corresponding Asana Task using Asana's asset upload API if the file is locally available, or as a link if the attachment URL points to an external system.

Project Nucleus time tracking data exists in some configurations but not universally. We extract time entries where present and map them to Asana's time tracking feature on Tasks. Asana Business and Enterprise tiers support native time tracking; Starter tier does not. If the destination is Asana Starter and time data is present, we preserve the data in a custom numeric field and note the limitation for the customer to decide whether upgrade or alternative tracking is needed.

Custom status labels in Project Nucleus vary by project. We preserve the status label as a text value and map it to an equivalent Asana status where possible (Not Started, In Progress, Complete). For statuses with no direct equivalent, we create a custom Asana field of type Text or Single-Select at the project level and preserve the original label. Status ordering is noted for manual recreation as Task Sections in Asana if the customer uses Sections for workflow visualization.

Project Nucleus Labels and Tags are migrated as Asana Tags. Where Project Nucleus uses a structured label system, we convert labels to Asana Tags by name. Asana Tags are workspace-level and can be applied across projects, which differs from Project Nucleus where label scope varies by project configuration. Any tags that cannot be matched to an existing Asana Tag are created during migration.