Migrate from Time Champ to Jira

Time Champ Users map to Jira User accounts via email as the dedupe key. The user's Time Champ tracking mode (Silent or Interactive) and team assignment become Jira User custom fields. Jira Global Permissions must grant the migration user the Jira Software Admin or Jira Admin role to create users; existing users resolve by email match and do not require re-provisioning.

Time Champ Teams map to Jira Groups. Jira's group membership drives Project role assignments (Developers, Testers, Project Admins) during Project provisioning. The Teams-N cap (2, 10, 50 by Time Champ tier) is validated against the Jira plan's group limit; if the customer exceeds the cap, we flag a consolidation step before migration. Jira Cloud Free caps at 10 groups.

Daily attendance entries (clock-in, clock-out, overtime, late-arrival flags) decompose into Jira Issue records of a custom Issue type (Absence Record). Each daily record becomes one Issue with a date custom field, status custom field (Present, Absent, Late, Overtime), and duration. We create the Absence Record Issue type and relevant custom fields during Jira schema setup before migration begins.

Time Champ Shifts (working-hours windows, days, break configurations) do not have a native Jira equivalent. Multi-Shift Configuration on Professional+ requires a decision: either map to Jira Sprints (Sprint Start, Sprint End) if the customer uses Scrum, or store shift hours as a custom User field (shift_start__c, shift_end__c, shift_days__c) and a Project component for break periods. We present both options during scoping and the customer chooses based on their Jira board type.

Time Champ timesheets aggregate auto-tracked activity into a summary. We decompose each timesheet into atomic Worklog records: each Worklog carries the original date, duration in seconds, user reference, and a link to the target Jira Project and Issue. If Time Champ records a timesheet against a Project/Task label, we resolve that label to a Jira Issue key during migration. Jira's Worklog API requires the parent Issue to exist, which enforces the Project and Issue creation order before Worklog ingestion.

App and URL usage logs map to Jira Worklog records on a synthetic Project Issue (e.g., a recurring Weekly Activity Issue per user) when no explicit task is associated. The Productivity Classification label (Productive, Unproductive, Neutral) migrates as a Jira custom field on the Worklog issue. URL-level detail is not preserved; we carry app name and classification label only, consistent with Time Champ's export format and Jira's custom field constraints.

Time Champ's tenant-scoped Productive/Unproductive app classification rules have no universal Jira equivalent. We create a Jira custom field (e.g., tc_productivity_classification__c) as a Select List with the customer's existing classification labels extracted as options during discovery. Each app/URL row in Time Champ's classification list becomes a custom field option rather than a mapped value, since the semantic labels are tenant-defined and must be manually recreated in Jira's field context.

Screenshots are binary blobs extracted from Time Champ with their capture timestamp preserved as the Jira attachment creation date. We associate each screenshot with the Jira Issue that corresponds to the time window during which it was captured. Starter plan has no screenshots; Professional retains for 1 week only. We check export eligibility early and warn if retention has aged out, in which case those activity windows appear as blank periods with no visual evidence.

Field employee GPS location logs (coordinates and timestamps) migrate as a Jira User custom field (tc_last_location__c storing the most recent timestamp and coordinates). Jira does not support native GPS tracking; we preserve the data as a structured custom field on the User profile so it is available for admin reference but does not appear in the standard Jira Issue view.

Time Claims (employee-initiated corrections or additions to auto-tracked time) migrate as Jira Issue records of a custom Issue type (Time Claim). Each claim carries the claim date, original entry, claimed adjustment, reason text, and status. Jira's Issue workflow states map to the Time Champ claim statuses (Pending, Approved, Rejected) as Jira workflow transitions.

Time Champ line-manager hierarchies map to Jira Group membership with Project role assignments (e.g., Employee reports to Manager via group membership, and the manager has a Jira Project role of Team Lead). We preserve the parent-child relationships as a CSV deliverable alongside the migration for the customer's admin to configure in Jira's Group management if the relationship needs to drive specific permission schemes.

Tenant-defined holidays migrate as a Jira custom field (tc_holidays__c) stored as a Multi-select List on the Project. Each holiday date and label becomes a multi-select option. Jira does not have a native calendar-of-holidays feature; this custom field enables filtering in Jira dashboards and reporting against non-working days.