Migrate from The Daily Project to Jira

The Daily Project Projects map directly to Jira Projects. We create the Jira Project with the matching name and a default issue type scheme. Jira projects have permission schemes and project role members that The Daily Project does not; these are configured post-migration by the customer's admin. Project-level metadata (colour label in The Daily Project) does not have a direct Jira equivalent and is noted as a cosmetic attribute not migrated.

Sections in The Daily Project provide horizontal grouping within a Project (e.g. Backlog, In Progress, Done). Jira does not have a native Section object, so we map Sections to Backlog groups (via a Jira Misc Workflow Extensions or JMWE app) or to Swimlane row labels on a board. Without a supporting Jira app, Sections are expressed as labels on Issues with a section_ prefix. Task ordering within each Section is preserved by setting a custom sort_order field or by ordering in the Jira API payload sequence.

Each The Daily Project Task maps to a Jira Issue. The Task title becomes Issue Summary, the description becomes Issue Description, due date maps to Due Date, priority maps to Jira Priority (P1-P5), and checklist items map to Jira sub-tasks if the number of checklist items per task is moderate. Sub-task creation is gated on Jira sub-task issue type being enabled in the project. Issues are created after their parent Project is provisioned and before Comments are attached.

The Daily Project stores recurrence as an RRULE string per Task (e.g. FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR). Jira does not have native RRULE parsing. We map recurring Tasks to Jira Issues and document the RRULE in a custom text field rrule_original__c. For Jira instances with Scheduler for Jira (Atlassian Marketplace) or Cycle for Jira installed, we configure the recurring schedule during destination setup. Complex or non-standard RRULE phrasing that cannot be parsed at migration time is flagged for manual configuration.

The Daily Project Labels are flat tag strings applied to Tasks. These map directly to Jira Labels. We extract all distinct label names, ensure they are valid Jira label strings (no spaces, lowercase normalisation), and apply them to the corresponding Issues during migration. Jira labels are not hierarchical; any hierarchical label structure from The Daily Project is flattened to a single-level tag.

Comments on The Daily Project Tasks migrate to Jira Issue Comments. Author name migrates as plain text (Jira does not automatically link text @mentions to Jira user accounts unless the mention syntax exactly matches a Jira username). Mentions in comment text are preserved as plain text @username strings. Timestamp of the original comment is preserved on the Jira Comment.created field.

The Daily Project stores only a URL reference to externally hosted files. We preserve the URL and original filename as a custom field attachment_url__c on the Jira Issue. The actual file must be downloaded from the source URL and re-uploaded to Jira's native attachment storage before the migration cutover. Any URL that is inaccessible at extraction time is flagged as a broken link and excluded from the URL field, with a list of missing files delivered to the customer for manual resolution.

The Daily Project does not have user accounts; assignee is a free-text name field on Tasks. We extract all distinct assignee names, match them by email or exact name against the Jira destination User table, and resolve each to a Jira User ID. Any name without a matching Jira User is held in a reconciliation queue for the customer to provision before production migration. Jira requires an Assignee field to reference an actual User record — a null or unresolved assignee causes import failure on standard issue type schemes.

The Daily Project task note (plain text or rich text description) maps to the Jira Issue Description field. If the note contains a checklist, we evaluate whether to convert individual checklist items to Jira sub-tasks based on count. Notes without checklists merge directly into the Description field as plain text.

The Daily Project archived Tasks are not returned by the standard API unless an explicit include-archived flag is passed during extraction. We set this flag at scoping. The archived state maps to an Issue status of Closed or to a Jira status category (Done) that the customer selects during scoping. If a customer does not want archived Tasks migrated, they must confirm exclusion in writing before extraction begins.