Migrate from Planview AdaptiveWork to monday Work Management

AdaptiveWork Projects map directly to monday.com Boards. Project name, description, start date, end date, and status map to Board name, description, and the board-level timeline if enabled. Custom fields on the Project entity (up to 500 on Business and Enterprise tiers) map to monday.com Board columns of the equivalent type: text fields to Text columns, picklists to Dropdown columns, dates to Date columns, and numeric fields to Numbers columns. We pre-create Board columns during scoping so that the column IDs are available for Item import. Note that monday.com Boards do not natively support project-level financial fields (budget, cost, revenue); these require either a supplemental Items-in-Board approach or a note in the migration handoff document recommending a dedicated financial tracking board or integration.

AdaptiveWork Tasks are the core work unit and support unlimited nesting via parent-child links, allowing grandchild tasks. Monday.com Items live inside Groups (one level of grouping per column status), and subgroups are not natively supported. We flatten AdaptiveWork task hierarchies by mapping the top-level Task to a monday.com Item and any direct children to Subitems (one level of Subitem nesting is available). Grandchild Tasks that are grandchildren of Projects through the parent-child chain are mapped to Subitems of the direct child Item, with a note in the migration report about the reduced hierarchy depth. Parent-child ordering is preserved by setting the Subitem rank and Activity timestamp.

AdaptiveWork Milestones are tracked as date-driven entities associated with Projects or Tasks. We map Milestones to Items within the destination Board using the Milestone name as the Item name, with the Milestone date mapped to a Date column. Alternatively, if the destination Board uses the Timeline view, the Milestone date is set as the End Date of a zero-duration Item in Timeline view with a Milestone-specific label. We preserve milestone status (on-track, at-risk, missed) as a Dropdown column value. The Roadmap visibility configuration in AdaptiveWork does not transfer; we document it as a monday.com board configuration step.

AdaptiveWork predecessor/successor dependency links do not have a structured equivalent in monday.com. The monday.com Timeline view supports visual dependency arrows between Items, but these are display-only and do not enforce scheduling logic. We migrate dependency data as a configuration step: for each AdaptiveWork dependency link, we set a visual dependency arrow in the monday.com Timeline view and add a Text column (Dependency) on the Item to record the predecessor Item name and dependency type (finish-to-start, start-to-start). This preserves the relationship data for admin reference even though schedule-triggering automation does not exist in monday.com.

AdaptiveWork Users map to monday.com Team Members by email address. We extract all distinct Users referenced in task assignments, resource allocations, and project ownership and resolve them against monday.com workspace invitations. Any AdaptiveWork User without a matching monday.com account is held in a reconciliation queue for the customer's admin to provision. Working calendar definitions in AdaptiveWork (regional holidays, personal working hours) do not transfer to monday.com; we document the active calendar exceptions as a monday.com Workload view configuration step.

AdaptiveWork picklist-type custom fields map to monday.com Dropdown columns or Tag columns depending on whether single-value or multi-value selection is used in AdaptiveWork. We preserve the picklist option labels as Dropdown values or Tag labels. Note that AdaptiveWork picklist fields render on hybrid view cards while free-text fields do not; this rendering difference is a source-platform limitation that we do not replicate. In monday.com, all column types are visible on Item cards by default, which may actually improve field visibility post-migration.

AdaptiveWork free-text custom fields map to monday.com Text columns or Long Text columns depending on the field length. We flag during scoping whether any free-text fields contain structured data (dates, numbers, URLs) that would benefit from a typed monday.com column instead of free text; if so, we apply the typed column during column creation and strip formatting from the source data as needed. Free-text field values that were invisible on AdaptiveWork hybrid view cards become fully visible in monday.com Item cards, which customers often interpret as a migration data improvement.

AdaptiveWork Time Entries track labor against Tasks and Projects with approval workflows. Monday.com's native Time Tracking feature is available on the Pro plan and above and supports hour logging per Item. We migrate Time Entry records as Time Tracking entries on the corresponding monday.com Item, preserving hours, date, and the user attribution. Approval workflows on time entries have no monday.com equivalent; we document the active approval workflows as a monday.com Workflow step for the admin to configure post-migration. On Basic and Standard monday.com tiers, Time Tracking is not available and we log time data in a Numbers column with a note in the migration scope.

AdaptiveWork Financials (budget, costs, revenue, cost types, budget-vs-actual) are first-class Project-level objects with line items. Monday.com has no native financial management. We map budget, cost, and revenue amounts to Numbers columns on a dedicated Board or as Board-level columns if the customer uses a single-project Board. We create a separate Financial Tracking Board as part of the migration deliverables and document the mapping between each AdaptiveWork financial field and the monday.com column name. For organizations relying on AdaptiveWork's billing and invoicing features, we flag this as a monday.com integration candidate (QuickBooks, Xero, or a custom ERP connector) and do not include ERP migration in standard scope.

AdaptiveWork resource capacity planning uses user working calendars, skills, and availability to calculate workload distribution with over-allocation alerts. Monday.com's Workload view (Pro and above) displays assigned hours per user but does not run capacity algorithms or cross-calendar availability calculations. We migrate the allocation data as person-hour assignments on Items, which the Workload view then displays. The capacity planning algorithms (regional calendars, skill-based availability, over-allocation alerts) do not transfer and require admin configuration of Workload view thresholds post-migration.

AdaptiveWork documents are managed via SharePoint or Box connectors and stored outside the platform. Monday.com Items support file attachments uploaded directly or from Google Drive, Dropbox, and OneDrive integrations. We migrate document URL references (SharePoint paths, Box links) as URL-type columns on the relevant Item. The actual file content must be transferred separately through the source document system (SharePoint or Box migration) as a parallel track outside the FlitStack AI scope. We explicitly flag the files track in the migration plan and recommend a document migration tool or a managed document move as a prerequisite before cutover.

AdaptiveWork Workflow Rules automate actions based on criteria such as status changes, field updates, or date thresholds. Monday.com Automate supports similar trigger-action patterns but the rule structure is not transferable. We do not migrate Workflow Rules as code. We export the full Workflow Rule inventory (trigger entity, criteria, action type, action parameters) as a written document during scoping and recommend specific monday.com Automation recipes that approximate each AdaptiveWork rule. The customer's admin or a monday.com implementation partner rebuilds Automations post-migration.

AdaptiveWork Project and Task templates encapsulate workflow structure, default fields, and pre-populated tasks. Monday.com's Template feature creates Boards from existing Boards. We export template definitions (structure, default values, pre-populated task lists) as a written document. The customer's admin creates monday.com Board Templates from the migrated Boards post-migration, which is the native mechanism for template reuse in monday.com. Template-as-structure does not automatically propagate from AdaptiveWork to monday.com.