Migrate from CatalystOne to Crelate

Crelate Contacts are the primary candidate record and map directly to CatalystOne Persons. We use email address as the dedupe key. Standard fields — FirstName, LastName, Email, Phone, Title, City, State, Country — map to equivalent Person attributes. The original Crelate Contact ID is stored in a custom field (e.g., crelate_contact_id__c) for cross-reference and reconciliation after cutover. Crelate's Candidate notes (boolean flag on Contact) maps to an active_candidate__c custom field on Person.

Crelate Company records map to CatalystOne Organisations. Company Name becomes the Organisation name; website becomes Organisation URL; industry maps to an industry picklist if configured in CatalystOne. Crelate's Company-level contacts are linked to the Organisation. If the customer uses Crelate's division or office structure, we map those to CatalystOne Departments and preserve the hierarchy as a separate mapping pass before Person import.

Crelate Job postings map to CatalystOne Positions. Job Name becomes Position title; department and office assignments on the Job map to the Position's department and hierarchy fields. Crelate's job status (open, filled, cancelled) maps to an active_position flag in CatalystOne. We preserve the Crelate Job ID in a custom field on the Position for post-migration reconciliation. Positions created from filled jobs carry a filled_by reference to the Person record who was placed.

Crelate Submission records (a candidate applied to a job) have no direct CatalystOne equivalent because CatalystOne does not model a recruiting pipeline natively. We collapse submission history into Activity records attached to the Person, with the Activity type set to 'Application' and fields for original_job_title, submission_date, submission_status, and source_channel. This preserves the application timeline without forcing submission records into objects they do not fit.

Crelate engagement records — email, call, meeting, note — map to CatalystOne Activity records. Activity type maps to the CatalystOne activity category; body/content maps to activity notes; date and time are preserved. We resolve the parent Person record by email lookup so each activity attaches to the correct employee record. Call duration and disposition migrate to custom activity fields where CatalystOne supports them.

Crelate Tasks map to CatalystOne Activity records with type set to 'Task'. Task status (open, completed), priority, due date, and assigned user migrate directly. We resolve the assigned user by email match against the Crelate user table and hold unresolved assignments in a reconciliation queue for the customer's admin to map before production import.

Crelate's tag system (key-value pairs across default and custom tag categories) maps to CatalystOne custom picklist fields or text fields depending on whether the customer wants controlled vocabularies or free-form entry. We document the full set of Crelate tag categories during discovery and create equivalent picklist options in CatalystOne during schema configuration before data load. Tags used for candidate sourcing or skill identification are mapped first to ensure they are available as filterable fields in the destination.

Crelate's custom Contact fields (Short Answer, Long Answer, Date, Numeric, Picklist, Monetary, Rating) map to equivalent custom fields on the CatalystOne Person object. We create the target custom fields in CatalystOne during the schema configuration phase before any Person data loads. Field types are matched directly where possible; Crelate rating scales (1-5 stars) map to numeric or picklist fields in CatalystOne depending on the customer's preferred display format.

Crelate Company custom fields map to custom fields on the CatalystOne Organisation object. We follow the same pre-migration schema creation approach used for Person custom fields, ensuring all target fields exist and are configured (required vs optional, picklist options, validation rules) before the Company import phase begins.

Crelate file attachments (resumes, cover letters, certifications) are exported as binary files with metadata (type, date uploaded, original filename). We attach these to the corresponding Person record in CatalystOne as employee documents with type classification. Resume files are mapped to the 'CV / Resume' document type; other file types are classified by extension and review against the customer's document type configuration. Binary files larger than 25 MB are flagged for alternative delivery because Crelate's import tools have file size constraints.

Crelate Opportunities track placement fees, client companies, and deal status. CatalystOne does not have a placement or deal-tracking object — its equivalent is the Succession Plan (position-to-candidate mapping with readiness rating). We handle this gap in two ways depending on the customer's need: if the goal is to preserve placement history, we create Succession Plan records linking the placed Person to the Position with the original fee as a custom note field; if placement records are purely commercial and not needed in the HCM, we document them in a delivered CSV for the customer's admin to retain externally.

Crelate custom objects map to equivalent custom objects in CatalystOne. We pre-create the destination custom object schema, including all custom fields, lookup relationships to Person, Organisation, or Position, and validation rules, during the schema configuration phase. Lookup references are resolved at migration time using the dedupe key strategy (email for Person lookups, company name for Organisation lookups). If the destination custom object has required fields that cannot be populated from Crelate data, we set sensible defaults and flag the records for admin review post-migration.