Migrate from Nostromo to Asana

Nostromo Projects map to an Asana Team (the organizational unit) plus a Project within that Team. If the customer's export contains multiple Projects, we create corresponding Asana Teams per Project or group them under a single Team depending on the export's scope. Team privacy settings inherit from the Asana organization's default unless the customer specifies otherwise during scoping.

Nostromo Tasks map to Asana Tasks. Parent-child relationships from the export are reconstructed: we identify a parent_id or equivalent column, resolve the parent Nostromo Task GID to its Asana GID after the initial insert, then update each child Task with the Asana parent reference. Without a parent_id column in the export, flat task lists insert without hierarchy and the customer decides whether to reconstruct subtasks manually or via Asana's bulk-edit capabilities.

Nostromo User records (email, display name, role) map to Asana Workspace or Organization Members. We match by email address. Any Nostromo User not found in the Asana destination is flagged in a reconciliation report for the customer's admin to provision before migration resumes. Role data maps to Asana member status (full member vs guest) depending on what role fields the export contains.

If the customer's export includes explicit Sprint records with start_date and end_date columns, we map these to Asana Sections (named by sprint label) or to date-based custom fields on Tasks. Without an explicit sprint record, we fall back to grouping Tasks by a due_date range or a custom sprint_identifier field inferred from the export structure. Asana does not have a native sprint object; sprint tracking is handled through workspace configuration or the Goals product on Business and Enterprise tiers.

Nostromo custom properties map to Asana Custom Fields. We infer the field type from the export data (text, number, date, enum) and pre-create the field in the destination Asana Project or Organization before inserting records. Asana supports global custom fields from Starter tier and above; local project-level fields are also supported. Enum fields require a choices array which we populate from the distinct values in the export column.

Nostromo Labels and Tags migrate to Asana Tags. We deduplicate the label set during mapping and normalize casing. Tags in Asana are per-project unless promoted to a global tag library at the Organization level. The customer's admin chooses whether migrated labels become local project tags or org-wide tags during scoping.

If the customer's export includes comment records with body text, author email, and timestamp, these migrate as Asana Comments on the relevant Task. Author attribution maps by email to the corresponding Asana Member. Note that Asana's API does not permit creating comments on behalf of other users; comments are posted under the migration account with the original author noted in the comment body text.

Nostromo did not expose file attachments through its documented export mechanisms. Any images, documents, or uploaded assets associated with Tasks or Projects are not recoverable from the archived backup format. We flag this gap in the scope document and recommend the customer re-attach any recoverable files manually post-migration if local copies exist outside the platform.

Nostromo automations and workflows do not migrate. We deliver a written inventory of every identified automation in the export (trigger conditions, actions, and configured rules) with a recommended Asana Rules equivalent so the customer's admin can rebuild them post-migration. Asana Rules run from Starter tier and above with trigger-based and scheduled variants.

If the export contains created_at, updated_at, or last_modified timestamps on Tasks, these migrate to Asana Task created_at, modified_at, and completed_at fields where the API supports them. Start date and due date from Nostromo map directly to Asana start and due date fields. Historical engagement records (calls, emails, meetings) are not recoverable from Nostromo's export format since they were not exposed as distinct objects in the documented backup mechanism.

If the Nostromo export contains story points, time estimates, or hour-tracking fields, these migrate to Asana as a number-type custom field named to match the original field label. Asana's native time tracking requires the Time Tracking add-on on Business and Enterprise tiers; we configure this during scoping if the customer's workflow depends on it.

Nostromo task status values (e.g., To Do, In Progress, Done) map to Asana Sections within a Project for visual grouping, or to a custom multi-select field for filtering across projects. The mapping choice is made during scoping based on how the customer used status in Nostromo and how they plan to use Asana's views.