Migrate from TimeHero to Trello

TimeHero tasks map directly to Trello cards. We extract title, description, due date, planned start date, and adaptive-scheduled date from the CSV and write them as card name, card description, due date, and two custom date fields (original_due_date and adaptive_scheduled_date) so that both the customer's intended deadline and TimeHero's auto-rescheduled date are preserved in Trello for manual review.

TimeHero projects map to Trello boards. The project name becomes the board name, and we preserve the project description as the board description. If the customer has multiple TimeHero projects, we create one Trello board per project. Workspace or organization mapping is configurable; customers can choose whether all boards land in one Trello Workspace or are distributed across multiple.

TimeHero folders (organizational containers within projects) map to Trello lists. Each folder becomes a named list on the project's board. Tasks inside the folder become cards inside the list. If a customer has deeply nested folder structures, we flatten to one level of lists per board and note the full path in the card description.

TimeHero time entries are embedded in tasks as actual duration (minutes worked) and remaining time fields. We create Trello custom fields of type Number named 'Actual Duration (min)' and 'Remaining Time (min)' on each card. These are card-level custom fields unless the customer has a Business Class subscription, in which case we use organization-wide custom fields. Trello has no native time-tracking UI; these fields provide the reference data for the customer's chosen time-tracking integration (Time Doctor, Toggl, or Butler).

TimeHero task work estimates (in minutes or hours depending on the task's configured unit) migrate to a Trello custom number field named 'Work Estimate (min)'. If the source data is stored as hours, we convert to minutes during the CSV transform. This field sits alongside the actual duration field so cards carry both the planned effort and the logged effort.

TimeHero task assignees map to Trello card members. We resolve each assignee by their TimeHero display name and map to the corresponding Trello Workspace member by email match. If a Trello user does not exist for the assignee, the card is created first and the member assignment is queued for the customer's admin to provision the Trello account before the migration completes.

TimeHero priority values (high, medium, low, none) map to Trello label colors. We create a standardized label set per board: red for high priority, yellow for medium, green for low, and gray for none. If the customer uses custom priority tiers beyond these four, we create additional labels and document the full mapping in the migration scope.

TimeHero recurring task patterns (daily, weekly, monthly recurrence with configurable intervals) have no native Trello equivalent. We document each recurring rule from the source as a written Butler command specification (trigger type, frequency, card duplication or checklist addition) so the customer's admin can implement the automation in Trello post-migration. We do not create Butler commands programmatically as part of the migration scope.

TimeHero supports task dependencies (x must complete before y begins). Trello has no native dependency graph. We represent dependencies as checklist items on the dependent card naming the blocking task ('Blocked by: [Task Name]'), or as Card Links (Trello's power-up feature) connecting the two cards. The customer chooses the representation during scoping.

TimeHero flags tasks at risk based on scheduling conflicts and deadline proximity. These are computed values. We capture the triggering conditions (deadline date, remaining time, assigned capacity) as a custom text field named 'Risk Context' on the card, populated with a human-readable summary ('Deadline in 2 days, remaining time: 480 min, capacity: available') so the Trello board user can assess the risk manually.

TimeHero uses connected Google and Outlook calendar events as scheduling context, not as stored primary records. We do not migrate calendar events as Trello cards unless the customer specifically requests it during scoping. If requested, we create a dedicated board with cards representing the calendar events and note that these are reference data, not schedule-automated cards.

TimeHero workflow templates (Premium feature) store project structure and process as application state that cannot be exported. We document the template structure during discovery by walking through each template in TimeHero's UI and producing a written board template specification: list names, default labels, default card templates, and recommended Butler commands. The customer's admin builds the Trello board template from this documentation post-migration.

If the customer used TimeHero's Asana connector to pull assigned tasks into the TimeHero inbox for scheduling, we identify those tasks and flag them as Asana-sourced in the migration data. We do not migrate Asana data; if Asana is in the customer's stack, we recommend either maintaining Asana as the task source or rebuilding the sync relationship via Zapier or the Asana-Trello native integration post-migration.

TimeHero attachments linked to tasks are not included in the CSV export and cannot be programmatically retrieved. We alert customers during discovery to manually download all task attachments from within TimeHero before migration, and we provide a checklist of cards requiring post-migration re-upload of those files. Trello card attachments are supported and can be re-linked after migration completes.