Migrate from Intervals to Trello

Intervals Clients are top-level organizational units containing Projects. In Trello, the closest analog is a Workspace (Atlassian-owned) or a top-level Board used as the client container. We discuss this distinction during scoping: if the customer manages multiple clients with separate billing or reporting needs, we recommend a Trello Workspace with one Board per client project. Workspace creation is scoped to the customer's admin and is a prerequisite before migration begins.

Intervals People (user accounts with timesheet permissions and roles) map to Trello Members. We match by email address and preserve the active/inactive status. Intervals access levels (admin/member) map to Trello Workspace roles during provisioning; the customer's admin sets these roles in Trello before we assign members to boards.

Each Intervals Project becomes a Trello Board. Project name, status (active/archived), start date, and end date migrate as Board metadata. We use the project start date as the Board creation date. If the original Intervals project carries a budget figure, we flag this as a custom field requiring post-migration setup because Trello has no native budget object.

Intervals Milestones are date-driven checkpoints within a Project. Trello has no native Milestone object. We simulate this by mapping Milestone target dates to the due dates on milestone-scope Cards, and we optionally create a Label named after the Milestone to visually group those Cards. For milestone checklists or completion flags, we add a Checklist item to each affected Card. This is a customer-facing configuration decision made during scoping.

Intervals Tasks map directly to Trello Cards. We preserve task name, description, status (open/complete), estimated hours, actual hours, assignees (People mapped to Members), and the milestone linkage where present. Task ordering within a List preserves the Intervals sequence order. Archived tasks in Intervals map to archived Cards in Trello.

Task-level comments in Intervals migrate as Card Comments in Trello. Comment author maps to the corresponding Trello Member by email. Comment timestamp is preserved. Intervals supports threaded comments; Trello does not — we flatten threads into sequential Card Comments ordered by timestamp.

Milestone comments migrate to the Card Comments of the Cards grouped under that Milestone via the due-date or Label mapping. If a Milestone has standalone comments not tied to a specific task, we add them as a Card Comment on the first Card in the Milestone group or as a Board Description update if no Cards exist under that Milestone.

Intervals Project Notes are standalone text entries scoped to a Project but not tied to Tasks or Milestones. We migrate these as Board Description updates in Trello, or as a pinned Card titled 'Project Notes' if the text is extensive. The customer chooses the strategy during scoping.

Intervals time entries are the primary data object in the platform and have no native Trello equivalent. We offer two strategies during scoping. Strategy one: migrate time-entry data (hours, date, billable flag, task association) as Trello Custom Fields on each Card using Trello Standard plan's custom field support. Strategy two: preserve time entries in a CSV export alongside the migration and connect to an external time-tracking Power-Up such as Clockify post-migration. The choice depends on the customer's reporting needs and Trello plan tier.

Intervals custom activity fields are user-defined properties attached to time entries. These vary per account and are not visible in the standard CSV export — they appear only via the API. We enumerate all active custom activity fields during discovery and map each to a Trello Custom Field on the relevant Cards. If the customer is on Trello Free, custom fields are not available; we surface this constraint upfront and recommend upgrading to Standard or migrating the fields to a companion spreadsheet.

Intervals Documents are file attachments stored per task. The platform explicitly does not allow bulk export — only individual downloads are supported. We document every document URL during the discovery scan and present the customer with a manual-download checklist organized by Project and Task. We do not attempt to script bulk document retrieval because no API-based workaround exists in Intervals. Once the customer completes the manual downloads, we attach the files to the corresponding Trello Cards during migration.

Intervals per-project and per-task budget fields have no native Trello equivalent. We map these to Trello Custom Fields (Number or Currency type) on the Board or Cards. If the customer is on Trello Free, we flag this as a limitation and recommend upgrading to Standard or using a Power-Up such as Planyard for budget reporting post-migration.