Migrate from Project Drive to Microsoft Project

Project Drive Projects map directly to Microsoft Project as the top-level container. We extract project name, description, status (Active, Completed, On Hold), start date, finish date, and creation timestamp. Project Drive's project-level metadata becomes project summary task fields in Microsoft Project. Export is straightforward via the application's project-level CSV export where available, or via scripted UI extraction sessions for accounts with many projects.

Project Drive Tasks map to Microsoft Project Tasks with Name, Start, Finish, Duration, and PercentComplete preserved. Task status (Not Started, In Progress, Completed) maps to the Microsoft Project PercentComplete and IsMarked flag. Task notes migrate as Task Notes field in Microsoft Project. Where Project Drive exports tasks with a parent-reference to indicate hierarchy, we preserve the outline level by setting the Summary field appropriately.

Project Drive Subtasks nest under Tasks. We collapse the two-level hierarchy by promoting Subtasks to Tasks linked under a Summary Task that represents the parent Task. The outline level in Microsoft Project is set to preserve the visual hierarchy. Some destination configurations may choose to flatten all Subtasks to a flat task list with a custom Parent_Task__c field; the customer chooses the flattening strategy during scoping.

Project Drive Milestones export as standalone records with a milestone flag and a target date. We create Microsoft Project Tasks with Duration set to zero and the Milestone checkbox enabled. The milestone name and date migrate directly. If Project Drive does not expose a dedicated milestone field in export, we identify milestones by their task type marker in the Gantt view layout data and create the equivalent Milestone task at migration time.

Project Drive displays task relationships visually in Gantt view, but exported data may flatten dependency links into simple ordering fields (e.g., PredecessorName or task sequence index). We reconstruct explicit dependency declarations from the Gantt visual layout data, inferring Finish-to-Start relationships from the sequential ordering. We then write Predecessor and Successor records in Microsoft Project using the Successors and Predecessors task fields. Any explicitly declared dependency types in the source (e.g., Start-to-Start) are preserved if present in the export data.

Project Drive Users and task Assignees map to Microsoft Project Resources. We extract the user roster from the export and create Resource records with the user's name and email. Per-task assignee assignments become Task Assignments in Microsoft Project with the Resource Name, Units, and Start/Finish dates mapped from the task assignment data. If Project Drive exports a generic assignee field without resource rate data, we create Material Resources rather than Work Resources in the destination.

Project Drive Budget fields map to Microsoft Project cost columns. We map the Project Drive budget amount to the project-level Budget field or a custom cost field, depending on whether the customer tracks budget at the project level or the summary task level. The customer chooses the cost tracking model during scoping: project-level budget as a single value, or cost-per-task using the Budget field with cost accumulation formulas.

Project Drive cost data per task or per project requires mapping to Microsoft Project's cost schema, which distinguishes between Fixed Cost (a lump sum assigned to a task), Fixed Cost Accrual, Per-Unit Cost (resource rate multiplied by units), and Cost resources. We analyze the Project Drive export schema during discovery to identify cost fields and propose a mapping to the appropriate Microsoft Project cost column. Any null or zero cost values are flagged for the customer's confirmation before migration.

Project Drive task and project attachments export as binary file blobs with original filename and content type preserved. In Microsoft Project for the web, attachments link to the project's associated SharePoint document library. We carry over the file blob and re-attach it to the corresponding task or project in the destination. Link integrity depends on the target's SharePoint storage being configured; we verify the SharePoint site exists and the migration user has contribute permissions before file re-attachment.

Project Drive Start Date and End Date on tasks migrate directly to Microsoft Project Start and Finish fields. If the project-level Project Guide Start Date is set, it applies as the project default; individual task dates migrate as-is. Where Project Drive exports only a Start date without an explicit End date, we compute Finish from Start plus Duration using the project calendar.

Project Drive task status values (Not Started, In Progress, Completed) map to Microsoft Project PercentComplete. Not Started maps to 0%, In Progress maps to a midpoint value (customer choice between 25%, 50%, or 75% based on the source data's granularity), and Completed maps to 100%. We flag any non-standard status values during discovery for manual mapping.