Migrate from The Daily Project to Trello

The Daily Project projects map to Trello boards. Project name becomes board name. Project colour label migrates as a Trello board background colour where the destination supports it. Archived projects require an explicit include-archived flag passed during extraction; by default only active projects are returned by the API query. Board-level permissions are set to the default workspace visibility unless the customer specifies invite-only boards.

The Daily Project sections (Backlog, In Progress, Done, or any custom grouping) map directly to Trello lists within the corresponding board. Section ordering is preserved as list ordering within the board. If The Daily Project uses sections to represent task grouping rather than strict workflow stages, we recommend the customer decide on list ordering during scoping.

The Daily Project tasks map to Trello cards. Card title carries the task name. Card description migrates as plain text from the task description field. Due date migrates as the card due date. Checklist items from the task migrate as Trello checklist items within the card. Archived status migrates as a Trello label (e.g. Archived) so that archived cards remain visible but flagged.

The Daily Project comments attached to tasks migrate as Trello card comments. Comment body text, author name, and timestamp transfer. Mentions (@username strings) in comment text are preserved as plain text and do not become functional Trello member tags; the customer's admin can re-link @mentions manually post-migration if desired.

The Daily Project flat tag strings map to Trello labels on the corresponding cards. Label names transfer as label names. If The Daily Project labels use colour coding, we attempt to match the nearest Trello label colour. Trello labels are scoped per board; if the source has workspace-wide labels, we replicate them on each destination board.

The Daily Project stores recurrence as natural-language strings or RRULE strings (e.g. FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR). Trello has no native recurrence engine. We parse each recurrence rule, re-express it in iCal RRULE format, and place it in the card description with a header note: 'Original recurrence: [rule]'. The customer's admin uses Butler to create a scheduled card-creation rule that fires at the recurrence interval, or accepts the static card as the migration endpoint for each recurring task.

The Daily Project stores only a URL reference for each attachment, not the file content. We transfer the URL and original filename as a Trello card attachment. The actual file content must be independently downloaded from the source URL and re-uploaded to Trello (or to a linked cloud storage service such as Google Drive or Dropbox) before or after migration. We flag any URLs that return HTTP errors during scoping so the customer can address them before the cutover window opens.

The Daily Project does not expose a custom fields object in its documented API. Any customer-specific field definitions discovered in the UI are treated as text-based task properties and migrated as plain text appended to the card description with the field name as a label prefix. Trello's native custom fields (Premium and Enterprise) are not populated because the source schema has no typed custom field definitions to map from.

The Daily Project has no native user or workspace role concept; task ownership is stored as a text owner name on each record. We extract all distinct owner names from tasks and cross-reference them against the destination Trello workspace members. Owners with a matching Trello member account receive cards assigned to them. Owners without a matching Trello account are documented in a reconciliation report; the customer's admin provisions accounts and re-assigns cards post-migration.

The Daily Project archived tasks require an explicit include-archived flag during API extraction. Archived tasks migrate as Trello cards with an 'Archived' label applied so they are visible but clearly flagged as inactive. If the customer does not want archived tasks migrated, they must confirm exclusion in writing before extraction begins.

The Daily Project priority flag on tasks migrates to a Trello label (e.g. High Priority, Medium Priority, Low Priority) using the label names closest to the source priority values. Trello does not have a native priority field; labels serve as the visibility mechanism for priority within each board.

Task due dates in The Daily Project migrate as Trello card due dates. The original timestamp (date and time if present) transfers exactly. Start date is not natively supported in The Daily Project and is not migrated. If the customer used start dates recorded in the task description, those migrate as text within the card description rather than as a typed Trello field.