Migrate from unstop to Recruit CRM & ATS

Unstop Users with candidate role map to Recruit CRM Candidate records. Education, skills, and work-history fields migrate as custom candidate properties. We flag any profile field sourced from Unstop's self-registration model as unverified in a custom verification_status__c field, directing the customer's recruiters to re-verify before using those fields for screening. The recruiter-side User records from Unstop (organizations posting jobs) map to Recruit CRM Client records.

Unstop Job postings migrate 1:1 to Recruit CRM Job records with title, description, location, and salary range mapped directly. Application deadline from Unstop maps to the Recruit CRM job expiry or close_date field. Active versus archived status is carried forward as the job visibility or publish flag.

Unstop Internship records follow the same schema as Job postings with added internship_type, duration, and stipend fields. These map to Recruit CRM Job records with internship-specific fields stored as custom properties. The internship_type discriminator identifies which records are internships versus standard job postings after migration.

Unstop Application records linking a User to a Job, Internship, or Competition migrate as Recruit CRM application entries attached to the corresponding Job record and Candidate record. Application status history (Applied, Shortlisted, Rejected, Withdrawn) migrates as a status log on the application record. The parent Job reference is resolved before application records are inserted to maintain referential integrity.

Competition enrollment lists migrate as Candidate Engagement or Activity records in Recruit CRM, with the competition name, organizer, enrollment date, and final status (Participated, Winner, Withdrew) stored as engagement metadata. Team-based competitions flatten team membership into individual participation records with a parent event reference. Competition-specific scoring is stored as a JSON payload in a custom engagement detail field to preserve all format-specific data.

Hackathon records holding team structures, submission URLs, judging scores, and leaderboard positions migrate as Candidate Engagement records. Team memberships are flattened into individual participation records with a parent Hackathon reference and role field. Scores and leaderboard positions are stored as custom numeric fields on the engagement record.

Scholarship records with eligibility criteria, award amount, application deadline, and applicant lists migrate as either Recruit CRM Job records (if the customer wants to track applicants within the ATS) or as a custom Program record type we create in Recruit CRM. The eligibility criteria field is preserved as a structured JSON payload in a custom field to avoid character limit truncation.

Individual quiz attempt records with start/end timestamps, score, passing status, and device platform migrate as Candidate Evaluation or Test Attempt activity records in Recruit CRM. We flag any record where the end_timestamp is missing or anomalous as a crash-affected record requiring manual review before use. We cross-reference against any locally cached screenshots the customer can provide to recover partial data where the server-side record is incomplete.

Unstop assessment configurations (question banks, time limits, scoring rubrics) are not a standard object in Recruit CRM's data model. We export the configuration as a structured JSON payload and store it as a custom property on the relevant Candidate record or as a linked Custom Object. The quiz session results (which reference the configuration) import separately and link to the candidate record by user ID.

Unstop Organization profiles containing company name, logo, description, and contact details migrate as Recruit CRM Client records. The organization contact email becomes the primary client contact. Multiple Unstop organizations under one recruiter account map to multiple Client records in Recruit CRM.