Migrate from Team Engine to Recruit CRM & ATS

Team Engine Job records map to Recruit CRM Positions. We preserve title, description, location, requirements, posting status, and post-date. Recruit CRM uses a Position object for internal postings and a Job Order object for client-facing placements—during scoping we determine whether Team Engine jobs are internal crew roles (Position) or client orders (Job Order) and map accordingly. Closing date maps to the close date field on the destination record.

Team Engine Applicant records map directly to Recruit CRM Candidate records. We preserve name, contact information, application date, status (applied, screening, hired, rejected), source, and rejection reason. Records in Applied or Screening status map to the Recruit CRM candidate pipeline with the corresponding stage. Hired applicants may be flagged for Contact record creation in Recruit CRM's CRM layer depending on whether the customer wants placement tracking.

Team Engine Employee records map to Recruit CRM Contacts. We preserve name, contact details, hire date, and group membership. Team Engine hire dates map to Recruit CRM's date_custom_field_hire or a custom hire_date field. Active employee status maps to a custom field rather than a native status object since Recruit CRM is ATS-focused and does not have a built-in employee lifecycle field. Employee records created from hired applicants resolve against the corresponding Candidate record.

Team Engine Employee Groups (customizable groups organizing employees by role, shift, location, or trade) have no direct Recruit CRM equivalent. We map group membership to Recruit CRM tags on the Contact record. If group names are standardized (e.g., Shift-A, Field-Crew-North), we map them as a custom multi-select field on Contact so that filtering by group is possible in Recruit CRM's candidate and contact views. Customers with highly custom group naming conventions should review group names during scoping to confirm mapping strategy.

Team Engine organizes message threads by contact phone number, not by the employee or applicant record directly. We resolve each thread to the corresponding Candidate or Contact in Recruit CRM by matching phone number. Unlinked contacts—applicants who were not hired, or crew members without a full employee record—require a scoping decision: create a stub Contact record to preserve message history, or exclude message history. We document this decision before migration and apply it consistently across all unlinked threads. Message content migrates as Note records attached to the resolved Contact or Candidate.

Team Engine referral records track which employee referred an applicant and the referral status. Recruit CRM does not have a native referral object as standard. We map referral source to a custom text field (referral_source_employee) on the Candidate record and referral status to a custom picklist (referral_status). The employee who made the referral is linked as a Contact lookup if the referrer has a Contact record in Recruit CRM. Customers that rely heavily on referral tracking should evaluate Recruit CRM's add-on modules or a Zapier-based referral tracking extension during the scoping phase.

Team Engine automated onboarding survey responses store answer data per employee. We extract response records and map them as Note records attached to the Contact, with the survey name preserved as the Note title. Individual survey questions with structured answers (e.g., Yes/No, rating scale) map to custom fields on Contact if the answer set is small and consistent. Survey questions themselves—stored as survey templates in Team Engine—are not migratable data and we do not replicate the survey structure in Recruit CRM.

Team Engine exit survey responses follow the same mapping logic as onboarding surveys: response data attaches as Note records or custom fields to the Contact record for the departing employee. Exit status (reason for leaving, tenure) maps to custom fields if the customer's Team Engine survey used structured questions. We note that Recruit CRM does not have a native onboarding or exit survey module; the customer's HR team will need to establish a new survey collection process post-migration.

Team Engine automated triggered messages—new hire welcome alerts, milestone reminders, survey triggers—are platform configuration settings, not data records. There is no documented export path for these automation rules. We do not migrate workflow triggers as data. We perform a configuration audit of active triggers in Team Engine, document each trigger's name, conditions, actions, and schedule, and deliver this as a written configuration inventory so the customer's team can manually rebuild equivalent automations in Recruit CRM's workflow builder or via a Zapier integration.

Team Engine supports custom fields on employee records but public-facing API references are limited, requiring manual discovery. We identify custom fields during the data extraction phase by reviewing the CSV export structure and comparing against standard field names. Custom field names and types are mapped to equivalent custom fields in Recruit CRM. Where a direct type match is not available (e.g., a Team Engine custom date field with conditional formatting), we document the discrepancy and propose a nearest-equivalent Recruit CRM field type during scoping.