Migrate from The Daily Project to Microsoft Project

The Daily Project tasks map to Microsoft Project tasks. Task title becomes Task Name. Description migrates to the Notes field. Due date maps to either Finish Date (in Fixed Duration scheduling mode) or to a custom Due_Date__c field if the customer uses Fixed Units or Fixed Work. Priority flag (low/medium/high) maps to the Priority field (1-10 scale). Checklist items within a task become subtasks with outline indentation preserved. Task order within a section is preserved by setting the Outline Number and WBS fields during import.

Each The Daily Project project maps to a separate Microsoft Project plan (MPP file or Project for the web project). Project name becomes the project title. Project colour label migrates as a custom text field project_colour__c since Microsoft Project does not have a native colour property. Task membership is preserved so all tasks within a section belong to the correct project. Archived projects require an explicit include-archived toggle during extraction; we set this flag in scoping but exclude archived projects from migration unless the customer requests them in writing.

The Daily Project sections provide horizontal grouping within a project (e.g. Backlog, In Progress, Done). Sections map to Microsoft Project summary tasks that act as grouping headers for their child tasks. The section name becomes the summary task name. Relative task order within each section is preserved by setting the Outline Level and ID fields during import. If the customer uses section colour coding, the colour value migrates to a custom summary task field. Microsoft Project's outline structure supports unlimited nesting; single-level sections from The Daily Project map to top-level summary tasks.

The Daily Project stores recurrence as natural-language RRULE strings (e.g. FREQ=WEEKLY;BYDAY=MO,TU,WE,TH,FR). We parse each RRULE at migration time and re-express it in Microsoft Project's recurrence dialog format: frequency (daily, weekly, monthly, yearly), interval, days of week, day of month, and end condition. Non-standard phrasing (e.g. 'every couple of weeks on Tuesday') cannot be fully parsed algorithmically and require a manual mapping step; we flag these during scoping and confirm the mapping with the customer before recurrence data is committed.

The Daily Project comments attached to tasks migrate as Microsoft Project task notes. Comment body text, author name, and timestamp are included. @username mentions within comment text are preserved as plain-text strings and are not automatically linked to Microsoft Project user accounts since The Daily Project has no native user concept. The customer may choose to manually tag colleagues post-migration if Microsoft Project user accounts exist.

The Daily Project stores attachment URLs pointing to externally hosted files, not the file content itself. We transfer the URL reference and original filename as a text value in a custom attachments_url__c field on the task. The actual file content must be independently downloaded from the source URL and re-uploaded to the destination SharePoint document library or Microsoft Project attachment layer. If the source URL becomes inaccessible before migration completes, the attachment migrates as a broken link and is flagged in the pre-cutover URL validation report.

The Daily Project labels are flat tag strings applied to tasks. We migrate label names and apply them to corresponding Microsoft Project tasks via a custom Text1 through Text10 field (or a named custom field if Project Plan 3 or above is in use). If the customer uses multiple labels per task, we concatenate them with semicolons in a single custom field or distribute across multiple custom fields based on the destination plan's custom field quota. Label colour information is not available from The Daily Project's API and cannot be migrated.

The Daily Project checklist items within a task map to subtasks in Microsoft Project with outline indentation one level below the parent task. The checklist item text becomes the subtask name. Checklist completion status (checked/unchecked) maps to the Percent Complete field: completed items set to 100%, incomplete items set to 0%. Task order among checklist items is preserved by the subtask ID sequence. Checklist items that reference external URLs may have those URLs preserved as task notes on the subtask.

The Daily Project due date maps to Microsoft Project Finish Date. Before migration, we confirm the scheduling mode in use: Fixed Duration (default for most imported plans) means the due date maps directly; Fixed Work or Fixed Units scheduling modes require a start date calculation based on the due date and estimated effort. We configure the scheduling mode in the destination project before import and document any due-date-only tasks that cannot be fully scheduled without start date information.

The Daily Project priority flag (low, medium, high) maps to Microsoft Project's Priority field on a 0-10 scale: low maps to 250, medium maps to 500, high maps to 1000. Tasks without a priority flag default to 500 (medium). The priority value affects task sorting in Project for the web views and is used by some reporting filters. We preserve the priority value but note that Microsoft Project does not have a native task importance or urgency flag beyond this numeric scale.