Migrate from Recooty to Crelate

Recooty Jobs migrate to Crelate Job Posts. Each job carries title, description, location, department, employment type, and publishing status. We preserve job creation date and any internal job ID from Recooty as a custom field for reconciliation. Job board publishing targets (Indeed, LinkedIn, Glassdoor) do not transfer because they are configured as OAuth connections in Recooty that cannot be replicated at Crelate without manual re-authentication.

Recooty Candidates map to Crelate Contacts. The candidate's full profile including name, email, phone, resume file, application date, and source channel migrates. Multiple applications from the same candidate (applying to different Recooty Jobs) collapse into a single Crelate Contact with multiple Job Post associations rather than duplicate records. We use email address as the dedupe key.

Recooty pipeline stages (Applied, Screening, Interview, Offer, Hired by default, configurable per job) map to Crelate Pipeline stages. Crelate uses a separate Pipeline configuration object that we configure during migration. Default Crelate pipeline stages are matched to the Recooty stage names, and stage ordering is preserved. Probability percentages from Recooty carry over if configured.

Each Recooty application (a candidate applied to a specific job at a specific stage) maps to a Crelate Job Application record linked to the Contact and the Job Post. If the candidate has applied to multiple jobs, each application is a separate record under the same Contact. Application timestamp and pipeline stage at time of migration are preserved as fields on the Job Application.

Recooty interview records (date, time, interview type, interviewer assignment, candidate ID) migrate to Crelate Activity Forms or Event records linked to the Contact. Crelate's Activity Forms support custom field mappings per question, matching the structured nature of Recooty interview records. Interviewer assignment resolves to Crelate Users by email match.

Recooty custom fields on candidate records (available on Business and Enterprise plans) map to Crelate Advanced Custom Fields on Contact. Crelate Business has a limit of 10 Advanced Custom Fields; we flag any Recooty custom field count exceeding this and work with the customer to consolidate or prioritize. Field data types are matched: Recooty text fields map to Crelate Text fields, date fields to Date fields, picklist fields to Picklist fields. Custom field labels and API names are preserved where possible.

Recooty job-level custom fields migrate to Crelate custom fields on Job Post. The same field-type mapping rules apply. If the destination Crelate plan does not support the equivalent field count, we prioritize fields used in active filtering or reporting workflows.

Recooty GDPR consent records, retention policy definitions, and audit trail logs are extracted as structured account data and re-created in Crelate's GDPR Compliance Management module. Candidate consent status (given, withdrawn, pending) maps to Crelate's consent tracking fields. Any candidates whose consent may have lapsed during the migration window are flagged with a status requiring admin review before they appear in active recruiting workflows.

Recooty branded career pages built with the drag-and-drop builder on Growth and above are builder-state dependent and cannot be directly migrated. We preserve the job content and description text from Recooty Career Pages so that Crelate branded job portal content can be manually re-created. The microsite URL is not preserved.

Recooty Owners (hiring managers, recruiters) map to Crelate Users. We resolve by email match. Any Recooty Owner without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Recooty notes attached to candidate records migrate to Crelate Notes or Activity Form entries linked to the Contact. Rich text formatting is preserved where the source data format allows. Inline comments from hiring managers on pipeline stages migrate as Activity Form entries with a reference to the associated Job Application.

Recooty tags on candidate and job records map to Crelate Tags or custom field values depending on usage. Tags used for candidate categorization migrate as Crelate Tags; tags used for structured classification migrate to the closest Crelate custom field equivalent. The customer chooses tag strategy during scoping.