Migrate from ProjectManager to Trello

Each ProjectManager Project maps to a Trello Board. Project name becomes Board name; Project description becomes the Board description. We create the Board via POST /1/boards/ using the authenticated Trello API, and set the Workspace (Team) member access during board creation. Projects with multiple task status columns (e.g., Design, Development, QA, Done) inform the initial List structure, but Lists are configurable post-migration based on the customer's workflow preferences.

Each ProjectManager Task maps to a Trello Card within the parent Project's Board. Task name becomes Card name; Task description becomes Card description. Due dates migrate to Card due dates. Task status maps to the Card's List position (by matching ProjectManager TaskStatus value to the most relevant Trello List). Parent-child task hierarchies migrate as Card checklists or as linked cards via Trello's cross-board card linking feature, depending on hierarchy depth. We flag hierarchies deeper than two levels for manual review because Trello's card model is not designed for deeply nested WBS structures.

ProjectManager TaskAssignees (Resources assigned to Tasks) map to Trello Card Members. We resolve ProjectManager Resources to Trello Workspace members by email match. Any Resource without a matching Trello user account goes to a reconciliation queue for the customer's admin to provision before card member assignment. Multi-assignee tasks create multiple Card Member records on the same Card.

ProjectManager Resources map to Trello Workspace members. Resource name, email, and availability windows are mapped to Trello member profile data. ResourceSkills are preserved as Labels on any Cards the Resource is assigned to, providing a tagging system that approximates ProjectManager's skill-based filtering. Note: Trello has no native availability or allocation tracking; we document this gap in the migration handoff for the customer to address via a resource management Power-Up or external tool.

ProjectManager ResourceTeams (groupings for scheduling and reporting) map to Trello Teams if the destination Trello workspace uses multiple Teams, or to Label color-codes if a single Team model is used. The customer chooses the mapping strategy during scoping. ResourceTeam membership does not have a native Trello equivalent, so we preserve it as a structured note on each member's profile card and as a Label on any Cards they are assigned to.

ProjectManager ProjectFields map to Trello Custom Fields where types match Trello's five supported types (text, number, dropdown, date, checkbox). String fields become text Custom Fields; number fields become number Custom Fields; date fields become date Custom Fields; choice fields with up to 25 options become dropdown Custom Fields; boolean fields become checkbox Custom Fields. Fields with types not supported by Trello (e.g., multi-select choice lists with more than 25 options, file attachments as field values) are preserved as structured text in the Card description with a [ProjectManager Field Migration] section for manual review and manual Custom Field population post-migration.

ProjectManager TaskFields migrate identically to ProjectFields, mapped to Trello Custom Fields on the Card. The same type-matching logic applies: string to text, number to number, date to date, choice to dropdown, boolean to checkbox. TaskField values written via PUT /api/data/projects/{projectId}/fields/{fieldId} are translated to Trello Custom Field values set via PUT /1/cards/{cardId}/customFields/{fieldId}.

ProjectManager Risk objects map to Trello Cards created in a dedicated Risk Board or a dedicated List within the parent Project Board. Risk severity maps to a Label (e.g., Critical, High, Medium, Low) using the customer's label color convention. Risk status (open, mitigated, closed) maps to Card List position. We preserve Risk.description, Risk.severity, Risk.status, and linked ProjectId as Card description fields. RiskFiles migrate as Card attachments. Risks without a linked ProjectId are placed in a standalone Risk Overview Board.

ProjectManager Timesheet records (hours logged by Resources against Tasks) have no native Trello equivalent. We migrate Timesheet data as a structured Card attachment or as a number Custom Field on the relevant Card (HoursLogged). ProjectManager's embedded billing rates do not migrate because Trello has no cost tracking. We flag Timesheet data during discovery and give the customer the choice to migrate hours only or export to a separate timesheet report for manual reconciliation. Historical Timesheet data is preserved as a CSV attachment on the parent Card.

ProjectManager Tags and TaskTags map to Trello Labels. Tag names transfer directly; tag associations transfer as Card-Label linkages. Trello Label colors are assigned based on the customer's label color convention or set to a default palette. We flag tag names exceeding Trello's 50-character limit for manual truncation.

ProjectManager UserRoles (permission profiles scoped to Workspaces) have no native Trello equivalent. We preserve UserRole definitions as a structured note on each member's Trello profile, and optionally as a Label on any Cards where the role-specific access pattern matters. The customer's admin uses the Trello Workspace settings to configure member permissions (Admin, Normal, Observer) post-migration.

ProjectManager Teams (organizational membership object, distinct from ResourceTeams) map to Trello Workspaces. We create the Trello Workspace if it does not exist, and map team memberships to Workspace members. ProjectManager team-level access control is translated to Trello Workspace member roles (Admin, Normal, Observer) based on the customer's access matrix.