Migrate your Nifty data

Projects are the top-level workspace container in Nifty. We migrate all projects with their metadata (name, description, dates, status). Custom project-level properties are captured as key-value pairs via the custom fields API.

Tasks are the primary work unit in Nifty. We preserve task title, description, assignees, due dates, priority, status, and task-level custom fields. Task ordering within sections is maintained via sort position values.

Subtasks exist as nested children of tasks. We preserve the parent-child relationship, the subtask's own fields, and the sort order. Migration into flat-task systems splits subtasks into checklist items on the parent task.

Milestones are standalone objects that link to tasks. We migrate the milestone name, due date, status, and the list of associated tasks with their linking IDs intact. Goal-oriented milestones are treated as a milestone with a special tag property.

Discussions are project-level comment threads attached to tasks or standalone. We extract the full thread, author, timestamp, and any embedded file references. Target systems without a native discussion object receive these as task comments or notes.

Nifty Docs are rich-text documents stored per project. We export document content as formatted HTML or plain text with embedded images resolved as URLs. The target system's document structure (Notion-style blocks, Confluence pages, etc.) requires a content-mapping step.

Custom fields are defined per-project via GET /operation/fieldsapi_controller_getcustomfields and GET /operation/fieldsapi_controller_getcustomfield. Field types include text, number, date, and choice lists. We export both the field schema and all populated values for each project, then map them to equivalent destination custom fields.

Nifty tracks time on tasks via a built-in time tracking feature. We export logged duration, date, and user attribution. Time entries are mapped to the destination's native time tracking or recorded as a custom numeric property on the task.

Nifty stores file attachments on tasks and discussions. We extract the file URLs and metadata. Files themselves are downloaded and re-uploaded to the destination storage. Large media files may require the customer to provision adequate storage in the target system first.

Nifty organizes members by role (Admin, Member, Guest). We export all user profiles including email, name, and role. Guest accounts are flagged separately — they cannot be assigned tasks in Nifty and may need to be converted to full Member status or excluded from the migration depending on the destination.

Nifty Goals are high-level objectives that can be linked to milestones or tasks. We export the goal name, status, timeframe, and linked milestone/task references. Goals without a direct equivalent in the destination system are converted to a tagged milestone.

Nifty's automation engine uses conditional if/then rules to trigger status changes, assignments, or notifications. These rules are not exposed via the public API. We document the automation configuration during discovery and recreate equivalent rules in the destination system manually, as the automation logic itself cannot be programmatically extracted.

Portfolios aggregate multiple projects for executive-level reporting. We export portfolio membership (which projects belong to which portfolio) and basic portfolio metadata. Not all destination systems support a portfolio layer, so this may be represented as a tag or group on the projects themselves.