Migrate from Time Champ to Microsoft Project

Time Champ Users map to Microsoft Project Resources. The User's name, email, and team membership map to Resource Name, Resource ID, and the team membership maps to a Resource Group in Project. The tracking-mode preference (Silent or Interactive) from Time Champ does not have a Project equivalent — we flag it as a custom Resource field (tc_tracking_mode__c) for admin reference. Max Units per resource is set to 100% unless the customer's shift configuration implies overtime, in which case we set a custom overtime flag on the resource.

Time Champ Teams (capped at 2 on Starter, 10 on Professional, 50 on Enterprise) map to Microsoft Project Resource Groups. Each team becomes a named Resource Group in the destination, and all resources belonging to that team are assigned to the group. We flag team counts against the destination plan cap during scoping to prevent silent truncation of group assignments.

Time Champ Shifts define working-hours windows per user with configurable days of the week and break periods. Multi-Shift Configuration is a Professional+ feature. We translate each shift into a Microsoft Project base calendar entry (Working Days and Working Hours per day) and assign the calendar to the corresponding resources. Break periods map as non-working time on the calendar. Multi-shift users require multiple calendars or a custom calendar with split working hours — we document the configuration step during setup.

Time Champ Attendance Records track clock-in/clock-out, overtime, and late-arrival flags per day per user. We decompose attendance records into Microsoft Project calendar exceptions: late arrivals map as partial-day non-working exceptions with a comment flag; overtime days map as overtime exceptions on the resource calendar; and absent days map as full-day non-working exceptions. The original late-arrival and overtime duration values are stored in custom fields on the task or resource for admin review.

Time Champ generates aggregated timesheets from auto-tracked activity. We decompose each timesheet into atomic time entries: date, duration, user, and task association. If the customer has an existing task structure in Project (or creates one during migration planning), each time entry maps to a Task Assignment with the hours value. If no task structure exists, we create placeholder tasks named by project and date and assign hours against them to preserve the hour totals.

Time Champ Time Claims are employee-initiated corrections or additions to auto-tracked time. We migrate Time Claims as separate task assignment entries with a custom flag (tc_time_claim__c = true) and the original claim duration. Claims without an approved status map as Proposed assignments in Project rather than Confirmed, preserving the review workflow for the project manager to action post-migration.

Time Champ Activity Logs capture app-level usage classified as Productive or Unproductive per the tenant's custom rules. Microsoft Project has no native app-usage tracking. We map app-level summary data (total hours per app per day, classification label) to a custom Task field (tc_app_usage__c) and attach the classification label as a Task Note. The customer uses this data to manually annotate tasks or as a reference for future project estimation. URL-level detail is not migratable as it has no structural equivalent.

Time Champ's Productive/Unproductive/Neutral classification system is entirely tenant-defined and has no universal taxonomy. Microsoft Project's custom fields support Text, Number, Date, Flag, and Lookup Table types. We extract the full classification ruleset (app name, URL pattern, category label) as a structured CSV and deliver it as a manual-setup checklist for the customer to configure as a lookup table on the custom Task field in Microsoft Project. There is no automatic mapping because the semantic labels differ per tenant.

Field employees carry GPS location logs tied to their user record and activity periods. Microsoft Project does not have native GPS or location tracking. We preserve location coordinates and timestamps in a custom Resource field (tc_location__c) as a text-formatted string. The customer uses this for auditing purposes or for manual site assignment during project planning. Not all teams require this; we confirm inclusion during scoping.

Screenshots are binary blobs with tier-gated availability (Starter: none, Professional: 1-week retention, Enterprise: extended with blur controls). Microsoft Project has no screenshot or visual-activity storage. We do not migrate screenshots as records. If the customer requires proof-of-work documentation, we recommend exporting screenshots to a separate file share and linking them to tasks via a URL in a custom Task field. We warn customers with Professional accounts if the 1-week retention window has already elapsed before migration scoping begins.

Time Champ Holiday records are tenant-defined date/name pairs. We migrate them as global non-working-day calendar exceptions in Microsoft Project's base calendar. The holiday name maps to the Exception Name field so project managers see which holiday applies to each non-working day.

Time Champ Reports are read-only aggregates generated from raw attendance and activity data. We do not migrate reports as records because they are derivative of source data we are already migrating. We instead migrate the underlying raw records (attendance, timesheets, activity logs) and deliver the report configuration parameters (report type, date range, user filter) as a structured handoff document. The customer rebuilds reports in Microsoft Project using the migrated data or exports to Power BI for analytical views.