Migrate from Planview Daptiv to monday Work Management

Daptiv portfolios map to monday.com Workspaces. We preserve the parent-child portfolio hierarchy by mapping top-level portfolios to monday.com Workspace folders and sub-portfolios to sub-Workspaces. Portfolio-level financial fields (aggregate planned cost, aggregate budget) are captured as number columns on a settings or documentation board within the Workspace rather than as a native aggregate value, since monday.com does not have a portfolio-level rollup object.

Daptiv projects map to monday.com Boards. The project name becomes the Board title, project dates map to the Timeline column, project status maps to the Status column using the tenant-specific translation table, and project owner maps to the Board owner. Sub-projects or phases under a parent project map to Groups within the same Board or to separate Boards linked via an Item column holding the parent project reference, depending on the customer's preference during scoping.

Daptiv tasks map to monday.com Items. Dates, assignments, effort, and planned cost fields map to the corresponding monday.com column types (Date, People, Numbers, Formula). Task dependencies in Daptiv map to monday.com's Dependencies column, which supports predecessor-successor or blocking relationships. We import dependencies in dependency order to prevent the Dependencies column from rejecting inserts for Items that do not yet exist.

Daptiv milestones are first-class objects with a target date and project association. We map them to monday.com Items with the Timeline column set to milestone type. The milestone date becomes the Timeline end date with zero duration. Project association maps to the parent Board or to a Group within the Board. Milestone deliverables are preserved as text columns on the Item.

Daptiv time entries linked to tasks map to monday.com Items using the Time Tracking column. Each time entry is recorded as a time-tracked entry on the parent Item, with the entry date, duration, and resource linked. The Daptiv time-entry-to-project reference is preserved by ensuring the Item belongs to the correct Board representing the project. If Daptiv tracks time at the project level rather than the task level, the time entry becomes an Item on the project Board without a parent task Item.

Daptiv custom fields on projects and tasks map to monday.com column types: dropdown and multi-select fields map to Status or Dropdown columns; numeric fields map to Number columns; date fields map to Date columns; text fields map to Text columns; boolean fields map to Checkbox columns. Any Daptiv custom field whose type cannot be represented as a native monday.com column type is flagged as a limitation during scoping and mapped to a Text column as a fallback, with the original field name preserved for the customer to refine post-migration.

Daptiv resources carry per-user billing rates that feed planned-cost calculations. Monday.com does not have a resource-level billing-rate or cost module. We capture all billing rate values during extraction and map them to a Number column on the relevant Board or Items. If the customer requires cost calculations in monday.com, we use a Formula column multiplying the billing rate by effort (hours), documented with the specific formula string. The cost calculation logic differs from Daptiv's built-in planned-cost engine and is flagged for the customer's admin to validate post-migration.

Daptiv stores file attachments in DeskDocs, a document management layer separate from task and project records. We extract attachments as binary blobs using file-level extraction (not a row export) and re-associate them to the correct monday.com Items using file naming conventions or embedded metadata to match the parent record. DeskDocs folder structure is preserved as a file-naming prefix or as a separate documentation board in monday.com. File-heavy migrations with hundreds of DeskDocs attachments require additional processing time beyond standard record migration and are flagged during scoping.

Daptiv allocation percentages and demand-vs-availability data export cleanly and map to monday.com Number columns on Items representing resource assignments. Availability data maps to a separate resource management board with People columns and percentage allocation columns. Monday.com's Workload view provides a visual representation of allocation across Items, though it does not natively support the demand-vs-availability matrix comparison available in Daptiv's resource management module. We document the demand-vs-availability structure from Daptiv so the customer's admin can configure equivalent Workload view filtering post-migration.

Daptiv planned cost (derived from billing rates and assigned effort) and actual cost (from time entries) map to monday.com Number columns. Variance is preserved as a Formula column calculating the difference. The underlying cost calculation logic differs between Daptiv and monday.com: Daptiv computes planned cost from per-user billing rates automatically, while monday.com requires explicit formula construction per column. We preserve the raw Daptiv cost figures and document the calculation approach used in the source so the customer's admin can configure equivalent formulas in monday.com or validate the migrated values against a manual calculation spreadsheet.

Daptiv's configurable workflow statuses are tenant-specific and vary beyond the default set. We collect the complete status vocabulary during discovery scoping and build a translation table mapping each Daptiv status value to the correct monday.com Status column value. This table is applied during the migration transform step so that records land in the correct status rather than defaulting to the first monday.com Status value or null. The translation table is delivered as a reference document alongside the migration output.

Daptiv's saved dashboards and report definitions are tightly coupled to its UI and data model and do not migrate. We deliver a written inventory of every Daptiv dashboard and report documenting its name, the data objects it references, the key metrics displayed, and the filters applied. The customer's admin rebuilds these in monday.com's Dashboard layer using the migrated data. This inventory is scoped and delivered as part of the standard migration handoff package.