Migrate from Time Champ to Asana

Time Champ user records (name, email, tracking mode preference, team assignment, license tier) map to Asana members. The Silent vs Interactive tracking-mode setting from Time Champ is preserved as a custom text field tc_tracking_mode__c on the Asana member for audit reference. Users must be provisioned in Asana before any cross-platform lookup can resolve task assignments or team memberships during migration.

Time Champ teams (users and optional line-manager hierarchy on Professional+) map to Asana Teams. We resolve the parent-child user relationships from Time Champ's org hierarchy and map them to Asana Team membership. If the customer exceeds Asana's free-tier seat limit for Teams (Starter caps at one Team; Starter trial allows three Teams), we route the migration to the paid Asana tier during scoping.

Time Champ generates timesheets from auto-tracked activity windows. We decompose each aggregated timesheet into atomic time entries with date, duration, user, and project/task association. Asana's native time tracking requires the paid Timesheets add-on ($10/user/mo); we verify this add-on is active before migration and warn if it is not. Time Claims (employee-initiated corrections to auto-tracked time) migrate as time entry line items with a tc_time_claim flag.

Time Champ attendance records (daily clock-in/clock-out, overtime, late-arrival flags) have no native Asana equivalent. Asana has no attendance or time-clock module at any tier. We export attendance records as a structured CSV (user, date, clock_in, clock_out, overtime_hours, late_arrival_flag) for the customer to load into their HRIS, payroll system, or a separate attendance tool. Attendance data is not deleted — it is preserved as a reference export with a rebuild recommendation for a dedicated attendance platform.

Time Champ shifts define working-hours windows, days of the week, and break configurations. Multi-Shift Configuration is a Professional+ feature. Asana has no native shift scheduling or working-hours configuration. We export shift definitions as a structured JSON file (shift_name, user, start_time, end_time, days_of_week, break_config) with a manual-setup checklist for the customer's admin to configure in their preferred scheduling or calendar tool.

Time Champ app and URL usage logs with tenant-scoped Productive/Unproductive classifications have no Asana equivalent. Asana does not track app usage or website activity. We export activity logs as a structured CSV (user, date, app_name, url, duration_seconds, productivity_classification) ordered by user and date for the customer's reference. The productivity classification ruleset (which apps are tagged Productive/Unproductive/Neutral) is exported separately as a configuration reference CSV.

Screenshots captured in Time Champ are binary blobs with a capture timestamp associated with an activity window. Asana has no attachment or storage mechanism for screenshot surveillance data. We export screenshot metadata (capture_timestamp, user, associated_activity_window_start, associated_activity_window_end, tc_blur_flag) as a structured CSV if retention is still within the plan's window. If the Professional-tier 1-week retention has already expired, we document this gap in the data completeness report before migration begins.

Field employee GPS location logs tied to user records and activity periods have no native Asana equivalent. We export location data as a structured CSV (user, timestamp, latitude, longitude, associated_activity_window) for the customer's reference. If the destination use case requires location tracking, we recommend a dedicated field workforce management or GPS attendance tool post-migration.

Time Champ's Productive/Unproductive app classification rules are entirely tenant-scoped custom definitions. These do not map to any Asana field because Asana has no native productivity classification system. We extract the full classification ruleset (app_name, url_pattern, classification_label) as a structured CSV and deliver it as a manual-setup checklist for the customer's admin to recreate in any classification tool they adopt post-migration.

Time Champ tenant-defined holidays are a flat list of date/name pairs. These do not have an Asana equivalent because Asana has no native holiday configuration for timesheet calculations. We export holidays as a structured CSV (holiday_date, holiday_name) and flag it for manual entry into the customer's HRIS or payroll tool.

Time Claims are employee-initiated corrections or additions to auto-tracked time. We treat them as a timesheet line-item type and migrate them alongside standard time entries with a tc_time_claim flag set to true. The Asana Timesheets add-on must be active for these to land as billable or trackable entries.

Time Champ burnout early-warning alerts, attrition risk signals, and real-time status notifications are computed at runtime from activity patterns. These are not persistent data records and cannot be migrated. We deliver a written inventory of active alert rules (alert_type, trigger_condition, notification_recipient, notification_channel) for the customer's admin to evaluate recreating in Asana Rules or a dedicated people analytics tool.