Migrate from CATS to Crelate

CATS Candidates map to Crelate People. Every Candidate record carries contact details (name, email, phone, address), status, source, and any custom field values. We export via CATS' built-in XLS/CSV export or direct API pull where available, normalize the name fields (first_name, last_name) to Crelate's Person object format, and preserve the original CATS candidate ID in a custom field cats_original_id__c for reconciliation. Duplicate detection in Crelate uses email as the dedupe key.

CATS Job Orders map to Crelate Jobs. Job Order fields (title, status, department, description, internal ID) map to equivalent Crelate Job fields. CATS pipeline stages (New, Screening, Interview, Offer, Hired, Rejected) are extracted during discovery and mapped to Crelate's configurable workflow stages, which we set up before Job import begins so that stage assignment resolves at migration time rather than defaulting to a null stage.

CATS Activities (calls, emails, notes, interviews) are linked to Candidates and Job Orders with timestamps, owners, and type flags. We preserve the full activity history and owner attribution. Call dispositions, durations, and meeting locations transfer to Crelate Activity records with original timestamps preserved for timeline integrity. Activities referencing a CATS Candidate that has not yet been migrated are held in a dependency queue and resolved after Person import completes.

CATS supports text, dropdown, date, and checkbox custom fields on Candidates and Job Orders. We export the full custom field schema (field name, type, and all picklist values for dropdowns) and re-create each field in Crelate with the equivalent field type before importing any records that reference those fields. Text fields map to Crelate text fields, dates to Crelate date fields, and dropdowns to Crelate picklists with the source picklist values migrated as options.

CATS user accounts (name, email, role, department) map to Crelate Users. We extract the user list and attempt email-based matching against Crelate's destination user roster. Any CATS Owner without a corresponding Crelate User is held in a reconciliation queue; the customer's admin provisions the missing Crelate Users before Person import resumes. Owner assignments on Candidates, Job Orders, and Activities are resolved at migration time using the validated user mapping.

CATS Departments categorize Job Orders and sometimes Users. We export the department list and re-create it in Crelate as a Department record before importing Job Orders that reference a department. Department order is preserved from the CATS export. If CATS has no Department records, we use CATS' Job Order grouping or owner department assignments as the basis for Crelate Department creation.

CATS allows free-text or pre-defined tags on Candidates and Job Orders, stored as comma-separated values in the export. We parse the tag list per record and create corresponding Tag records in Crelate, then attach them to the migrated Person or Job. If the destination uses a different tag taxonomy, we flag this during scoping and present the customer with a choice between a direct tag-to-tag mapping or a tag consolidation step before import.

Candidate sources (LinkedIn, Referral, Job Board, etc.) are stored as a field on CATS Candidate records. We preserve source attribution during migration and create corresponding Source records in Crelate if the destination does not already have matching source values. If CATS uses a source taxonomy that does not map cleanly to Crelate's source options, we present a mapping table for the customer's admin to approve before import.

CATS stores resumes, cover letters, and other file attachments linked to Candidates. We pull attachments via the CATS export tool or API, preserve file names and association metadata (which Candidate the file belongs to, file type, upload date), and re-upload them to Crelate's document storage linked to the corresponding Person record. File associations are resolved after Person import completes using the cats_original_id__c reconciliation field.

CATS uses a configurable pipeline with named stages. We extract the complete pipeline configuration (stage names, order, and any status-change rules) during discovery and map it to Crelate's recruiting workflow stages. Crelate's workflow builder supports stage customization beyond CATS' default set, so we present the customer's admin with the full stage mapping table and allow additions (e.g., a Crelate-specific stage the customer wants to introduce at migration) before the Job import.

CATS Workflows define record routing, email triggers, and status-change rules as application configuration. Workflows cannot be exported as data from CATS and are not included in standard migration scope. During discovery, we identify every active CATS workflow rule, document its trigger, conditions, actions, and target object, and deliver a written workflow inventory with recommended Crelate Business Plus automation equivalents. The customer's admin rebuilds workflows in Crelate post-migration using this deliverable.

If CATS contains Placement records (hired candidates tied to Job Orders), we map them to Crelate Placement records with the Person-Job relationship preserved. Placement status, start date, and bill rate transfer to Crelate Placement fields. Placements referencing Candidates or Job Orders that were not migrated are flagged for the customer's admin to resolve manually after migration.