Migrate from CONTACT Project Office to Trello

Each CONTACT Project Office Project maps to one Trello Board. We preserve the Project name as the Board name and the Project description as the Board description (imported as a card or stored in the Board settings). If the CONTACT Project has multiple task lists or status categories, we map these to Trello Lists within the Board. Project-level custom fields are applied to every Card within the Board as Trello card-level custom fields, configured once and inherited per Card.

CONTACT Tasks map directly to Trello Cards. The Task name becomes the Card title, the Task description becomes the Card description (Markdown-formatted), and the Task status maps to one of the target Board's Lists. If the customer uses a Kanban-style list in CONTACT with open/in-progress/completed/on-hold columns, these map to Trello Lists by status. We preserve the original Task creation date as a Card custom field or as the Card creation timestamp.

CONTACT Subtasks map to Trello checklist items within the parent Card. The Subtask name becomes the checklist item text, and Subtask completion status maps to checked/unchecked on the checklist item. We resolve the parent Task-to-Card relationship during extraction so each checklist item lands under the correct Card. Subtask assignees are noted as Card members or as a custom field on the checklist item if the Power-Up supports it.

CONTACT Task assignees (members assigned to a specific Task) map to Trello Card members. We resolve assignees by email match against the target Trello workspace membership. Any assignee without a matching Trello user goes to a reconciliation queue for the customer's admin to provision before Card assignment migration. Project-level assignees are mapped to Board membership separately.

CONTACT Task custom fields (text, number, date, dropdown, checkbox) map to Trello card custom fields. We configure the custom field in the target Board before migration using Trello's custom field types (text, number, date, dropdown, checkbox, rating). The mapping is applied at the Card level, so each Card receives its source Task's custom field values. Custom fields on Subtasks are stored as checklist item labels or as Card-level custom fields with a subtask prefix notation.

CONTACT Task and Subtask attachments migrate as Card attachments in Trello. We preserve the original filename, file size, and uploader metadata. Attachments are uploaded directly to Trello's attachment storage (subject to Trello's per-file size limits: 10 MB on Free, 250 MB on Premium and Enterprise). Large files from CONTACT self-hosted instances are chunked if needed and re-assembled at the destination. Image attachments become Cover images on Cards if the customer requests this during scoping.

CONTACT Task and Subtask comments map to Trello Card comments. The comment body migrates as plain text or Markdown-formatted text. We preserve the original commenter name and timestamp. If the source CONTACT instance stores internal notes separately from public comments, internal notes migrate as Card comments with an [Internal] prefix so the customer can identify them post-migration.

CONTACT Project Office task statuses (open, in progress, completed, on hold, or custom statuses) map to Trello Lists. We define the List names during scoping based on the customer's current status labels and the target Kanban workflow. If the customer wants a four-list Kanban (To Do, In Progress, Review, Done), we map the CONTACT statuses to those lists during extraction before Card creation. Custom status values are preserved as Card labels if the customer prefers label-based categorization over list-based.

CONTACT Task Priority (if used as a custom field or native property) maps to Trello Card Labels. We define the label colors and names during scoping to match the CONTACT priority scheme (e.g., Critical = red label, High = orange, Medium = yellow, Low = green). Priority values stored in custom fields map to custom field drop-down values instead of labels at the customer's preference.

CONTACT Task due dates migrate to Trello Card due dates directly. If a Subtask has its own due date, we store it as a checklist item label with the date or as a note on the checklist item. Completed date from CONTACT Task maps to the Card's due date completion status.

CONTACT Project Office project start and end dates have no direct Trello Board equivalent. We migrate project-level dates as Card custom fields on all Cards in the Board, or we configure the Trello Calendar Power-Up with the Card due dates to visualize the project timeline. If the customer uses milestone tasks (tasks with zero duration), we create milestone Cards marked with a label.

CONTACT Project Office workflow rules (automated actions triggered by task status changes, assignments, or date triggers) have no direct Trello Butler equivalent. We audit every active workflow rule, document its trigger, conditions, and actions in a written handoff inventory, and recommend a Butler rule or Automation Power-Up configuration for each. The customer's admin rebuilds the automations in Trello post-migration.