Migrate from Microsoft Project to Trello

Each Microsoft Project file (.mpp) or PWA project becomes one Trello board. The board name uses the project name. We preserve the project description as the board description and the project start date as a custom field on the board. Enterprise projects from PWA become Enterprise workspaces in Trello if the org has Trello Enterprise.

Standard tasks map 1:1 to Trello cards. Task name becomes card title. Task notes/description becomes card description. Start date, finish date, and duration migrate as due dates and custom fields. % complete does not map to Trello natively — we preserve it as a Progress__c custom field (number). Assignee resolves by email match to Trello members.

Summary tasks with child sub-tasks split into a parent card representing the summary, with sub-tasks created as child cards linked under it. Trello does not have a native parent-child relationship between cards — we use a Power-Up like Treejack or card links to preserve the WBS hierarchy. Outline level is stored as a custom field on each card.

Microsoft Project resource names map to Trello board members by email match. Resource max units, cost rate tables, and accrual type (prorated, front-loaded, back-loaded) have no Trello equivalent — we preserve them in a Resource_Mapping__c custom field on each card where the resource is assigned. Unmatched resources are flagged before migration.

Each resource assigned to a task creates a Trello card assignee for that task. If a task has multiple resource assignments (e.g., a developer at 50% and a designer at 25%), we capture the unit percentage in Resource_Units__c on the card. Trello natively shows all assignees on a card regardless of allocation percentage.

Microsoft Project FS dependencies (the most common type) map to Trello card links via a dependency Power-Up. Each predecessor-successor pair becomes a blocked-by or blocking link on the card. Trello's built-in card linking is directional — we preserve the FS semantics in the link type.

Trello has no native representation for Start-to-Start, Finish-to-Finish, or Start-to-Finish dependencies. We preserve these dependency types and their lag/lead time as a Custom_Dependencies__c text field on each card listing the non-FS relationships. Your team rebuilds these as Butler rules or a dependency Power-Up after migration.

Microsoft Project enterprise custom fields migrate into Trello's Custom Fields Power-Up. Text fields map to Trello text, numbers to number, dates to date, and pick-lists to dropdown. Currency and cost fields migrate as number fields — Trello has no native currency formatting. Flag/checkbox fields map to Trello checkbox custom fields.

File attachments on Microsoft Project tasks re-upload to Trello card attachments. Trello Enterprise allows 250 MB per file; Standard/Premium allow 10 MB per file on the free/standard tiers. We flag files exceeding Trello's size limit so your team can store them externally and link to them instead.

Task notes in Microsoft Project, including any rich text formatting, become card descriptions in Trello. HTML formatting in task notes is stripped to plain text with basic markdown preserved where possible. Hyperlinks in task notes re-embedded as markdown links. If the original notes contain tables or embedded images, FlitStack AI converts them to plain-text tables or external image links to maintain readability within Trello's description field.

Microsoft Project baselines (baseline start, baseline finish, baseline cost) have no Trello equivalent. We export baseline data as a separate CSV alongside the migration and deliver a baseline-restore specification as a Trello Power-Up configuration guide for teams that need to track schedule variance in Trello Premium.

Microsoft Project task calendars and non-default working time (e.g., night-shift calendars) cannot be represented in Trello. We preserve calendar assignments as Calendar_Name__c on each affected card and note that Trello uses a 24/7 default calendar — teams recreate working-time constraints in Butler if needed.