Migrate from Nifty to Microsoft Project

Nifty Projects map to Microsoft Project plans. The project name, description, start date, and target end date migrate as the MPP file or Project Online project properties. Project-level status (Active, Completed, Archived) maps to a custom Project Status field in Microsoft Project since the platform uses the project plan state rather than a discrete status property.

Nifty Tasks map directly to Microsoft Project Tasks. Task name, description, Start Date, Due Date, Priority (Low/Medium/High/Critical), and Status (To Do/In Progress/Complete) migrate. Nifty's Priority mapping to Microsoft Project Priority field (1-10 scale) uses a transform: Critical=10, High=7, Medium=4, Low=1. Task-level custom fields migrate to Microsoft Project custom fields (up to 10 per project, enforced by the destination).

Nifty Subtasks map to Microsoft Project Tasks indented under the parent Task as Summary Tasks. The outline level and WBS code preserve the Nifty parent-child relationship. In Project for the web or Project Online, subtasks render as checklist items or subtasks within the parent task. We set Duration=1d for subtasks where Nifty did not record a duration and link them to the parent Task ID.

Nifty Milestones map to Microsoft Project Tasks with Duration=0 and the Milestone flag set to Yes. The milestone name and due date migrate as the task name and Finish date. Nifty's milestone-to-task linkages migrate as predecessor-successor relationships in Microsoft Project: each task linked to a milestone in Nifty receives a Finish-to-Start dependency to the milestone task. We resolve the dependency graph during transformation before inserting into the destination.

Nifty Discussions are project-level and task-level comment threads. Microsoft Project has no native discussion or comment thread feature. We extract the full thread content, author, timestamp, and parent task reference and deliver it as a structured CSV and Markdown documentation package. The customer's admin decides whether to paste discussion summaries into task Notes fields or archive them externally.

Nifty Docs are rich-text documents per project. Microsoft Project (desktop and cloud) has no native document management. We export document content as HTML or plain text and deliver a file package. Embedded images are extracted as separate files with relative URL references. The customer's admin uploads documents to SharePoint or a document management system and links them from the project plan.

Nifty custom fields are defined per-project. Microsoft Project limits custom fields to 10 per project (Text1-Text30, Number1-Number20, Date1-Date10, Flag1-Flag20, OutlineCode1-OutlineCode10). We deduplicate Nifty custom field definitions across projects during scoping: same-named fields with matching types become one destination custom field; same-named fields with conflicting types are renamed with a project suffix. Field type mapping: Nifty Dropdown and User fields map to Outline Code or Text fields in Microsoft Project; Nifty Date fields map to Date fields; Nifty Number fields map to Number fields.

Nifty time tracking entries (duration, date, user attribution) have no native Microsoft Project equivalent in most editions. We export time entries as a structured CSV keyed to the parent task name and date range. For organizations that need the data inside the schedule, we create a custom Number field (TimeHours__c) per task and populate it with the sum of logged time for that task. A separate Timesheet CSV is delivered as a reference for external payroll or billing integration.

Nifty Members map to Microsoft Project Resources. We extract member name, email, and role (Admin/Member). Nifty's role concept maps to Resource Notes or a custom Resource field in Microsoft Project. Guest accounts (read-only in Nifty) require explicit scoping decision: either map them as Resources with zero max units or document them separately since Microsoft Project has no guest-tier equivalent and requires a full license for access.

Nifty Goals are high-level objectives that link milestones or tasks. Microsoft Project has no Goal object. We map Goals to Summary Tasks at the top of the WBS with a custom Goal field set to the goal name. Linked milestone and task IDs are preserved as task Notes. The customer's admin reviews goal alignment post-migration.

Nifty Portfolios aggregate multiple projects for executive reporting. Microsoft Project does not have a native portfolio object. We export portfolio membership (which projects belong to which portfolio) and deliver it as a portfolio mapping CSV. If the destination is Project Online, we recommend organizing projects within SharePoint sites or using Project for the web's grouping features to approximate portfolio visibility.