Migrate from Crelate to Recruit CRM & ATS

Crelate Contact records carry a type or tag field distinguishing candidates from client contacts. We split them during transform: candidate-type Contacts map to Recruit CRM Candidate records with all professional and skills fields preserved; client-type Contacts map to Recruit CRM Client records. The original Crelate Contact type is stored as a custom field migration_tag__c on the destination record for audit. If no type field exists, we use email domain patterns and job-application history to infer classification, flagging ambiguous records in the reconciliation report.

Crelate Company records map directly to Recruit CRM Client. The Company name becomes the Client name field, and the domain or website URL is preserved. Recruit CRM's Client object links to associated Job records and Candidate submissions, so we import Companies first to satisfy the parent dependency before any child record (Job, Candidate, Deal) is inserted. We deduplicate on company name plus domain during import.

Crelate Job records map to Recruit CRM Job. We preserve the Job-to-Company linkage (Crelate's company_id) as a reference to the imported Client ID. Job status, job title, location, and compensation fields transfer directly. If Crelate Job records carry a pipeline stage (for job-order tracking), we map it to Recruit CRM's Job status values and document any stage-specific automation that will require manual rebuild.

Crelate Opportunity records map to Recruit CRM Deal. The Opportunity name, stage, monetary value, and close date transfer directly. We resolve the Company reference to the imported Client ID and the Owner reference to the matched User. Stage probability percentages are mapped to Recruit CRM's Deal stage weights if available. Pipeline stages are preserved as a configuration mapping rather than a raw field copy.

Crelate Placements map to Recruit CRM Placements. A Placement is derived from an existing Job and Candidate relationship, so both parent records must exist in Recruit CRM before Placement migration begins. We use the Candidate email and Job title as the linkage key during the Placement import phase, and we preserve placement fee percentage, billing rate, and start date from the source record.

Crelate's 20-field per-entity cap is audited during scoping. Any Crelate entity with fewer than 20 fields migrates directly to Recruit CRM custom fields of the matching type (text, number, date, picklist). If the source entity uses the full 20-field cap and the destination has remaining capacity, we migrate all 20. If fields must be dropped, we surface the full ranked inventory during scoping and the customer makes the trade-off explicitly before migration begins.

Crelate Activities are gated behind a specific pricing tier. We verify the source Crelate plan includes Activity access before including them in migration scope. If included, Activities link to Contacts and Companies and transfer as timestamped activity records on the matching Candidate or Client in Recruit CRM. The Activities object in Crelate does not export via bulk CSV; we retrieve them through the Crelate REST API with pagination and 120 req/min rate-limit handling.

Documents attached to Crelate Contacts, Companies, Jobs, or Placements are exported via Crelate's bulk export or API and re-uploaded to the corresponding Recruit CRM record. We preserve document file names, MIME types, and upload timestamps. If Crelate's document export produces file URLs rather than file binaries, we download over HTTPS and re-upload to Recruit CRM. Large document volumes may require a separate document migration phase.

Crelate Tags applied to Contacts, Companies, and Opportunities are extracted and applied as Tags in Recruit CRM. Tags are flat label-based categorizations in both systems, so the mapping is direct. If the customer uses tags as a lightweight segmentation system (e.g., sourcing channel, candidate tier), we preserve the full tag set and note any tag-to-custom-field reclassification options in Recruit CRM.

Crelate Users (team members who own records) map to Recruit CRM Users by email address match. Any Crelate Owner without a matching Recruit CRM User account is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Crelate users with historical record ownership are mapped to inactive Recruit CRM users so that Owner attribution is preserved in historical reporting.

Crelate Opportunity and Job pipeline stages transfer as stage configuration documentation rather than raw data. We export the stage names, order, and probability weights from Crelate and provide Recruit CRM with the equivalent stage definition for their Deal and Job pipelines. Stage-specific automations (e.g., triggers firing on stage entry) are documented in the automation inventory and do not migrate as active logic.