Migrate from Recooty to Recruit CRM & ATS

Recooty Jobs map to Recruit CRM Jobs as the primary container. Job title, description, location, department, employment type, and publishing status migrate directly. Active versus archived status maps to the Recruit CRM Jobs active flag. We extract the job content during the discovery phase so it is available for manual republishing to job boards via Recruit CRM's own integrations post-migration.

Recooty Candidates map to Recruit CRM Candidates with full profile data: contact info, email, phone, source, application date, and pipeline stage. Resume files (PDF, DOC, TXT) migrate as attachments. Any custom fields defined in Recooty on Business or Enterprise migrate to Recruit CRM custom fields created during schema setup. Starter-plan source accounts without custom field support migrate only standard candidate fields.

Recooty's per-job visual pipeline stages (Applied, Screening, Interview, Offer, Hired, and any custom stages) map to Recruit CRM pipeline statuses. We extract the full stage definition including stage order and any custom stage colors or labels. Stage-level migration notes from Recooty migrate as candidate activity notes in Recruit CRM.

Recooty interview records (date, time, interview type, interviewer assignment, candidate link) map to Recruit CRM interview records. We preserve the interviewer name and candidate link. Note that Recruit CRM does not support bidirectional sync for deleted meetings with Google Calendar per user reports; calendar invites created in Recruit CRM post-migration will appear as new events rather than updating existing ones.

Recooty custom fields (available on Business and Enterprise plans only) map to Recruit CRM custom fields. We detect all custom field definitions during discovery, map field types (text, number, date, picklist) to their Recruit CRM equivalents, and pre-create the destination schema before migration begins. Starter or Growth source accounts without custom field support do not have this object to migrate.

Recooty Owners and team member assignments map to Recruit CRM Users by email match. We resolve owner IDs during the migration to populate the assigned Recruit CRM user on candidate and job records. Any Recooty Owner without a matching Recruit CRM User enters a reconciliation queue for the customer's admin to provision before record import continues.

Recooty GDPR consent records, retention policy configurations, and audit trail logs migrate as structured data into Recruit CRM compliance fields. We map candidate consent status to Recruit CRM's consent tracking fields and preserve retention policy metadata as note records. Audit trail logs migrate as structured CSV for the customer's compliance officer to review and act upon in the destination system.

Recooty branded careers pages built with the drag-and-drop builder (Growth and above) or hosted microsites (Business and Enterprise) cannot be directly migrated. The page content, job listings, and branding assets extract as reference data for manual rebuild in Recruit CRM's careers page builder post-migration. We do not migrate builder state or URL structure.

Recooty's 100+ job board integrations are configured as OAuth or API connections within Recooty. These tokens are not portable. Job board posting history (which boards a job was published to, at what times) is logged in Recooty but not exportable as structured data. We preserve the job content itself for republishing; the customer re-authenticates board integrations in Recruit CRM post-migration.

Recooty's pipeline metrics, hire velocity, and candidate rating analytics migrate as a reference export for the customer's admin to rebuild in Recruit CRM's reporting module. We do not migrate dashboard configurations or saved report definitions because the underlying data model differs between platforms. The migration deliverable includes a written list of Recooty report names and their source field definitions for manual rebuild.