Migrate from Team Tracker to HighLevel

Team Tracker member profiles map to HighLevel contacts. Email, phone, job title, address, and system ID transfer directly. Role and department migrate as custom fields (Role__c, Department__c) on the contact. Team Tracker timezone stored as Timezone__c custom field. Custom fields preserve original data while enabling HighLevel-native reporting.

HighLevel has no native time-entry object. FlitStack creates a TimeEntry__c custom object in HighLevel with fields for clock-in datetime, clock-out datetime, idle minutes, break minutes, total hours, project reference, and notes. Original timestamps and owner preserved. Custom object must be configured in HighLevel before migration.

Team Tracker projects map to HighLevel opportunities. Project name becomes opportunity name, status maps to pipeline stage via value mapping, start and end date map to created date and close date, estimated hours stored as Estimated_Hours__c custom field, client name stored as Client_Name__c custom field.

HighLevel has no task-list entity. Team Tracker task lists migrate as a TaskList__c custom object linked to the parent opportunity via a lookup relationship. Custom fields on the task list (custom fields from Team Tracker Express/Professional tiers) become custom fields on the custom object. Task list status values map to a Status__c pick-list.

Individual tasks within task lists map to HighLevel tasks. Task name becomes subject, description maps to notes, due date maps to due date, assigned user resolves by email to HighLevel user, status maps via value mapping. Custom task fields become custom fields on the HighLevel task.

HighLevel has no native attendance model. Daily attendance records (date, member, status: present/absent/late/half-day, overtime hours) migrate as Attendance__c custom object linked to the contact. Overtime flag stored as Overtime_Hours__c custom field. This custom object requires setup in HighLevel's schema before migration begins, ensuring all attendance data transfers correctly without loss.

Team Tracker departments have no direct equivalent in HighLevel. Department name stored as Department__c pick-list custom field on the contact. If departments have managers, manager assignment stored as Manager__c lookup field on the contact. This approach maintains organizational hierarchy while allowing filtering and reporting by department within HighLevel's native tools.

Team Tracker tracks field-employee locations. Location name stored as Location__c text custom field on the contact for reference. GPS coordinates if captured stored as Location_Coordinates__c text field. This preserves location context for field service teams, enabling route optimization and territory management within HighLevel's reporting capabilities.

Team Tracker leave records (type, start date, end date, status) migrate as a Leave__c custom object linked to the contact. Leave type stored as Leave_Type__c pick-list. Status maps via value mapping (approved/pending/rejected). This preserves complete leave history and enables HR reporting on attendance patterns within HighLevel's dashboard.

Team Tracker owner resolved by email match against HighLevel user accounts. Unmatched owners flagged before migration for team invitation or fallback assignment. System ID stored as Source_User_ID__c on the contact for traceability. This ensures audit trails remain intact and ownership assignments are preserved throughout the migration process.

Files attached to tasks, time entries, or projects are re-uploaded to HighLevel's file storage linked to the relevant record. File size limits from HighLevel apply (25MB per file). Inline images in notes downloaded and rehosted. Large files exceeding HighLevel's limits are flagged for manual review before migration completes.

Team Tracker alert rules (overtime alerts, idle-time notifications, leave approval workflows) do not migrate. FlitStack exports rule definitions as a JSON reference document that your HighLevel admin uses to rebuild equivalent automations in HighLevel's workflow builder. This reference preserves the logic and triggers from your existing rules for manual reconfiguration in HighLevel.