Migrate from Recruitee to Crelate

Recruitee Job records map directly to Crelate Job records with title, department, location, employment type, and status preserved. The Start plan's 5 active job post limit is a scoping constraint we flag before migration begins; any account with more than 5 active positions must upgrade to Advance or Optimize before we can import all jobs in a single pass. We extract job department linkage to maintain reporting by department in Crelate after migration.

Recruitee Candidates map to Crelate Contacts using the Contact Type set to Candidate. We preserve name, email, phone, social profiles, source attribution, and creation timestamp. Custom candidate properties map to Crelate custom fields with type conversion (text, number, date, single-select, multi-select) applied during the transform phase. Any property with a conflicting field name receives a suffixed API name per Crelate naming conventions.

Recruitee Application records link a Candidate to a Job with a specific stage and timestamp. We preserve this relationship in Crelate as a Submission record attached to the Job and Contact. Application creation date migrates for pipeline velocity analytics, and the original application stage maps to the corresponding Crelate pipeline stage via the stage mapping we extract during discovery.

Recruitee's pipeline stages are customizable per Job, meaning the same stage name can appear in different order or with different criteria across roles. We extract stage configurations per pipeline during discovery, produce a written stage mapping table that maps each Recruitee pipeline stage to the equivalent Crelate stage, and apply that mapping before Job records are imported. This ensures stage-based reporting remains consistent after cutover.

Recruitee Talent Pools are organized candidate collections used for future roles. We migrate pool membership by attaching a Crelate Tag to each Candidate record that was a member of a given pool. Pool-level notes and tags attached to the pool itself migrate as a Crelate note on a designated administrative Contact record that serves as the pool artifact. If the customer uses pools as formal candidate segments, we map them to Crelate Tags with a naming convention of Pool_[PoolName].

Recruitee Offer records include status, salary details, start date, and candidate linkage. We map Offers to Crelate Opportunity records with the Contact as the primary WhoId and the Job as a secondary reference. Offer status (pending, accepted, rejected, withdrawn) migrates as a custom Opportunity field so historical offer analytics can be rebuilt in Crelate's reporting module.

Recruitee interview scorecards use attribute-level ratings (for example, 'Technical Skills: Strong Yes') attached to a specific interviewer and timestamp, embedded in application activity rather than a standalone object. There is no single scorecard export endpoint. We extract scorecard data as structured notes using a parseable format (Attribute|Rating|Interviewer|Date) so historical evaluation data survives the migration and remains searchable in Crelate even without a native scorecard object.

Recruitee Departments are organizational units that classify jobs and team members. We migrate department records as Crelate Tags on Job records, maintaining the job-to-department linkage so reporting by department is consistent after migration. If the customer uses departments as a formal taxonomy, we map them to a Crelate custom single-select field on Job.

Recruitee Users include name, email, role, and department assignment. We map users to Crelate Users by email match. Role terminology differs: Recruitee's Admin, Recruiter, and Hiring Manager map to Crelate's corresponding permission levels, and we document any role that does not have a direct equivalent for the customer's admin to configure post-migration.

Recruitee Notes are free-text entries attached to candidate profiles. Activity history includes stage changes, emails sent, and interview events. We export notes with timestamp and author attribution and map them to Crelate Activity records (Note subtype) linked to the Contact. Stage change history migrates as Activity records with a structured description field capturing the before/after stage and timestamp.

File attachments stored in Recruitee's document store export as binary files that we re-upload to Crelate's document storage. We use filename and candidate email to establish linkage, creating a Crelate Activity record of type Attachment pointing to the uploaded document. The original file name and upload date are preserved as metadata on the Crelate side.

Custom fields on Candidates, Jobs, and Applications require field-level mapping to the Crelate schema. We extract the full custom field list via the Recruitee API, evaluate each for type compatibility with Crelate's supported field types (Text, Number, Decimal, Money, Date, Single-Select, Multi-Select), and pre-create destination fields before migration. Any field without a direct type equivalent is mapped to the closest Crelate type and documented in the field mapping reference.

Recruitee Workflow Automations live as proprietary rule constructs (triggers, conditions, actions) inside the platform and cannot be extracted via the API. We document the active automation logic during discovery, including trigger type, conditions, actions, and affected records, so your team can rebuild equivalent rules in Crelate's Automation & Sequencing module (Business Plus tier) or document them for a separate workflow rebuild engagement. This review is scheduled during the delta phase, not after cutover.