Migrate from Nostromo to Trello

Nostromo Projects map to Trello Boards, with the Workspace created at the top level to serve as an org container. If the customer's export contains a Workspace or Organisation field, we use that to create or select the destination Workspace; otherwise we create a single Workspace named after the customer's organisation. Each Nostromo Project becomes a Board with the original project name and description preserved in Board metadata.

Nostromo Tasks map directly to Trello Cards. We preserve the task name as the Card title, description as the Card description field, due dates as the Card due date, and priority or urgency flags as either Trello Labels or Custom Fields depending on the destination tier. The task's status field maps to the target List (e.g., To Do, In Progress, Done) in whichever List structure the customer configures in the destination Board.

Nostromo subtasks that are exported as child records of a parent Task are split into Trello Checklist items on the parent Card. Each subtask name becomes a checklist entry with a checkbox. We preserve the subtask's completion status and any assignee information as a note on the checklist item. If the customer's export treats subtasks as independent records with their own fields, we map the top-level ones to Cards and any deeper nesting to checklists on the parent Card.

Nostromo User records (email, display name, role) map to Trello Workspace Members invited to the destination Board. We resolve by email match. Role information from Nostromo (admin, member, viewer) is preserved as a custom field or label on the Board for admin reference. Any Nostromo user without an email in the export is flagged in the scope document for the customer to resolve.

If the customer's Nostromo export includes Sprint records with start date, end date, and assigned task IDs, we map Sprint to either a dedicated List (named with the sprint name and date range) or to a Custom Field of type Date if the customer has the Custom Fields Power-Up. The customer chooses the strategy during scoping. Without explicit sprint records in the export, we fall back to date-based grouping of Cards by due date.

Nostromo Comments migrate as Card descriptions or as a chronological comment log appended to the Card description. Authorship (commenter name and timestamp) is preserved in a formatted header above each comment. Trello does not have a native comment object in its REST API outside of Actions, so we embed the comment history in the Card description with clear attribution so it is readable without requiring a separate review tool.

Nostromo Labels and Tags migrate to Trello Labels with colour mapping where the export contains colour data. We deduplicate and normalise the label set during mapping. Label names are preserved as the Trello Label name; if the destination Board has an existing label with the same name, we use the existing label rather than creating a duplicate.

Typed Nostromo custom fields (text, number, date, dropdown, checkbox) map to Trello Custom Fields Power-Up on the Standard or Premium tier. Free-tier destinations map typed custom fields to Labels or to the Card description as structured text. We confirm the destination Trello tier during scoping because the Custom Fields Power-Up requires a paid workspace plan.

Nostromo did not expose file attachments through its public export mechanism. Binary files (images, documents, uploaded assets) associated with tasks or projects are not recoverable from the archived export format. We flag this gap in the scope document and recommend that the customer re-attaches critical files manually post-migration or retrieves them from a separate backup source if one exists.

Automations, workflow rules, or triggers configured in Nostromo during its active period do not have a documented export format and cannot be reverse-engineered from archived data. We do not migrate them as code. We deliver a written inventory of any detected automation logic (trigger conditions, actions, recipients) inferred from the export's data patterns, and the customer rebuilds these in Trello's Butler or in a third-party automation tool post-migration.

If the customer's Nostromo export contains nested projects (projects within projects), we map the top-level project to a Board and any sub-projects to either additional Boards within the same Workspace or to Lists within the parent Board, depending on the customer's preference and the depth of nesting. We document the inferred hierarchy in the scope document and the customer selects the flattening strategy before migration begins.

Task created dates, last modified dates, and any completed-date fields from the Nostromo export migrate to Trello Card createdAt and due dates where applicable. Trello Cards do not expose a native last-modified timestamp in the REST API, but we set the Card creation date to the original Nostromo task creation date for historical record preservation. Closed or completed task status is inferred from the target List position rather than a separate field.