Migrate your Recruitly data
Cloud-based recruiting CRM and ATS built for staffing agencies and independent recruiters, combining candidate sourcing, placement tracking, invoicing, and AI matching into a single platform.
In its favor
Why people choose Recruitly
The signal that keeps Recruitly on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Recruitly combines ATS, CRM, and AI candidate matching in one platform, eliminating the need to juggle separate systems for sourcing, client management, and billing.
The pricing model scales from free (200 contacts, 1,000 candidates) to enterprise with no feature gating — all plans include every feature, differentiated only by data volume limits.
Customer support receives consistent praise across G2 and Capterra reviews, with users highlighting fast response times and hands-on assistance during setup and integrations.
Implementation typically takes 2–4 weeks, which is fast for a full recruitment platform, and Recruitly offers a dedicated migration specialist for inbound switches.
The startup program offers 75% off for three years for agencies founded within the last three years, making it accessible for new entrants.
Agencies with complex multi-brand or matrix organisational structures find Recruitly's hierarchy and approval workflows less flexible than enterprise alternatives like Bullhorn or Salesforce.
Users migrating from full-featured ATS platforms report that Recruitly's reporting and analytics dashboards lack the depth needed for executive-level recruitment reporting.
The platform's focus on small-to-mid-size agencies means enterprise-grade compliance features (government contracts, healthcare regulations) require custom configuration or the top Enterprise tier.
Some users cite difficulty getting granular automation rules to behave as expected without significant configuration effort, especially for multi-step candidate nurture sequences.
Reasons to switch
Why people leave Recruitly
The recurring reasons buyers give for replacing Recruitly. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Recruitly fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Recruitly pricing overview
Recruitly uses a per-seat, per-month pricing model with annual billing (20% savings). All plans include every feature — differentiation is purely by record volume limits (Contacts, Candidates, Jobs) and API call quotas. The Free tier is a genuine trial option with real data limits, the Solo tier targets independent recruiters, Professional serves growing agencies, and Enterprise offers custom contracts for 50+ person organisations.
Free
Tier 1 of 5
$0/user/month
What's included
Need help selecting your HRMS?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Recruitly's schedule — see our quote-based pricing →
What gets migrated
Recruitly object support
Object-by-object support for Recruitly migrations. Per-pair details surface during scoping.
Candidates
Fully supportedThe primary recruitment object in Recruitly. Supports export from list view, folders, and saved searches. Custom fields are preserved via the Export Data module. We map all standard fields and handle the Candidate status/lifecycle stage explicitly.
Contacts
Fully supportedClient-side contacts managed under the Sales module. Record limits apply per tier (200 Free, 5,000 Solo, 25,000+ Professional). We scope total record counts during discovery to flag tier compliance at the destination.
Companies
Fully supportedClient company records with highly customizable column views across Sales Analytics, Recruiting Analytics, Recruiting Performance, Billing, General, Recent Activities, and Custom field groups. We map all visible columns and preserve custom field configurations.
Jobs
Fully supportedJob postings linked to Companies and Pipelines. Tier limits apply (5 Free, 25 Solo, unlimited Professional). Job status, requirements, and board distribution settings are migrated along with the job record.
Placements
Mapping requiredPlacements track the full lifecycle from offer acceptance through onboarding, guarantee period, invoicing, and commission. Placement-to-invoice linkage requires field mapping at the destination as invoicing structures differ across platforms.
Pipelines
Fully supportedCandidate pipelines are structured with stages tied to Jobs. We preserve pipeline stage names, candidate order within stages, and stage-to-stage movement history where available via the API.
Activities
Fully supportedRecruitly logs engagement activities on both Candidates and Contacts. We export Recent Activities fields and map them to the destination's activity or engagement log objects.
Outreach Campaigns
Mapping requiredEmail campaigns with per-tier recipient limits (100 Free, 500 Solo, higher on Professional). Campaign templates, send history, and open/click metrics require field-level mapping as campaign structures vary across CRMs.
Custom Fields
Mapping requiredRecruitly supports custom fields across all major objects. Custom field definitions are exported from the column customisation interface. We preserve them as custom properties at the destination, applying naming conventions as needed.
Folders and Saved Searches
Mapping requiredCandidates can be organised in Folders and via Saved Searches. These are soft-organisation constructs — we migrate the underlying record sets rather than the folder structure itself, and note folder names as tags at the destination.
Attachments
Mapping requiredCVs, cover letters, and supporting documents attach to Candidates and Jobs. We export attachments via Recruitly's export interface where the Export Data privilege is granted. Document format conversion may be required for non-PDF formats.
Users and Owners
Mapping requiredUser records and Owner assignments on Candidates, Jobs, and Placements map to the destination's user object. Recruiter names are preserved as custom fields if the destination has no matching user record.
Invoices and Billing Records
Mapping requiredPlacement-linked invoicing tracks revenue. Invoice line items, payment status, and trust account references require manual mapping review because billing workflows differ significantly between recruitment platforms.
| Object | Support | Notes |
|---|---|---|
| Candidates | Fully supported | The primary recruitment object in Recruitly. Supports export from list view, folders, and saved searches. Custom fields are preserved via the Export Data module. We map all standard fields and handle the Candidate status/lifecycle stage explicitly. |
| Contacts | Fully supported | Client-side contacts managed under the Sales module. Record limits apply per tier (200 Free, 5,000 Solo, 25,000+ Professional). We scope total record counts during discovery to flag tier compliance at the destination. |
| Companies | Fully supported | Client company records with highly customizable column views across Sales Analytics, Recruiting Analytics, Recruiting Performance, Billing, General, Recent Activities, and Custom field groups. We map all visible columns and preserve custom field configurations. |
| Jobs | Fully supported | Job postings linked to Companies and Pipelines. Tier limits apply (5 Free, 25 Solo, unlimited Professional). Job status, requirements, and board distribution settings are migrated along with the job record. |
| Placements | Mapping required | Placements track the full lifecycle from offer acceptance through onboarding, guarantee period, invoicing, and commission. Placement-to-invoice linkage requires field mapping at the destination as invoicing structures differ across platforms. |
| Pipelines | Fully supported | Candidate pipelines are structured with stages tied to Jobs. We preserve pipeline stage names, candidate order within stages, and stage-to-stage movement history where available via the API. |
| Activities | Fully supported | Recruitly logs engagement activities on both Candidates and Contacts. We export Recent Activities fields and map them to the destination's activity or engagement log objects. |
| Outreach Campaigns | Mapping required | Email campaigns with per-tier recipient limits (100 Free, 500 Solo, higher on Professional). Campaign templates, send history, and open/click metrics require field-level mapping as campaign structures vary across CRMs. |
| Custom Fields | Mapping required | Recruitly supports custom fields across all major objects. Custom field definitions are exported from the column customisation interface. We preserve them as custom properties at the destination, applying naming conventions as needed. |
| Folders and Saved Searches | Mapping required | Candidates can be organised in Folders and via Saved Searches. These are soft-organisation constructs — we migrate the underlying record sets rather than the folder structure itself, and note folder names as tags at the destination. |
| Attachments | Mapping required | CVs, cover letters, and supporting documents attach to Candidates and Jobs. We export attachments via Recruitly's export interface where the Export Data privilege is granted. Document format conversion may be required for non-PDF formats. |
| Users and Owners | Mapping required | User records and Owner assignments on Candidates, Jobs, and Placements map to the destination's user object. Recruiter names are preserved as custom fields if the destination has no matching user record. |
| Invoices and Billing Records | Mapping required | Placement-linked invoicing tracks revenue. Invoice line items, payment status, and trust account references require manual mapping review because billing workflows differ significantly between recruitment platforms. |
Gotchas
What to watch for in Recruitly migrations
Issues we've hit on past Recruitly migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Tier-based record limits are migration-critical
API rate limits restrict bulk migration throughput
Export Data privilege gates all bulk exports
Delta migration window is a tight Friday–weekend cutover
Companies module columns require explicit field mapping
| Severity | Issue |
|---|---|
| High | Tier-based record limits are migration-critical |
| High | API rate limits restrict bulk migration throughput |
| Medium | Export Data privilege gates all bulk exports |
| Medium | Delta migration window is a tight Friday–weekend cutover |
| Low | Companies module columns require explicit field mapping |
Leaving Recruitly?
Where Recruitly customers move next
5 destinations Recruitly can migrate to.
How a Recruitly migration works
Four steps, Recruitly-specific
Connect
API key (token-based) into Recruitly. Scopes limited to read-only on the data we move.
Map
We translate Recruitly-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Recruitly quirks before production.
Migrate
Full migration with Recruitly rate-limit handling. Rollback available throughout.
FAQ
Recruitly migration FAQ
Answers to the questions buyers ask most during Recruitly migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Recruitly migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther HR systems we support
Ready when you are
Migrate Recruitly.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Recruitly setup and destination — written quote back within a business day.