Migrate from Simplicant to Crelate

Simplicant Jobs (title, description, department, location, pipeline stage) map to Crelate Job records. We preserve the job status (published, draft, closed) and the associated department and location metadata so that jobs appear in the correct Crelate pipeline. If the Simplicant job references a custom workflow for posting approval, we flag the workflow for manual reconfiguration at the destination.

Simplicant creates a separate record for each candidate application. Crelate uses a Contact-person model where a single Contact can have multiple Job Applications tied to different Jobs. We deduplicate by candidate email during scoping: matching email addresses produce one Crelate Contact with multiple Job Applications; unique emails produce separate Contacts. Application dates, source attribution, and stage history are preserved as Job Application metadata.

Simplicant departments are organizational metadata attached to Jobs and requisitions. We export department names and IDs and recreate them as Crelate pipeline or job metadata fields. Crelate does not have a standalone Department object, so we use a lookup field or a tagged text value consistent with the customer's naming conventions.

Simplicant location records attached to Jobs (city, state, remote/hybrid designation) migrate as Crelate job location fields. We preserve the full geographic data so that job postings reflect the correct location at the destination without manual re-entry.

Simplicant Offers (salary, start date, terms, e-signature status) migrate to Crelate's offer tracking tied to the Job Application. E-signature audit trail links migrate as document references attached to the offer record. We preserve offer state (pending signature, accepted, declined, retracted) so the customer's hiring team can resume the offer workflow in Crelate without re-entering terms.

Simplicant organizations add custom fields to Jobs and Candidate profiles for industry-specific data. Crelate stores custom fields on Contact, Company, and Opportunity objects. We recreate each Simplicant custom field as a Crelate custom field with a matching data type, then configure Crelate field mappings so that form responses and data-entry actions copy directly to the appropriate Contact, Company, or Opportunity column.

Simplicant pipelines define stage sequences per job type. We map Simplicant stage names and counts to Crelate Pipeline and Stage configuration. Stage probability percentages migrate as stage weights in Crelate. Any automation rules attached to stage transitions are flagged as manual rebuild candidates because Crelate handles automation separately through its Automation and Sequencing feature on Business Plus.

Simplicant stores resumes, cover letters, and HR files in cloud document management. We extract available files from Simplicant and attach them to the corresponding Crelate Contact records using Crelate's Resume Toolbox. File availability depends on Simplicant plan tier and whether the export mechanism (API or UI) provides attachment access.

Simplicant interview packets bundle structured evaluation forms with scoring conventions. We map the form schema to Crelate Activity Forms, configuring field mappings to copy each response to the corresponding Contact, Company, or Opportunity field. Completed form responses migrate as Activity records with the evaluation data preserved in the mapped custom fields.

Simplicant user accounts (hiring managers, recruiters, interviewers) with role-based permissions map to Crelate User records by email match. We resolve each Simplicant owner reference on Jobs, Candidates, and Offers to the Crelate User. Any Simplicant user without a matching Crelate account goes to a reconciliation queue for the customer's admin to provision before record import continues.

Simplicant's onboarding module stores completed workflow steps, task lists, and new hire setup state. Crelate does not have a native onboarding module. We migrate onboarding records as Crelate Activity and Task history so that the new hire's timeline and completed steps are visible within the Contact record. Active workflow definitions and branching rules do not transfer; we deliver a written inventory of the active onboarding workflows for the customer's admin to rebuild in Crelate manually.

Simplicant structured screening scores and evaluation ratings per candidate per stage migrate as custom numeric or picklist fields on the Crelate Contact. Score ranges and weighting logic from Simplicant forms are preserved as field metadata. We set up Crelate field mappings so that future evaluation forms in Crelate Activity Forms auto-populate the same custom fields, maintaining consistency with the migrated score history.