Migrate from Project Nucleus to Microsoft Project

Project Nucleus Projects map directly to Microsoft Project plans. Project metadata including name, description, status, start date, end date, owner, and creation timestamp migrate intact. We import via CSV orMPP file format into Project desktop or Project for the web depending on the destination license. Archived or completed projects migrate with status preserved; active projects are migrated first and validated before archived records are processed.

Tasks inherit parent project context and include name, description, status, assignees, due dates, and priority. We preserve task ordering and hierarchy, mapping the Project Nucleus task order to the Microsoft Project task sequence. Start and finish dates migrate directly; if Project Nucleus uses a different working-hours default, we apply a task-calendar mapping during transform to prevent scheduling drift.

Project Nucleus sub-task hierarchy maps to Microsoft Project outline indentation. The nesting depth migrates as-is up to the outline depth the destination plan supports. We flatten hierarchies that exceed the destination plan's recommended depth and flag any subtasks that lose parent context. Milestone tasks in Project Nucleus map to Microsoft Project milestone tasks (duration of zero with the milestone diamond marker).

Project Nucleus custom fields are defined per-project and map to Microsoft Project task, resource, or project-level custom fields. We extract the full custom field definition for each Project Nucleus project during scoping, including field name, type, and options. Fields with types unsupported by Microsoft Project (for example, formula fields or linked-record fields) are flagged for manual handling. Microsoft Project supports up to 10 custom fields per category; projects with more than 10 custom fields require prioritization.

Project Nucleus attachments are linked file references. We validate all attachment URLs post-migration to confirm they resolve. Broken links are flagged for manual re-upload to the destination SharePoint or OneDrive location and re-linkage to the corresponding task. Documents that are migrated to Microsoft Project via SharePoint integration are attached using the Documents tab on the plan.

Project Nucleus team structures and memberships map to Microsoft Project resource pools and resource groups. Each Project Nucleus team becomes a resource group in the destination plan, with team members added as resource records. We merge members who belong to multiple Project Nucleus teams into the corresponding multiple resource groups in Microsoft Project. Archived or inactive memberships are flagged for manual review.

Project Nucleus user records include name, email, and role. We match users by email for de-duplication and map each user to a corresponding resource in Microsoft Project. The customer chooses during scoping whether to assign resources as named (person) or generic (role-based) resources; this affects resource leveling behavior in the destination plan.

Comments on tasks and projects in Project Nucleus are appended to the corresponding Microsoft Project task notes field with a formatted header including the comment author and timestamp. Thread ordering is preserved. For tasks with more than 20 comments, we summarize into a single annotated notes block to avoid exceeding the notes field length limits.

Documents linked within Project Nucleus projects require SharePoint path validation. We confirm document accessibility post-migration and flag any documents that cannot be reached through original paths. If the destination Microsoft Project plan is connected to a SharePoint site, we re-link documents to the appropriate document library and list. Unreachable documents are flagged for manual re-upload.

Time tracking data exists in some Project Nucleus configurations but not universally. We extract what is present and map it to Microsoft Project task assignment fields (Assignment Notes) or as a custom task number field with the time entry value. Microsoft Project Plan 3 does not include a native timesheet object; teams requiring timesheet functionality typically use Microsoft Project Online with Project Service or integrate with a third-party timesheet tool post-migration.

Custom status labels in Project Nucleus vary by project configuration. We preserve the status label text and map it to the closest equivalent Microsoft Project task status (Not Started, In Progress, Completed, On Hold, Cancelled). Where no direct equivalent exists, we preserve the original label in a custom text field and flag for manual status workflow configuration.

Labels and tags in Project Nucleus migrate as text annotations appended to the task notes field or as a custom text field carrying the label value. Microsoft Project does not have a native tag or label object; if the destination plan uses a structured categorization system, we convert labels into the appropriate custom field values and flag any labels that require manual categorization after migration.