Migrate from Team Tracker to Twenty CRM

Team Tracker employee records map directly to Twenty's People object. Email, phone, job title, and name fields translate 1:1. Custom employee properties (idle-time thresholds, monitoring tier, department) migrate as custom fields on the Person record. Employee records without a customer-facing email or role are flagged for review before migration.

If Team Tracker stores any company or client data alongside employee records, it maps to Twenty's Companies object. Company name, domain, and any billing or industry properties translate as direct fields or custom fields. Team Tracker has no native Account model — companies must be sourced from your own records or a secondary export.

Team Tracker task assignments map to Twenty Tasks linked to the corresponding Person record. Task name, description, due date, and assignee (via email match to Twenty Members) migrate directly. Custom status values from Team Tracker Express/Professional become a custom pick-list field on the Task object.

Timesheet rows (date, duration, associated task name) convert to Task records in Twenty with a custom datetime field for the work date and a custom number field for hours logged. Each timesheet entry becomes a separate Task record linked to the Person who logged it, preserving audit-level timesheet detail.

Clock-in and clock-out timestamps from Team Tracker's attendance module migrate as custom datetime fields on the Person record — Clock_In_Time__c and Clock_Out_Time__c — or as a custom Relation field linking to a dedicated Attendance object if you prefer a separate tracking entity.

Idle-time percentage and activity-level score from Team Tracker Professional migrate as custom number fields (Idle_Time_Pct__c, Activity_Score__c). These are descriptive metrics — useful for internal reporting in Twenty but not tied to any CRM workflow. The values are preserved as reference data for historical performance analysis, even though Twenty has no native productivity-scoring module.

Team Tracker screenshot records (image files with timestamps) have no analogue in Twenty CRM. Screenshots are re-uploaded to Twenty as Notes with a timestamp and a link back to the Person record, but the surveillance metadata (blurriness score, window title) is discarded. Screenshot files are stored in Twenty's file attachment limit.

Leave balances and holiday entries from Team Tracker Express/Professional migrate as custom number or select fields on the Person record (Leave_Balance__c, Leave_Type__c). Individual leave events become separate Task records linked to the Person, with a custom leave-type pick-list field to categorize each entry by type (annual, sick, unpaid).

Team Tracker department or group assignments map as a custom select field on People (Department__c). This preserves the organizational hierarchy from Team Tracker and allows you to filter or segment Twenty records by department. If Twenty introduces a native Team construct in a future release, the custom field can be migrated to the native construct at that time.

Any custom fields defined on the Employee object in Team Tracker Express or Professional are read during the audit phase. Each custom property is created as a matching custom field in Twenty's Settings → Data Model before the migration run, with the same field type (text, number, date, select, multi-select).

Team Tracker alert rules (idle-time notifications, clock-in reminders, access-blocking triggers) do not migrate. We export the rule configuration as a structured JSON reference document so your Twenty admin can rebuild equivalent triggers in Twenty's workflow builder, which supports time-based and field-change triggers.

Team Tracker productivity reports and employee analytics have no direct equivalent in Twenty. The underlying data (task completion rates, hours logged) migrates into Twenty Tasks and custom fields, where you can build new Views and use Twenty's built-in charting for reporting.