Migrate from Planview Daptiv to Trello

Daptiv portfolios form a multi-level parent-child hierarchy with rollup of status, budget, and resource data. Trello has no portfolio concept; a Workspace is a top-level container for Boards with no rollup capability. We map all Daptiv portfolios to a single Trello Workspace, using Portfolio name as the Workspace name and recording the portfolio hierarchy as a custom field (portfolio_parent__c) on each Board for documentation. The customer accepts that portfolio rollup data does not transfer.

Daptiv Projects map directly to Trello Boards. Project name becomes Board name, project description becomes Board description, project start and target dates become custom fields on the Board, and project status maps to a Label color on Cards or to the first List name. We resolve the parent portfolio reference at migration time using the portfolio_parent__c custom field. Project owner becomes a Board Member with Admin role.

Daptiv Tasks map to Trello Cards. Task name becomes Card title, task description becomes Card description, task start and target dates become Card due dates, and task status maps to the Card's current List position. Assignments migrate to Card Members by resolving Daptiv resource email addresses to Trello Member accounts. Predecessor dependencies (Gantt links) cannot map to Trello's model; we document them in a linked Card attachment or in a separate dependency inventory delivered alongside the migration.

Daptiv Resources map to Trello Board Members by email address. We invite each resource as a member of every Board associated with projects where they have assignments. Billing rates, skill classifications, and demand-vs-availability data have no Trello equivalent and are not migrated. We deliver a resource inventory CSV with billing_rate__c and skill__c fields so the customer's admin can reference this data outside Trello if needed.

Daptiv Milestones are first-class objects with dates and deliverables. We map milestone name to a Trello Card (creating the card if no task is associated), milestone target date to Card due date, and milestone status (achieved, missed, pending) to a Color-coded Label (green=achieved, red=missed, yellow=pending). Milestone deliverables migrate as Card description text or as a Checklist item.

Daptiv time entries track actual hours logged against tasks and resources. Trello does not have a native time-tracking structure at any tier. We export time-entry records as a CSV with fields (task_name, resource_name, hours_logged, entry_date, billing_rate, total_cost) and deliver it to the customer as a supplemental data file. If the customer uses a Trello Power-Up for time tracking (Toggl Plan, Planyway, or TimeCamp), we document the import format requirements during scoping.

Daptiv project-level custom fields map to Trello Board-level Custom Fields. Trello supports text, number, date, dropdown, checkbox, and label custom field types. We inventory all Daptiv custom fields during scoping, map them to the nearest Trello Custom Field type, and pre-create them on each Board before Card import. Custom fields on Daptiv that use unsupported types (currency with formatting, multi-select from external lists) become text custom fields in Trello.

Daptiv task-level custom fields map to Trello Card Custom Fields. The same type-mapping logic from project-level custom fields applies. Trello Enterprise allows Board-level Custom Fields that propagate to all Cards; Standard and Premium require manual Custom Field application per Card or a Power-Up for bulk application. We note the customer's Trello tier during scoping and adjust the migration approach accordingly.

Daptiv stores files in DeskDocs, a document management layer separate from task and project records. Files are extracted as binary blobs with naming conventions or metadata linking them to parent records. We extract DeskDocs files, resolve the parent Daptiv record (Project or Task), find the corresponding Trello Board or Card, and upload the file as a Card Attachment. Trello Standard allows 10MB per attachment; Premium allows 250MB; Enterprise allows 50MB. Files exceeding the customer's Trello tier limit are flagged for manual handoff.

Daptiv resource allocation percentages (demand vs. availability per resource per project or task) map to Trello Board Members plus a custom field (allocation_pct__c) on Cards. We preserve the percentage value but note that Trello does not calculate load charts or flag overallocation. The customer accepts this limitation and can use Trello Power-Ups (resource planning boards) as a supplemental tool.

Daptiv allows organizations to define custom workflow states per tenant, which vary from the default set. We collect the complete status vocabulary during discovery, map each to a Trello List (representing workflow stages) or a Color-coded Label (representing status categories), and document the mapping table. Lists are the preferred Trello native representation for sequential workflow states; Labels are preferred for non-sequential categorical flags.

Daptiv calculates planned cost from billing rates and actual cost from time entries. Trello has no cost or budget model. We extract budget and cost data as a supplemental CSV (project_name, planned_cost, actual_cost, variance) and deliver it alongside the migration. The customer can attach this CSV to the Board as a reference document or maintain it in a spreadsheet.

Daptiv saved dashboards and report definitions are tightly coupled to its UI and data model. We do not migrate dashboards as code. We deliver a written inventory of every Daptiv Dashboard listing each chart widget, its data source object, the metric displayed, and the refresh cadence. The customer's admin uses this inventory to manually configure Trello Board overview charts or rebuild dashboards in a supplemental BI tool (Google Data Studio, Power BI, or Excel).

Daptiv reports are stored definitions tied to the platform's reporting engine. We do not migrate report definitions. We deliver a written inventory of every Daptiv Report listing its name, object scope, filters applied, columns displayed, and grouping logic. The customer's admin rebuilds these manually in Trello Board overview or exports to a spreadsheet for ad-hoc reporting.