Migrate from Team Tracker to Odoo CRM

Team Tracker members hold name, email, phone, and role data that maps directly to Odoo's res.partner. Email addresses are unique identifiers for de-duplication during import. If Team Tracker's members function as employees, a separate hr.employee record is also created — FlitStack AI flags dual-role members for your Odoo admin to confirm.

When Team Tracker members represent employees rather than external contacts, hr.employee records are needed in Odoo HR. FlitStack AI creates the employee record with name and user linkage, and preserves the Team Tracker member_id as a custom field (team_tracker_member_id) on the employee for traceability and delta-run matching.

Team Tracker's Team object (name, manager, parent_team) maps to Odoo's hr.department. Odoo departments are hierarchical; parent_team resolves to parent_path in hr.department. Team-level custom fields migrate as custom fields on the department record. Note that Odoo department is not a CRM-specific object — your Odoo admin may prefer crm.team for sales team routing.

Team Tracker projects map 1:1 to Odoo project.project. Project name, description, start_date, end_date, status, and user_id (project manager) transfer directly. The project privacy_visibility setting defaults to 'employees' in Odoo and can be adjusted per project post-migration. Additionally, the active flag, color index, and tags from Team Tracker map to Odoo's active boolean, color field, and project.tags many2many relation respectively — these require the tags to exist in Odoo before migration or be created during the schema setup phase.

Task records map to project.task with name, description, priority, project_id, user_id (assigned to), date_deadline, and create_date preserved. The key mapping challenge is custom_status — Team Tracker's freeform status values map to project.task.stage_id via value-by-value mapping per project. FlitStack AI generates the Odoo stage names from your Team Tracker custom_status vocabulary.

Team Tracker's custom_status field stores freeform text values like 'In Progress', 'Needs Review', 'Blocked'. These are not tied to a formal stage schema. FlitStack AI creates Odoo Kanban stages named from your actual custom_status vocabulary, scoped to each project, so the stage names match your original workflow labels. Probability and fold settings are applied as Odoo defaults.

Team Tracker time entries (date, duration_hours, billable, task_id, user_id, description) map to Odoo analytic lines linked to the corresponding project.task via project_id and task_id. Note that Odoo's native timesheet model (project.timesheet) expects a different entry format — analytic lines preserve all data but a timesheet-compatible project configuration is recommended post-migration.

Team Tracker attendance records include check_in, check_out, location, device_type, apps_screamshotted, websites_visited — data that does not fit Odoo hr.attendance's check-in/check-out model. FlitStack AI creates custom fields on hr.employee (check_in_custom, check_out_custom, location_custom, device_type, productivity_metrics) to preserve the full record. Odoo's standard hr.attendance can be configured independently if needed.

Team Tracker allows custom fields on member records (priority_level, alert_enabled, alert_threshold, etc.). Odoo has no pre-built equivalent for most of these. FlitStack AI creates matching custom fields on res.partner (and optionally hr.employee) using Odoo's ir.model.data approach, preserving field type, selection options, and default values. Field metadata is included in the migration plan.

Task-level custom fields in Team Tracker (custom_field_1 through custom_field_n) require custom field creation in Odoo. FlitStack AI inspects the Team Tracker field schema, creates matching fields on project.task using Odoo field types (char, selection, date, float, etc.), and includes the full field list in the Odoo Studio setup guide delivered with the migration plan.

Team Tracker notes and file attachments attach to the relevant parent record (member, task, project). They migrate as ir.attachment records in Odoo with res_model and res_id pointing to the mapped Odoo record. File content is re-uploaded to Odoo's filestore. Inline images in notes are extracted and re-hosted as attachment binaries.

If Team Tracker teams use Tasks to store informal lead or deal records (deal name in task title, deal value in a custom field), FlitStack AI surfaces this pattern during the pre-migration audit. These records are migrated to crm.lead with the mapped field values, and the mapping plan flags which tasks to reclassify as leads versus project work.