---
title: "Migrate to Recruit CRM & ATS: HRMS Migration Guide & Service"
description: "Migrating to Recruit CRM & ATS? Import limits, the migration checklist and every source we move into it."
url: "https://flitstack.ai/migrations/hrms/recruit-crm-ats"
---

# Migrate to Recruit CRM & ATS

Recruit CRM is an agency-focused ATS+CRM whose import model rewards teams that pre-create custom fields, pace their bulk loads, and load entities in the strict Company → Contact → Candidate → Job → Hotlist order.

Short answer

FlitStack AI migrates employees, payroll, and benefits into Recruit CRM & ATS from 200+ HR systems. Every field is mapped to Recruit CRM & ATS's objects, history and associations come across, the Recruit CRM & ATS setup is configured alongside, and the whole migration stays reversible in one click.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See every source →](https://flitstack.ai/migrations/hrms/recruit-crm-ats#sources-list)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

From Your system

Destination Recruit CRM & ATS ![](https://flitstack.ai/platforms-trim/recruit-crm-ats.webp)

200+ sources mapped into Recruit CRM & ATS

## What Recruit CRM & ATS supports, and where its import tools stop

- Agencies choose Recruit CRM for its full customizability — pipelines, stages, and fields can be tailored to any recruitment workflow without developer involvement.
- Small teams value the built-in CRM and ATS combined in one subscription, eliminating the need to purchase and sync separate systems.
- The Chrome extension for one-click LinkedIn profile collection streamlines candidate sourcing and reduces manual data entry for recruiters.
- Responsive customer support with fast issue resolution is consistently cited as a reason teams stick with the platform long-term.

**REST only** API key (token-based authentication)

**Rate limits** 60 requests per minute for accounts with 6 or fewer licenses; 10 requests per minute per license for larger accounts

| Object                | Support | Note                                                                                                                                                                                                                                                                                   |
| --------------------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Candidates            | full    | Candidates are the primary object in Recruit CRM, storing profile data, resume files, skills, status, and source. The API exposes candidates at /v1/candidates with standard CRUD endpoints. We migrate all candidate fields including custom properties and associated job histories. |
| Jobs                  | full    | Jobs represent open requisitions with associated pipeline stages and assigned recruiters. The Jobs endpoint supports associated custom fields per job-candidate pair. We preserve job structure, stage configurations, and assignment records during migration.                        |
| Contacts              | full    | Contacts are distinct from candidates in Recruit CRM, representing hiring managers, referrers, or other business contacts separate from job-seeking candidates. Contacts support custom fields and can be linked to companies.                                                         |
| Companies             | full    | Companies store client organizations, with associated contacts, jobs, and deals. The Companies endpoint supports custom fields. We map company-contact associations and preserve deal linkage during migration.                                                                        |
| Deals                 | mapped  | Deals track placement or business transactions tied to companies and candidates. Deal stages and values map to destination CRM opportunity objects but require value translation since field names and stage labels differ across platforms.                                           |
| Tasks                 | full    | Tasks linked to candidates, contacts, or jobs are exposed via the API. We preserve task assignments, due dates, and status but note that completed versus open task counts affect the migration scope.                                                                                 |
| Meetings              | full    | Meeting records with date, time, attendees, and outcome are migrated as activity records. The API exposes meeting endpoints that we map to the destination's calendar or activity object.                                                                                              |
| Notes                 | full    | Notes attached to candidates, companies, or jobs are stored as free-text records. We preserve the full note content and its association to the parent object during migration.                                                                                                         |
| Call Logs             | full    | Call log records include duration, outcome, and linked contact or candidate. We migrate call log entries as activity records in the destination system, preserving timestamps and outcomes.                                                                                            |
| Hotlists              | mapped  | Hotlists are curated candidate lists with custom names and saved search criteria. We migrate the candidate IDs in each hotlist as a tagged group or list in the destination platform since hotlist structure is platform-specific.                                                     |
| Custom Fields         | mapped  | Recruit CRM supports nested custom fields on Candidates, Jobs, Contacts, Companies, and Deals. Custom field schemas vary by organization and must be mapped field-by-field to the destination's equivalent custom properties.                                                          |
| Sequences             | mapped  | Email sequences are automation objects defining outreach cadences. We do not migrate sequence logic directly; instead we identify which candidates are enrolled in active sequences and preserve enrollment status as tags or notes in the destination.                                |
| Files and Attachments | mapped  | Files attached to candidates (resumes, cover letters) and companies (contracts, briefs) are accessible via the Files API. Large volume file migrations require chunked extraction and re-upload to the destination's file storage.                                                     |
| Users and Assignees   | mapped  | Recruit CRM user accounts map to recruiters, consultants, and admins. We map active user assignments on Jobs, Candidates, and Deals to the corresponding user records in the destination platform. Inactive or archived users require separate handling.                               |
| Pipeline Stages       | mapped  | Pipeline stages are fully customizable per pipeline. We extract the complete stage configuration including stage names, order, and any automation triggers, then rebuild the equivalent pipeline structure in the destination ATS.                                                     |

## The Recruit CRM & ATS migration guide

## Why teams migrate to Recruit CRM

*The four shapes a Recruit CRM migration takes, and what makes the platform easier — or harder — than the category average.*

Recruit CRM is operated by Workforce Cloud Tech, Inc. and headquartered in Norwood, New Jersey[1](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-1). The platform packages applicant tracking, CRM, sequencing and a Chrome sourcing extension into a single subscription aimed at recruitment agencies and executive-search firms, and is SOC 2, GDPR and AICPA-aligned[3](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-3).

The typical Recruit CRM customer is an agency of two to a hundred recruiters running perm, contingent or executive search desks. Compared with Bullhorn, Recruit CRM positions on a flatter onboarding curve, a unified Candidate/Contact/Company/Job/Deal model and a Chrome Extension that turns LinkedIn profiles into candidate records in one click[4](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-4). Compared with Crelate or JobAdder, it positions on AI tooling — an AI Resume Parser, AI Sourcing, and the Recruit CRM AI Voice agent for outbound calls[4](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-4).

The shapes of migration that actually land on Recruit CRM tend to fall into four patterns. First, homegrown replacements: an agency moving off a spreadsheet, a shared Google Drive of resumes, or a bespoke in-house tool. Second, enterprise-ATS downshifts, where the source is Bullhorn, Vincere or PCRecruiter and the agency wants a lighter platform with the same agency workflow but less administrative overhead[9](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-9).

Third, vertical-ATS swaps — Crelate, JobAdder, Loxo, Tracker — where object parity is reasonable but custom fields and pipeline stage names diverge. Fourth, generalist-CRM exits, where Zoho Recruit, HubSpot or a Salesforce build is being replaced by a recruitment-native tool. A Bullhorn-to-Recruit-CRM migration usually has clean entity parity but a much tighter custom-field budget; a Zoho-Recruit migration has cleaner picklist labels but loses Blueprint state machines on cutover[9](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-9).

What makes migrating to Recruit CRM easier than the category average is the built-in bulk importer — accessible from the candidates, contacts, companies and jobs pages, accepting XLS and CSV, and supporting an Override Data toggle and a Merge Duplicates matching parameter[7](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-7). Recruit CRM's own data-migration team also runs free imports for paid plans on basic Excel and CSV files[3](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-3) [6](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-6).

What makes it harder than the average is the strict bulk-load throughput budget that paces every migration script. The base subscription tier also caps custom fields at 15 and total candidate records at 10,000 — small migrations sail through but mid-size agencies often need to upgrade just to land their data.

Email and SMS Sequences, automation triggers, the Recruit CRM AI Agent rules and Kanban board configurations do not import — they are rebuilt from documentation. Teams that scope for that work up front finish on time; teams that assume parity do not.

> Teams that scope for the rebuild work up front finish on time; teams that assume parity do not.

## The Recruit CRM data model you need to map into

*Modules, custom fields, Hotlists, Hiring Pipelines, and the upsert keys you'll wire on every load — the destination schema decoded.*

Recruit CRM's ATS is built around five core modules — Candidates, Contacts, Companies, Jobs and Deals — plus engagement modules (Tasks, Meetings, Notes, Call Logs), collection modules (Hotlists, Lists), and operational modules (Placements, Timesheets, Invoices, Files).

Before you can map a field on the source side, you need to know which destination module the row belongs on, which fields it requires, and which value will serve as its upsert key. The table below summarises the modules you will touch.

| Object                               | What it stores                                          | Required                                        | Tier                                                                                                          |
| ------------------------------------ | ------------------------------------------------------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Candidates                           | People you place — applicants, contractors, perm hires  | First name, last name, email or phone           | All plans (base plan capped at 10,000 records)                                                                |
| Contacts                             | Hiring-manager-side individuals at client companies     | First name, last name, company link             | All plans                                                                                                     |
| Companies                            | Client and prospect organisations                       | Company name                                    | All plans; Parent/Child links supported[11](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-11)   |
| Jobs                                 | Open requisitions tied to a Company + Contact           | Job title, company, hiring stage, status        | All plans                                                                                                     |
| Deals                                | Sales / BD opportunities (CRM side)                     | Deal name, company, stage, owner                | All plans                                                                                                     |
| Hotlists                             | Lightweight shortlists of candidates for a job or pitch | Name; candidates attached individually          | All plans[4](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-4)                                   |
| Notes / Tasks / Meetings / Call Logs | Engagement and activity history per record              | Body / subject, owner, timestamp, parent record | All plans                                                                                                     |
| Placements / Timesheets / Invoices   | Confirmed hires, billable hours, client invoicing       | Candidate, job, start date, employment type     | Business Plan+ for invoicing and timesheets                                                                   |
| Files                                | Resumes, cover letters, document attachments            | Parent record, file binary, file type           | All plans; subject to attachment size cap[22](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-22) |

Recruit CRM does not expose a customer-settable external ID property in the same way Bullhorn does. Instead, the bulk importer matches on one of three unique parameters — email, phone or name — chosen on the Merge Duplicates dropdown at import time[7](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-7). The canonical key is the slug Recruit CRM assigns each record on creation; capture it in your source for re-runs.

Plan an external-ID strategy on day one: create a custom single-line text field named Legacy ID on each module, stamp the source primary key into every row before export, and use it both as the import-time match column (where supported) and as a stable reconciliation key in every post-cutover audit query.

Custom field types determine validation and storage; the catalogue below covers what you can model and the limits that apply.

| Field type                           | Limit                       | Notes                                                                                                                            |
| ------------------------------------ | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Single-line text                     | Defined per field           | Free-form string; pre-create one for Legacy ID per module                                                                        |
| Paragraph / text block               | Multi-line free text        | Used for legacy notes, summaries, or rich-text capture                                                                           |
| Number / Currency / Percentage       | Numeric storage             | Currency tracks the account's base currency; strip symbols on import                                                             |
| Date / Date-Time                     | Stored per account timezone | Confirm the account timezone before loading historical dates[13](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-13) |
| Dropdown (single-select)             | Defined per field           | Internal value matches display label; pre-create every option                                                                    |
| Multi-select                         | Defined per field           | Semicolon-delimited on bulk import                                                                                               |
| Checkbox / Boolean                   | True/false                  | Accepts true/false, yes/no, 1/0 on import                                                                                        |
| Nested custom fields                 | Per parent custom field     | Parent value gates the child options                                                                                             |
| Custom fields per module (base plan) | 15 per module               | Upgrade to Pro / Business / Enterprise for more                                                                                  |

Relationships in Recruit CRM are modelled as to-one and to-many associations. A Job belongs to one Company and one primary Contact; a Candidate can be attached to many Jobs through assignments and Hotlists.

**15 / 10,000** Base-plan custom-field and candidate caps Recruit CRM's base plan limits each module to 15 custom fields and total candidate records to 10,000 — a mid-size agency that exceeds either has to upgrade before importing.

There is no native cascade-delete: deleting a Job does not delete its assigned Candidates, Hotlists, Notes or Tasks — a behaviour to reproduce via scripted cleanup or workflow automation if your source relied on it.

## Pre-migration prep — the work before you touch Recruit CRM

*What must be true on the source, the destination, and across the team before the first row hits the bulk importer.*

The single best predictor of a clean Recruit CRM migration is how much work you do on the source side before the first import button is pressed. Recruit CRM's own data-migration guidance is explicit that stale candidate records, duplicate emails and outdated tags are the main reason post-migration search results drift from what recruiters expect[9](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-9).

> The single best predictor of a clean migration is how much work you do before the first import button is pressed.

Treat the source export as raw material that needs shaping to Recruit CRM's expected formats — email lowercased, phone in a single canonical format, picklist values rewritten to destination dropdown values, dates in the account timezone, and owners resolved to Recruit CRM user emails.

### Source-side prep

- Audit and dedup the source candidate database before export — Recruit CRM's bulk importer offers email / phone / name dedup, but the more cleaning you do up front, the fewer surprise merges you discover post-load[7](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-7).
- Stamp a Legacy ID on every source record — Candidate, Contact, Company, Job, Deal and Placement. Use the source primary key or a UUID and load it into a custom single-line text field. Every re-run and reconciliation query will lean on this.
- Normalise picklist values for Candidate Status, Job Hiring Stage, Job Status and every custom dropdown. Recruit CRM matches dropdown options exactly; rows targeting an undefined option arrive with an empty field, not an error.
- Decide resume-file scope. Each candidate has zero, one or many resumes. Decide latest-only, all-versions, or none — the resume leg is its own pipeline that runs after candidate rows land, and the AI Resume Parser will rewrite candidate fields if you let it[19](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-19).
- Confirm the account timezone and base currency before loading historical dates and salary fields. Recruit CRM stores dates per account timezone; mismatched offsets surface as one-day shifts on candidate timelines[13](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-13).

### Destination-side prep

- Choose the right subscription tier for the migration. The base plan caps custom fields at 15 per module and total candidate records at 10,000 — mid-size agencies usually need Pro or Business before they can load their data.
- Provision Users first under Admin Settings → Account Management → Users, ideally via SSO, and assign roles before importing — owner assignment falls back to the importing user if a referenced owner email does not exist[16](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-16).
- Pre-create every custom field under Admin → Custom Fields on the right module with the right type. Field types are not easily changed after rows arrive; get this right before the first import.
- Build Hiring Pipelines and Hiring Stages for each job type before importing Jobs. Multiple pipelines are supported and each job is assigned to one pipeline; Hiring Stage internal labels must exist before candidate assignments can target them.

### People prep

Cutover only works if humans cooperate. Lock down a source-system freeze window — typically 24 to 72 hours — and train recruiters on candidate search, Hotlist creation, Hiring Stage transitions, the Kanban board, and the Chrome Extension before go-live. A small-agency migration handled by the in-house team typically runs one to two weeks; a mid-size firm with resume backfill, Custom Field rebuilds and Sequence reconstruction runs two to four weeks of elapsed time[9](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-9).

## Import mechanisms: Bulk Importer and managed migration

*Two main paths in, each with different limits and shapes. Picking the wrong one is how agency migrations stall at scale.*

Recruit CRM exposes two main load paths and the right one depends on dataset size and module mix. The Bulk Importer covers most one-shot Candidate, Contact, Company and Job loads. Recruit CRM's own data-migration team runs managed imports for paid plans and is usually the cheapest path for small agencies[6](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-6).

### Bulk Importer (UI)

The native Bulk Importer is reached from any module index page — Candidates, Contacts, Companies, Jobs — via the Import button[7](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-7). It accepts XLS and CSV, walks through a column-mapping step, and exposes two import-time toggles that change the load semantics: Merge Duplicates (with a one-of-three match parameter — email, phone or name) and Override Data (whether incoming values overwrite existing values on a matched row).

With Merge Duplicates off, every row is a fresh insert and the importer will happily create candidates with the same email. With Override Data off, matched rows only update empty fields — non-empty existing values stay untouched[7](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-7). The right combination for most migrations is Merge Duplicates on, Override Data on, with email as the match parameter, but verify on a 50-row pilot before scaling.

**15 / 10,000** Base-plan custom-field and candidate caps Recruit CRM's base plan limits each module to 15 custom fields and total candidate records to 10,000 — a mid-size agency that exceeds either has to upgrade before importing.

### Managed migration (Recruit CRM team)

Recruit CRM offers a free data-migration service to paid customers on basic Excel and CSV imports of Candidates and Companies[6](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-6) [3](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-3). The service runs against a three-step process — Data Discovery (export from the old ATS), Importing (the Recruit CRM engineer loads into your account), and Deployment & Reviewing (quality check) — and is bundled with the implementation contract for Pro and above tiers[3](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-3).

For more complex migrations — multiple modules, large resume estates, picklist remapping, Hotlist reconstruction — the in-house service caps at what their team can do in CSV without writing custom scripts, and the residual work goes to either a third-party migration vendor or an in-house engineering effort.

Under 5,000 Candidates / Contacts / Companies and standard fields → Bulk Importer (or managed migration). Hotlist reconstruction, resume-file backfill, and re-runnable loads typically benefit from a specialist vendor on the Business Plan tier.

## Mapping your data into Recruit CRM

*The longest section — because field mapping is where almost every migration that fails actually breaks.*

Mapping is where every agency-ATS migration earns its scars. The schema decisions in your mapping spreadsheet determine whether recruiters find candidates on day two, whether Hotlists rebuild correctly by day five, and whether placement reports trust the data by day thirty.

Work module by module in strict import order: Companies first (so Contacts and Jobs can associate), then Contacts, then Candidates, then Jobs, then Hotlists and assignments, then Notes / Tasks / Meetings / Call Logs, then resume files, and Deals / Placements last.

### Candidates and resume files

The Candidate module is the centre of gravity for an ATS migration. Each candidate has a profile (name, email, phone, address, status, owner), one or more resumes attached as files, a set of skills and tags, optional EEOC fields (typically as custom dropdowns), and timeline activity from Notes, Tasks, Meetings and Call Logs.

Recruit CRM's AI Resume Parser can extract candidate fields from an uploaded resume — name, email, phone, current employer, skills[19](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-19). This is brilliant for net-new sourcing but dangerous on migration: a resume uploaded against a candidate you just loaded can overwrite your carefully-mapped fields. Either disable parser overwrite via Account Settings before resume backfill, or load resumes as plain document attachments rather than triggering the parse flow[19](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-19).

| Source                                    | Destination                              | Note                                                                                                                                   |
| ----------------------------------------- | ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| candidate\_id                             | Legacy ID (custom single-line text)      | Stamp source primary key; use as match column on re-runs                                                                               |
| first\_name / last\_name                  | first\_name / last\_name                 | Required; preserve case as candidate-entered                                                                                           |
| email                                     | email                                    | Lowercase, trim; default match parameter for Merge Duplicates[7](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-7)        |
| phone                                     | contact\_number                          | Single canonical format; alternative match parameter to email                                                                          |
| status / pipeline\_stage                  | candidate\_status (dropdown)             | Map to a value pre-created in Admin → Custom Fields; mismatched values arrive empty                                                    |
| owner / recruiter                         | owner (User reference)                   | Map by user email; unresolved owners default to the importing user[16](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-16) |
| skills / tags                             | specialty / tags                         | Multi-value; semicolon-delimited; pre-create parent tag list                                                                           |
| source / referral\_source                 | source (dropdown) + custom Legacy Source | Drives source-effectiveness reporting; collapse out-of-range values to Other                                                           |
| gender / ethnicity / veteran / disability | EEOC custom dropdowns on Candidate       | Sensitive — respect retention and consent policies before loading[3](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-3)    |
| resume\_url / resume\_file                | File attachment on the Candidate record  | Upload as a document; consider disabling parser overwrite[19](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-19)          |

### Companies and Contacts

| Source               | Destination                      | Note                                                                                                                               |
| -------------------- | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| company\_name        | Company.company\_name            | Required                                                                                                                           |
| company\_id          | Company.Legacy ID (custom field) | Stable reconciliation key; reference from Contact and Job loads                                                                    |
| industry             | Company.industry (dropdown)      | Pre-create values under Admin → Custom Fields                                                                                      |
| parent / subsidiary  | Parent/Child Company link        | Set via the three-dot menu on each company or a follow-up pass[11](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-11) |
| contact email + name | Contact with company association | Cross-reference resolves the parent company at load time                                                                           |
| contact owner        | Contact.owner (User reference)   | Map by user email; falls back to importing user if unresolved                                                                      |

### Jobs, Hiring Pipelines and Hiring Stages — the ATS deep dive

The job-requisition pipeline runs Job → Candidate Assignment → Hiring Stage transitions → Placement, with each candidate-on-a-job tracked as an assignment that moves through Hiring Stages on the Job's Hiring Pipeline. A Job is the open requisition (e.g. Senior RN, Boston), an assignment is a candidate's application against it (often rendered as a card on the Kanban board), and a Placement is the confirmed hire.

Recreate every Hiring Pipeline and every Hiring Stage (Sourced, Screened, Submitted to Client, Interview Scheduled, Offer Extended, Placed, Rejected) in Admin → Settings before loading Jobs. Multiple pipelines are supported — agencies typically run separate pipelines for Perm, Contract and Executive Search. Jobs that target an undefined Hiring Stage on the named pipeline arrive at the pipeline's default stage with no error.

| Source          | Destination                                        | Note                                                                                                                                    |
| --------------- | -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| job\_id         | Job.Legacy ID (custom field)                       | Upsert key for cross-reference from assignments and Placements                                                                          |
| job\_title      | Job.name                                           | Required                                                                                                                                |
| client\_company | Job.company (Company reference)                    | Resolve via Legacy ID; Company row must exist first                                                                                     |
| hiring\_manager | Job.contact (Contact reference)                    | Resolve via Legacy ID; Contact row must exist first                                                                                     |
| current\_stage  | Job.hiring\_stage + Hiring Pipeline reference      | Map to defined Hiring Stage label; mismatched values default to the pipeline's first stage                                              |
| application\_id | Assignment on the Job                              | Candidate row + Job row must exist first                                                                                                |
| applied\_at     | Assignment timestamp                               | Stored per account timezone — convert source UTC offsets explicitly[13](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-13) |
| stage\_history  | Sequence of update operations per stage transition | Status transition history is built by repeated updates, not a history table                                                             |

Hiring Stage transition history is one of the most-asked-about pieces of an ATS migration and one of the least-supported on import. Recruit CRM has no stage-history table — the audit trail is built by repeated updates that each shift the assignment's current Hiring Stage. To preserve the timeline, capture each transition as `(assignment_id, hiring_stage, timestamp, user)` and replay updates in date order, accepting that the modifying user will be the migration user.

Alternatively, store the legacy stage history verbatim in a Candidate-level paragraph custom field named Legacy Stage History so it stays searchable, and let live history accrue forward from cutover. Most agencies pick the second path because it costs zero throughput and zero attribution loss.

### Hotlists — candidate shortlists per job or pitch

Hotlists are Recruit CRM's lightweight candidate-collection construct — a recruiter builds a Hotlist of, say, Boston RN shortlist – Memorial Hospital, adds five candidates, and shares it with the hiring manager. Hotlists do not behave like Jobs or Assignments — they are tags-of-tags, not pipeline records[4](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-4). On migration, source equivalents (Crelate Lists, Bullhorn Tearsheets, JobAdder Folders) map cleanly to Hotlists.

Build the Hotlist load as a second pass after Candidates have slugs assigned. Create the Hotlist, then attach each candidate individually. There is no bulk-attach in a single operation; every member is a separate write, which makes Hotlists a non-trivial fraction of total throughput on agencies with hundreds of named lists.

### Candidate sources, EEOC and consent

Candidate source tracking lives on the Source dropdown plus, often, a custom Legacy Source text field that preserves the original verbatim value. Source-effectiveness reporting in Recruit CRM keys off the standard Source field — populate it during candidate load rather than letting it default to blank.

EEOC data (ethnicity, gender, veteran status, disability) is typically modelled as a set of custom dropdown fields on Candidate. Treat them as sensitive: confirm the source export is permitted under your retention policy and that the destination's privacy posture matches. Recruit CRM is GDPR-aligned and stores data in AWS-managed data centres with AES-256-bit encryption[3](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-3).

### Notes, Tasks, Meetings, Call Logs — historical activity

Recruit CRM supports importing Notes, Tasks, Meetings and Call Logs against existing Candidates, Contacts, Companies and Jobs. Each Note carries a body, owner, timestamp, and one or more parent associations. The bulk importer does not cover these — they are a follow-up leg via the platform's bulk-load workflows.

Rich-text formatting on Notes is partially supported via the UI editor but does not always survive a programmatic write — paste-from-Word, embedded images and complex table markup get flattened. Convert source rich-text bodies to plain text or a Markdown-style structure during transform, and archive the original HTML in a Candidate-level paragraph custom field if downstream search depends on the original wording.

### Custom-field mapping strategy

Resist the urge to map every source custom field one-to-one. The base plan limits you to 15 custom fields per module; even on Business and Enterprise tiers, excess fields weaken search relevance, slow the Kanban board and make the AI Resume Parser less effective. Migrate only the custom fields used by an active recruiter workflow or report in the last 12 months.

For picklist fields whose source values do not match the destination, either: (1) extend the destination dropdown in Admin → Custom Fields, (2) collapse adjacent values during transform, or (3) introduce a parallel single-line text field holding the legacy value verbatim. Calculated / formula fields do not import — Recruit CRM has no formula field type, so source formulas must be pre-computed before export or replicated via external automation.

### Audit trail, ownership and original timestamps

Recruit CRM maintains an account-level Audit Log accessible to admins for monitoring user activity[17](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-17). The modifying user on every imported row is recorded as the migration user, which means historical attribution to the original recruiter is not preserved unless you stamp a custom Legacy Owner text field with the source user's name.

Created Date and Modified Date on every record are system-managed and stamped to import day — you cannot override them through the bulk importer. Create a Legacy Created Date datetime custom field on each module and populate it from the source export. Owner assignment during import works only if the user email exists in Recruit CRM at load time; unresolved owners default to the migration user, silently breaking per-recruiter reporting until cleaned up[16](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-16).

## The pitfalls that derail Recruit CRM migrations

*Specific failure modes — ranked by impact, each tied to the exact Recruit CRM mechanism that breaks.*

**high AI Resume Parser overwrites curated candidate fields on import**

If the AI Resume Parser is enabled and you load resumes alongside Candidate rows, the parser will re-populate first name, last name, email, phone and skill tags from the resume content — overwriting the values you carefully migrated[19](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-19). The fix is to either disable parser overwrite behaviour via Account Settings during the migration window, or to upload resumes as plain document attachments rather than through the parse flow, and re-enable parsing only for net-new candidates post-cutover.

**high Base plan's 15-custom-field and 10,000-record cap hit mid-migration**

Recruit CRM's base plan caps custom fields at 15 per module and total candidate records at 10,000. Agencies that planned the migration against the website's feature list but did not check the tier-specific limits discover the cap when they try to create custom field number 16 or import row 10,001 and get a hard error. Confirm your tier before the load and upgrade to Pro / Business / Enterprise if your dataset or schema exceeds the base cap.

**high Override Data and Merge Duplicates toggles silently change semantics**

The Bulk Importer's two toggles change everything. With Merge Duplicates off, every row is a fresh insert and you get duplicate candidates by the same email. With Override Data off, matched rows only fill empty fields — corrections in your cleaned CSV never reach the existing record[7](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-7). The right combination for most migrations is Merge Duplicates on with email as the match parameter, Override Data on — but verify on a 50-row pilot before scaling, because the wrong combination is invisible until you start spot-checking.

**high Created Date and Modified Date cannot be overridden on import**

Recruit CRM's system-managed Created Date and Modified Date are stamped to import day regardless of what your source export holds. Teams discover this on day two when reports filtered by Created Date return everything stamped to the import window[15](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-15). The mitigation is to create Legacy Created Date and Legacy Modified Date custom datetime fields on every module, populate them from the source export, and rewrite all historical-period reports to use the legacy fields.

**medium Hiring Stage history cannot be loaded as a history table**

Recruit CRM does not expose a stage-history table that accepts bulk inserts. The audit trail is built by repeated updates that each shift the assignment's current Hiring Stage, so preserving the original timeline means replaying every transition in date order — and the modifying user becomes the migration user, not the original recruiter. Most agencies pick the simpler path: store the legacy stage history verbatim in a paragraph custom field named Legacy Stage History and let live history accrue forward from cutover.

**medium Picklist dropdown values drop silently when not pre-created**

Recruit CRM matches dropdown values exactly against the options pre-created in Admin → Custom Fields. Rows whose source value does not exactly match a destination option arrive with the field blank — not with an error. This is invisible until a recruiter notices that Candidate Status is empty across half the database. The fix is to extract every distinct picklist value from the source, pre-create each option in the destination dropdown, build a value-mapping lookup, and validate the lookup against the live dropdown export before loading at scale.

**medium Sequences and AI Voice rules do not migrate — they rebuild from scratch**

Email and SMS Sequences, automation triggers, and the newer Recruit CRM AI Voice agent rules are not exposed in a way that round-trips from another platform[4](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-4). Teams that assume their Bullhorn Automation journeys or Crelate workflows will move across discover the gap mid-cutover. The fix is to inventory every active sequence and automation rule in the source, recreate them manually in Recruit CRM under Settings → Sequences and Settings → Automations, and re-enroll active candidates post-cutover via Hotlist-driven bulk enrolment.

**medium Datetime fields shift because they store in account timezone, not UTC**

Recruit CRM stores dates per account timezone rather than as offset-aware UTC values[13](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-13). A source `applied_at` of `2024-08-14 12:00 NZST` loaded without timezone conversion can appear one day earlier on the candidate timeline if the account is set to US Eastern. The fix is to confirm the account timezone before loading, convert every source datetime to the account timezone during transform, and document the convention in the migration spec so post-cutover edits stay consistent.

**low EEOC field migration without consent or retention audit**

Candidate ethnicity, gender, veteran and disability data are sensitive personal data under GDPR and US EEOC reporting rules. Recruit CRM is GDPR-aligned with AES-256 encryption on AWS infrastructure[3](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-3), but loading EEOC fields into a new account without checking the destination's retention configuration and the original collection consent is the kind of mistake that surfaces in a compliance audit, not QA. Confirm EEOC fields are in scope with legal before exporting, document the lawful basis, and lock access so only authorised users see them.

## Validation and cutover

*What to verify after the import job, in what order — and how to fail safely when something is wrong.*

Validation is the bridge between the import finishing and recruiters being allowed in. A three-stage validation works best: a 10 percent pilot load with recruiter spot-checks, the full load with real-time row-count monitoring, and a 30-day audit driven by Recruit CRM's Reports module[9](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-9). The most reliable signal is recruiters verifying their own desks — they know what right looks like better than any reconciliation script.

Build a reconciliation queries spreadsheet that compares source and destination on each of these counts. Anything outside a 0.5 percent variance gets investigated before users get login access.

- Total Candidates loaded vs. source — minus deliberately excluded rows (stale, opt-out, duplicate emails). Confirm none of the excluded rows landed by accident.
- Total Companies and Contacts loaded vs. source — checking that name-based collapse via the Merge Duplicates toggle did not over-merge separate clients.
- Total Jobs per Hiring Stage vs. source, plus distinct Hiring Pipeline counts — a non-trivial variance signals a stage-mapping error or a pipeline-routing mistake.
- Total Candidate Assignments per Job vs. source, and assignment counts per Hiring Stage — confirms the candidate pipeline shape per requisition matches.
- Hotlist membership — count candidates per Hotlist and compare against the source list. Hotlists are easy to miss because they sit outside the Job → Assignment chain.
- Notes / Tasks / Meetings / Call Logs per parent record with timestamp round-tripped — date-bucket the comparison to confirm Legacy Created Date conversion worked.
- Owner distribution per module — group by owner email and confirm no record landed owned by the migration user that should not have been[16](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-16).
- Resume-file counts per Candidate — count attached files per candidate and compare against the source. Missing files surface on day two as recruiters look up profiles.
- Legacy ID integrity — count distinct Legacy IDs per module; any nulls or duplicates indicate the upsert key was not consistently set.

On top of reconciliation, run a manual spot-check: pick 30 random Candidates across statuses and verify each field against the source UI. Pick five high-value Jobs and trace the full association graph — Company, Contact, Assignments, Hiring Stage, Hotlists, Notes, Files. If discrepancies show up in three or more of the 30, halt the load, fix the root cause, and re-import the affected rows by Legacy ID upsert.

Recruit CRM does not ship a native bulk-undo. The recovery path: every imported row carries a Custom Text field stamped Import Batch ID, and if catastrophe strikes, a bulk-delete in each module filtered by that batch ID rolls the import back[14](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-14). Recruit CRM Support can run a full account purge for catastrophic scenarios, but the operation is one-way and irreversible; it is queued like any support request.

Before the load starts, take a full export via Admin Settings → Account → Full Export — this captures CSVs of all candidates, contacts, jobs, companies and deals plus attached files for each, and can be run once every 90 days[14](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-14). The lighter Data Export (CSV only, once per day) is fine for daily backups, but the Full Export with files is the one to take immediately before any non-trivial import.

Cutover sequencing: (1) source ATS goes read-only and the desk is notified; (2) a final delta export captures everything changed during the test-import window; (3) delta is loaded via Bulk Importer against Legacy ID; (4) reconciliation runs; (5) recruiters get login access and a 48-hour hyper-care window; (6) source decommission is scheduled 30 to 90 days out, never same-day.

## Migration partners and tools

*In-house migration team, ETL vendors, specialist migration shops — what each is good for and how to choose.*

Recruit CRM ships a free in-house data-migration service to paid customers — Pro, Business and Enterprise tiers — that covers basic Excel and CSV imports of Candidates, Contacts, Companies and Jobs end-to-end, with a three-step process of Data Discovery, Importing and Deployment & Reviewing[3](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-3) [6](https://flitstack.ai/migrations/hrms/recruit-crm-ats#source-6). For most small agencies moving off a spreadsheet or a homegrown database, this is the cheapest and lowest-risk path.

Where the in-house service runs out of road is multi-module migrations from another ATS (Bullhorn, Crelate, JobAdder, Vincere, PCRecruiter), resume-file backfill at scale, Hotlist reconstruction, Hiring Stage history replay and Sequence rebuilds. Those workloads exceed what a CSV-driven import can handle and either move to a specialist migration vendor or to an in-house engineering effort.

On the third-party side, a small cohort of recruitment-tech consultancies offer Recruit CRM-bound migration packages with extraction-from-source plus programmatic loading. Pricing typically tracks record volume and resume-file depth, with a setup fee plus per-module line items for Candidates, Companies, Jobs, Hotlists and resumes.

ETL and iPaaS tools — Fivetran, Airbyte, Workato, Integrate.io — do not yet ship native Recruit CRM connectors as broadly as they do for Salesforce or HubSpot. Plecto and a small number of analytics integrations exist for read-side reporting, but write-side migration is almost always custom work or a Workato recipe written for the project.

Managed-migration cost ranges vary widely. A clean spreadsheet-to-Recruit-CRM load of under 10,000 Candidates with no resume backfill often lands free on the in-house service, or in the $1,500–$6,000 range with a specialist vendor. A Bullhorn-to-Recruit-CRM or Crelate-to-Recruit-CRM project with Hiring Stage history, Hotlist rebuild, resume backfill and Sequence reconstruction typically runs $8,000–$40,000, driven by record count, custom-field complexity and resume-file volume.

For teams that want to outsource the migration end-to-end, FlitStack specialises in Recruit CRM migrations and handles the field mapping, Legacy ID design, resume-file pipeline, Hotlist reconstruction, Hiring Stage history rebuild and validation work described in Sections 5 and 7. Pricing is fixed-fee, based on record count and source platform, with separate line items for resume-file depth and Hotlist volume so scope is transparent before signature.

This is one of several legitimate paths — the right choice depends on whether you want the free in-house Recruit CRM migration team, a Workato- or Fivetran-driven build, or a specialist migration vendor. \[Explore FlitStack →]\(/contact)

In this guide

## Recruit CRM & ATS migration checklist

An eight-phase, task-by-task punch list for moving candidates, contacts, companies, jobs, deals, hiring pipelines, resumes, and placement history into Recruit CRM. Typical timeline: 4–12 weeks.

0\. Decide & Plan 9 tasks

- **Document the in-scope Recruit CRM modules.** Decide which of Candidates, Contacts, Companies, Jobs, Deals, Tasks, Meetings, Notes, Call Logs, Hotlists, Placements, Invoices, and Timesheets are part of this project. Record each as in or out of scope.*If skipped: Mid-project scope additions force re-running mapping, sandbox tests, and Hiring Pipeline design from the start.*
- **Define historical-data scope per object.** Decide how many years of candidates, contacts, jobs, notes, call logs, meetings, and email history move across. Record cut-off dates per object so the export job is bounded.*If skipped: Without an explicit cut-off, the export expands into a multi-year dump that no one budgeted for transforming.*
- **Decide whether candidate Hiring Stage history is in scope.** Recruit CRM does not preserve historical Hiring Stage transitions through bulk import. Choose between replaying transitions in the destination to rebuild the trail, dumping the trail into a long-text custom field, or accepting current stage only.*If skipped: Discovering this constraint mid-cutover forces an emergency decision that loses years of placement-funnel analytics.*
- **Confirm base-plan record and custom-field caps.** The base plan caps candidate records at 10,000 and custom fields at 15 across modules. Confirm whether the target tier raises these caps or whether scope must be trimmed to fit.*If skipped: Loading past the record or field cap halts the import partway and forces unplanned plan changes during the cutover window.*
- **Assign a single accountable migration owner (DRI).** Name one person responsible for go/no-go on cutover. Document an escalation chain that includes Recruiting Operations, Sales (for Deals), IT, and Finance representatives.
- **Capture GDPR, residency, and retention obligations.** Recruit CRM hosts data on AWS with AES-256 encryption at rest. Document the Data Processing Agreement, transfer-impact assessment, candidate-consent provenance, and any retention rules that change on cutover.*If skipped: Legal blocks the import on go-live day when candidate-consent provenance or DPA review was not completed earlier.*
- **Set the cutover date, source freeze window, and parallel-run window.** Choose a date that avoids active client placements, candidate offer-stage activity, and invoicing periods. Define the freeze window during which the source ATS goes read-only.*If skipped: A cutover during an active placement push forces a partial cutover and a hand-reconciled candidate pipeline.*
- **Document the migration success criteria in writing.** List the row counts, candidate-pipeline reconciliations, and recruiter-acceptance checks that must pass before the project is closed. Include the source-system decommission date.
- **List explicitly out-of-scope items.** Examples: legacy email sequences, archived candidate pools, source-side automations, sourcing-extension caches. Capture them so they do not silently re-enter scope mid-project.

1\. Pre-Migration Prep 25 tasks

- **Run dedup on source candidate records using email plus phone.** Resolve duplicates in the source before export so two profiles do not merge into one candidate in Recruit CRM.*If skipped: Duplicate source rows merge into a single candidate record and historical notes attach to the wrong person.*
- **Run dedup on source companies using legal name and domain.** Normalize company name casing, strip Inc./LLC/Ltd. suffixes consistently, and resolve duplicates before export. Recruit CRM links Contacts and Jobs to a single Company record.*If skipped: Duplicate companies fork the contact graph and break Parent/Child Company linkage on the destination side.*
- **Standardize email casing and trim whitespace.** Lowercase emails and remove trailing spaces. Email is the practical upsert key for candidates and contacts.
- **Standardize phone numbers to E.164 format.** Strip parentheses, spaces, and dashes; prefix the country code with a leading plus.
- **Resolve candidates with missing required fields.** Recruit CRM requires first name, last name, and at least one contact channel. Fix missing values in the source rather than padding them with placeholder data later.
- **Export baseline record counts per object.** Count candidates, contacts, companies, jobs, deals, notes, meetings, call logs, placements, and attached files. These become the Phase 6 reconciliation reference.*If skipped: Without a count baseline you cannot prove later whether a number mismatch is a migration loss or a source-side change.*
- **Inventory custom fields across all source modules.** Capture field name, type, picklist values, required-on-import flag, and example values per source module. This becomes the master mapping reference for Phase 3.
- **Inventory pipeline stages and Hiring Stage history per job.** Per active job, capture the current stage, the dates of stage transitions per candidate, and the names of any rejection or disposition reasons.*If skipped: Stage-transition history is the foundation of placement analytics; missing it leaves recruiters blind to source-of-hire and time-to-fill trends.*
- **Audit Source field values across the candidate base.** Recruit CRM uses the Source field to track where each candidate came from (LinkedIn, Indeed, referral, etc.). Standardize source values now so they collapse cleanly to the destination picklist.*If skipped: Fragmented source values break source-of-hire reporting after cutover and force a manual cleanup per candidate.*
- **Audit candidate resume file inventory.** Per candidate, count attached resumes and identify the latest version. Recruit CRM's AI Resume Parser can overwrite candidate fields when a resume is re-parsed, so the file you load matters.*If skipped: Loading an out-of-date resume triggers AI Resume Parser to overwrite current candidate fields with stale values.*
- **Provision the Recruit CRM production tenant and confirm subdomain.** Confirm the app.recruitcrm.io login URL and any white-label subdomain match what you will hand to candidates, clients, and integrations.
- **Create users with appropriate roles before any load.** Pre-create every recruiter, hiring manager, and admin who will own records. Assign roles and team memberships so the import can attach ownership in one pass.*If skipped: Loading records before users exist forces a two-pass ownership update and leaves audit logs attributing every change to the migration account.*
- **Configure currency, timezone, and date format under Admin Settings.** These settings change how dates, fee amounts, and meeting timestamps are interpreted at import time. Set them before any sandbox load.*If skipped: A wrong tenant timezone shifts every imported datetime by hours and corrupts meeting and call-log audit trails.*
- **Build Hiring Pipelines with the full Hiring Stage list per pipeline.** Pre-create every Hiring Pipeline the team uses (Perm, Contract, Exec Search, RPO, etc.) and every stage on each pipeline before importing any jobs.*If skipped: Importing a job with stages that do not exist forces a re-create of the pipeline mid-load and drops historical stage data.*
- **Pre-create all picklist values for Candidate Status, Job Status, and Deal Stages.** Recruit CRM does not auto-create picklist values on import. Add every source value to the destination picklist via Admin Settings before any upload.*If skipped: An unknown picklist value silently drops the field on that row and produces blank statuses on hundreds of candidates.*
- **Create all custom fields across Candidate, Contact, Company, Job, and Deal modules.** Add custom fields via Admin → Module Settings, matching source data types from the audit. Stay under the per-plan custom-field cap.*If skipped: Importing into a field that does not exist yet drops the data on the row with no error indication.*
- **Pre-create Hotlists for shortlists you intend to preserve.** Hotlists are lightweight candidate collections used for ongoing roles, talent pools, and submitted-to-client lists. Create the destination Hotlist before assigning candidates.
- **Pre-create EEOC custom fields where required.** Recruit CRM does not ship a native EEOC schema. Add custom fields for gender, race/ethnicity, veteran status, and disability status with picklist values aligned to EEO-1 reporting categories.*If skipped: Loading EEOC values into Notes or free-text fields breaks the federal reporting workflow at year-end.*
- **Create a dedicated Data Migration user account.** Use a service account for bulk loads so audit logs cleanly attribute the changes to the migration project rather than to a named recruiter.
- **Pause Chrome Extension, AI Voice, and sequence automations during the load.** Disable the Chrome Extension's auto-import hook, pause active email and SMS sequences, and confirm AI Voice agents will not call back-dated candidate phone numbers during cutover.*If skipped: Active sequences fire during the bulk load and send weeks-old outreach to candidates the moment their record lands.*
- **Verify mobile app readiness for recruiters.** Confirm the Recruit CRM mobile app is installed and authenticated on recruiter devices so they can access migrated records on day one.
- **Communicate the source-system freeze window to all users.** Send the freeze date and time in advance and post it where recruiters, sourcers, and account managers will see it.*If skipped: Source-system changes after the freeze produce a delta the cutover plan cannot reconcile cleanly.*
- **Schedule role-based training before go-live.** Sessions for recruiters (Kanban board, candidate submissions, Hotlists), account managers (Deals, client portal), and admins (full UI). Use the Recruit CRM Help Centre as the baseline.
- **Designate first-responders for the first 14 days post-cutover.** Pick two recruiting-ops admins and one IT contact who will triage user questions and data fixes in Recruit CRM.
- **Distribute the new login URL and password-reset path.** Confirm every user knows where to log in and how to recover access on day one.

2\. Source Export 18 tasks

- **Export the master candidate list to CSV with all standard and custom fields.** Include first name, last name, primary email, phone, current employer, current title, location, salary expectations, Source, current Hiring Stage, owner, and every custom field from the Phase 1 audit.
- **Export the master contact list to CSV.** Include first name, last name, email, phone, title, linked company name, owner, and every contact-side custom field. Contacts are the hiring-manager and client-side records.
- **Export the company list to CSV.** Include company name, domain, industry, address, owner, and every company-side custom field. Capture Parent/Child relationships so they can be rebuilt post-load.*If skipped: Without Parent/Child mapping data, multi-entity client groups collapse into a flat company list and break account-level reporting.*
- **Export the job list to CSV with pipeline assignment.** Include job title, linked company, hiring manager, status, open date, close date, salary range, location, assigned recruiter, Hiring Pipeline name, and every job-side custom field.
- **Export deal records to CSV.** Include deal name, linked company, deal stage, value, currency, expected close date, owner, and every deal-side custom field.
- **Export Hiring Stage history per candidate per job.** For every candidate that touched a job, export the full sequence of stage transitions with stage name, timestamp, and the user who made the move. This is the input to the Phase 3 history-rebuild decision.*If skipped: Without the transition log, source-of-hire and time-to-fill reports cannot be reconstructed in the destination.*
- **Export placement records.** Per placement: candidate, job, start date, fee structure, commission split, and invoice status. Recruit CRM uses Placements as the bridge between Jobs and revenue tracking.
- **Export candidate-to-job association records.** Per candidate, export every job they are linked to with current stage on each. This is the junction data that drives the candidate's Jobs tab in Recruit CRM.*If skipped: Loading candidates and jobs separately without the association file leaves the destination Kanban boards empty.*
- **Export notes, meetings, tasks, and call logs as separate files.** Each object has a different schema. Include the parent record id, timestamp, owner, and content. Tag each row with whether it relates to a candidate, contact, company, job, or deal.
- **Export email correspondence as a per-record file.** Include sender, recipients, subject, body, sent date, and the linked candidate or contact. Decide whether to load as Notes attached to the timeline or to archive separately.*If skipped: Importing thousands of emails as Notes can blow past per-record activity limits and slow timeline rendering for the rest of the system's life.*
- **Export Hotlist memberships per candidate.** For each Hotlist, export the candidate ids on the list with the date they were added. Hotlists are lightweight collections that drive ongoing-role and talent-pool workflows.
- **Export candidate resume files with metadata.** Pull resume binaries (PDF, DOCX) and a metadata file with candidate id, original filename, upload date, and whether the resume is the latest version.*If skipped: Without metadata you have a folder of resumes no one can re-attach to the right candidate.*
- **Export candidate and company attachments beyond resumes.** Pull signed contracts, offer letters, right-to-work documents, and any portfolio uploads. Capture the linked record id, original filename, and document category.
- **Export the user list with roles and team assignments.** Capture which users were recruiters, sourcers, account managers, or admins in the source so Phase 1 user-creation stays grounded in reality.
- **Export pipeline and workflow definitions.** Pull every Hiring Pipeline configuration, every Deal Stage list, and any workflow-automation rules. Configurations do not transfer; they will be rebuilt.
- **Capture screenshots of source dashboards and reports.** Time-to-fill, source-of-hire, placement-revenue, and pipeline-funnel reports will be rebuilt by hand. Screenshot the definitions and filter criteria.
- **Capture screenshots and configuration exports of source automations.** Email sequences, candidate-status auto-updates, SMS reminders, and integration hooks will be rebuilt by hand. Document the trigger conditions and the actions taken.
- **Record the exact timestamp of each export.** Log the date and time per export file. The delta between this timestamp and cutover is what you re-export on cutover day.

3\. Transform & Map 32 tasks

- **Build a field-by-field mapping spreadsheet per object.** Columns: source field, source type, Recruit CRM field name, Recruit CRM type, transformation rule, required-on-import flag, sample value, mapping owner.*If skipped: Without one source of truth, two engineers map the same field two different ways and the discrepancy surfaces only at validation.*
- **Resolve picklist-value mismatches against Recruit CRM picklists.** Examples: source 'Submitted to Client' → destination 'Client Submission'; source 'On Hold' → destination 'Hold'. Document every replacement so it can be re-applied on cutover day.*If skipped: A picklist value that does not exist in the destination drops the field on that row with no error marker.*
- **Choose the upsert key per object.** Email for candidates and contacts; company domain or normalized name for Companies; legacy id stored in a custom field for Jobs, Deals, and Placements. Document the decision per module.
- **Decide handling for source fields with no Recruit CRM equivalent.** Per field: drop, concatenate into Notes, or create a new custom field. Record the decision in the mapping spreadsheet, mindful of the per-plan custom-field cap.
- **Reserve a Legacy ID custom field on every module.** Add a Legacy ID text field on Candidates, Contacts, Companies, Jobs, Deals, and Placements. Stamping the source id into this field enables idempotent re-runs and cross-module linkage rebuild.*If skipped: Without a stable legacy id, a failed reload duplicates every record because there is no key to upsert against.*
- **Convert all dates to YYYY-MM-DD with timezone awareness.** Reject anything not in ISO-8601 before upload and confirm the tenant timezone setting matches the import file.*If skipped: MM/DD vs DD/MM ambiguity silently swaps day and month on every row of stage-transition history.*
- **Normalize currency values to plain decimals with a period separator.** Strip thousands separators and currency symbols. For deal values in non-default currencies, structure the value with an ISO-4217 currency code.
- **Encode every CSV as UTF-8 without a byte-order mark.** Re-save every file in UTF-8. Special characters in non-Latin candidate names break parsing if the file is in Windows-1252 or ISO-8859-1.*If skipped: Mis-encoded files corrupt accented characters and force a name fix per candidate after the fact.*
- **Escape commas, quotes, and newlines inside text fields.** Wrap any field that contains a comma, double quote, or newline in double quotes and double the inner double quotes per RFC 4180.
- **Truncate text fields that exceed Recruit CRM column limits.** Confirm each text-field length cap against the destination schema and decide truncation vs. moving overflow into Notes.
- **Validate phone-number formatting per the phone-field type.** Confirm digits, plus signs, and approved separators only. Reject extensions in unsupported formats and either drop or move to a custom field.
- **Pre-resolve duplicates in the import file before relying on the Merge Duplicates toggle.** Recruit CRM's Bulk Importer offers a Merge Duplicates option keyed to one parameter at a time (email, phone, or name). Pick a single match key per file and ensure the source data has been deduped on that key first.*If skipped: Trusting the importer's auto-merge with a weak match key (name only) merges unrelated candidates and is hard to unwind.*
- **Decide the Override Data toggle setting per import batch.** Recruit CRM's Override Data toggle controls whether the import overwrites existing field values or only fills empty fields. Document the choice per file so reloads remain predictable.*If skipped: Running an import with Override Data on by accident overwrites manually edited destination records with stale source values.*
- **Decide the strategy for original Created and Modified timestamps.** Bulk-imported records stamp Created and Modified to the upload date, not the source date. Either accept the re-stamp or preserve the original timestamps in a Legacy Created and Legacy Modified custom date field.*If skipped: Field history starts on cutover day with no way to back-fill, surprising auditors and tenure reports.*
- **Decide record-ownership strategy at import time.** Either assign every imported row to the dedicated Data Migration user and bulk-update ownership after the load, or include the owner email in the import file so ownership lands correctly on the first pass.
- **Plan the post-import bulk-update pass for record owners.** Use the Update → Owner bulk action on the candidates, contacts, companies, and jobs pages to re-attribute records to the correct recruiter after the initial load completes.
- **Shape the Candidate database with paired Resume file references.** Per candidate row: ensure email, phone, current title, location, Source, and Hiring Stage are filled. Attach a single resume binary per candidate as a document after the candidate id is known.*If skipped: Bulk-uploading multiple resume versions per candidate triggers the AI Resume Parser to re-parse and overwrite current candidate fields with stale resume content.*
- **Stage resume binaries for upload as documents, not via the parser.** Attach resumes as document files rather than letting the AI Resume Parser overwrite fields. Disable parser auto-run for the migration batch where supported.*If skipped: Letting the AI Resume Parser run on every imported resume overwrites manually verified candidate fields with whatever the resume text says.*
- **Map the Source field per candidate to the destination picklist.** Recruit CRM's Source field drives source-of-hire reporting. Resolve every source value (LinkedIn, Indeed, referral, sourced via Chrome Extension, etc.) to a destination picklist value before upload.*If skipped: Loading Source values that do not match the picklist leaves the field blank and breaks source-of-hire dashboards.*
- **Shape the Job → Hiring Pipeline → Hiring Stage assignment per job.** Per job row, name the Hiring Pipeline and the current Hiring Stage. Confirm both exist on the destination tenant from Phase 1.*If skipped: A job that names a missing pipeline imports with no stages and strands all linked candidates outside the Kanban board.*
- **Decide and implement the Hiring Stage history rebuild pattern.** Pick one of two patterns. Replay pattern: after loading candidates and jobs, write each historical transition in chronological order. Paragraph-field pattern: concatenate the transition log into a Stage History long-text custom field on the candidate-job association.*If skipped: Skipping both patterns leaves placement analytics blind to source-of-hire and time-to-fill trends across migrated jobs.*
- **Sequence the replay-pattern transitions ascending by timestamp.** When replaying transitions, sort per candidate-job pair ascending by date and replay one at a time so the resulting current stage is correct.*If skipped: Out-of-order replay loads transitions backwards and the final state no longer reflects the candidate's true current stage.*
- **Shape the Placement records linked to Job and Candidate.** Each placement row carries candidate legacy id, job legacy id, start date, fee structure, and commission split. Load placements only after both candidates and jobs have been upserted.
- **Shape Hotlist membership data for the destination Hotlists.** Per Hotlist, build a candidate-id list and load after candidates exist. Tag each Hotlist with the source date-added in a custom field if the chronology matters.
- **Shape EEOC custom-field values to the destination picklists.** Map source gender, race/ethnicity, veteran-status, and disability-status values to the EEO-1 reporting categories on the destination custom fields. Decline-to-answer must be preserved as a distinct value.*If skipped: An EEOC value that does not match the destination picklist leaves the field blank and breaks EEO-1 reporting at year-end.*
- **Shape candidate-to-job association rows with current stage.** Per candidate-job pair: candidate legacy id, job legacy id, current Hiring Stage, date assigned, owner. Load after candidates and jobs both exist.
- **Prepare the Interview meeting payload with linked candidate, job, and panel.** Per interview meeting: candidate id, job id, panel member emails, start time, end time, location or video URL, and any Feedback Form responses. Load after candidates and jobs exist.
- **Stage Feedback Form responses against interview meetings.** Per interview, attach the scorecard rating per competency, free-text comments, and overall recommendation. Map source scorecard fields to the destination Feedback Form schema.*If skipped: Losing scorecard data forces hiring managers to re-interview candidates that were already vetted.*
- **Prepare the Parent/Child Company linkage file.** Per company pair: parent legacy id, child legacy id. Load after companies exist by calling the Parent/Child link action on each company page.
- **Stage email-history payloads as records on the timeline or as Notes.** Per email: candidate or contact id, sender, recipients, subject, body, sent date. Decide whether to load as full email records (preserves threading) or to drop each email as a Note (simpler load, no threading).
- **Pre-check resume and attachment file sizes against the platform cap.** Confirm every file is under the platform's per-file cap and route oversize content out to external storage with a link in the candidate's notes.*If skipped: Files over the per-file cap silently fail to upload and the metadata-linkage check fails at validation.*
- **Document that Chrome Extension, AI Voice, and sequence configurations will not transfer.** These workflow features are not importable. Capture configuration screenshots in Phase 2 and budget Phase 7 time to rebuild them by hand.

4\. Sandbox Test Migration 16 tasks

- **Set up a sandbox or trial tenant configured identically to production.** Mirror the Phase 1 setup: same users, same Hiring Pipelines, same custom fields, same picklist values. Keep both tenants in lockstep so sandbox results extrapolate.*If skipped: A sandbox that drifts from production hides bugs that only fire under the production schema.*
- **Load a 1–5% candidate sample through the Bulk Importer.** Pick a sample that covers active candidates, placed candidates, rejected candidates, and candidates with non-Latin characters in their name so edge cases surface early.*If skipped: A sample of only active North American candidates hides the bugs that hit the harder cases in production.*
- **Walk the recruiter who will run the import through the Bulk Importer UI.** Confirm the operator understands the Merge Duplicates match-key picker and the Override Data toggle before they touch a real file.*If skipped: An accidental Override Data import overwrites manually maintained destination records with stale source values.*
- **Validate 10 random sandbox candidates field by field.** Compare each value side-by-side against the source. Note date, currency, Source-field, and custom-field mismatches.
- **Test edge cases: names with non-ASCII characters, multi-line addresses, leading zeros in IDs.** Confirm the importer round-trips special characters and preserves leading zeros on text-typed numeric fields.
- **Test resume-file attachment as documents without parser auto-run.** Upload sample resumes against the sandbox candidates and confirm the AI Resume Parser does not overwrite candidate fields you populated from the source CSV.*If skipped: If the parser fires by default, plan a per-candidate field-restore pass before production.*
- **Test loading a sample job with a pre-existing Hiring Pipeline assigned.** Confirm the job lands with the correct Hiring Pipeline and that every stage is visible on the Kanban board.
- **Test the Hiring Stage history rebuild pattern end-to-end.** If using the replay pattern, throttle the loader and confirm transitions land in the correct order. If using the paragraph-field pattern, confirm the long-text field renders the transition log correctly.*If skipped: Effective-date order issues only show up in the UI; queries return rows in id order, which masks the problem until UAT.*
- **Test the candidate-to-job association load.** Confirm the candidate appears on the job's Kanban at the right stage and that the candidate's Jobs tab lists the job correctly.
- **Test Hotlist membership loading.** Add a sample of candidates to a sandbox Hotlist and confirm the membership renders on the Hotlist page.
- **Test Parent/Child Company linkage on a small set.** Link two sandbox companies as parent/child and confirm both pages display the relationship correctly.
- **Test interview meeting and Feedback Form load.** Load a sample interview with attached scorecard responses and confirm both render on the candidate's profile and the job's panel view.
- **Run a full-volume dry run within the sandbox throughput budget.** Load the entire candidate and job set in the sandbox and time the run. Multiply by a safety factor to forecast the cutover-window duration.*If skipped: A cutover window that turns out to be too short forces a partial go-live with candidates split between systems.*
- **Capture every error code and row id from the Bulk Importer logs.** Categorize errors as recoverable (fix the transform) vs. non-recoverable (drop the row, document the reason).
- **Have a domain expert review 25 sandbox candidates and 10 jobs.** Pick a senior recruiter who is not on the migration team. Their job: spot anything that 'looks wrong' to a daily user.
- **Get written sign-off on sandbox results before cutover scheduling.** The DRI signs off on row counts, stage-history reconciliation, resume-attachment integrity, and the sandbox UAT report.*If skipped: Skipping sign-off lets the cutover proceed with known sandbox defects still unresolved.*

5\. Production Cutover 20 tasks

- **Confirm the source-system freeze is in effect.** Verify there are no candidate, job, or deal changes in the source in the hour before export.*If skipped: Late source-side edits create a delta that the cutover plan has no time to reconcile.*
- **Take a final full export of source data.** Re-run every export from Phase 2 at the freeze time so the import file reflects the exact state at cutover.
- **Confirm Chrome Extension, AI Voice, and sequences are still paused.** Re-verify the paused state on every automation that could fire on imported records.*If skipped: An unpaused sequence fires during the bulk load and sends weeks-old outreach to candidates the moment their record lands.*
- **Load users and team assignments first.** If users were created in Phase 1, only refresh team and role assignments now. If not, create users before any record load so ownership can attach correctly.
- **Load Companies first via the Bulk Importer.** Use email-domain or normalized-name as the merge key. Stamp the source id into the Legacy ID custom field on every row.
- **Load Contacts second, linked to Companies by legacy id.** Match Contacts to Companies via the Legacy Company ID field. Confirm every contact lands with its linked company name visible.
- **Apply Parent/Child Company linkages in a third pass.** Once all companies exist, run the Parent/Child link action per pair via the company page.
- **Load Candidates next via the Bulk Importer.** Use email as the merge key with Merge Duplicates on and Override Data set per the Phase 3 decision. Stamp Legacy ID on every row.
- **Load Jobs next, linked to Companies and Contacts.** Match Jobs to their company and hiring-manager contact via legacy ids. Confirm every job lands with its Hiring Pipeline assigned.*If skipped: A job that loads without a pipeline strands every linked candidate outside the Kanban board.*
- **Load candidate-to-job associations with current Hiring Stage.** Write each association in. Throttle the loader to fit within the platform's documented throughput budget.
- **Replay Hiring Stage history in chronological order, throttled.** If using the replay pattern, walk each candidate-job pair's transition list ascending by timestamp and write each transition.*If skipped: Out-of-order replay loads transitions backwards and the final stage no longer reflects the candidate's true current state.*
- **Load Deals linked to Companies and Contacts.** Match Deals to their company and primary contact via legacy ids. Confirm every deal lands with the correct deal stage.
- **Load Placements linked to Candidates and Jobs.** Placements bridge revenue tracking. Confirm fee structure and commission split land intact.
- **Attach resume binaries as documents with parser auto-run disabled.** Upload one resume per candidate. If the AI Resume Parser is configured to auto-run on upload, batch-run a re-stamp pass after the load to restore overwritten fields.*If skipped: Letting the parser run during cutover overwrites manually verified candidate fields with raw resume text.*
- **Attach non-resume documents in a separate batch.** Load offer letters, signed contracts, right-to-work documents, and portfolio uploads as document files, tagged by category.
- **Load Hotlist memberships per candidate.** Add candidate ids to each Hotlist. Confirm membership counts match the export.
- **Load interview meetings and Feedback Form responses.** Create each meeting linked to its candidate, job, and panel. Attach Feedback Form scorecards per the Phase 3 decision.
- **Load notes, calls, and tasks linked to their parent records.** Create each note, call log, and task with the candidate, contact, company, job, or deal id. Time-throttle the loader.
- **Capture row counts, error logs, and job ids for every load step.** Save the Bulk Importer history and the load job ids in the migration runbook for audit and rollback evidence.*If skipped: Without per-step evidence a partial failure has no recovery point and the team starts the load over from row one.*
- **Re-enable Chrome Extension, AI Voice, and sequences.** Resume each automation only after every load step is reconciled. Confirm sequences do not back-fire on imported records by adjusting their trigger conditions if needed.

6\. Validate 20 tasks

- **Reconcile total candidate count between source and Recruit CRM.** Pull the candidate count via a custom report. The number must match the Phase 1 baseline minus any agreed exclusions.*If skipped: An unexplained delta of even a handful of candidates signals a silent drop somewhere in the transform.*
- **Reconcile total contact, company, job, deal, and placement counts.** Per module, compare the destination count to the Phase 1 baseline. Investigate every variance over 0.1%.
- **Reconcile active candidate count across every Hiring Pipeline.** Sum candidates on each pipeline's Kanban and compare to the source figure. Investigate any pipeline with a delta.*If skipped: A pipeline-level delta hides a bad Hiring Pipeline assignment that leaves candidates outside any board.*
- **Reconcile aggregate deal pipeline value.** Aggregate deal value by stage and compare to the source figure. Mismatches usually signal a currency-conversion or decimal-separator issue.
- **Cross-check 30 random candidates field by field against the source.** Pick candidates at random across stages, sources, and recruiters. Walk every field on each profile and confirm parity, including the linked resume.
- **Cross-check 20 random jobs against the source.** Confirm Hiring Pipeline name, current stage, hiring manager link, company link, and every custom field match.
- **Verify candidate-to-job associations on a sample of 25 candidate-job pairs.** Open each candidate's Jobs tab and confirm the job appears at the correct Hiring Stage with the correct owner.
- **Sample 20 Hiring Stage history rebuilds for ordering and date accuracy.** If using the replay pattern, walk each pair's stage-change history and confirm chronological order. If using the paragraph-field pattern, confirm the long-text field renders the full log.
- **Verify Parent/Child Company links on every multi-entity client group.** Open each parent company and confirm every expected subsidiary appears in the linked list.
- **Spot-check 15 candidates' resume attachments for filename and access.** Open each resume from the candidate profile, confirm it renders, and confirm the AI Resume Parser did not overwrite the candidate's manually verified fields.*If skipped: A silent parser overwrite is not visible until a recruiter notices that current title or salary expectations have reset to stale values.*
- **Spot-check 10 Hotlists for membership counts and date-added accuracy.** Per Hotlist, confirm the candidate count matches the export and that the date-added custom field is populated where chronology was preserved.
- **Verify Source field distribution against the source-of-hire baseline.** Run a Source-field report and confirm the destination distribution matches the source within 1%.*If skipped: A skewed Source distribution signals a picklist mismatch that silently dropped values across thousands of records.*
- **Verify interview meetings and Feedback Form scorecards on 10 sampled jobs.** Per job, open the panel view and confirm interviews render with the correct candidate, panel members, and scorecard responses.
- **Verify Placement records and commission-split accuracy.** Cross-check 15 placements between source and destination. Mismatched commission splits will surface as billing disputes within weeks.
- **Verify note, call-log, and task association with parent records.** Sample 25 activities and confirm each one is attached to the correct candidate, contact, company, job, or deal.
- **Trigger a Full Export to capture a post-cutover snapshot.** Run Admin → Account → Full Export to produce CSV files plus all attached binaries. This becomes the rollback baseline. Full Export is available once every 90 days.*If skipped: Without a Full Export captured immediately after cutover, a later data-corruption event has no clean restore point until the next 90-day cycle.*
- **Run a GDPR and SOC 2 evidence collection pass.** Capture the import job ids, who ran them, and when. File alongside the DPA and transfer-impact assessment captured in Phase 0.
- **Have 3–5 recruiters complete their day-one workflows in Recruit CRM.** Cover candidate search, Kanban move, submission to client, Hotlist add, interview schedule, and Feedback Form submit.*If skipped: Workflow gaps surface only at this layer and are cheaper to fix before go-live than after.*
- **Document every UAT-surfaced data issue and assign an owner.** Triage as block-go-live vs. fix-post-cutover. Block-go-live items go back into the cutover runbook for re-load.
- **Get written sign-off from the migration sponsor before Phase 7.** Sponsor signs off on row-count reconciliation, stage-history validation, resume integrity, and the UAT report.

7\. Post-Migration Cleanup 15 tasks

- **Announce go-live to all users with login URL and help contact.** Include the Recruit CRM mobile-app download links and a short FAQ for password reset, Kanban basics, and submission workflows.
- **Run role-based training sessions.** Recruiter Kanban workflows (30 minutes), account manager Deals (20 minutes), admin deep dive (60 minutes). Record each session for new hires.
- **Set the source ATS to read-only.** Disable writes per the freeze-window plan. Communicate the read-only date to anyone who still references historical data.
- **Rebuild source-system reports and dashboards inside Recruit CRM.** Time-to-fill, source-of-hire, placement-revenue, and pipeline-funnel reports do not transfer. List the top 10 reports the team relied on and rebuild each via Recruit CRM's reporting UI.*If skipped: Without rebuilt reports the team falls back to the source system within a week, undermining cutover.*
- **Rebuild email and SMS sequences from the Phase 2 screenshots.** Re-create every sequence in the destination. Re-attach trigger conditions, candidate filters, and step delays. Confirm sequences do not back-fire on imported records.
- **Re-deploy the Chrome Extension to every sourcer's browser.** Install the Recruit CRM sourcing extension on every active sourcer's Chrome profile and authenticate it against the new tenant. Confirm LinkedIn and Indeed profile capture flows work.
- **Reconfigure AI Voice agent profiles and call scripts.** Recruit CRM AI Voice agentic outreach configurations do not transfer. Rebuild voice prompts, qualification scripts, and routing rules. Run a paired-test before enabling outbound calls.
- **Re-establish downstream integrations.** Confirm payroll, calendar sync, video-interview, and BI integrations work against the new tenant. Validate at least one round-trip before disabling the manual export path.
- **Run the bulk Update → Owner pass to finalize record attribution.** If records were loaded under the Data Migration user, use the Update → Owner bulk action on each module to re-attribute records to their named recruiter.
- **Schedule a 30-day post-migration retrospective.** Capture what went well, what surprised the team, and which Phase 3 transform rules need updating for any future re-runs.
- **Set the source-system decommission date.** Typically 90 days after cutover, after the final retention window has closed. Document who signs off on shutdown.
- **Archive source-system exports and the migration runbook to long-term storage.** Encrypt the archive, store the key separately, and record retention duration per compliance policy.
- **Schedule the recurring Full Export cadence.** Full Export is available once every 90 days. Calendar the recurring run as the long-term rollback baseline. Data Export (CSV only) runs daily for lighter snapshots.*If skipped: Without a calendared Full Export cadence, the team forgets the 90-day cycle and a data-corruption event finds no recent restore point.*
- **Lower the migration service account to read-only or deactivate it.** Reduce the Data Migration user's privileges once the audit trail is captured and bulk-update passes are complete.
- **Close the migration project formally.** Final status report, lessons learned, and a project-closure note distributed to stakeholders.

Questions, answered

## Migrating to Recruit CRM & ATS: questions

How long does migration to Recruit CRM take?

A small-agency migration with under 5,000 Candidates and standard modules runs one to two weeks of elapsed time when handled by Recruit CRM's in-house team. A mid-size firm with Hiring Stage history, Hotlist rebuild and resume-file backfill runs two to four weeks, including prep, pilot loads, validation and hyper-care.

Can I migrate from Bullhorn to Recruit CRM?

Yes — Bullhorn-to-Recruit-CRM is a well-trodden path. Bullhorn's JobOrder, JobSubmission and Placement entities collapse into Recruit CRM's simpler Job + Assignment + Placement model, so the mapping work is more about reshaping pipeline records than copying fields. Watch the 15-custom-field-per-module base-plan cap — Bullhorn schemas often exceed it without upgrading.

Can I migrate from Crelate or JobAdder to Recruit CRM?

Yes — both are common Recruit CRM migration sources. Crelate's Contacts-on-a-Job model and JobAdder's Job + Candidate + Submission chain map cleanly to Jobs + Assignments. The bigger work is rewriting picklist dropdown values, collapsing legacy tags into Recruit CRM's specialty + tag system, and rebuilding Hotlists from source Lists or Folders.

Does Recruit CRM preserve original timestamps on import?

No, not on system-managed Created Date and Modified Date — those are stamped to import day regardless of source value. Activity timestamps on Notes, Tasks, Meetings and Call Logs are accepted at write time. For audit-trail preservation, create Legacy Created Date and Legacy Modified Date custom datetime fields per module.

Can I migrate resume files into Recruit CRM?

Yes, by attaching each resume to the Candidate record as a file. The AI Resume Parser will attempt to re-extract candidate fields from any resume uploaded through the standard parse flow, potentially overwriting your migrated data — either disable parser overwrite during the migration window, or upload resumes as plain attachments rather than triggering parsing.

What happens to Hiring Stage history during migration?

Recruit CRM does not expose a Hiring Stage history table that accepts bulk inserts — the audit trail is built by repeated updates. Either replay each transition in date order (slow, and the modifying user becomes the migration user) or store legacy stage history verbatim in a paragraph custom field.

Is there an undo or rollback for Recruit CRM imports?

There is no native bulk-undo. Stamp every imported row with a Custom Text Import Batch ID field and bulk-delete by that field if recovery is needed. Take a Full Export (Account → Full Export, CSV plus files) immediately before any non-trivial import — Full Export runs once every 90 days.

## Sources

1. [About Recruit CRM — Workforce Cloud Tech, Inc.](https://recruitcrm.io/about-us/)
2. [Seamless ATS data migration — Recruit CRM](https://recruitcrm.io/data-migration/)
3. [Top Recruit CRM features — Chrome Extension, AI Resume Parser, AI Voice](https://recruitcrm.io/features/)
4. [Recruit CRM Frequently Asked Questions](https://recruitcrm.io/frequently-asked-questions/)
5. [Bulk importing records — Recruit CRM Help Center](https://help.recruitcrm.io/en/articles/1466454-bulk-importing-records)
6. [Mastering data migration in recruitment — Recruit CRM Blog](https://recruitcrm.io/blogs/recruitcrm-exclusives/data-migration-in-recruitment/)
7. [Parent/Child Company Relationship — Recruit CRM Help Center](https://help.recruitcrm.io/en/articles/5569636-parent-child-company-relationship)
8. [Changing timezone and currency in Recruit CRM](https://www.youtube.com/watch?v=_qTGtX08Zi4)
9. [Exporting All Data for Recruit CRM Account Owners — Data Export and Full Export](https://help.recruitcrm.io/en/articles/3591116-exporting-all-data-for-recruit-crm-account-owners)
10. [Import Created Time and Modified Time — system-managed timestamps on ATS import](https://help.zoho.com/portal/en/community/topic/import-created-time-and-modified-time)
11. [Assigning Owners To Records — Recruit CRM Help Center](https://help.recruitcrm.io/en/articles/1794001-assigning-owners-to-records)
12. [Scheduling audit log reports in Recruit CRM](https://www.youtube.com/watch?v=1LOBbMCGo9M)
13. [AI Resume Parser and Resume Parsing Agent — Recruit CRM](https://recruitcrm.io/features/)
14. [Upload an Attachment — ATS file-attachment size limits and supported types](https://www.zoho.com/recruit/developer-guide/upload-attachment.html)

Get a quote

## Moving to Recruit CRM & ATS?

Tell us where your data lives today and roughly how much there is. We scope the migration and the Recruit CRM & ATS setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
