Migrate from Nifty to Asana

Nifty Projects map directly to Asana Projects. We preserve project name, description, start date, due date, and status. Nifty project-level properties (not custom fields) map to task-level fields or project notes. If the Nifty project was created in a Portfolio, we create a corresponding Asana Portfolio and add the migrated project to it post-import. Projects without a Nifty Portfolio association are created as standalone Asana projects under the destination Team.

Nifty Tasks map to Asana Tasks with title, description (as rich text), assignees, due date, start date, priority, and status preserved. Nifty's task-level custom fields map to Asana project-level or global custom fields. Assignee resolution is done by email match against Asana workspace members; unresolved assignees are flagged in the reconciliation report.

Nifty Subtasks map to Asana Subtasks under the parent Task. The parent-child relationship is preserved via the subtasks relationship field in Asana's API. If Nifty subtasks have their own subtasks (nested deeper than one level), we flatten the deeper hierarchy into checklist items or child subtasks and note the flattening in the reconciliation report. Nifty does not enforce a hard subtask depth limit, but Asana Subtasks are a single-level construct.

Nifty task Sections (grouped task lists within a project) map to Asana Sections within the project. The section name and task ordering within section are preserved. We create sections in the same sequence as the Nifty project and assign tasks to sections during import.

Nifty Milestones map to Asana Milestones attached to the parent Project. The milestone name, due date, and status transfer directly. Nifty milestones linked to specific tasks maintain the association through a task-level custom field or note referencing the linked task's Asana GID. Milestones without a linked project are attached to the nearest migrated project during reconciliation.

Nifty Goals (name, status, timeframe, linked milestones and tasks) do not have a native equivalent in Asana. Asana's Goals feature is available in Business and Enterprise tiers and operates as a lightweight objective tracker rather than a structured Goal object with its own timeline fields. We export Goal metadata and the list of linked tasks and milestones, then deliver a written handoff document specifying which Asana Portfolio or Workload view the Goal maps to. The customer's admin rebuilds the Goal structure in Asana Goals or as a portfolio-level tracking board.

Nifty Discussions are project-level comment threads that can be attached to tasks or standalone. We extract the full thread content, author, timestamp, and any embedded file references. Each Discussion thread becomes a comment on the migrated task it was attached to in Nifty. Standalone Discussions (not linked to a specific task) are attached to the nearest migrated project as a task note or converted to a task with a comment thread. Author attribution migrates by email match.

Nifty Docs (rich-text project documents) are exported as HTML or formatted plain text. For short documents (under 4,000 characters), we insert the content into the Asana project description field or a designated task description. For longer documents, we upload the formatted content as an attachment (HTML or PDF) to the migrated project or an overview task, and note the document in the handoff document for the customer's admin to re-create in their preferred documentation tool (Notion, Confluence, or Google Docs).

Nifty custom fields are defined per-project via the custom fields API endpoints. We deduplicate field names across all projects: if 'Client Name' exists in Project A and Project B with the same type, we consolidate into a single Asana custom field. If the same name has different types across projects, we append a numeric suffix to the Asana field name and flag the conflict for the customer to resolve. Field types (text, number, date, choice) map to Asana's corresponding custom field types. Nifty multi-select choices map to Asana multi-select custom fields.

Nifty time entries (duration, date, user attribution, task association) are exported and attached to the migrated task as a formatted note in the task description or as a custom field (Time Logged) capturing the duration. Asana does not have a native time tracking object in its core PM tiers. If the customer requires time tracking in Asana, we recommend enabling Asana's native time tracking (available in Business tier) or migrating to a third-party integration (Toggl, Harvest) post-migration. We do not implement third-party integrations as part of the standard migration scope.

Nifty file attachments on tasks and discussions are downloaded from the file URLs provided in the API response and re-uploaded to the corresponding Asana task as an Attachment. Files over 100MB require the customer to host externally and link via URL attachment, since Asana's API does not support attachments exceeding 100MB. We flag files exceeding this threshold in the scoping phase. Image attachments embedded in task descriptions are extracted and re-uploaded separately.

Nifty Members (Admin, Member roles) map to Asana workspace members by email address. We create a user mapping table and resolve each Nifty user to an Asana User GID before importing any record with an OwnerId or assignee field. Nifty Guest accounts are flagged separately: Asana treats guests as full members with seat billing on some tiers, so we confirm guest seat availability with the customer before mapping. Any Nifty user without a matching Asana account is held in a provisioning queue.

Nifty Guests are read-only collaborators who cannot be assigned tasks, delete tasks, or adjust milestones. Asana Guest seats allow task assignment but are billed per seat on Professional and Business tiers. We flag all Nifty Guest accounts during discovery and confirm whether each guest should become an Asana Member (full collaborator) or Guest (limited access). If Nifty guests were used as lightweight external reviewers, the customer decides on Asana guest seat licensing during scoping. Guest-to-member conversion happens before migration if write access is needed.

Nifty Portfolios aggregate multiple projects for executive-level reporting. We export portfolio membership (which projects belong to which portfolio) and basic portfolio metadata. Asana Portfolios provide the same cross-project overview with portfolio-level progress metrics. Each Nifty Portfolio becomes an Asana Portfolio, and we add the migrated Asana projects to the corresponding portfolio post-import. If the customer uses Nifty Portfolios with custom portfolio-level fields, we create equivalent custom fields in Asana Portfolio.

Nifty if/then automation rules are not exposed through the developer API and cannot be extracted programmatically. During discovery, we ask the customer to walk through their active automation rules and document the trigger conditions, action types, and affected project or task filters. We deliver a written inventory of every automation with its logic and a recommended Asana Rules equivalent. The customer's admin rebuilds the rules in Asana Rules (Premium and above) post-migration. This is a manual step, not an automated migration.