Migrate from Output Time to Trello

Output Time Projects map to Trello Boards. Each project name, description, status, start date, and end date become the Board name, description, and optional start date Power-Up field. We create one Board per Project and map the project's team members to Board members. Output Time's one-time payment unlimited-user model means all project members are available for Board invitation without per-seat restrictions.

Output Time Tasks map to Trello Cards on the appropriate Board. Task name becomes Card title, description maps to Card description (preserving rich text where present), assignee maps to Card member, due date maps to Card due date, priority maps to a Card label (we use color-coded labels for Low/Medium/High/Critical), and status maps to the Card's List position. If the destination Board has Lists representing task stages (To Do / In Progress / Done), we map Output Time status to the corresponding List.

Output Time Subtasks are children of Tasks. Trello Cards do not have native nested cards on Standard plans; we convert subtasks to Checklist items on the parent Card. Subtask name becomes checklist item text, assignee maps to a @mention note in the item description, and due date is preserved as a note in the checklist item. For migrations where subtasks have their own subtasks, we flatten the hierarchy to a two-level structure: parent task card contains all child subtask checklist items.

Output Time Time Entries (hours logged, billable flag, notes, user, date) have no native Trello equivalent. We store the most recent time entry per task as a number Custom Field named Hours Logged on the Card, and the billable flag as a checkbox Custom Field named Billable. For multiple entries per task, we aggregate total hours into the Custom Field and preserve a summary in the Card description. The full time entry log (per-entry date, user, notes, duration) is delivered as a CSV export alongside the migration so customers can import into a time-tracking Power-Up post-migration.

Output Time Milestones are dated checkpoints within a project. Trello has no native milestone object. We map milestones with a target date to the Card with the closest due date, using a label named Milestone to flag them. If a milestone has multiple tasks, we add a Milestone label to each related Card and set the Card due date to the milestone target date. Milestone ordering is preserved as a note in the Card description naming the milestone phase.

Output Time Users (email, display name, role) map to Trello Members on each Board. We resolve by email match. Users without a corresponding Trello account are added as Workspace Members during migration so they appear as Board invitees. Output Time's role (Admin, Manager, Member) maps to Trello Workspace admin or standard member status. We flag any user without an email for manual mapping.

Output Time Clients are contact records associated with projects. Trello does not have a native client or company object. We map client name to a Card label (e.g., Client: Acme Corp) so customers can filter boards by client. If the client's email is present, we also add them as a Board member with read-only access if the Trello plan supports guest accounts.

Output Time project-level custom fields map to Board-level Custom Fields in Trello. We attempt type inference from stored values: text values become text Custom Fields, dates become date Custom Fields, numbers become number Custom Fields. Where the inferred type conflicts with Trello's allowed field types (e.g., multi-value text into a dropdown field), we create a text field and flag the conflict in the pre-migration field map for customer review.

Output Time task-level custom fields map to Card Custom Fields in Trello. Trello Custom Fields are available from the Standard tier ($5/seat/month). We map the custom field name and value, applying the same type-inference logic as project-level fields. The customer must ensure Trello Standard or above is active before migration if task-level custom fields are in use; we flag this as a pre-migration requirement.

Output Time Tags applied to tasks map directly to Trello Labels on Cards. Tag name becomes Label name; we attempt to match to a Trello standard color where the tag name matches a Trello color label (e.g., red, orange, yellow, green, purple, blue, sky, lime, pink, black), otherwise we assign a default color. Tags with multiple values per task create multiple Label assignments on the Card.

Output Time stores file attachments on tasks and projects internally with no API access to retrieve them. We do not migrate attachments. We inventory every attachment by filename, the task or project it is attached to, and its approximate size, and deliver this inventory as a CSV. The customer manually downloads attachments from Output Time and re-uploads them to the corresponding Card in Trello post-migration. We provide a re-attachment guide mapping each file to its destination Card.

Output Time invoicing records (line items, totals, status) have no equivalent in Trello. We extract invoice data as a structured CSV (client, project, line items, total amount, status, date) and deliver it alongside the migration. The customer recreates invoices in a dedicated billing tool or exports them to a spreadsheet for record-keeping. Trello does not support invoice import.