Migrate from Recruitly to Crelate

Recruitly Candidates map to Crelate's Candidate/Person record. Standard fields (name, email, phone, location, current_title, current_company, source, status, owner) map directly. We extract the full column configuration from Recruitly's candidate list view during discovery to capture all visible custom fields. Crelate supports custom fields on Person records (via Settings > Core Records > People), so custom field definitions from Recruitly are created as matching Crelate custom fields before the candidate import phase begins.

Recruitly Contacts (the client-side sales module records) map to Crelate Contacts. We scope total Contact record counts during discovery to flag compliance against the customer's Recruitly plan tier (200 Free, 5,000 Solo, 25,000+ Professional) and verify the target Crelate plan's contact storage limits. Owner assignment on Recruitly Contacts resolves to Crelate User records by email match. Contact status, source, and custom fields migrate as typed Crelate fields.

Recruitly Companies map to Crelate Companies. This is the most schema-complex mapping because Recruitly's Companies module exposes customizable columns drawn from Sales Analytics, Recruiting Analytics, Recruiting Performance, Billing, General, Recent Activities, and Custom field groups. We extract the customer's live column configuration before export to ensure every visible field is captured. Hidden default columns still exist in the Recruitly schema and are available for explicit mapping. Crelate Company records support custom fields via Settings > Core Records > Companies, and all Recruitly custom column values are migrated as matching Crelate custom fields.

Recruitly Jobs map to Crelate Job Orders. Job status, requirements, skills, salary range, location, and board distribution settings migrate. Tier limits apply on Recruitly (5 Free, 25 Solo, unlimited Professional) — we scope total Job count during discovery. Crelate Job Orders link to Companies (client) and support candidate submittal workflows. Job owner assignments migrate by email-to-User resolution.

Recruitly Placements (offer acceptance through onboarding, guarantee period, and commission tracking) map to Crelate Placements. The placement-to-invoice linkage requires field mapping because Recruitly and Crelate handle placement-linked billing differently. We preserve placement start date, end date, fee percentage, guaranteed period, and commission fields as typed Crelate custom fields if the destination Placements module does not have equivalent native fields. Recruitly's placement owner migrates as the Crelate User owner.

Recruitly Pipelines (candidate pipelines structured with stages tied to Jobs) map to Crelate Pipelines. We preserve pipeline stage names, candidate order within each stage, and stage-to-stage movement history where the Recruitly API returns this data. Crelate Pipelines support visual drag-and-drop management and are configurable per Job Order type. Stage probabilities from Recruitly migrate to Crelate as custom fields or are set as defaults per pipeline.

Recruitly logs engagement activities on both Candidates and Contacts (notes, call summaries, emails, meeting records). These map to Crelate Activity records and Notes linked to the relevant Person (Candidate or Contact) or Company. ActivityDate from Recruitly is preserved to maintain the engagement timeline ordering in Crelate. Recruitly's Recent Activities fields migrate as structured Crelate Activity records with type (Call, Email, Note, Meeting, Task) and body content preserved.

Recruitly custom fields across Candidates, Contacts, Companies, Jobs, and Placements are exported via the column customization interface. Custom field definitions are extracted during discovery, and matching Crelate custom fields are created (with equivalent field types: Text, Number, Date, Picklist, Boolean, etc.) in the destination Crelate tenant before data import begins. Crelate's Logical Name field on custom fields supports API-friendly naming, and we align the Crelate logical names with the source Recruitly field names for traceability.

CVs, cover letters, and supporting documents attached to Candidates and Jobs in Recruitly export via Recruitly's Export Data module (Export Data privilege required). We confirm privilege assignment during kickoff. Documents are mapped to Crelate's Document module and linked to the corresponding Candidate (Person) or Job Order record via ContentDocumentLink. Document format conversion is applied if Recruitly exports in a non-standard format, and all document links are verified post-import.

Recruitly User records and Owner assignments on Candidates, Jobs, and Placements map to Crelate Users. We resolve owners by email match across both platforms. Any Recruitly Owner without a matching Crelate User is held in a reconciliation queue for the customer's Crelate admin to provision before record import resumes. Inactive Recruitly users are migrated as inactive Crelate Users to preserve historical assignment data.

Recruitly Outreach Campaigns (with per-tier recipient limits: 100 Free, 500 Solo, unlimited Professional) do not migrate as active campaigns because Crelate's campaign model differs structurally. Campaign templates, send history, and open/click metrics are documented in a written campaign inventory we deliver to the customer's admin. On Business Plus, the customer rebuilds campaigns using Crelate's Automation & Sequencing module; we provide the source campaign structure, recipient counts, and send-date history for reference.

Recruitly placement-linked invoices with line items, payment status, and trust account references map to Crelate Invoice records where available. Crelate's Business Plus plan includes expanded billing and trust accounting features. Billing workflows differ significantly between platforms, so invoice line items are mapped field-by-field and the customer's admin reviews the invoice mapping before production import. Payment status and trust account fields migrate as custom fields if no native Crelate equivalent exists in the customer's target tier.

Recruitly Folders and Saved Searches are soft-organization constructs that do not have a structural equivalent in Crelate. We migrate the underlying record sets rather than the folder hierarchy itself. The full record sets returned by each Saved Search are captured at export time as tagged record sets and imported with a custom field folder_name__c carrying the source folder name, allowing the customer's team to rebuild folder-style views in Crelate.

Individual pipeline stages within Recruitly Jobs map to Crelate Pipeline Stages. Each Recruitly pipeline maps to a Crelate Pipeline, and each stage within it maps to a corresponding Crelate Stage with its probability percentage and name preserved. Stage ordering from Recruitly is preserved in Crelate's pipeline configuration. This mapping is applied during the Crelate pipeline setup phase before any candidate records are loaded.