Migrate from Planview AgilePlace to Microsoft Project

Each AgilePlace Board maps to a standalone Microsoft Project file (.mpp) or a Project Online project within a PWA. We extract board metadata including board name, description, and Lane structure during the first pass. If multiple boards represent phases of a single program, we consolidate them into one Project plan with Summary Tasks per board. The customer's PMO defines the consolidation boundary during scoping.

AgilePlace Lanes map to Summary Tasks in Microsoft Project, preserving the hierarchical relationship between parent Lanes and child Swimlanes. Each Lane's WIP limit is stored as a custom field WIP_Limit__c so PMs can reason about flow. Lane color coding maps to a Text field Color_Code__c. Swimlanes within a Lane become sub-summary tasks. If the destination is a flat task list without WBS hierarchy, Lanes map to a Phase label custom field on individual tasks.

AgilePlace Cards map to Microsoft Project Tasks. Card title becomes Task Name. Card description (rich text) migrates as Task Notes. Card type maps to a Text custom field Card_Type__c. Card priority maps to Priority (1-5 in MS Project). Due date on the Card becomes the Task Finish date; if no due date exists, the card is placed in the Lane without a scheduled date and the PM schedules it post-migration. Created, Moved, and Updated timestamps from AgilePlace are stored in custom fields Orig_Created__c, Orig_Moved__c, and Orig_Updated__c for audit and cycle-time reporting.

Card Dependencies in AgilePlace are stored as a separate API relationship linking child cards to parent cards. We export these as a dependency table keyed by Card ID, then map each dependency to a Microsoft Project predecessor link (FS, SS, FF, SF). We resolve predecessor IDs after task creation using the temporary ID mapping table generated during import. Circular dependency detection runs against the graph before insertion to prevent invalid schedule structures.

Card Assignees map by email address to Microsoft Project resources. If the destination is Project Online, we match against the PWA resource list. If the destination is desktop MS Project with no connected PWA, we create local resources from the assignee list. Unmatched assignees (cards assigned to inactive or archived AgilePlace users) are flagged in a reconciliation report for the customer's PMO to resolve before final import.

AgilePlace Custom Fields are defined per-board. We export field definitions alongside card data and map each to a Microsoft Project custom field of equivalent type: Text fields to Text, number fields to Number, date fields to Date, and dropdown values to Flag or Outline Code. Note that AgilePlace Custom Field edit permissions are role-gated — a user without project-level write access cannot update a custom field. We detect permission-sensitive fields during discovery and ask customers to confirm the migration user has write access to all custom fields at the board level.

Card Comments are appended to the Task Notes field in Microsoft Project, separated by a timestamp and author line (Author: name | Date: ISO date). If Task Notes already contains content, comments are appended to the existing text. If the destination is Project Online, comments may alternatively be stored in the associated SharePoint task list for a more collaborative experience.

AgilePlace Tasks (sub-items within a Card) map to Microsoft Project subtasks (Outline Level > 1). Completion status and assignee are preserved. If a Card has more than 20 sub-tasks, we flag it as a scope-risk item during scoping because deeply nested WBS structures in MS Project can degrade performance in the desktop client.

AgilePlace Tags are flat string labels. In desktop MS Project, tags map to a Text custom field Tags__c storing comma-separated values. In Project Online, tags may map to a multi-select Flag field if the customer's PWA supports that configuration. Tags used for card-type classification map to Card_Type__c instead.

File attachments on cards are downloaded from AgilePlace and uploaded to the associated SharePoint document library (for Project Online) or a shared network location (for desktop MS Project). The original file name and AgilePlace card reference are preserved in a Text field Attachment_Ref__c on the Task. Large attachment volumes increase migration duration and require storage capacity planning, particularly for Project Online where SharePoint storage has org-level quotas.