Migrate from Team Tracker to Microsoft Dynamics 365 Sales

Team Tracker user records map to Dynamics 365 Contacts. Email, name, job title, phone, and department migrate as Contact fields. Users resolved by email match against existing Dynamics 365 Users; unresolved records land as new Contacts. Any unmatched users receive a custom needs_license flag so your admin knows which records require Dynamics 365 user provisioning before the delta-pickup window closes.

Team Tracker users who will log into Dynamics 365 must be provisioned as SystemUsers. The migration flags each user record with a needs_license flag so your admin assigns Dynamics 365 licenses before granting access. Existing SystemUsers in the target environment are identified by email match; records without a match require manual provisioning in Azure Active Directory before they can access Dynamics 365.

Team Tracker projects that represent client accounts map to Dynamics 365 Accounts. Client-facing project names become Account names. Internal-only projects migrate as custom Project tables in Dataverse to preserve the hierarchical structure. We validate that client_name uniqueness across all projects maps cleanly to Account name constraints in Dynamics 365.

Team Tracker tasks map to Dynamics 365 Tasks. Subject, description, due date, priority, and status transfer as direct field mappings. Task ownership resolves by email match to the assigned Team Tracker user against Dynamics 365 Users. Unmatched task assignments are flagged for manual owner assignment in the target system after migration.

Time entries have no native Dynamics 365 equivalent. We create a TimesheetEntry custom table with columns for user (lookup to Contact), project (lookup to Account), date, duration, and notes. Original create timestamps and user attribution preserved as audit columns on the custom table for compliance and reporting continuity.

Team Tracker departments map to a custom Department table in Dataverse. Each Team Member record links to its Department via a lookup. If Dynamics 365 Business Unit isolation is required for data security, departments map to Business Units instead. We provide a mapping table showing how each Team Tracker department translates to the chosen approach.

Team Tracker screenshots re-upload to SharePoint attached to the relevant Contact or Account record. Inline screenshots in task notes are downloaded, re-hosted in SharePoint, and the share link inserted as a Note record with a reference URL pointing back to the originating entity. SharePoint storage capacity must be confirmed before migration runs for high-volume screenshot environments.

Clock-in/clock-out timestamps migrate as AttendanceRecord entries linked to the Team Member (Contact). Attendance data does not map to standard Dynamics 365 entities; a custom table preserves the full clock history for compliance or HR-adjacent reporting. The migration preserves original timestamps and links each attendance record to the correct Contact via lookup.

Team Tracker idle detection logs migrate as IdleTimeEntry records with user, date, idle duration, and discard flag. This data is reference-only in Dynamics 365 since idle tracking has no native CRM equivalent. The discard flag preserves the original include/exclude decisions from Team Tracker for audit continuity.

Team Tracker alert rules export as JSON definitions for manual rebuild in Dynamics 365 Power Automate. We deliver the exported rules with a mapping guide showing which trigger/action pairs map to Power Automate connectors. Idle-detection alerts require alternative approaches since Dynamics 365 lacks native idle-time event triggers.

Team Tracker productivity scores and reports do not have a direct Dynamics 365 equivalent. We export the underlying data (active time, task completion, app usage) to a staging table so your Power BI admin can rebuild dashboards from the migrated data.

Team Tracker custom fields and custom statuses migrate to corresponding Dataverse columns on the appropriate table. Field type mapping: text to Single-Line Text, picklists to Choice columns, numeric fields to Decimal or Whole Number, dates to Date Only or Date/Time columns.