Migrate from The Daily Project to monday Work Management

The Daily Project Projects map directly to monday.com Boards. We preserve the project name and any colour label by mapping it to the board's accent colour or icon. The board type (Team, Personal, or Project) is set based on the destination workspace configuration. Archived projects are included only if the customer confirms inclusion in writing before extraction; the API requires an explicit include-archived flag that we set during scoping.

The Daily Project Sections (Backlog, In Progress, Done, etc.) map to monday.com Groups within the target Board. We preserve the section names and the relative ordering of groups. The group ordering is read from the source API and replicated by setting the group's position parameter during board creation. If section names are duplicated within a project, we prefix them with the parent project name to avoid monday.com group-merge conflicts.

The Daily Project Tasks are the primary data unit and map to monday.com Items. Title, description (rich text preserved), due date, priority flag, and checklist items transfer directly. Subtask ordering within a checklist is preserved by maintaining the original sequence of checklist items. Item status (open/resolved) is derived from the absence or presence of an archived flag. We create items in their correct Group by resolving the section membership from the source before insert.

The Daily Project stores recurrence as a natural-language string or RRULE in a single field with no normalised schema. We parse each rule at migration time and attempt to re-express it as an iCal RRULE string in the monday.com Recurrence column. Rules using non-standard phrasing such as 'every couple of weeks on Tuesday' may require a manual mapping step before confirmation. We flag any rule that cannot be parsed automatically for the customer's review before the cutover window opens.

The Daily Project Labels are flat tag strings applied to tasks. We migrate label names and recreate them as monday.com Labels attached to the corresponding Items. Where The Daily Project label colours exist, we attempt to match them to the closest monday.com label colour. monday.com labels are workspace-level, so all labels from multiple The Daily Project projects land in the same monday.com workspace label set.

The Daily Project Comments attached to tasks map to monday.com Updates on the corresponding Item. We preserve comment body text, author name (as text, not linked to a monday.com user account since The Daily Project has no user concept), and timestamp. Mentions within comment text (e.g. @username) are preserved as plain-text strings and are flagged for manual relinking in monday.com.

The Daily Project stores only a URL reference for attachments, not the file content. During migration we preserve the URL and original filename in a monday.com File column with a link type. The actual file content must be independently downloaded from the source URL and re-uploaded to monday.com's native file storage. If the source URL becomes inaccessible before migration completes, the attachment record migrates as a broken link and we flag it during the pre-cutover validation scan.

The Daily Project does not expose a custom fields object in its documented API. Any customer-specific fields discovered in the UI that appear as text-based task properties are migrated as monday.com Text columns. The customer should review these after migration to determine whether a more appropriate column type (Date, Number, Dropdown, Link, etc.) applies.

The Daily Project priority flag (if present as a boolean or enumerated value) maps to the monday.com Priority column where available on the destination plan. If the destination plan does not include the Priority column, we map the value to a coloured Label or a Number column with a 1-4 scale.

The Daily Project checklist items within a task are mapped to monday.com Subitems attached to the parent Item. Subitem text, completion status, and ordering are preserved. monday.com Subitems are available from the Basic plan tier onward. If the destination account is on the Free plan, we map checklists to a text-formatted list within the Item's description instead.

The Daily Project has no native user concept; assignee fields that exist as plain-text owner names do not automatically link to monday.com user accounts. We preserve the text name in a Person column or a Text column as appropriate for the destination plan, and flag every unique assignee name for manual relinking to monday.com workspace members post-migration.

Archived tasks are not returned by the standard The Daily Project API query unless an explicit include-archived flag is passed. We set this flag during extraction and mark archived Items in monday.com as archived using the Items archive API call. If the customer does not want archived tasks migrated, they must confirm exclusion in writing before extraction begins.