Migrate from Nostromo to monday Work Management

Nostromo Projects map to monday.com Boards. Each Board is created at the Workspace level with a name and description derived from the exported project record. If the customer's export includes project-level metadata (start date, deadline, status), we create a Board with those values reflected in the Board settings and a reference group. Boards are created before any Items load to satisfy referential integrity.

Nostromo Task records map to monday.com Items within the corresponding Board. Task title becomes the Item name. The task description, priority, due date, and status migrate as typed Columns (Text, Status, Date) matching the source field names where the export preserves them. We create the Board columns first based on the inferred field types, then load Items in batches.

Nostromo's parent-child subtask hierarchy maps to monday.com Subitems. The Subitems feature must be enabled on the destination Board before load; it is available from the Standard plan. We preserve the parent reference by linking each Subitem to its parent Item using monday.com's Subitem API relationship. Ordering within the Subitem list follows the sequence number or index field if the export contains one.

Nostromo User records map to monday.com People column values. We resolve each User by email address against the destination monday.com workspace members. Any User in the Nostromo export without a matching monday.com account is flagged in the scope document and held in a reconciliation queue for the customer to provision accounts before Item loading begins. Role data from the export is stored in a Text column for reference.

Nostromo custom field definitions and values map to monday.com Column types based on the inferred data type in the export. Text fields become Text or Long Text columns. Numeric fields become Numbers columns. Date fields become Date columns. Multi-select or tag fields become Labels columns. We preserve the original field name as the Column title. Because Nostromo did not publish a documented schema, column type inference is based on the actual data values in the customer's export file.

If the customer's export includes explicit Sprint records with start and end dates, we map them to monday.com Groups within the Board. Group naming follows the Sprint name. Tasks belonging to that Sprint are assigned to the Group by matching the task-sprint relationship in the export. If the export does not contain sprint data, we fall back to date-based grouping or a default group named 'Imported Tasks'.

Nostromo Labels and Tags migrate as monday.com Tags on the Items they were assigned to. Tags are created at the Workspace level for reuse across Boards. We deduplicate the label set during transformation and normalise the tag names to lowercase. The tag relationship is resolved at Item load time using the export's item-label association data.

Nostromo Comments migrate as monday.com Updates on the relevant Items. Authorship (display name and email) and timestamp are preserved from the export. Updates are loaded after Items to ensure the Item IDs exist as parents. Long comment threads are posted in reverse chronological order to maintain the discussion flow. Rich text in comments is preserved as plain text in the Update body.

Nostromo did not expose file attachments through its public export mechanisms. Binary files (images, documents, uploaded assets) associated with tasks or projects are not recoverable from the archived backup format. We document this gap in the scope document and recommend re-attaching files post-migration using monday.com's native file upload feature or connected cloud storage integration.

Created date, last modified date, and any historical milestone dates in the Nostromo export migrate as Date column values or Timeline column ranges on the corresponding Items. We preserve the original timestamps as entered in Nostromo rather than the export date. If the export uses epoch timestamps, we convert to ISO 8601 format before loading.

We create a dedicated monday.com Workspace for the migrated Nostromo data, named after the customer's Nostromo workspace or organisation name from the export. Within the Workspace, each Board corresponds to a Nostromo Project. The Workspace is created before any Board or Item migration begins. If the customer already has an existing monday.com account with Workspaces, we discuss the appropriate target Workspace during scoping.

Because Nostromo did not publish a public data dictionary or migration guide, every migration requires an initial schema-inference pass over the customer's specific export file. We parse the top-level object types, identify field names and inferred data types, and build a custom mapping for that export format before any load begins. Different backup tools or export methods may produce different structures; the mapping is always export-specific.