Migrate from Nifty to Trello

Nifty Projects map directly to Trello Boards as the top-level workspace container. We preserve the project name as the board name, project description as the board description, project start and end dates as custom date fields on the board, and project status (active, archived) as the board state. Nifty's project-level custom properties migrate as Trello Custom Fields on the board's cards. The board URL is stored for reference. We do not migrate Nifty's Portfolio grouping (multiple projects aggregated for executive reporting) — these are documented as board-grouping recommendations post-migration.

Nifty Tasks map to Trello Cards within the appropriate Board List. We preserve task title as Card name, task description as Card description (rich text converted to plain text or markdown), task status (To Do, In Progress, Done) mapped to the target List position or Label, assignees as Card members, due date as Card due date, priority (Low, Medium, High, Urgent) as Trello Labels or priority Labels, and task ordering within sections via List position. Task URLs are preserved as a custom field for audit traceability.

Nifty Subtasks are first-class objects with their own fields, assignees, and ordering nested under a parent Task. Trello Cards do not have independent subtask objects — they use Checklist items which are text-only and owned by the parent Card. We convert all Nifty Subtasks to Trello Checklist items on the migrated Card, preserving the subtask title and completion status (checked/unchecked). Subtask assignees cannot map to Trello because Checklist items have no member field — the parent Card retains the member assignment. If the customer needs independent subtask assignment tracking, we recommend using linked Cards via the Card-Linker Power-Up or a separate Board for sub-items.

Nifty Milestones are standalone objects with a name, due date, status (On Track, At Risk, Off Track, Complete), and a linked list of associated Tasks. Trello has no native Milestone object. We re-implement Milestones as follows: the milestone name becomes a Card in a dedicated Milestones List on the Board with the milestone due date set as the Card due date; the milestone status maps to a colored Label (Green = On Track/Complete, Yellow = At Risk, Red = Off Track); and the milestone's linked tasks are referenced as a Checklist on that Card or as a custom field linking back to their respective Cards. Teams with many milestones may instead use Trello Labels with date-based filtering as a milestone proxy. The chosen strategy is decided during discovery.

Nifty Discussions are project-level or task-level comment threads with author, timestamp, and embedded file references. Trello Cards have a native comment system with author, timestamp, and @mention capability. We extract each Discussion thread as a sequential set of Card comments, with the thread author and timestamp preserved. If a Discussion was attached to a standalone topic (not a specific task), we create a dedicated Card in a Discussions List to serve as the comment thread container. File references in discussions are preserved as links in the comment body if the file URL is accessible.

Nifty Custom Fields are defined per-project via GET /operation/fieldsapi_controller_getcustomfields and per-task via GET /operation/fieldsapi_controller_getcustomfield. A field named 'Client Name' in Project A may be a different type or set of options than 'Client Name' in Project B. We deduplicate and consolidate all custom field definitions across the workspace: same-named fields with consistent type and option sets collapse into one Custom Field definition per Trello Board; same-named fields with conflicting types or options are disambiguated with a project-prefix (e.g., ProjectA_ClientName vs ProjectB_ClientName). Field types (text, number, date, dropdown, checkbox) map to Trello's Custom Fields Power-Up supported types. Custom fields are applied per-board, not globally across the Workspace.

Nifty Docs are rich-text documents stored per project. We export document content as formatted HTML with embedded images resolved as URLs. Trello Cards have no native document repository — Docs are mapped to Card descriptions (if short and task-specific) or attached as files (if longer or standalone). For projects with many Docs, we deliver a written inventory mapping each Doc to a recommended Card, external link, or Confluence space (if the customer uses Atlassian) post-migration. Nifty Wiki pages follow the same mapping path as Docs.

Nifty's built-in time tracking logs duration, date, and user attribution per task. Trello has no native time tracking. We export the total logged time per task and write it to a Trello Custom Field (number type showing hours) on the Card. If granular time entries (multiple sessions per task) are required, we create a Checklist on the Card with each entry as a checklist item formatted as 'Date — Duration — User'. The customer should be advised that Trello does not natively track billable time; Trello Time Tracking Power-Up or a third-party integration (e.g., Toggl, Harvest) is recommended for ongoing time capture post-migration.

Nifty Goals are high-level objectives linked to milestones or tasks with name, status (On Track, At Risk, Off Track), timeframe, and linked task/milestone references. Trello has no native Goals object. We re-implement Goals as either a dedicated Goals Board (one Card per Goal, with linked task Cards referenced via Checklist or Card Linker Power-Up) or as colored Labels on existing Cards combined with a Goals overview Card in a dedicated list. The chosen structure depends on Goal count and whether the customer wants cross-board Goal visibility. Goals without linked milestones are documented in the Goals inventory for manual categorization.

Nifty Members (Admin, Member roles) map to Trello Workspace Members by email match. Nifty Guests — who cannot be assigned tasks or modify milestones in Nifty — are flagged separately. If the destination Trello Workspace is on the Free or Standard plan, all migrated users become normal Workspace Members. If the destination is Business Class or Enterprise, Nifty Guests can map to Trello Guests with full task-level write access, which is an improvement over Nifty's Guest restrictions. The customer's admin configures the Trello Workspace member roles (normal, admin) before migration begins.

Nifty stores file attachments on tasks and discussions. We extract the file URLs and metadata (filename, file type, upload date, uploader). Files themselves are downloaded from Nifty and re-uploaded as Trello Card attachments. Large media files (images, videos, PDFs) transfer directly. Files attached to Discussions migrate as attachments on the target Card or the standalone Discussion Card. Trello's per-board attachment limits apply (10MB on Free, higher on paid plans) — we alert the customer during discovery if any attachments exceed Trello's size limits.

Nifty's if/then automation rules (triggering status changes, assignments, or notifications based on conditions) are not exposed through the developer API and cannot be extracted programmatically. We document every active automation rule during discovery — the customer walks through each rule, and we capture the trigger, conditions, and actions in a written automation inventory. The handoff document maps each Nifty rule to a recommended Butler action or Power-Up automation (e.g., Trello's native Butler, or the Automation Power-Up) with step-by-step rebuild instructions. This is a manual post-migration step performed by the customer's admin.