Migrate from Time Champ to monday Work Management

Time Champ Users (name, email, tracking mode, license tier) map to monday.com Workspace Members. We use email as the dedupe key. The monitoring-mode setting (Silent vs Interactive) has no monday.com equivalent and is not migrated; we include it in the User export as a reference field for the customer's compliance team. The tracking-mode preference becomes a custom column label in the exported user CSV rather than a native monday.com field.

Time Champ Teams (up to 2 on Starter, 10 on Professional, 50 on Enterprise) map to monday.com Workspaces or Board Groups depending on the customer's org structure preference. We scope the team count during discovery and flag whether it exceeds the destination plan's workspace cap. Teams with a line-manager hierarchy map to monday.com's person column assignments and group-by-person views. If the customer has more than 50 teams, we recommend a consolidation step before migration.

Time Champ Shifts define working-hours windows, days of the week, and break configurations. monday.com has no native shift-management object, so we reconstruct shift logic using date columns (start time, end time, break duration) and status labels (On Shift, Off Shift, Break). Multi-shift users receive multiple monday.com Items or item groups with distinct date ranges. The customer configures these as recurring calendar events or automated status updates post-migration.

Time Champ daily attendance records (clock-in, clock-out, overtime, late-arrival flags) map to monday.com Items in an Attendance board with date columns for clock-in and clock-out and a status column for Present/Absent/Late/Overtime. We preserve the overtime duration and late-arrival flag as separate numeric columns. Monthly and daily attendance reports from Time Champ do not migrate as reports; we deliver the underlying raw attendance records so the customer rebuilds aggregations as monday.com dashboards.

Time Champ auto-tracks timesheets from activity logs, combining idle time, active time, and task associations into aggregated entries. We decompose each timesheet into atomic time entries (date, user, duration, associated project or task label) and create monday.com Items in a Time Tracking board with the time tracking column enabled (Pro+ feature). If the customer uses Time Champ's Time Claims feature, we include them as additional time entry Items with a Time Claim status label. This decomposition prevents duplication when the customer later queries total hours by person or by project.

Time Champ Activity Logs (app name, URL, category, duration per day) are preserved as a structured CSV export rather than a monday.com native object because monday.com has no app-usage or URL-tracking schema. We include the tenant-defined Productivity Classification (Productive/Unproductive/Neutral) per app in the CSV. The customer can optionally create a monday.com board for Activity Reference with app name, category label, and average duration columns, but this is a manual setup step after migration.

Time Champ screenshots (Professional: 1-week retention; Enterprise: extended with blur controls) have no monday.com equivalent. We export all accessible screenshots as timestamped binary files in a file archive keyed by user and date. The customer receives a data completeness report noting any screenshots that aged out of retention before the export window. Screenshot timestamps migrate as reference dates in the user activity export CSV.

Time Champ GPS location logs for field employees map to a location reference CSV (coordinates, timestamp, user) rather than a monday.com native object because monday.com does not support GPS or geolocation fields on Items. The customer can optionally attach the location CSV as a file to a Field Operations board for reference, but this is a post-migration manual step. We flag this gap in the data completeness report.

Time Champ's tenant-defined app classification rules (Productive, Unproductive, Neutral per app or URL) are tenant-scoped and have no universal mapping to any monday.com taxonomy. We export the full classification ruleset as a structured CSV (app name, URL pattern, category label) and deliver it as a manual-setup checklist for the customer's monday.com admin. The customer recreates the categories as monday.com Tags, status labels, or a separate Classification board as preferred.

Time Champ Reports (Daily Timesheet, Monthly Attendance, App Usage, Productivity, Late Employees, Suspicious Activity) are read-only aggregates computed from raw data. We migrate the underlying raw data records (attendance entries, time entries, activity logs) and deliver a report inventory listing every Time Champ report with its configuration parameters. The customer or a monday.com partner rebuilds each report as a monday.com Dashboard using the imported board data as the source.

Time Champ alerts (burnout early-warning, attrition risk, suspicious activity, summary emails) are computed at runtime from activity pattern analysis. They are not persistent data records and cannot be migrated. We deliver an alert inventory listing every active alert type, its trigger condition, and its action. The customer rebuilds equivalent monitoring using monday.com Automations (Standard+ plans: 250 actions/month; Pro: 25,000 actions/month) or integrates a third-party monitoring tool.

Time Champ tenant-defined holidays (date and name pairs) map to a monday.com Holidays board with a date column. The customer recreates holiday entries as recurring calendar events or marks them in a dedicated non-working-day board that they reference when reviewing attendance and timesheet data.