Migrate from Jobsoid to Recruit CRM & ATS

Jobsoid Candidate records map directly to Recruit CRM Candidate records via field-to-field mapping: first name, last name, email, phone, current company, current designation, location, source attribution, and candidate status all transfer. Jobsoid's multi-job assignment for a single candidate creates multiple application records in Recruit CRM with a primary flag set on the designated primary job. Custom candidate fields in Jobsoid map to equivalent custom fields in Recruit CRM; any Jobsoid custom fields without a matching destination field require a custom field creation step before migration.

Jobsoid Jobs map to Recruit CRM Job records. Job title, description, location, department, employment type, experience level, salary range, and job status all migrate field-to-field. Jobsoid's Jobs API exposes published jobs directly; we confirm all active, paused, and closed jobs are captured including those in draft state if the customer requests them. The destination job record is created before candidate applications are imported so the job reference is satisfied at insertion time.

Jobsoid Locations are organizational lookup values tied to job openings. We migrate the full location list from Jobsoid's lookup API and reassign affected jobs during migration. Recruit CRM uses a Location field on the Job record rather than a separate location object; we insert the location value directly and validate that job count by location matches post-migration.

Jobsoid Departments are organization-level lookup values exposed via the lookup API. We preserve the full department list and reassign affected jobs in Recruit CRM's department structure. Recruit CRM uses a Department field on the Job record. Department mapping is 1:1 with department name as the dedupe key.

Jobsoid Divisions represent top-level organizational units in its lookup structure. Recruit CRM supports Division as a field on the Candidate and Job record. We carry over division records and link them to associated departments and jobs. If the destination account uses a simplified department-only structure, division records are consolidated into the department field with a prefix notation.

Jobsoid Functions categorize job types (Engineering, Sales, Operations, etc.) and are exposed as lookup values. Recruit CRM uses a Function field on the Job record. Function values map 1:1; any Jobsoid functions not recognized in Recruit CRM's predefined list are added as custom values before migration.

Jobsoid tracks candidate origination (job board, referral, direct, etc.) as a field on the candidate record. We map source values field-to-field into Recruit CRM's Candidate Source field. Any Jobsoid source labels that do not have an exact match in Recruit CRM are flagged during scoping for the customer to confirm consolidation or addition to the destination's picklist.

Jobsoid allows fully custom pipeline stage names and counts per job or organization. Recruit CRM uses configurable pipeline stages per job. We map each Jobsoid pipeline to a Recruit CRM pipeline and apply the customer's agreed stage consolidation rule when the destination has fewer stages. We surface this decision during the scoping call and apply the agreed mapping before import. Stage probability percentages are carried forward if Jobsoid tracks them.

Jobsoid activity records (interview events, emails, notes) appear in the candidate profile but are not an independently exportable API resource. We extract activity text from candidate profile exports and reconstruct a best-effort chronological timeline. Interview dates, interviewer name, and interview notes migrate to Recruit CRM's candidate activity section. If activity history is critical, we recommend exporting candidate profiles as PDFs from Jobsoid before migration to capture the full activity panel in human-readable form.

Candidate profiles can include uploaded files and resumes in Jobsoid. We extract binary attachments separately from record data, storing them with a named reference to the source candidate email and job assignment. At the destination, we re-attach files to the corresponding Recruit CRM candidate record using the candidate's email address as the matching key. Resume files are associated with the primary candidate record; secondary job-assignment attachments are linked to the relevant application record.