Migrate from Project KickStart to Trello

Project KickStart Projects map to Trello Boards. Project name becomes the board title, description maps to the board description field, and cost maps to a custom field on the board. We preserve the source Project ID as a reference field for audit and reconciliation. If the customer uses multiple Project KickStart projects that share a theme, we create a Trello Workspace to contain the corresponding boards.

Phases are the second level of the Project KickStart outline and map directly to Trello Lists within the target board. Phase name becomes the List name, and the planned phase start and end dates are recorded as custom date fields on the first card in the list or as board-level custom fields depending on the Trello plan. We use the phase order from the outline to set List ordering.

Tasks are the primary work unit and map to Trello Cards. Task name becomes the card title, planned dates map to card due date and due date complete, owner maps to card members, cost maps to a custom number field, and completion percentage maps to card checklist progress or a custom number field. SubTask-level details from Project KickStart append to the card description with a structured prefix for disambiguation.

Project KickStart SubTasks nest under Tasks. Where Trello Business Class or above is in use, we create nested Cards under the parent task Card. For Standard and Free plans, we flatten SubTasks into Checklist items on the parent Card, prefixing each name with the SubTask label for disambiguation. The customer selects the nesting strategy during scoping.

Goals are a Project KickStart concept with no native Trello equivalent. We preserve them as a custom text field on each board card, or as a dedicated label with a structured prefix in the card title. Customers on the Standard or Premium Trello plan with custom fields enabled receive Goals as a custom long-text field; Free plan customers receive them as card description entries prefixed with GOAL: for manual extraction.

Notes are free-text entries at Project, Phase, and Task levels. We append them to the target Card description field with a prefix indicating the source level. If the card description already contains structured content, we attach Notes as Card Comments to avoid overwriting existing data. The author and timestamp are preserved in the comment attribution.

Project KickStart assigns Tasks to named team members. We map Assignee names to Trello Workspace members by email match. Where the assignee has no corresponding Trello account, we flag the card for reassignment during the reconciliation step before production migration. Member mapping is validated in the sandbox migration before the production cutover.

Obstacles and Risks are Project KickStart-specific project risk entries with no direct Trello equivalent. We map them to a dedicated Card Label (RISK: or OBSTACLE:) on the related task card, or to a checklist titled Risk Register with each item containing the risk title and description. The customer's choice of label versus checklist is confirmed during scoping based on their risk-tracking workflow.

Project KickStart generates explicit finish-to-start and start-to-start dependencies between tasks. We reconstruct these as native Trello Card Dependencies (available with the Card Dependencies Power-Up) where that Power-Up is active. For Free and Standard plans without the Power-Up, we convert dependencies to checklist-based sequencing on the predecessor card, ensuring that follow-on tasks are clearly ordered within the card structure. The customer chooses the dependency strategy during scoping.

Attachments linked to Project KickStart Tasks and Projects migrate as Card Attachments in Trello. We copy files to Trello by uploading directly to the card via the Trello API. File path references are not preserved since Trello stores attachments on its own servers. Customers with many large attachments should flag this during scoping to confirm that Trello storage limits are acceptable for their use case.

Project KickStart Comment Logs on Tasks migrate to Card Comments in Trello, preserving the comment text, author name, and timestamp. Comment ordering follows the original timestamp sequence. If a Comment references a SubTask or dependency context, we include a prefix in the comment body identifying the referenced element from the Project KickStart outline.

Project KickStart templates contain the outline structure, phases, and placeholder tasks. We export the template structure as a documented board layout in Trello and provide a written template rebuild guide specifying which Lists, standard cards, and custom fields to create in Trello to replicate the template. Trello Board Templates are rebuilt manually using the guide, as template export-import is not part of the automated migration scope.

Project KickStart pushes tasks and calendar events to Act! CRM and Microsoft Outlook via proprietary integration. These external sync records do not live in Project KickStart's own data store and cannot be extracted from the export files. We do not migrate them. The customer's admin reconfigures Act! or Outlook sync integrations directly in Trello post-migration using the appropriate Trello Power-Up or native Atlassian Connect integration.