Migrate from GoHire to Recruit CRM & ATS

GoHire Jobs map directly to Recruit CRM Job records. We transfer job title, description, requirements, department, location, employment type, and open/closed status. GoHire's job-board distribution metadata (which boards received the listing) is preserved as a custom multi-select field on the Job in Recruit CRM, but the re-publishing action is manual in Recruit CRM — we provide the board list as a reference so the customer's team can re-post directly. Active versus closed status maps cleanly; archived jobs can be imported as closed records at the customer's preference.

GoHire Candidate profiles map to Recruit CRM Candidate records with full contact information (name, email, phone, address), work history, education, and skills preserved. Resume files must be exported from GoHire's bulk-download tool by the customer before account closure; we reimport them as attachments linked to the Candidate record in Recruit CRM. If the customer no longer has GoHire admin access, resumes may need manual retrieval or may be inaccessible. We flag this requirement during migration kickoff.

GoHire Application records link a Candidate to a Job and carry source attribution (which job board or direct link generated the application). These map to Recruit CRM's application records with the Candidate and Job lookups resolved at migration time. Source channel data (Indeed, Monster, direct referral) transfers as a text field on the application record. We preserve the application date and any score or rating values as structured fields.

GoHire uses a configurable candidate pipeline with customer-defined stage names (e.g. Applied, Screening, Interview, Offer, Hired). We map these to Recruit CRM pipeline stages using a naming convention agreed with the customer during scoping. If GoHire stage names differ significantly from Recruit CRM's defaults, we create matching stages in Recruit CRM before migration and update the destination pipeline configuration accordingly.

GoHire custom screening questions attached to a Job are stored as custom fields in GoHire's data model. Their response values transfer as structured data into Recruit CRM custom fields that we pre-create during schema mapping. The question text itself is documented as part of the migration handoff so the customer's admin can recreate the question label in Recruit CRM's field configuration if desired.

GoHire interview scheduling records and associated calendar invite data transfer as calendar events in Recruit CRM. We note that Recruit CRM's Google Calendar sync is two-way for created and updated meetings but does NOT sync deleted meetings back to Google Calendar — if a meeting is deleted in Recruit CRM, it remains in Google Calendar and must be removed manually. Meeting link preferences (Google Meet versus Microsoft Teams versus a custom scheduling link) do not transfer and must be reconfigured in Recruit CRM's calendar settings.

GoHire hiring team accounts (recruiters, hiring managers) transfer as User records in Recruit CRM. Role-based permissions from GoHire map to Recruit CRM's permission model, which may require manual review for admin versus recruiter versus hiring manager distinctions. Users without a matching email in Recruit CRM at migration time are placed in a reconciliation queue for the customer to provision before the user-dependent records are imported.

GoHire supports custom fields on Jobs at all paid tiers. We discover these at scan time and map them to equivalent custom fields in Recruit CRM's Job configuration. Any fields that cannot be matched by name or data type are flagged in the mapping document for the customer's admin to review and resolve before the final import.

GoHire Candidate custom fields are discovered during scan and mapped to Recruit CRM custom fields on the Candidate object. Multi-select or checkbox fields in GoHire map to multi-select picklist fields in Recruit CRM where supported. Free-text custom fields map directly to text fields. The customer chooses during scoping whether to include or exclude specific low-value custom fields to keep the destination clean.

GoHire's built-in careers page builder configuration (branding, layout settings, job listing display preferences) does not transfer as live pages in Recruit CRM. We export the careers page template settings as a written document — domain, branding colours, header content, footer content, and the list of jobs displayed — so the customer's admin can reconfigure the Recruit CRM careers page using that reference. Recruit CRM provides a careers page builder but the setup is manual.