Migrate from Team Tracker to HubSpot

Team Tracker user profiles (name, email, phone, job title, department, manager, hire date) map 1:1 to HubSpot contact properties. Team Tracker user_id stored as Source_System_User_ID__c for traceability and delta-run deduplication. Unmatched users flagged before migration. This mapping also preserves the original employee IDs for future reference and audit.

Team Tracker users who will log into HubSpot are matched by email to HubSpot user accounts. Users without HubSpot login access are migrated as contacts only. Manager hierarchy from Team Tracker preserved as a custom Manager_Email__c property on the contact record.

Time entries (clock-in timestamp, clock-out timestamp, duration in minutes, billable flag, project link, task link) have no native HubSpot equivalent. Each field becomes a custom property on the associated contact or deal. Duration aggregates migrate as Total_Hours_Tracked__c for reporting continuity.

Team Tracker projects representing billable client work map to HubSpot Deals (name, budget, status, start date, end date, manager). Internal or non-billable projects map to a HubSpot Custom Object named Project. Project-to-deal mapping decision documented in the pre-migration plan. All mapping decisions are reviewed with your team during the discovery phase.

Team Tracker tasks under a project map to HubSpot Deal Tasks (subject, status, priority, due date, assignee). Task descriptions and custom fields become custom properties on the deal. Task status values map to HubSpot pick-list values per the migration plan.

Attendance records (date, status: present/absent/leave, leave type) migrate as custom datetime and pick-list properties on the HubSpot contact. Leave balances and accruals have no HubSpot equivalent and are archived as custom read-only fields for HR reference. These archived fields retain historical leave data for compliance and reporting.

App and website tracking data (URLs visited, app usage duration) has no meaningful HubSpot CRM equivalent and cannot migrate due to privacy and GDPR considerations. Aggregate productivity scores migrate as Productivity_Score__c custom number property for reporting. These metrics help maintain visibility into employee performance trends.

Screenshots captured by Team Tracker do not migrate to HubSpot. HubSpot is a customer relationship management platform, not an employee monitoring tool. Screenshots are excluded from the migration due to GDPR data minimization requirements and the absence of a native storage equivalent in HubSpot's data model.

Team Tracker Express and Professional custom user profile fields migrate as HubSpot custom contact properties. Field types map: text to single-line text, number to number, pick-list to pick-list, date to date. Custom property names use HubSpot's snake_case naming convention. The naming convention ensures consistency across all imported fields.

Team Tracker custom fields on projects and tasks become custom properties on the corresponding HubSpot Deal record. Type-aware mapping applied: currency fields to HubSpot currency, percentages to number with % formatting, URLs to single-line text. These mappings ensure that all financial and contextual data renders correctly in HubSpot reports.

Leave policies, holiday calendars, and accrual balances have no HubSpot equivalent. These HR data points are archived as read-only custom fields for reference but cannot drive HubSpot workflow triggers. Although they cannot automate processes, retaining them provides a historical HR record within HubSpot for compliance audits.

Team Tracker departments map to HubSpot Teams for access-control purposes. If HubSpot Teams are not configured, departments migrate as a Department__c custom pick-list property on contacts for segmentation and reporting. This dual approach ensures that departmental context is preserved for both permissions and analytical segmentation.