Migrate from unstop to Crelate

Unstop candidate Users map to Crelate Candidate records. We preserve the unstop candidate ID in a custom field unstop_user_id__c for audit traceability. Education, declared skills, and work-history fields migrate as Crelate custom fields or parsed resume data where available. Unstop's self-registration model means education and employment claims are self-reported; we set an unverified_claims__c flag on the Crelate Candidate record and flag these fields for re-verification during onboarding in Crelate.

Unstop recruiter Users map to both Crelate Client (organization) and Contact (individual recruiter) records. We use the Unstop organization profile as the Crelate Client source of truth, and individual recruiter email addresses as Contact records linked to that Client. This split ensures Crelate's client management and recruiter accountability structures are populated from day one.

Unstop job postings migrate as Crelate Job records with a 1:1 field mapping: title, description, location, employment_type, and application deadline map directly. Salary_range and remote_policy migrate as Crelate custom fields. The Unstop job ID is preserved in unstop_job_id__c on the Crelate Job record. Application deadline maps to the Crelate job close date field. Active and inactive status is preserved from Unstop.

Unstop internship records use the same base schema as job postings with the addition of internship-specific fields (duration_in_months, stipend_amount, stipend_currency, work_arrangement). These fields migrate as Crelate custom properties on the Job record, and the job type is set to Internship so that Crelate's pipeline filters can isolate internship postings from full-time roles.

Unstop competitions map to a Crelate Job record with a job_type discriminator set to Competition, plus an Activity record containing the competition rules, scoring rubric, and participant enrollment list as structured text. Team membership structures from coding challenges and hackathons are flattened into individual participation Activity records with a parent reference to the Competition Job. Competition format (quiz, coding, case study) is stored in a Crelate custom picklist field. The raw enrollment data migrates as JSON in a custom long-text field to preserve all metadata.

Unstop hackathon records hold team structures, submission URLs, judging scores, and leaderboard positions. These map to a Crelate Job record with job_type set to Hackathon, and team memberships are flattened into individual participation Activity records with a parent Hackathon reference. Submission URLs, judging scores, and final leaderboard rank migrate as Crelate custom fields on each participation record. Hackathon data is preserved but stored as structured Activity notes rather than as native Crelate pipeline records, since Crelate's native pipeline does not support hackathon-specific stages without custom configuration.

Unstop scholarship postings migrate as Crelate Job records with job_type set to Scholarship. Eligibility criteria, award amount, application deadline, and provider organization migrate as Crelate custom fields. Scholarship applicant lists (if exported as application records) migrate as Crelate Application records linked to the Scholarship Job. We note that Crelate's native pipeline does not track scholarship status workflows; any status stages need to be implemented as custom picklist values or as a separate scholarship tracking workflow post-migration.

Unstop quiz session records (start/end timestamps, score, passing status, device) map to Crelate Activity records with custom fields capturing score_value, passing_status, duration_seconds, and assessment_name. Quiz configurations and question banks migrate as a JSON payload in a custom long-text field on the Crelate Candidate record. We validate end_timestamp presence on each quiz session record; sessions where end_timestamp is missing or anomalous (likely crash-affected) are flagged with a score_status discriminator set to unverified for manual admin review before these candidates are advanced in the Crelate pipeline.

Unstop recruiter organization profiles (company name, logo, description, industry, website) map to Crelate Client records. The organization's unstop domain or company name is used as the dedupe key during import. Any contact details attached to the organization profile migrate as Crelate Contact records linked to the Client. Client records are created before any Candidate import so that Crelate's client-candidate lookup relationship is satisfied at the moment of candidate insert.

Unstop application records link a candidate User to a Job, Internship, or Competition and track status (Applied, Shortlisted, Rejected, Withdrawn). These map to Crelate Application records preserving the candidate_id, job_id, application_status, and submission_timestamp. Application status values are mapped to Crelate's application stage picklist. Any score or ranking attached to the application in Unstop migrates as custom fields on the Crelate Application. This object has the most consistent schema between the two platforms, minimizing transformation risk.

Skills declared by candidates in Unstop profile registrations migrate as Crelate Tags on the Candidate record. The skill taxonomy from Unstop may be broad (self-reported tags not validated against a structured ontology). We normalize skill entries to lowercase, deduplicate within the candidate record, and set a tag_source discriminator to unstop_profile to identify skills that require verification. The customer's recruiting admin can curate the skill taxonomy in Crelate post-migration to align with their internal skill taxonomy.

Unstop assessment objects store quiz configurations, question banks, time limits, and scoring rubrics. The configuration itself migrates as a JSON payload stored in a custom long-text field on the Crelate Job record (for assessments tied to a specific job) or on the Crelate Candidate record (for standalone assessments). Candidate responses and individual attempt results migrate as Crelate Activity records linked to the Candidate. Score values and pass/fail status populate custom numeric and picklist fields on the Activity for filtering and reporting. This split preserves both the assessment template and the candidate's result without requiring Crelate's native assessment module.