Migrate from GoHire to Crelate

GoHire Job records map directly to Crelate Job records with full field fidelity: title, description, requirements, department, location, employment type, and open/closed status transfer as structured fields. GoHire's job board distribution metadata (which boards the listing was published to, and the board-specific job ID) is preserved in a Crelate custom text field so that re-syndication to Indeed, Monster, CareerBuilder, and other aggregators does not require manual re-entry of board associations. We flag any source job descriptions that may fail destination job board standards during the pre-migration scan.

GoHire Candidate profiles map to Crelate Contact records. Full name, email address, phone number, current company, current title, LinkedIn URL, and candidate notes transfer as standard Crelate fields. Any candidate tags or labels from GoHire migrate to Crelate Tags. Resume files are exported from GoHire via the bulk download tool (a manual in-platform action we request the customer perform before migration kickoff) and reimported as Crelate Document records attached to the Contact.

GoHire Application records link a Candidate to a Job and carry the source attribution (which job board or direct link generated the application). We preserve this linkage and the source channel in Crelate's Application record, which ties to both the Job and the Contact. The application date, current pipeline stage, and any application-specific notes transfer as structured fields on the Crelate Application.

GoHire's candidate pipeline uses configurable stage names that vary by customer setup. We map source stage names to destination Crelate pipeline stage names based on a naming convention agreed with the customer during scoping. If GoHire stages map to Crelate deal/opportunity stages rather than candidate stages (common in staffing agency workflows), we configure both the candidate pipeline and the opportunity pipeline in Crelate during migration. Stage ordering and probability percentages transfer where available.

GoHire custom screening questions attached to a Job are stored as custom fields in the export. Their response values transfer as structured data to Crelate custom fields on the Job record. The screening question text itself (the question wording) does not auto-populate in Crelate; it is recreated as a Crelate custom field label during the schema setup phase, and the customer's admin confirms the field names and types before migration runs.

GoHire interview scheduling records and associated calendar invite details transfer as Crelate Activity records (Event type) linked to the relevant Job and Contact. Interview date, time, duration, interviewer name, location (or meeting link), and any scheduling notes transfer. We do not transfer GoHire's specific self-scheduling link preference (GoHire's built-in scheduling tool vs Google Calendar vs Outlook); the customer reconfigures the scheduling integration in Crelate post-migration.

GoHire hiring team member accounts (recruiters, hiring managers, administrators) transfer as Crelate User records. We extract the email address, full name, and role designation from GoHire and resolve each by email match against the Crelate destination tenant's User table. Any GoHire Team Member without a matching Crelate User goes to a reconciliation queue for the customer's admin to provision the account before record import resumes. Role-based permissions map to Crelate's permission model, which the admin reviews post-migration for fine-grained access control.

GoHire supports custom fields on Job records beyond the standard fields. We discover these at scan time and create equivalent Crelate custom fields with matching field types (text, picklist, date, numeric, monetary). Fields that cannot be matched by name or type are flagged in the mapping spreadsheet for the customer to resolve. Custom field values migrate as structured data into the corresponding Crelate custom fields.

GoHire custom fields on Candidate records transfer to Crelate Contact custom fields. Crelate supports custom field types including short/long answer, date, numeric, monetary, picklist (single and multi-select), and star ratings. We map GoHire field types to Crelate field types during the discovery phase and flag any fields that cannot be matched by name or compatible type in the mapping document.

GoHire Application records carry the source channel (which job board, direct application, referral link, or careers page generated the candidate). We preserve this as a Crelate Tag on the Contact record and as a custom text field sourced__c for reporting. If the customer uses GoHire's UTM and referrer tracking, we attempt to preserve that metadata as additional custom fields or tags in Crelate.

GoHire Candidate profiles may include current employer company name as a free-text field. If the customer is an agency using Crelate's CRM side, we can promote these to Crelate Company records linked to the Contact. If the customer is an in-house team without a client CRM use case, the company name remains as a text field on the Contact record. We confirm the customer's preference during scoping.

GoHire's core differentiator is one-click multi-job-board publishing to Indeed, Monster, CareerBuilder, SimplyHired, and other aggregators. The board-specific job IDs and distribution history transfer as a structured set of Crelate custom text fields (one per board). The customer's admin reviews and confirms these before re-syndication in Crelate, at which point Crelate's own job board distribution settings take over for new postings.