Migrate from Team Tracker to Pipedrive

Team Tracker User maps directly to Pipedrive Person. The user's name, email, phone, job title, and department transfer as Person fields. The user's department or role property becomes a custom field on the Person record. Owner assignment in Pipedrive is resolved by email match against existing Pipedrive users — if no match exists, the record is assigned to a designated fallback user and flagged for manual reassignment.

Team Tracker Tasks map to Pipedrive Deals when they represent billable work units or project milestones. The task name becomes the Deal name, the estimated or logged hours become a custom currency field, and the task status (active, paused, completed) maps to the corresponding Pipedrive Deal stage. Tasks used purely for monitoring (e.g., idle-time triggers) have no Deal equivalent and are dropped or documented in an audit field.

Time Entries map to Pipedrive Activities (type='task' or 'call') with original start time, end time, and duration preserved in custom fields (Original_Start_Time__c, Duration_Minutes__c). The linked Task becomes the linked Deal. The monitored employee's user record becomes the Activity's subject Person. This preserves the full work-history timeline inside Pipedrive's activity feed for reporting continuity.

Screenshots are downloaded from Team Tracker's storage and re-uploaded to Pipedrive as File attachments linked to the Person record of the monitored user. Each file is named with the Team Tracker timestamp convention (e.g., screenshot_2025-03-15_14-32-00.png) to preserve traceability. Pipedrive's 25MB per-file limit is enforced — screenshots exceeding this are skipped and logged in the audit report.

Website and app usage logs (URL, duration, category) have no native Pipedrive equivalent. We aggregate the most-active domains per user into a custom text field (Top_Sites__c) on the Person record as a JSON array. If granular reporting is needed, the full log exports as a separate CSV attachment on the Person record for reference without cluttering the CRM UI.

Team Tracker Departments map to Pipedrive Organizations when the department functions as a business unit with external contacts. The department name becomes the Organization name, and the department head's contact details become the primary Person linked to that Organization. For purely internal departments with no external counterpart, the mapping is skipped and the department name is stored as a custom field on each Person.

Team Tracker custom properties on users (e.g., employment_type, clearance_level, cost_center) are migrated as Pipedrive custom fields on the Person object. Each custom field must be pre-created in Pipedrive via POST /personFields before migration — we generate a field-creation checklist from the source schema as part of the migration plan. Pick-list values are mapped value-by-value using Team Tracker's stored options.

Task-level custom properties (e.g., billable_rate, project_code, client_id) transfer as Pipedrive Deal custom fields. These require pre-creation in Pipedrive via POST /dealFields. For fields referencing external IDs (client_id, project_code), we store the raw value as a text field and flag whether it should be re-linked to a Pipedrive Organization or Deal after migration.

Idle time records are a Team Tracker-specific monitoring construct with no Pipedrive equivalent. We aggregate total idle minutes per user per day and store the figure as a custom integer field (Idle_Minutes_Daily__c) on the Person record. The raw idle-time log entries are not individually transferred as they represent internal productivity data that does not map to CRM activity semantics.

Mobile GPS logs from Team Tracker's field-employee tracking mode map to Pipedrive custom address or text fields on the Person record. The most-recent location is stored as a formatted address string (Last_Location__c). Historical location data is exported as a time-series CSV and attached to the Person record as a reference file — not as individual CRM fields, which would cause schema bloat.

Team Tracker workflows — idle-time alerts, screenshot triggers, website block rules, overtime notifications — have no equivalent in Pipedrive's automation engine and are not migrated. We provide a structured export of all workflow definitions (trigger conditions, actions, thresholds) as a JSON reference file that your Pipedrive admin can use to rebuild equivalent automations in Pipedrive's automation builder.

Leave and holiday records from Team Tracker's HR module (available on Express and Professional tiers) have no Pipedrive equivalent as Pipedrive is a sales CRM, not an HR system. Leave balances are stored as a custom text field (Leave_Balance__c) on the Person record for reference. Full leave history is exported as a CSV attachment. Teams requiring leave tracking post-migration should use a dedicated HR tool.