Migrate from Planview Daptiv to Microsoft Project

Daptiv portfolios with parent-child rollup data have no direct Microsoft Project equivalent. Project Desktop and Project Online operate on individual plans, not portfolio hierarchies. We extract portfolio-level financial fields (total budget, total cost, rollup status) and deliver them as a structured CSV for the customer to model in Power BI or as SharePoint lists. If the organization uses Project Online, we can map portfolio records to Project Online-level projects with a naming convention flag indicating their portfolio-role. This is a known limitation disclosed upfront during scoping.

Daptiv project records map to Microsoft Project project files (MPP) or Project Online project sites. Project-level fields including Start Date, Finish Date, Project Owner, Status, Priority, and Description migrate 1:1. Any Daptiv-specific workflow states are translated to Microsoft Project task status values (Not Started, In Progress, Completed, Delayed, Cancelled) using the mapping table built during discovery. Budget fields from Daptiv migrate to the project's Cost fields in Microsoft Project, but planned cost calculations differ because Daptiv derives cost from billing rates while Microsoft Project derives cost from resource rates configured within the plan.

Daptiv tasks migrate to Microsoft Project tasks with Start, Finish, Duration, Work, and Dependency relationships preserved. We sequence the import in dependency order so predecessor-successor links resolve at insert time. Assignments (resource-hour allocations per task) migrate to the Assignment fields in Microsoft Project. Actual work and actual duration from Daptiv time entries map to the task's Actual Work and Actual Duration fields to preserve progress data.

Daptiv milestones are first-class objects with a target date and deliverables list. They migrate as Microsoft Project milestones (zero-duration tasks marked as Milestone). The milestone name, target date, and associated deliverables text migrate to the task Name, Finish Date, and Notes fields respectively. Milestones maintain their project association through the parent project import sequence.

Daptiv resources carry name, email, billing rate, skill assignments, and max allocation percentage. They map to Microsoft Project resource sheet entries with Max Units from Daptiv allocation %, Cost Per Use, and Pay Rate fields populated from the billing rate. We extract the full resource pool during discovery and generate a resource mapping table. Resources without a clear Microsoft Project equivalent (such as Daptiv skill taxonomies) are documented as a separate skill matrix for the customer to manually configure in the resource sheet.

Daptiv allocation records (demand vs availability data per resource per project) map to Microsoft Project task Assignments with Units derived from the allocation percentage. Over-allocation flags from Daptiv migrate as notes on the Assignment record. Percentage precision rounding differences between Daptiv and Microsoft Project are documented so the customer's PM can validate resource utilization post-migration.

Daptiv time entries track actual hours worked per resource per task. We aggregate time entries by resource-task pair and set the Actual Work field on the corresponding Microsoft Project assignment. Billing amount from Daptiv time entries migrates to a custom Cost field if the customer's Microsoft Project plan includes cost tracking. If the organization uses Project Online, we can alternatively land time entry history as Project Online timesheet records in a separate import pass.

Daptiv custom fields on projects and tasks are inventoried during discovery and mapped to Microsoft Project custom fields. Text custom fields map to Text custom fields; numeric fields map to Number custom fields; date fields map to Date custom fields; picklist-style fields map to Flag or Outline Code custom fields depending on the use case. The customer's admin defines the custom field names in Microsoft Project before migration begins, and we provide a field mapping table that names the source Daptiv field, the destination custom field label, and the destination field type.

Daptiv stores file attachments in DeskDocs, a document management layer separate from the task and project records. We extract files as binary blobs using Daptiv's file export API (or manual export where API access is unavailable), match them to the correct parent project or task using file naming conventions or metadata headers, and re-associate them as attachments within the Microsoft Project plan file or as linked files in SharePoint Online if the organization uses Project Online. This requires additional processing time beyond standard record migration and is scoped separately during discovery.

Daptiv calculates planned cost from per-user billing rates assigned to resources. Microsoft Project calculates cost from resource rates configured within the plan. We preserve the raw planned cost and actual cost figures from Daptiv in custom fields on the project and task records, flagging that the destination cost model may produce different values. The customer's PM reviews post-migration to confirm the cost figures align with their reporting expectations.

Daptiv's configurable workflow statuses vary by tenant and are collected during discovery scoping. We build a translation table mapping each Daptiv status value to the nearest Microsoft Project task status (Not Started, In Progress, Completed, Delayed, Cancelled). Statuses with no direct equivalent are mapped to a custom flag field for manual review. This ensures records land in a recognizable state rather than defaulting to Not Started post-migration.