Migrate from Team Engine to Crelate

Team Engine Jobs (title, description, location, requirements, posting status, post-date, closing date) map 1:1 to Crelate Job records. We extract job status from Team Engine's posting status field and map it to Crelate's Job Status picklist (Open, Closed, On Hold, Draft). Location fields transfer to Crelate's address fields. Active job postings with candidates in pipeline are prioritized in migration order so that candidate-to-job lookups resolve correctly.

Team Engine Applicant records (name, contact info, application date, status, source, rejection reason) map 1:1 to Crelate Candidate records. We preserve the Team Engine status values (Applied, Screening, Hired, Rejected) as Crelate pipeline stages or custom picklist values. Application source attribution transfers to Crelate's Candidate Source field. Rejection reasons migrate as a custom field or note if Crelate's standard rejection field is not configured.

Team Engine Employee records (name, contact details, hire date, group membership) map to Crelate Contact records. We use the employee's email address as the dedupe key during import. Hire date transfers to a custom Contact field te_hire_date__c. Active employees who were previously Applicants may have duplicate records; we flag these for reconciliation to avoid duplicate Candidates when the employee record is also a past applicant.

Team Engine Employee Groups (customizable by role, shift, location, or trade) have no native Crelate equivalent. We map group names to Crelate Tags on the Contact record, with each distinct group name becoming a tag value. If the customer prefers structured fields, we map group membership to a custom picklist field te_employee_group__c. Conflicts with existing Crelate tags are resolved during scoping, and group name casing is normalized to avoid tag fragmentation (e.g., 'Field Crew' vs 'field crew').

Team Engine message threads are organized by contact phone number, not by employee record, and do not map to a standard Crelate object natively. We reconcile each message thread to the corresponding Crelate Contact by matching the phone number. Threads linked to Applicants who were not hired are flagged for decision: create a stub Contact record or exclude message history. Each individual message becomes a Crelate Activity or Task record with the message body, timestamp, direction (inbound/outbound), and sender/recipient preserved. Teams requiring full SMS/WhatsApp preservation should plan for a parallel communication platform migration since Crelate does not store mobile-worker messaging natively.

Team Engine Referral records track which Employee referred an Applicant and the referral status (Pending, Hired, Paid). Crelate has no native referral object, so we map referral data to the Candidate record using custom fields: te_referral_employee__c (the referring employee's name or email) and te_referral_status__c (picklist matching Team Engine values). If the referring employee is already a Crelate Contact, we create a lookup relationship. Referral bonuses and payout tracking do not migrate and must be handled separately in payroll or HR systems.

Team Engine automated onboarding and exit survey responses are extracted and mapped to the corresponding Employee Contact record in Crelate. Survey questions and configuration settings are not migratable (they are platform configuration, not data). We extract response data and transfer it as a formatted Note or as structured custom fields (e.g., te_onboarding_survey_response__c). If survey responses contain multiple questions, we normalize them to a single concatenated text field or split into individual custom fields per question during scoping.

Team Engine automated triggered messages (new hire alerts, milestone reminders, survey triggers) are platform configuration, not data records. There is no documented export for these automation rules, and Crelate's automation engine uses a different trigger model (record-based and scheduled flows). We do not migrate workflow triggers. We document which triggers are active in Team Engine, their trigger conditions, and the message content, and provide a configuration audit log so the customer's admin rebuilds them manually in Crelate's automation settings.

Team Engine Owner records (the team member who owns a job, applicant, or employee) map to Crelate User records. We resolve owners by email match against the Crelate destination's User table. Any Team Engine Owner without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Team Engine applicant status values (Applied, Screening, Interviewing, Offered, Hired, Rejected) map to Crelate pipeline stages. We configure Crelate's pipeline stages to match the Team Engine status values during migration setup, using a custom pipeline if the customer's Team Engine setup has non-standard stages. The mapping is defined in the migration specification and applied during candidate import.

Team Engine captures applicant source (referral, job board, direct apply, etc.) and maps it directly to Crelate's Candidate Source field. Source values that do not exist in Crelate's picklist are added as new picklist values or mapped to an 'Other' value with the original source preserved in a custom field.

Employee Group membership is a many-to-many relationship in Team Engine (one employee can belong to multiple groups). Crelate Tags support multiple tag values per Contact, so we transfer each group membership as a separate tag. Group names with special characters or spaces are normalized to valid Crelate tag format. If the customer uses Team Engine groups for shift scheduling or location assignment, these tags can be used in Crelate filters and reports for segmentation.

Team Engine custom fields on employee records map to Crelate custom fields on Contact. Custom fields that do not have a documented export in Team Engine's public API references require manual field discovery during scoping. We work with the customer's Team Engine admin to identify all active custom fields, their data types, and map them to equivalent Crelate custom field types (Text, Picklist, Date, Numeric, etc.). Field-level mapping is documented in the migration specification before import begins.

Team Engine custom fields on applicant records map to Crelate custom fields on Candidate. Similar to employee custom fields, applicant-level custom fields that are not well-documented require manual discovery during scoping. We flag any custom fields with unknown data types and resolve them with the customer before migration. Crelate's custom field types (Short Answer, Long Answer, Date, Numeric, Picklist, Rating) guide the type mapping from Team Engine field formats.