Migrate from JOIN to Crelate

JOIN Job records map directly to Crelate Job postings. We extract title, description, department, location, employment type, and posting status. JOIN's internal job ID becomes a Crelate custom field for cross-reference. Job posting distribution settings (the 250+ board network) do not transfer because Crelate handles posting through its own career portal and optional distribution partners; we document the original posting channels as a text field so the customer can re-establish distribution in Crelate manually or via a third-party distributor.

JOIN Candidate records map to Crelate Contact. Standard fields (name, email, phone, address, work history, education, skills) migrate 1:1. Source attribution and lifecycle stage transfer to Crelate's candidate status fields. JOIN custom fields on Candidates are subject to Crelate's 20-custom-field-per-entity cap; we flag anyJOIN custom fields exceeding this limit at scoping and either compress them into structured picklists or land them as free-text notes for post-migration re-entry.

JOIN Application records link a Candidate to a Job with applied date, referral source, and rejection/offer flags. We resolve the parent Contact and Job references during migration and attach the Application as a pipeline entry on the Crelate Job. Applied date and referral source migrate as metadata on the pipeline stage entry. Applications in rejected or offer stages preserve those statuses as Crelate stage entries with timestamp metadata.

JOIN exposes stage names (Screening, Interview, Offer, and custom stages per job) that vary by plan and by job. We extract the full stage list per job during the scan phase and build a customer-specific mapping table. Where Crelate's pipeline template has fewer stages, we collapse intermediate stages and preserve stage-entry dates as metadata so timing context is not lost. The customer approves the stage mapping before any pipeline data loads.

Structured interview evaluations and free-text feedback stored in JOIN transfer to Crelate as Notes attached to the Contact record or as custom fields if the destination template supports typed feedback fields. Where the customer uses Crelate's custom question forms, we flatten the JSON evaluation data into readable text and attach it to the relevant Contact as a note for recruiter review during the hiring process.

JOIN employer-defined custom fields on Jobs map to Crelate custom fields on the Job object. Crelate enforces a maximum of 20 custom fields per entity, and the Job object is included in this limit. We extract all JOIN Job custom fields during scoping, assess which fall within the 20-field cap, and surface any overflow to the customer for prioritisation before migration begins.

JOIN custom fields on Candidates map to Crelate custom fields on Contact. Field types (Short Answer, Picklist, Date, Numeric, Monetary) are mapped to equivalent Crelate field types during the transform phase. If the total exceeds the 20-field cap, we compress low-value fields into a structured note or deferred re-entry list. Picklist values from JOIN transfer as Crelate picklist options; the customer confirms the picklist configuration during scoping.

Candidate resume files and supporting documents export from JOIN and upload to Crelate as linked file references on the Contact record. JOIN filenames are derived from internal IDs and require normalisation to a consistent convention (CandidateName_JobTitle_Date) to prevent collisions and ensure files are identifiable after ingestion. We apply this normalisation during the export phase before bulk upload to Crelate's document storage.

JOIN does not expose email threads, scheduled interview events, or call log entries through a documented API endpoint. We cannot retrieve this data programmatically. During scoping we flag this gap and instruct the customer to export the activity timeline as a CSV from the JOIN dashboard. We ingest this CSV alongside the API extract and attach the activity history as Notes or a linked document on the Crelate Contact record so that the timeline context survives cutover. The customer must perform the CSV export before the migration date.

JOIN Owners map to Crelate Users. We resolve Owners by email match against the destination Crelate User table. Any JOIN Owner without a matching Crelate User is held in a reconciliation queue, and the customer's admin provisions the missing User before record import resumes. Inactive JOIN Owners map to inactive Crelate Users to preserve historical attribution.

For agency recruiting workflows where Jobs represent client engagements rather than internal hires, JOIN Job records map to Crelate Company or Opportunity records in addition to Crelate Job. The customer specifies during scoping whether the migration follows an internal hiring model (Job as requisition) or an agency model (Job as client engagement with candidates as contacts on the client Company record). We configure the mapping accordingly before any data loads.

JOIN's referral source field on Applications (indicating where the candidate heard about the role) migrates as a custom picklist field on the Crelate Contact or as metadata on the Application entry. The customer confirms the preferred landing during scoping. If Crelate's standard source tracking fields are available in the destination plan, we map to those instead of a custom field.