Migrate your Recruiterflow data

Candidates are the core object in Recruiterflow's ATS. Standard fields (name, email, phone, status, source) are well-documented and map 1:1 to most destination ATS platforms. Custom candidate fields are supported and we preserve them as custom properties in the destination.

Contacts in Recruiterflow represent client relationships separate from candidates. They include company associations, contact details, and lifecycle stages. We map Contacts to the equivalent Contacts or Leads object in the destination CRM, preserving custom field data.

Jobs represent open reqs with standard fields (title, description, location, employment type, owner). Job pipeline stages are configurable per job type. We migrate Jobs as Jobs/Reqs with their associated pipeline stage configurations intact.

Placements track hired candidates tied to a Job and a Client/Company. They carry compensation data, start dates, and placement status. We map these to Placements or Offer objects but flag that placement-to-candidate linking logic varies significantly across ATS platforms and may require post-migration reconciliation.

Companies store client organization data including address, industry, size, and associated contacts. We map Companies to the Accounts/Companies object in the destination. Custom company fields are supported.

Deals track revenue opportunities tied to Companies, analogous to Opportunities in Salesforce. The deal value, stage, and owner map to the destination's opportunity object, but deal-specific fields like commission percentages may need custom field mapping.

Custom fields are available on Candidates, Contacts, Jobs, Placements, Companies, and Deals. The custom field schema varies by account. We export the custom field definition via the API alongside field values and remap them to destination custom fields during import, warning if destination lacks equivalent field types.

Activities include call logs, notes, and custom activity types. The API exposes separate endpoints for each activity category. We migrate activity history and associate it with the parent record, but note that not all ATS platforms expose activity history in the same timeline view.

Documents attached to candidates or jobs are accessible via GET /api/external/document/get. We download documents and re-upload them to the destination as attachments on the corresponding record.

Multi-channel sequences are core to Recruiterflow's outreach engine. Sequence definitions and enrollment status are stored per contact/candidate. We migrate sequence membership and step data but cannot migrate active campaign-sending state — contacts may need re-enrollment in the destination platform.

Recruiterflow's Off-Limits feature enforces compliance boundaries per client. We preserve these boundaries as Tags or a custom property in the destination to maintain the same client confidentiality rules.

Users map to the Owner/User assignment on Jobs, Candidates, Deals, and Activities. We migrate user records and re-link all owned records to the corresponding user identity in the destination system.