Migrate from TimeHero to Microsoft Project

TimeHero tasks map to Microsoft Project tasks with Task Name, Duration (computed from work estimate), Work (in hours), Start Date (both original due date and current scheduled date as separate fields), Finish Date, Priority, and percent complete preserved. TimeHero's work estimate maps to the Work field; actual duration maps to Actual Work. We store the original due date in a custom text field (Original Due Date) and the current adaptive-scheduled date as the standard Start and Finish fields, so the destination has full planning context.

TimeHero projects and folders map to individual Microsoft Project .mpp files or Project Online project plans. Each TimeHero project folder becomes a standalone plan. Tasks within that project retain their outline structure from the CSV export. We create the project in Microsoft Project using the first task's start date as the project start date and configure the project calendar before task import.

TimeHero embeds time entry data as fields on each task: actual duration and remaining time. We parse these and write them to Microsoft Project's Actual Work and Remaining Work fields respectively. The percent complete is calculated as Actual Work divided by Total Work if TimeHero provides both. Note that TimeHero's timesheet CSV does not produce a separate time log with date-stamped entries; it produces task-level aggregates.

TimeHero recurring tasks have a recurrence rule (daily, weekly, monthly, with interval and end condition) stored as application state. We extract the recurrence pattern and regenerate future instances in Microsoft Project using the Recurring Task dialog. Each generated instance becomes an individual task in the destination plan. Past completed instances are imported as regular tasks with Actual Work and dates set.

TimeHero task assignees are individual team members. We extract the assignee list and either map them to named Microsoft Project resources (if resource management is enabled) or write them to a custom Text field (Assignee) on each task. If the destination uses resource pools, we pre-create resource records with names matched from the assignee list.

TimeHero task priority (high, medium, low) maps directly to Microsoft Project Priority field. Values are numeric in Microsoft Project (500=high, 300=normal, 100=low) and we transform accordingly.

TimeHero risk indicators are computed values (tasks flagged at risk when deadlines are at risk or capacity conflicts exist). These are not stored fields and cannot be exported directly. We capture the triggering conditions — deadline proximity, assigned capacity, scheduling conflicts — as a text note on the task and flag it using a custom Flag field in Microsoft Project so project managers can manually assess and address risk.

TimeHero uses Google and Outlook calendar events as scheduling context for its adaptive engine, but these events are not stored as primary data in TimeHero. We do not migrate calendar events. If the customer requires calendar-based scheduling in Microsoft Project, we document the connected calendar accounts during discovery and recommend importing calendar data as a separate step using Power Automate or a third-party integration.

Workload reports in TimeHero (Premium feature) show team capacity and task distribution. We extract the underlying task data for each team member and reproduce a workload view in Microsoft Project by grouping tasks by resource name or custom assignee field. True resource leveling in Microsoft Project requires resource management to be enabled in the destination plan.

The TimeHero Asana connector syncs assigned tasks from Asana into TimeHero's inbox for scheduling. These tasks appear in TimeHero as regular tasks with Asana context. We import them as standard Microsoft Project tasks without the Asana reference. If the customer maintains Asana as the task management system, the Asana-to-Microsoft Project migration is a separate engagement.