Migrate from TimeHero to monday Work Management

TimeHero Tasks map to monday.com Items. Each task's title, work estimate, actual duration, remaining time, original due date, current scheduled date, assignee, and priority migrate as separate columns. We preserve both the original due date and the current scheduled date as distinct columns so the destination board shows the planned date and the AI-adjusted date. The monday.com board column types are: Text for title, Numbers for estimates and durations, Date for due dates, Person for assignee, and Status (or dropdown) for priority.

TimeHero Projects and Folders map to monday.com Boards. Each project becomes a board with groups representing task groupings within that project. If TimeHero has nested folder structures, we create a monday.com Workspace folder hierarchy and place boards inside the corresponding workspace level. Board names and descriptions migrate as-is; column architecture is designed per-board during migration scoping.

TimeHero stores actual duration and remaining time as embedded fields in each task record. The CSV export exposes these as numeric values per task. We map them to the monday.com Time Tracking column (available on Pro and above), which stores start time, end time, and duration per item. We normalize TimeHero's actual duration and remaining time into combined Time Tracking entries per item. monday.com aggregates time tracking at the item and board level for dashboards.

TimeHero recurring tasks are defined with a recurrence pattern that generates future task instances. The CSV export shows the recurrence rule but not the generated instances. We extract the recurrence pattern (daily, weekly, monthly, custom interval), map it to a monday.com automation recipe with a 'Recurring' trigger and the same interval, and set the recipe to create a new item in the target board with the appropriate due date logic. The customer rebuilds these in monday.com's Automation Builder using the documented recurrence pattern as reference.

TimeHero uses connected Google and Outlook calendar events for scheduling context but does not store them as primary data. We do not migrate calendar events as records. If the customer needs calendar context preserved, we recommend exporting calendar data separately from Google or Outlook and importing it as items on a dedicated monday.com board or linking it through the monday.com Google Calendar integration post-migration.

TimeHero's Asana connector pulls assigned tasks into the TimeHero inbox for scheduling. If the customer has been using TimeHero as a scheduling layer for Asana-assigned work, those tasks appear in the TimeHero export. We map them to monday.com Items with the original Asana task name preserved in a Text column. The customer can optionally connect monday.com to Asana directly post-migration if the Asana relationship needs to continue.

TimeHero flags tasks at risk based on scheduling conflicts and deadline proximity. These are computed values not stored fields. We capture the triggering conditions (deadline, assigned capacity) and reproduce them as monday.com Status column values (e.g., 'On Track', 'At Risk', 'Blocked') using the same criteria. The admin defines the threshold values during board configuration.

TimeHero Workload reports (Premium feature) show team capacity and task distribution. We extract the underlying task data and assignee workload numbers from the export and use them to configure monday.com's Workload View, which is available on Pro and above. The migration delivers the capacity numbers as a reference so the monday.com admin can configure the Workload View using the same baseline data.

TimeHero CSV export does not include file attachment references or download links. We flag this gap and require the customer to manually download all attachments from within TimeHero before migration begins. Post-migration, the customer re-attaches files to the corresponding monday.com items. We provide a mapping checklist that lists each task with its attachment count so nothing is missed.

TimeHero Premium workflow templates store project structure and scheduling rules as application configuration. They cannot be exported. During discovery we inventory every workflow template the customer has built, document its structure and rule logic, and deliver a written rebuild guide with equivalent monday.com automation steps. The customer's admin rebuilds templates in monday.com's Automation Builder post-migration.

TimeHero task assignees map to monday.com Person column values. We resolve assignees by email address. If a monday.com account does not yet exist for a TimeHero user, the person column entry is created as an invited guest pending account provisioning. Team members without assignments are left blank on the monday.com item.

TimeHero priority values (High, Medium, Low) map to monday.com Status column color-coded values or Label columns. We use the same priority vocabulary to maintain consistency. The customer chooses between Status or Labels during board design based on how many priority tiers they use.