Migrate your Team Engine data

Jobs include title, description, location, requirements, and posting status. We map them 1:1 into the destination's job or requisition object. Post-date and closing date are preserved as standard date fields.

Applicant records export via CSV with name, contact info, application date, status (applied, screening, hired, rejected), source, and rejection reason. We map these fields directly and flag records where status requires normalization across systems.

Employee records include name, contact details, hire date, and group membership. We map these 1:1 but flag group assignments for review since Employee Groups use custom naming conventions per organization.

Customizable groups organize employees by role, shift, location, or trade. Group names and membership are exported; we map them as tags or custom fields in the destination and flag conflicts with existing taxonomy.

Message threads are stored but organized by contact, not by employee record. Migrating message history requires mapping each thread to the corresponding employee in the destination HRMS. Thread-level metadata (timestamps, direction) is preserved.

Referral records track which employee referred an applicant and the referral status. We map referral source and status but note that not all HRMS platforms have a native referral object—these may become custom fields on the applicant record.

Automated onboarding and exit survey responses are stored. We extract response data and map it to the corresponding employee or applicant record in the destination. Survey questions themselves are not migrated.

Automated triggered messages (e.g., new hire welcome, milestone reminders) are configuration settings, not data records. These do not export as structured data and are not migratable to a destination system with a different automation engine.