Migrate your Time Champ data

User records carry the core identity: name, email, tracking mode preference, team assignment, and license tier. The tracking-mode setting (Silent or Interactive) is preserved as a custom field on the destination. No schema differences between tiers.

Teams hold users and optionally a line-manager hierarchy on Professional and above. The Teams-N cap (2, 10, 50 by tier) is a migration scoping constraint — we flag which users exceed the cap and route them to the appropriate tier or reorganise team membership before import.

Shifts define working-hours windows, days of the week, and optional break configurations. Multi-Shift Configuration is a Professional+ feature. We preserve shift-to-user assignments and reconstruct the schedule hierarchy in the destination.

Daily attendance entries track clock-in/clock-out, overtime, and late-arrival flags. Daily and Monthly Attendance Reports are generated from these records. We map present/absent status and overtime duration directly to the destination attendance object.

Time Champ generates timesheets from auto-tracked activity. We decompose the aggregated timesheet into atomic time entries (date, duration, user, task) to avoid duplication in destination systems that manage time at the entry level. Time Claim entries are handled as a separate timesheet adjustment type.

App and URL usage logs are classified as Productive or Unproductive per the tenant's custom rules. We preserve the classification label and duration per app per day. The underlying URL-level detail is available on Professional+ and is mapped to the destination's activity tracking schema.

Screenshot capture is a tier-gated feature (Starter: none, Professional: 1-week retention, Enterprise: extended). Screenshots are binary blobs — we preserve the capture timestamp and associate it with the relevant activity log entry. Retention limits mean older screenshots may already be absent from the export.

Field employees carry GPS location logs tied to their user record and activity periods. We preserve location coordinates and timestamps. Not all destination systems support GPS as a native field; we map it to a custom address or notes field as appropriate.

Each tenant defines which apps and URLs are Productive, Unproductive, or Neutral. These are tenant-scoped custom rules — not a universal taxonomy. We map the full classification set and its assignments to equivalent custom fields or tags in the destination so the classification intent is preserved.

Reports (Daily Timesheet, Monthly Attendance, App Usage, Productivity, Late Employees, Suspicious Activity) are read-only aggregates. We extract the underlying raw data records instead and regenerate the reports in the destination system, preserving the source report configuration as a reference.

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.

Line-manager hierarchies and org charts are available on Professional+ and use a custom configuration per tenant. We map the parent-child user relationships to the destination's org structure or user-manager field.

Tenant-defined holidays are a flat list of date/name pairs. We migrate them as a standard holiday or non-working-day list applicable to the timesheet calculation in the destination.

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 — they are regenerated by the destination platform's own analytics engine.