Migrate from Recruitly to Recruit CRM & ATS

Recruitly Candidates map directly to Recruit CRM Candidates. We preserve all standard fields (name, email, phone, skills, experience, status, source) and custom candidate fields extracted from Recruitly's Export Data module column list. Owner assignments map via email match to Recruit CRM Users. Any Candidate without a matching owner is assigned to the admin user during migration and flagged for manual reassignment. Recruitly's folder structures are not migrated as folders; we deliver the folder membership as a tag or custom multi-select field in Recruit CRM.

Recruitly Contacts (client-side, Sales module) map to Recruit CRM Contacts. We scope total Contact record count during discovery against Recruitly's tier limits (200 Free, 5,000 Solo, 25,000+ Professional) and confirm the destination Recruit CRM plan can accommodate the volume. Standard fields (name, company, role, email, phone) and any custom Contact fields migrate as Recruit CRM custom properties.

Recruitly Companies map to Recruit CRM Companies. The Companies module in Recruitly uses heavily customizable column views across Sales Analytics, Recruiting Analytics, Billing, and Custom field groups. We extract the full column list from the customer's live system before export to ensure every visible and hidden-in-schema field is captured and mapped to the equivalent Recruit CRM property. Company domain from Recruitly maps to the Website field in Recruit CRM for deduplication.

Recruitly Jobs map to Recruit CRM Jobs. Job status (open, filled, cancelled), requirements, board distribution settings, and associated Job description fields migrate directly. Tier limits on Jobs (5 Free, 25 Solo, unlimited Professional) are validated against the migration volume during scoping. Job-to-Company linkage is preserved as a Company lookup in Recruit CRM.

Recruitly Pipelines structured with named stages tied to Jobs map to Recruit CRM's Kanban pipeline view. We preserve stage names, candidate order within stages, and stage-to-stage movement history where available via the Recruitly API. Recruit CRM allows pipelines to be shared across Jobs or assigned per Job; we confirm the customer's preference during scoping and configure accordingly.

Recruitly's Placement object tracks the full commercial lifecycle from offer acceptance through guarantee period, invoicing, and commission. Recruit CRM uses Deals as the commercial tracking object rather than a dedicated Placement object. We map Placements to Recruit CRM Deals, with the original Placement status preserved in a custom field (e.g., placement_status__c) and the guarantee period mapped to custom Deal fields. Placement-to-invoice linkage requires a manual mapping review because billing workflows differ between platforms. This is the most significant schema decision during scoping.

Recruitly engagement activities logged on Candidates and Contacts migrate to Recruit CRM's Note, Call Log, and Meeting objects. We preserve the original activity timestamp and the linked record reference. Call duration and disposition from Recruitly map to custom fields on Recruit CRM Call Log. Meeting location and attendee data migrate to Recruit CRM Meeting records.

Recruitly outreach campaigns with templates, recipient lists, and send history map to Recruit CRM Sequences. Campaign send history and open/click metrics require field-level mapping because campaign structures differ between platforms. We deliver a written campaign inventory with the sequence name, step count, cadence, and recommended Recruit CRM Sequence rebuild steps for the customer's admin.

Recruitly custom fields across all major objects (Candidate, Contact, Company, Job) are extracted from the column customization interface and mapped to equivalent Recruit CRM custom properties. Field types are matched to Recruit CRM's available types (text, number, date, picklist, multi-select, checkbox). Any Recruitly custom field without a direct Recruit CRM type equivalent is mapped to a text field and flagged for the customer's admin to review and re-type post-migration.

Recruitly attachments on Candidates and Jobs (CVs, cover letters, branded CVs, supporting documents) migrate as Files in Recruit CRM linked to the parent Candidate or Job record. Document format conversion is handled where required. We require the Export Data privilege on Recruitly to initiate bulk attachment export; this is confirmed during kickoff.

Recruitly Users and Owner assignments on Candidates, Jobs, and Placements map to Recruit CRM Users by email match. Recruiter names without a matching Recruit CRM User are preserved as a custom Owner field on the record for manual assignment post-migration. We request the complete user list from Recruitly during discovery to reconcile against the destination account's active licences.