Migrate from OpenCATS to Recruit CRM & ATS

OpenCATS Candidate records map directly to Recruit CRM talent records. We extract first name, last name, email, phone, current company, current title, source, and all skill tags from the candidate_skill join table. OpenCATS stores skills as a many-to-many tag relationship rather than parsed resume fields; we flatten these into Recruit CRM's tag or skill field using a delimiter-separated string. Candidate status values map to Recruit CRM status options (Active, Passive, Placed, Rejected) based on the mapping agreed during discovery.

OpenCATS Job Orders map to Recruit CRM Job records. The job order title, description, status, openings count, assigned recruiter, and client company all transfer cleanly. OpenCATS job order status values (Opened, On Hold, Completed, Canceled) map to Recruit CRM status equivalents. We preserve the internal job order ID as a custom reference field so the customer's team can cross-reference the migration audit log back to the original OpenCATS record.

OpenCATS Company records map to Recruit CRM Client records. The company name, industry, website, address, and any notes transfer as standard fields. OpenCATS supports multiple locations and departments per company stored in separate address records; we flatten the primary address into the client record and hold additional locations in a structured CSV for the customer to review post-migration.

OpenCATS Contact records (hiring managers and client-side individuals) map to Recruit CRM Contacts. The contact's name, title, email, phone, and associated company link transfer as direct field mappings. OpenCATS Cold Call List entries are a subtype of Contact; we map them to standard Contact records with a cold_call_list flag custom field set to true.

OpenCATS Activity records (calls, emails, meetings, notes logged against Candidates and Job Orders) map to Recruit CRM Activity or Note entries. Activity type determines the destination object: calls and tasks map to Activity, email logs and general notes map to Note. We preserve the activity date, description, and associated candidate or job order ID as lookup references. Activity history volume is assessed during discovery; large histories (over 100,000 entries) may require staged migration with chunking.

OpenCATS Saved Lists are user-curated candidate groupings with no native equivalent in Recruit CRM's standard model. We extract list membership (candidate ID plus list name) and recreate associations as Recruit CRM candidate lists or tags depending on the customer's preference. List ordering and ranking within a list may not transfer; we document the original ordering as a separate CSV for manual reconstruction if ranking is business-critical.

OpenCATS User accounts with their name, email, and role map to Recruit CRM User accounts. We match by email address. Role-permission structures differ substantially between OpenCATS and Recruit CRM, so we map active users to the nearest Recruit CRM role (Admin, Standard User, Read-Only) and flag any users requiring a specific permission for the customer's admin to configure post-migration.

OpenCATS stores resume files as filesystem paths on the server disk, not as database BLOBs. We flag every candidate record with a resume file reference and provide a structured file list (candidate ID, original file path, filename) for the customer to transfer via SFTP to Recruit CRM. We then map the transferred file to the corresponding candidate record using the original filename and candidate name as the dedupe key. If the original file structure is not preserved during transfer, filename-matching fallback is used.

OpenCATS Calendar Events with title, start datetime, end datetime, location, and associated candidate or job order map to Recruit CRM Events or Activities. Recurrence patterns and reminder settings are not preserved; we note the original recurrence pattern in a custom field for manual reconstruction. Events without an associated candidate or job order are held in a queue for the customer to re-link post-migration.

OpenCATS installations commonly add custom fields to Candidate, Job Order, and Company records via the database schema. We audit the OpenCATS database for non-standard columns during discovery, map each to a Recruit CRM custom field of the appropriate type (text, number, date, picklist, checkbox), and create the destination schema before migration. Custom field logic such as conditional display rules does not transfer; we note these for the customer to reconfigure in Recruit CRM's field settings.