Migrate from Jobsoid to Crelate

Jobsoid Candidate records map to Crelate Person (People) objects. The Jobsoid candidate profile fields (name, email, phone, current title, current company, LinkedIn URL, source, rating, tags) map to corresponding Crelate Person fields. We preserve the Jobsoid candidate's primary job assignment and any secondary job assignments as Crelate Job Order links on the Person record. Jobsoid's multi-job assignment per candidate requires us to create multiple Person-to-Job-Order relationship records during import.

Jobsoid Job records map directly to Crelate Job Order. We extract job status (Open, Closed, On Hold, Draft), job title, job description, employment type, remote/hybrid/onsite designation, and the associated department and location. Jobsoid's custom job fields (configured via Settings > Job Openings > Custom Fields) map to Crelate custom fields on the Job Order object. The Jobsoid Job API (exposed publicly) allows us to pull published job data without requiring CSV export for this object type.

Jobsoid Location lookup values map to Crelate Location records. Both platforms expose locations at the organization level. Jobsoid auto-resolves addresses via Google Maps; we carry over the full location record (city, state, country, address) and link them to the corresponding Crelate Job Orders during import. If Crelate's destination account uses a different location naming convention, we apply the agreed location mapping during the transform step.

Jobsoid Departments map to Crelate Categories, which serve as the organizational classification for Job Orders. Both platforms expose departments at the organization level via lookup API. We migrate the full department list and reassign all affected Job Orders to their corresponding Crelate Category during import. Division and Function lookup values from Jobsoid map to Crelate custom picklist fields on Job Order where no native equivalent exists.

Jobsoid Divisions represent top-level organizational units and are exposed as lookup values. We map Division values to a custom picklist or multi-select field on Crelate's Job Order object, depending on how Crelate is configured in the destination account. The customer chooses between a flat picklist or a hierarchical representation during scoping.

Jobsoid Functions categorize job types (e.g., Engineering, Sales, Operations). We map Function values to a Crelate custom picklist field on Job Order. This field does not exist by default in Crelate; we create it during the destination schema configuration step if the customer's Jobsoid account uses Functions to classify roles.

Jobsoid Candidate Source values (referral, job board, career site, direct application, etc.) map to Crelate Source values on the Person record. Source is a field on the candidate/Person rather than a standalone object in either platform. We map source values field-to-field but flag any unrecognised source labels in Jobsoid that have no matching Crelate value; these require the customer to create a corresponding Crelate source value or map to a default 'Other' value.

Jobsoid Activities (interview events, emails, notes, call records) are embedded in the candidate profile UI but are not exposed as a separate API resource. We extract activity text and timestamps from the candidate profile export block and decompose them into a normalized engagement table. We then map each engagement type to the corresponding Crelate Activity: interviews map to Events, emails and notes map to Tasks, and call records map to Tasks with a Call subtype. We preserve original timestamps and link each activity to the corresponding Person record via the WhoId relationship. The customer may also export candidate profiles as PDFs before migration to capture full activity history as a backup record.

Jobsoid Pipelines use fully customizable stage names and counts per job or organization with no standard set. Crelate uses configurable Workflow stages tied to a workflow model. We work with the customer during scoping to define a stage mapping table: each Jobsoid pipeline stage maps to a corresponding Crelate Workflow stage. If Jobsoid has more stages than Crelate's configured workflow, we consolidate by mapping multiple source stages to a single destination stage based on the customer's process logic. This mapping is applied as a transform rule before CSV import into Crelate.

Candidate profiles in Jobsoid contain uploaded files and resumes. We export binary attachments from Jobsoid separately from record data, maintaining the original filename and file type metadata. We re-attach each file to the corresponding Person record in Crelate during the post-record ingestion phase, using the candidate email address as the matching key. Large resume files may require chunked upload handling if Crelate's attachment limits are encountered.

Jobsoid allows custom fields on candidate profiles. We migrate custom field values field-to-field where destination Crelate custom fields of the same name and type exist. We pre-create any missing Crelate custom fields (with the correct field type: text, number, date, picklist, checkbox, etc.) during the destination schema configuration step before candidate data ingestion begins. Custom fields with complex logic (e.g., dependent picklists) are flagged during scoping for manual configuration review.

Jobsoid integrates with email and calendar for interview scheduling; interview records appear as activities on the candidate profile. We extract interview dates, times, location or meeting link, interviewer name, and interview type from the candidate profile export block and map them to Crelate Event records. Calendar invite links (Google Meet, Zoom, Microsoft Teams) are preserved as the Event Location field. We do not migrate calendar invites as transferable objects; they require re-creation in the destination calendar system post-migration.

Jobsoid supports tags and star ratings on candidate profiles. Tags migrate to Crelate's Tag system on the Person record. Ratings migrate to a Crelate custom numeric field (Rating scale) if the destination account uses a numerical rating model, or to a custom picklist if Crelate is configured with a named rating tier. We preserve the original values and confirm the mapping with the customer during the scoping call.