Migrate from ClearCompany to Crelate

ClearCompany Candidate records map to Crelate Contact records. We extract contact information (name, email, phone, address), application status, source, and candidate activity history. The association between a Candidate and the originating Job is preserved as a Crelate Job Application record linked to the Contact. Custom fields on Candidates map to Crelate custom fields by type: picklists to picklists, dates to date fields, freetext to short/long answer. Picklist values in ClearCompany must be pre-created in Crelate before import or the records will reject on insert.

ClearCompany Employee records (employment details, department, manager assignment, start date, and custom properties) map to Crelate Contact records with a custom employment flag. We map the ClearCompany manager field to a Crelate lookup on the Contact record by resolving the manager's email against the imported Contact list. Active and inactive employee status transfers as a Contact status field. Department assignment is resolved against the imported Department records using the same lookup resolution pattern.

ClearCompany Job records (title, department, location, status, and description) map directly to Crelate Job records. We export both active and closed positions to preserve historical context. Job-to-candidate associations migrate as Crelate Job Application records linking the Contact to the Job. Department reference on the Job is resolved to the imported Department record before Job insert to satisfy Crelate's required lookup constraints.

Organizational structure including departments, offices, and reporting relationships is exported from ClearCompany and mapped to Crelate's org hierarchy. We preserve parent-child department relationships using Crelate's lookup reference fields on the Department record. Department resolution is sequenced before Employee and Job import because both record types reference department as a required or conditional field.

ClearCompany User accounts (name, email, role, active/inactive status) map to Crelate User records. We resolve users by email match during import. Any ClearCompany User without a matching Crelate User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Role naming conventions differ between platforms and are mapped during scoping; we document the role mapping in the migration specification.

Performance review records, goals, and calibration data in ClearCompany do not have a native Crelate equivalent since Crelate lacks a performance management module. We export review records as structured Note or Attachment records linked to the corresponding Employee Contact, preserving the review date, rating, and free-text commentary. The customer decides during scoping whether to include historical review data or limit the export to current-year records.

Crelate does not include a learning management system. LMS content from ClearCompany (courses, learning paths, completion records, compliance data) cannot be imported into Crelate. We export course metadata and completion records as structured documents for the customer's L&D admin to re-enter in a destination LMS of their choosing. SCORM packages require explicit handling: we flag packages during scoping and either extract the package files as-is or confirm the customer wants content metadata only. This decision is made before any LMS extraction begins.

ClearCompany onboarding task checklists and new-hire workflows do not migrate as automation logic. Crelate has no onboarding workflow module. We export task definitions, completion status, and checklist structure as a written inventory document for the customer's admin to rebuild manually or through a separate onboarding configuration engagement. The task checklist content itself is preserved in structured CSV format for reference.

ClearCompany custom fields on Candidates, Employees, and Jobs vary by module and tenant configuration. We discover field definitions during scoping, flag any with picklist constraints, and pre-create the corresponding Crelate custom fields by type before record import. Picklist values in ClearCompany must have corresponding Crelate picklist values created first or the import will fail. Custom field mapping is documented in the migration specification with source field API name, destination field API name, data type mapping, and any transformation logic applied.

Documents attached to Candidate, Employee, and Job records are exported by reference. We extract file content where accessible and attach to the corresponding Crelate Contact or Job record. Files exceeding typical size thresholds are flagged during scoping. Crelate's document storage limits (15 GB on Business plan) are verified against total attachment volume before migration to confirm adequate destination storage.

Integration configurations and reference data (countries, job functions, source taxonomy) are exported for context. Active integration credentials including ADP, LinkedIn, and Indeed connections cannot be exported from ClearCompany for security reasons and must be re-established manually in Crelate. We deliver a reference inventory of every active integration with its configuration parameters so the admin knows exactly which integrations to re-connect after cutover.

ClearCompany tagging and categorization data on Candidates and Jobs migrates to Crelate's Tags feature. Tags are mapped by category using Crelate's tag structure, with the default category receiving the source tag name. Multi-value tags on a single record are split into individual tag assignments per Crelate's tag API format.