Migrate from OpenCATS to Crelate

OpenCATS Candidate records map to Crelate Person. We extract first_name, last_name, email, phone, skills (stored as comma-separated tags in OpenCATS), and the candidate's status field, mapping to Crelate's Person Status values. The original skill tags from OpenCATS migrate to Crelate's Tags on the Person record. Candidate resume file paths are extracted as a separate list and flagged for SFTP transfer to Crelate's document storage, then re-linked by filename match post-migration.

OpenCATS Job Orders map directly to Crelate Jobs. The OpenCATS fields title, description, status, public_description, and assigned_recruiter map to Crelate's Job title, description, status, jobDescription, and assigned recruiter respectively. OpenCATS job type (full-time, part-time, contract) maps to Crelate's employmentType. We preserve the original open_date and close_date as custom fields if the customer requires historical job timing data.

OpenCATS Companies map to Crelate Organizations. Company name, address fields, phone, website, and industry map directly. OpenCATS supports multiple departments and locations per company stored as separate rows; we map these to Crelate Organization location records. The company name is the dedupe key during import, and we resolve Organization IDs before inserting any related Person or Job records.

OpenCATS Contact records (hiring managers and client contacts distinct from Candidates) map directly to Crelate Contacts. We extract name, title, company (linked to the Organization mapping), email, phone, and notes. Cold Call List entries from OpenCATS migrate as Crelate Contacts with a Cold Call List tag applied during import.

OpenCATS Activity records (calls, emails, meetings, notes tied to Candidates and Job Orders) map to Crelate Activities. The activity type maps to Crelate's activityType, date maps to activityDate, and notes content maps to Crelate's notes field. We resolve the parent Person and Job references at migration time using the record IDs extracted from the OpenCATS database. Activity ordering is preserved by timestamp.

OpenCATS Saved Lists are user-curated candidate groupings stored as list membership records in the database. We extract every Saved List name and its member Candidate IDs, then recreate the list associations in Crelate as either Tags on Person records or as a Crelate List (Group). The customer chooses the target structure during scoping. List order and ranking do not transfer; we document the original ordering for manual reconstruction if needed.

OpenCATS stores candidate resume files as filesystem paths on the server, not as database BLOBs. We extract every candidate_attachment record (file path, filename, file type) and produce a separate file-transfer manifest listing all resume paths and their associated Candidate IDs. The customer transfers files via SFTP to Crelate's document storage. We then re-link each file to the corresponding Crelate Person record by filename match. This is a two-step process requiring coordination between data migration and file transfer timelines.

OpenCATS Calendar Events map to Crelate Events with event title, start time, end time, and description. Recurrence patterns and reminder settings do not transfer; OpenCATS stores these in a format that has no direct Crelate equivalent. We flag recurrence configurations for manual rebuild in Crelate's calendar settings.

OpenCATS User accounts map to Crelate Users. We extract user_id, first_name, last_name, email, and role, matching by email against the destination Crelate User table. If the Crelate org is provisioned before migration, we validate that all OpenCATS users have matching Crelate accounts. Users without a Crelate match enter a reconciliation queue for the admin to provision. OpenCATS role-permission structures (admin, limited-access recruiter) map to Crelate permission roles, but the mapping is reviewed against Crelate's role model during scoping because permission structures differ between platforms.

OpenCATS Reports are not exportable artifacts. OpenCATS generates reports from live database queries at the moment of display; report definitions are not stored as separate objects. We do not migrate report definitions. We deliver a written list of every OpenCATS report the customer has accessed in the last 90 days with the query parameters and filter logic, so the customer's admin can recreate them in Crelate's reporting module post-migration.

OpenCATS custom fields added by the customer to any core object (Candidate, Job Order, Company, Contact) are stored as columns in the MariaDB schema. We audit the full OpenCATS database schema before migration, identify every custom column, map it to the equivalent Crelate custom field, and configure the destination field before importing the related records. Crelate enforces limits on custom field counts by tier, which we surface during scoping. If the customer's custom field count exceeds the Business tier limit, we recommend Business Plus or Enterprise.

OpenCATS Job Order status values (New, Open, On Hold, Cancelled, Filled) and custom status definitions map to Crelate Job Pipeline stages and status values. We extract the full status list from the OpenCATS database and recreate it as Crelate Pipelines and Stages during the schema setup phase before any record import begins. Stage probability values (if configured in OpenCATS) migrate as Crelate stage weights.