Migrate from Nozbe to Trello

Each Nozbe Project maps to a Trello Board. We preserve the Project name as the Board title, the project description as the Board description, and the visibility setting (team-wide vs. member-limited) as the Board's permission level (Private vs. Workspace). If the customer uses Nozbe Business Spaces, we create a separate Trello Workspace per Business Space and nest Boards inside. Board creation runs before any List or Card creation because Lists require a Board ID reference.

Nozbe Tasks map to Trello Cards within a Board. The task name becomes the Card title, the task description becomes the Card description (stored as plain text or Markdown), and the Done/undone state becomes the Card's List position or a Label flag. Due dates migrate to Trello due dates. Assignees migrate as Card members. We set the destination List based on the task's Done status: completed tasks go to a List named Done or Archive; open tasks go to a configurable default List (typically To Do or In Progress).

Nozbe Comments on Tasks migrate as Trello Card Comments. We preserve author, timestamp, and @mention content. If the destination Trello workspace uses the Free plan (which limits some Power-Up features), comments remain as native Card Comments which are visible in the Card's Activity section. Chronological ordering is preserved by setting the comment timestamp at insert time via the Trello REST API.

Nozbe Categories (GTD @context labels like @calls, @home, @office) map to Trello Labels on each Card. Since Trello Labels are Board-scoped, we create a standard set of Labels per Board that mirrors the Nozbe Category list. We work with the customer during scoping to assign Label colours that match their existing Nozbe Category colour coding. If Nozbe Categories are not present in the JSON export (which is a known export limitation), we scrape the workspace Category list from the Nozbe web interface during scoping and recreate it as Labels.

Nozbe Tags are a flat workspace-level label list distinct from Categories. We merge Tags and Categories into a single Label set per Trello Board during migration, deduplicating any overlap. Tags stored on tasks with no matching Label are created as new Labels. If the tag list is unavailable from the export or web interface, we extract unique tag strings from task data and generate Labels from those.

Nozbe Tasks carry a Priority flag (1-3 or custom). Trello has no native priority field, so we convert Priority to a Label. We agree on a colour scheme during scoping: Priority 1 (Critical) becomes a red Label, Priority 2 (High) becomes an orange Label, Priority 3 (Normal) is unlabelled or a green Label. The customer approves the mapping before migration runs.

Nozbe stores recurrence as a rule on a Task. Trello does not have a native recurrence model. We offer two migration paths: for simple recurrence patterns (daily, weekly, monthly), we expand the recurrence into individual Cards with sequential due dates, placing each instance on the correct List based on its completion status at migration time; for complex patterns (biweekly for 3+ years, custom skip patterns), we store the recurrence rule as a Card comment field (Recurrence: RRULE or human-readable description) and recommend rebuilding via Trello Butler post-migration. We flag the task count impact during scoping so the customer chooses before migration begins.

Nozbe file attachments on Tasks migrate as Trello Card Attachments. We extract attachment URLs from the Nozbe JSON export, download the files to a staging environment, and re-upload to Trello via the Card attachments endpoint. Attachment author, filename, and MIME type are preserved. If files are hosted inside Nozbe without external URL access, we flag the limitation and recommend the customer export files manually from Nozbe before migration, providing a file manifest as a migration deliverable.

Nozbe Team Members (users in a workspace) map to Trello Workspace members. We resolve by email address. Members without a matching Trello account go to a reconciliation queue for the customer's admin to provision before Card import resumes. Member roles (admin vs. member) in Nozbe translate to Trello Workspace admin vs. normal member if the destination workspace supports role management on its plan.

Nozbe Inbox items are GTD capture entries without a Project assignment. Trello has no Inbox concept. We migrate Inbox items as Cards on a dedicated Trello Board named Inbox or Unsorted, with each Card holding the original capture text, timestamp, and source attribution. The customer's admin reviews and distributes Cards to the correct Project Boards post-migration. This is a design choice made during scoping; Inbox items can alternatively be discarded if the customer prefers a clean-start approach.

Nozbe Task due dates migrate directly to Trello Card due dates. Time-of-day on due dates transfers where supported by the Trello API. Overdue dates are preserved as-is. We set the due date remider offset to the customer's preference (typically 24 hours) during migration. Nozbe reminders do not migrate because Trello does not support per-Card reminder scheduling outside of Butler automation.

Nozbe Business Spaces (enterprise organisational units in new Nozbe) map to Trello Workspaces. Each Business Space becomes a Trello Workspace, with all contained Projects migrated as Boards inside that Workspace. This mapping applies only for customers on Nozbe Enterprise tier; Nozbe Premium users with a single workspace map to a single Trello Workspace.