Migrate from Nozbe to monday Work Management

Each Nozbe Project maps to a monday.com Board. Project name becomes Board name, and Project visibility settings (team-wide or member-limited) map to Board sharing settings in monday.com. If the customer uses Nozbe Business Spaces to group multiple projects, we create a monday.com Workspace as the parent container with separate Boards for each Project. The Board structure (group layout, default columns) is designed during scoping to match the customer's workflow.

Nozbe Tasks map directly to monday.com Items. Task name becomes Item name, due date maps to a Date column, priority maps to a Status or Labels column (customer chooses during scoping), assignee maps to the People column, and Done status maps to the Status column with a Done group. Task description migrates to the Item's Text column or Description field. The parent Project-Group relationship is resolved by creating a Group in monday.com per task list within a Project, or by placing items directly in the Board for single-list Projects.

Nozbe Comments are threaded under Tasks and represent the primary communication mechanism. We map them to monday.com Item Updates (the @mention-aware conversation thread). Author, timestamp, and @mentions are preserved. If the customer uses comments for structured status updates (e.g., daily standup notes), we may map these to a separate Text column per item rather than updates to keep the board view clean.

Nozbe Tags are a flat workspace-level list with no hierarchy. They are not included in the Nozbe Classic JSON export, so we scrape the workspace tag list from the Nozbe web interface during scoping if the customer grants read access. Tags migrate to monday.com Tags (workspace-level, queryable across boards) if the customer prefers global tagging, or to a Labels column on the Board if they prefer per-board categorization. The customer chooses the strategy during scoping. If the tag list is unavailable, we recreate tags as a Labels column derived from task metadata.

Nozbe Categories (GTD context labels like @calls, @home) are distinct from Tags and appear in the left sidebar. They are not included in the Classic export. We extract the Category list from the Nozbe UI during scoping and map Categories to a monday.com Labels column on the Board, allowing items to be filtered by context across the board. If multiple Categories apply to a single task, the Labels column supports multi-select.

Files attached to Nozbe Tasks are extracted from the Classic JSON backup zip. We transfer attachment URLs and re-attach them as links in a Link/URL column in monday.com. For attachments hosted in Nozbe's cloud storage, we download and re-upload to monday.com's file storage. If a file exceeds monday.com's storage limits on the customer's plan, we store a link back to the original file location in Nozbe (until the customer migrates away entirely). New Nozbe does not expose attachments via API; the Classic export is the only path.

Nozbe stores recurrence as a rule on a Task object (daily, weekly, monthly, custom). Monday.com does not have a native per-item recurrence object; instead, it uses automations triggered by date columns to create new items or update existing ones. We offer two strategies during scoping: (1) Expand recurrence into a series of individual Items with explicit due dates, preserving the full calendar in monday.com. This can inflate task counts dramatically — biweekly for 3 years becomes 78 items. (2) Store the recurrence rule in a Text column (e.g., 'RRULE:FREQ=WEEKLY;INTERVAL=2') as an annotation and document the monday.com automation recipe to reproduce the pattern. The customer chooses per-project or globally.

Nozbe Tasks carry a Priority flag (High, Medium, Low, or numeric 1-10). We map this to a monday.com Status column with matching priority values, or to a numeric Priority column if the customer prefers a 1-10 scale. Status columns offer color coding and grouping that Priority columns do not, so we default to Status unless the customer specifies otherwise.

Nozbe due dates map to a monday.com Date column. If a task has both a start date and due date in Nozbe (available on Premium), we map to the Timeline column in monday.com to preserve the full date range. Time-of-day information is dropped since monday.com Date columns are date-only by default; if time is critical, we use a separate Text column for the time component.

Nozbe Team Members are users in a workspace with roles (admin, member). We map Members to monday.com Users by email address. The customer provisions monday.com seats before migration; we match by email and flag any Nozbe member without a corresponding monday.com user for admin action before record import.

Nozbe Business Spaces (Premium/Enterprise organizational units) map to monday.com Workspaces. Each Business Space becomes a separate monday.com Workspace containing Boards for the Projects within that space. If the customer has a flat project structure with no Business Spaces, we create a single monday.com Workspace.

Nozbe's Inbox is a GTD capture zone and has no direct equivalent in monday.com. We do not migrate Inbox items as a separate object type. Instead, we offer two options: (1) Create an 'Inbox' group on the primary Board and migrate all Inbox items as Items in that group with a 'Source: Inbox' label column. (2) Skip Inbox migration entirely if the customer prefers to treat Inbox as ephemeral capture that does not need to persist. The customer chooses during scoping.