Migrate from Team Tracker to Nutshell

Team Tracker users map to Nutshell People by email match. Username becomes the Person's name fields; email becomes the primary contact email. Active/inactive status from Team Tracker maps to Person's active flag. Users who are also clients (dual-role) create both a Nutshell Person and, if the domain matches an Account, a linked Account record.

Team Tracker Departments represent organizational units rather than companies. If the department maps to a client organization in Nutshell, it creates an Account record with the department name. Nutshell's Teams feature (separate from Accounts) handles internal user grouping — FlitStack surfaces this distinction in the migration plan before committing.

Team Tracker Projects map directly to Nutshell Deals — project name becomes Deal name, project budget maps to Deal value, and close date maps to Deal close date. Nutshell's single pipeline model applies; if Team Tracker has multiple project pipelines (per customer), each maps to a Nutshell Deal stage. Custom fields on the project (budget, billable flag, client name) migrate as Nutshell custom fields on the Deal.

Team Tracker tasks map to Nutshell Activities — completed tasks become closed Tasks in Nutshell with the completion timestamp preserved, open tasks become open Tasks with the due date mapped. Recurring tasks create Nutshell Activity records per occurrence or are consolidated into a single Task with a description note. Task status values map to Nutshell task status values by name.

Each Team Tracker time entry becomes a Nutshell Task with a subject line of '[Project Name] — Time Entry' and the duration stored as a custom field. The original start time, end time, and idle-time discard flag are preserved as custom datetime and boolean fields on the activity. Multiple time entries per day for the same project are aggregated into a single daily summary task or stored as individual entries per your specification.

Team Tracker attendance (clock in/clock out) has no Nutshell CRM equivalent. FlitStack stores attendance flags (present/absent per day) as a custom long-text field on the Person record formatted as 'YYYY-MM-DD: clock_in | clock_out | duration'. Your HR team retains access to Team Tracker for attendance reporting post-migration.

Team Tracker leave records (PTO, sick, holiday) map to a custom Leave_Balance__c field on the Nutshell Person record. FlitStack preserves the leave type, dates, and status as a serialized JSON string in the custom field — your HR tool remains the system of record for leave policy, but the data is accessible within Nutshell for context during deal reviews.

Team Tracker screenshots have no natural home in Nutshell's CRM model. FlitStack downloads all PNG/JPG screenshots, re-uploads them to Nutshell's file storage, and attaches them to the corresponding Person or Activity record as a reference — you retain the visual record without it cluttering the deal pipeline. Screenshots that contain client-identifiable information can be flagged for manual review before upload.

Team Tracker's app/website tracking logs (URLs visited, applications used) do not map to any Nutshell object. FlitStack exports these as a newline-delimited text file and attaches it to the relevant Activity or Person record as a file for reference. The raw data is preserved but requires manual interpretation — it does not surface in Nutshell's standard Activity feed.

Team Tracker calculates a productivity/activity-level percentage per user. This has no Nutshell CRM equivalent since Nutshell does not track employee productivity. FlitStack creates a custom number field (Activity_Level__c) on the Nutshell Person record and stores the most recent score for historical reference — your HR team should continue using Team Tracker for monitoring post-migration.

Team Tracker marks time entries where idle time was discarded during tracking. In Nutshell, this becomes a custom boolean field (Idle_Time_Discarded__c) on the Activity record. The flag is informational — Nutshell does not use it in any workflow. FlitStack preserves it so your team can audit time-entry accuracy post-migration.

Team Tracker allows custom fields on tasks at the Starter tier and above. These map directly to Nutshell Activity custom fields — FlitStack creates the corresponding Nutshell custom fields under the Activity entity type and copies values over. Field types (text, number, date, pick-list) are preserved through Nutshell's custom field API.

Team Tracker Express and Professional tiers support custom fields on projects (internal order numbers, client codes, billable/non-billable flags). These map to Nutshell Deal custom fields — FlitStack creates the custom field in Nutshell's Deal entity schema before writing any Deal records so all values land correctly on the first pass.

Team Tracker owner IDs on tasks and projects are resolved by email match against existing Nutshell People. Unmatched owner IDs are flagged before migration — your team either creates a Nutshell user account for that owner or reassigns records to a fallback Nutshell user. No record lands without a valid Nutshell owner reference.