Migrate from The Daily Project to Asana

The Daily Project Projects map directly to Asana Projects. We migrate project name, colour label (as a project colour hex value), and all contained task memberships. Archived projects require the include-archived flag set during API extraction; we set this by default and the customer confirms in writing if archived records should be excluded. Project-level custom properties migrate as Asana task custom fields if the destination project is on Starter or above.

The Daily Project Tasks are the primary record unit and map to Asana Tasks. We transfer title, description (as rich text notes), due date, priority flag (as a numeric priority value), and created/modified timestamps. The Asana Task gid is generated at insert time; we store the source task ID in a custom field td_source_id__c for audit traceability.

The Daily Project Checklist items are flat child records under a task. Asana supports multi-level subtask nesting, so we create a first-level subtask for each checklist item with the item text as the subtask name and the completion state preserved. If a checklist item itself contains a nested checklist in The Daily Project, we create a second-level subtask. Subtask ordering is preserved by setting the sort_order field on each subtask.

The Daily Project Sections provide horizontal grouping within a project (Backlog, In Progress, Done). We map sections to Asana Sections, preserving the section name and the relative task order within each section. Section-level sorting is applied during the task import phase by referencing the section's task ordering array.

The Daily Project Labels are flat tag strings applied to tasks. Asana uses Tags as a separate tagging object, so we map each unique label name to an Asana Tag and create TagAssignments linking the tag to the migrated tasks. Where Asana's destination project uses custom field dropdowns for task categorisation instead of tags, we map label names to the relevant dropdown options during the field-mapping step.

The Daily Project stores recurrence as a natural-language string or an RRULE text field (e.g. FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR). We parse the rule and re-express it in iCal RRULE format for Asana's recurrence field. Standard rules (daily, weekly on specific days, monthly on a date) map cleanly. Non-standard phrasing such as 'every couple of weeks on Tuesday' requires a manual mapping step before we confirm the recurring schedule is replicated; we flag these at scoping and resolve them before production migration begins.

The Daily Project Comments attached to tasks migrate as Asana Task stories with story_type = comment. We transfer comment body text, author name (stored as plain text, not linked to an Asana User unless the author email is recoverable from the API), and the original timestamp. @mentions within comment text are preserved as plain-text @username strings and do not create Asana @mention notifications.

The Daily Project stores only a URL reference and filename for attachments, not the file content itself. We preserve the URL reference and filename in Asana task attachments. Before migration, we validate each URL for HTTP 200 availability; inaccessible URLs are logged as broken links in the pre-cutover validation report. The actual file content requires a separate download-and-upload step that the customer handles independently or via a file-transfer addendum to the migration scope.

The Daily Project has no native user account concept. Assignee fields in The Daily Project store plain-text names or email addresses. We extract every distinct assignee reference and attempt to match against the destination Asana org's User table by email. Unmatched assignees go to a reconciliation queue; the customer's Asana admin provisions the missing User accounts before the task import phase. We do not create Asana User accounts programmatically.

The Daily Project due dates map directly to Asana due_date. Due dates set as All Day events migrate as All Day tasks in Asana. Dates in non-ISO formats are normalised to YYYY-MM-DD during the extraction transform. Tasks with no due date are imported as undated tasks.

The Daily Project does not expose a custom fields API object. Any customer-defined fields discovered in the UI (stored as task-level text properties or label-like values) are migrated as plain-text task properties during extraction. We document each discovered field and recommend a typed Asana custom field equivalent (dropdown, number, date, checkbox) during the scoping call. Typed fields are created in the destination Asana project before production migration begins.

The Daily Project workspaces are individual or client-side concepts without a defined API object. All migrated data is imported into a single Asana Workspace created by the customer. If the customer has multiple distinct workspaces in The Daily Project, we map each to a separate Asana Project or to Asana Teams within a single workspace, depending on the collaboration structure the customer defines during scoping.