Migrate from Recruit CRM & ATS to Crelate

Recruit CRM Candidates map directly to Crelate's People records. Core profile fields (name, email, phone, current title, current company, location) migrate directly. We preserve source tracking fields, status, and stage assignments. Resume files attached to Candidates extract via the Recruit CRM Files API and re-upload to Crelate as resume attachments on the corresponding Person record. Active sequence enrollments are flagged as custom properties on the Person record for the customer's admin to rebuild in Crelate Sequencing.

Recruit CRM Contacts (hiring managers, referrers, business contacts distinct from candidates) map to Crelate People with a Contact type designation. We preserve all custom field values, contact type, and any associated notes or tasks. The Contact-Company association maps to the Crelate Organization lookup.

Recruit CRM Companies map directly to Crelate Organizations. Company name, website, industry, address, and custom properties migrate as Organization fields. The Organization record is created before any Contact or Candidate import so that the lookup relationship is satisfied at the moment of insert. Files attached to Companies (contracts, briefs) extract and re-upload with the same Organization association preserved.

Recruit CRM Jobs map to Crelate Job Requisitions. Job title, description, status, assigned recruiter, and custom properties migrate directly. We preserve the job pipeline stages and any stage-specific custom fields. The recruiter assignment on Jobs maps to the Crelate User lookup by email match. Job-to-Candidate associations (applications) migrate as Crelate submissions linked to the corresponding Person and Job Requisition.

Recruit CRM Deals track placement or business transactions tied to Companies and Candidates. Deal fields (deal name, value, stage, expected close date, assigned owner) map to Crelate Opportunity. The Deal-Company association maps to the Organization lookup; Deal-Candidate associations map to the Person lookup. Deal stage names and probabilities migrate as Opportunity stage configuration.

Recruit CRM's customizable pipeline stages per Job or Deal migrate as Crelate's hiring workflow stages. We extract the complete stage configuration including stage names, order, probability percentages, and any automation triggers, then configure the equivalent Crelate workflow stages before record import begins. Stage counts and naming conventions are preserved.

Recruit CRM Hotlists are curated candidate lists with custom names and saved search criteria. We migrate the candidate IDs in each hotlist as tagged groups in Crelate. The saved search criteria (Boolean logic, filter combinations) cannot migrate as executable filters; we document each hotlist's criteria so the customer's admin can rebuild equivalent filters in Crelate. Hotlist membership migrates as a custom tag field on the Person record.

Notes attached to Candidates, Companies, Contacts, or Jobs in Recruit CRM migrate as Note records in Crelate, linked via the appropriate parent reference (Person, Organization, or Job Requisition). Note content migrates as-is. Notes associated with multiple objects in Recruit CRM create multiple Note records in Crelate, each with the appropriate parent reference.

Recruit CRM call log records include duration, outcome, date/time, and linked contact or candidate. We migrate these as Crelate Activity records with type set to Call. Call disposition, duration in seconds, and outcome values migrate to corresponding Crelate Activity fields. The activity timestamp preserves the original call date/time for timeline ordering.

Recruit CRM meeting records with date, time, attendees, and outcome migrate as Crelate Activity records with type set to Meeting. Start time, end time, location, and outcome migrate directly. Attendee information migrates as linked Person references on the Activity record.

Recruit CRM Tasks linked to Candidates, Contacts, Companies, or Jobs migrate to Crelate Tasks. Task subject, description, due date, status, priority, and assigned owner migrate directly. We resolve the assignee by matching the Recruit CRM owner email to the corresponding Crelate User. Completed vs. open task status is preserved. Tasks without a matching assignee are assigned to the migration-admin user for reconciliation.

Files attached to Candidates (resumes, cover letters) and Companies (contracts, briefs) in Recruit CRM are accessed via the Files API endpoint. Each attachment is downloaded individually and re-uploaded to Crelate with the same parent object association preserved. Large volume file migrations (over 1,000 attachments) run in parallel batches with exponential backoff to avoid throttling. File names and MIME types are preserved during re-upload.

Recruit CRM user accounts (recruiters, consultants, admins) map to Crelate User records. We resolve users by email match across both platforms. Any Recruit CRM user without a matching Crelate User is placed in a reconciliation queue for the customer's admin to provision. Inactive Recruit CRM users may be mapped as inactive Crelate users depending on the customer's preference for historical assignment preservation.

Recruit CRM supports nested custom fields on Candidates, Jobs, Contacts, Companies, and Deals, with schemas fully defined per organization. We resolve the actual custom field set during discovery by querying the Recruit CRM API field definitions for each object. Each custom field is mapped individually to a Crelate custom property of the equivalent type (text, number, date, picklist, checkbox, multi-select). Any fields that cannot be matched are flagged with a recommendation for manual entry or alternative handling. Nested field structures are flattened into dot-notation custom property names in Crelate.