Migrate from JobScore to Crelate

JobScore Candidate records map directly to Crelate Contact. We carry name, email, phone, address, resume blob, tags, and notes. The JobScore uid is preserved as crelate_source_uid__c for audit traceability. Any phone-number collision detected during scoping is presented to the customer with a skip, merge, or overwrite choice before the import batch runs.

JobScore Job records map to Crelate Job Order. We handle the published-job constraint by extracting all Job records from the admin panel before relying on the v2 API, then cross-referencing against the API export to surface any roles saved as Draft or Unpublished. Those missing roles are flagged for manual publication before migration or captured as a supplementary JSON package. Title, description, location, and status transfer to Crelate Job Order fields.

JobScore Application records (the join table linking Candidate to Job) map to Crelate's Application model. Stage history, application date, and custom form field responses migrate. The most recent Active sub-stage name from JobScore is preserved as a custom property on the Crelate Application record because Crelate does not natively support multi-level Active sub-stages.

JobScore Interview records (date, interviewer assignment, interview type, outcome) map to Crelate Activity records with Activity Type set to Interview. Interviewer assignments migrate by resolving JobScore user uid to Crelate User email match. Interview notes and outcome ratings attach as Activity notes.

JobScore Scorecard records (ratings, comments, interviewer uid) migrate as Activity notes on the parent Interview Activity in Crelate. Rating values and comment text are appended to the Activity note body with the interviewer name prefixed. Where Crelate custom fields exist for rating, we map ratings to those fields.

JobScore Document blobs linked to Candidates or Applications export as binary attachments. We reattach them to the corresponding Crelate Contact record via the Resume Toolbox or as Document records linked via ContentDocumentLink. Parsed resume data (skills, experience) maps to custom Contact fields if configured.

JobScore Location records (address, city, state, country) map to the location fields on the Crelate Job Order. Remote, hybrid, and onsite designations migrate as a custom picklist field on Job Order.

JobScore Users and Employees (interviewers, recruiters, owners) map to Crelate User records resolved by email match. Owner assignments on Jobs, Applications, and Interviews reference the resolved Crelate User. Any JobScore User without a matching Crelate User email goes to a reconciliation queue for admin provisioning before record import.

JobScore custom form field schemas (per-job custom fields and their types) extract from the source account and recreate as Crelate Application Forms. Crelate's field mapping feature allows form responses to copy directly to Contact, Company, or Opportunity fields; we configure these mappings during the development phase. Form-level field type conversion (text, number, date, picklist) is preserved.

JobScore Tags (unlimited freeform labels on Candidates) map to Crelate Tags on Contact records. We preserve all tag associations per Candidate. Crelate's tag implementation is a simple label set; we do not convert tags to multi-select picklist fields unless the customer requests that configuration.

JobScore Email Templates (body, subject, trigger conditions) export with template body and subject preserved. Crelate Email Templates are stored as platform templates and can be used with Automation & Sequencing on Business Plus tier. We deliver the template bodies as a package; Crelate does not preserve JobScore's native trigger conditions, which must be rebuilt in Crelate's automation module.

JobScore's five top-level stages (New, Active, Declined, Withdrawn, Hired) map to Crelate pipeline stages. Custom Active sub-stages collapse into a single 'Active' stage label in Crelate, with the most recent sub-stage name stored as a custom property on the Application record. Disposition codes from JobScore Application Statuses map to Crelate Status values for Declined and Withdrawn stages.

JobScore Offer Fields (standard and custom currency, date, number, text, and multiple-choice fields used in offer templates) map to Crelate custom fields on the Job Order or as separate offer-related custom fields if the destination org supports that object. Token mappings from offer templates are documented but not migrated as active template code.

JobScore's published Job Feed URLs and career site job listings are validated against the extracted Job set as a completeness check. Crelate's Branded Job Portal replaces the JobScore careers site; we document the feed URL mappings for the customer's admin to reconfigure the destination job portal feeds post-migration.