Migrate from Team Tracker to Freshsales

Team Tracker user records (name, email, phone, job title, department) map 1:1 to Freshsales Contacts. Owner assignment in Freshsales is resolved by email match against Freshsales user accounts. Inactive users without a CRM contact role are archived in Freshsales as inactive Contacts with a Source_System__c flag.

Team Tracker users categorized as field employees who also appear in external client-facing records map to Freshsales Leads. If the employee record contains a client association, that record additionally creates an Account and a Deal. Freshsales Lead Status defaults to 'New' unless the Team Tracker record contains a status field.

Team Tracker company or client records map to Freshsales Accounts. Account.Name, industry, website, employee count, and billing address fields map directly. Multi-office clients require manual consolidation in Freshsales or creation of child Accounts under a parent Account record using the Parent_Account__c lookup.

Team Tracker projects map to Freshsales Deals — Project.name becomes Deal.name, and Project.budget or total logged hours become Deal.amount (using an hourly rate if provided). Project.stage maps to Freshsales pipeline stage values via value_mapping. Projects without a linked client are attached to a placeholder Account.

Team Tracker tasks with a due date map to Freshsales Tasks. Time-logged tasks with start and end timestamps map to Freshsales Events. Task.subject, description, status, and priority map to the corresponding Freshsales fields. Tasks without time data become open Tasks in Freshsales.

Team Tracker time entries have no native Freshsales equivalent. Total hours logged per project become a custom Number field (Total_Logged_Hours__c) on the corresponding Deal. Detailed time-entry history is exported as a CSV and attached to the Deal as a File. Freshsales Enterprise may use custom modules for granular time tracking if reporting requires.

Clock-in/clock-out records, idle time, and break duration logs in Team Tracker have no Freshsales equivalent. These records are exported as a CSV archive and attached to the relevant Contact or Account for audit purposes. Freshsales is a sales CRM, not an HR or workforce-monitoring platform.

Website/app usage logs, screenshot captures, and productivity scores in Team Tracker do not map to any Freshsales object. These are retained as an exported archive. Freshsales records engagement signals like email opens and page visits through Freddy AI, which is sourced differently and cannot consume Team Tracker activity logs directly.

Team Tracker custom fields on user records (e.g., employment_type, cost_center, certifications) map to Freshsales custom fields on Contact. Field type is preserved where possible: pick-list values become Freshsales pick-list fields, text fields remain text. Custom fields require Freshsales Pro or Enterprise depending on field type.

Team Tracker custom fields on projects (e.g., project_type, client_tier, billing_model) map to Freshsales Deal custom fields. Projects that used multiple custom properties heavily may trigger Freshsales Enterprise-level custom module requirements if the Deal object exceeds field limits on Pro. The migration audit phase identifies which project fields exceed Pro limits, ensuring accurate Freshsales plan recommendations before migration begins.

Team Tracker alert rules (e.g., overtime triggers, idle-time alerts, break reminders) cannot migrate to Freshsales. They must be rebuilt using Freshsales Workflow Designer on the Pro or Enterprise plan. FlitStack exports the rule definitions as a structured JSON document for the Freshsales admin to reference during rebuild.

Team Tracker departments map to Freshsales Territories on Pro+ plans, or to a custom pick-list field (Department__c) on Contact and Deal objects. If the department structure is complex (nested groups), a custom module or Salesforce-style parent-territory setup in Freshsales Enterprise may be required.