Migrate from unstop to BambooHR

Unstop Users with a candidate role map to BambooHR Employee records. Candidate profile fields — firstName, lastName, email, phone, dateOfBirth, education, skills, workHistory — map to BambooHR standard Employee fields. We flag education and work-history fields as self-reported and recommend marking them as unverified in BambooHR until HR verification is complete. The migration user performing the import must be a BambooHR administrator. BambooHR cannot create net-new users via API provisioning from a non-BambooHR source; we coordinate with the customer's admin to pre-provision employeeNumber assignments or use BambooHR's bulk employee import CSV template.

Unstop Organization profiles (company name, logo, description, contact details) map to BambooHR Company records if the context is an employer account being tracked. If the migration scope includes converting the recruiting organization itself into a BambooHR customer account, we treat the Organization as a Company lookup entity and preserve contact information in a custom field.

Unstop Job postings map directly to BambooHR Job records in the ATS module. Fields — title, description, location, employmentType, salaryRange, applicationDeadline — migrate 1:1. BambooHR's ATS is a separate add-on at $99-$199 per month; we confirm during scoping whether the destination BambooHR account has ATS enabled. If not, we document each Job as a written record for the customer to recreate in BambooHR post-migration.

Unstop Internship records follow the same schema as Jobs with additional fields for internshipType, durationMonths, and stipendAmount. We map these to BambooHR Job records with internshipType and duration stored as custom fields, and stipendAmount stored as a custom compensation field. The internshipType discriminator allows the customer to filter BambooHR Job listings by internship versus full-time role.

Unstop Application records linking a User to a Job, Internship, or Competition map to BambooHR Candidate Records in the ATS module. Application status (Applied, Shortlisted, Rejected, Offer Extended) migrates to BambooHR's status pipeline. The candidate's resume and cover letter attach as documents to the BambooHR Candidate Record via ContentDocumentLink. BambooHR does not support a native Application object separate from Candidate Record; the application lifecycle maps to Candidate Record status transitions.

Unstop Competitions (coding challenges, quizzes, design contests, case studies) each have distinct metadata and scoring structures that do not map directly to any standard BambooHR object. We normalize competition metadata — name, organizer, startDate, endDate, rules, formatType — into a structured JSON payload stored as a custom Employee field called competition_history__c on the relevant Candidate or Employee record. Format-specific scoring and leaderboard data store as additional JSON fields within the payload. The customer decides whether to apply this data to an Employee record post-hire or retain it on a Candidate Record for reference.

Unstop Hackathon records include team structures, submission URLs, judging scores, and leaderboard positions. Team membership flattens into individual participation records on each candidate's profile, with a parent hackathon reference. Submission URLs store as custom text fields; judging scores and leaderboard rank store as numeric custom fields. We recommend creating a BambooHR custom object called Hackathon_Participation if the BambooHR plan supports custom objects, or storing as JSON in a custom Employee field if it does not.

Unstop Assessment objects store quiz configurations, question banks, time limits, and scoring rubrics. We export the assessment configuration as structured metadata and candidate response summaries as JSON attached to the relevant Candidate Record. The raw assessment configuration (question banks, rubrics) does not migrate as executable content; BambooHR does not run quiz sessions natively. We deliver a written assessment inventory listing each Unstop assessment with its configuration details so the customer's admin can recreate the assessment in BambooHR's document repository or a third-party assessment tool integrated via BambooHR's API.

Unstop Quiz Session records — start/end timestamps, score, passingStatus, device, platform — map to custom fields on the BambooHR Candidate Record. We validate server-side score records against original timestamps, flag any session with a missing end_timestamp or anomalous duration as a likely crash-affected record per the Unstop platform gotcha documentation, and store a data_quality flag on those records. BambooHR's ATS does not support native quiz session objects; these fields store as custom Candidate Record properties.

Unstop Scholarship records — eligibility criteria, award amount, application deadline, applicant list — do not map to a standard BambooHR object. We create a written scholarship inventory document enumerating each Unstop scholarship with its full details (name, eligibility, amount, deadline, recipient list) for the customer to recreate as BambooHR Benefit Program records or as a documented program list maintained outside BambooHR. BambooHR's Benefits Tracking module manages employee benefit plans, not scholarship programs, so a schema-equivalent object does not exist.